WEBVTT

00:00:00.745 --> 00:00:03.162
(soft music)

00:00:05.820 --> 00:00:07.270
<v Shelby>Welcome to
the California Public</v>

00:00:07.270 --> 00:00:08.410
Utilities Commission

00:00:08.410 --> 00:00:12.110
on this day, Tuesday, April 20th, 2021.

00:00:12.110 --> 00:00:13.490
This is the Pacific Gas

00:00:13.490 --> 00:00:15.578
and Electric Tree Overstrike Workshop.

00:00:15.578 --> 00:00:17.673
Joyce Steingass, you may begin.

00:00:20.240 --> 00:00:22.388
<v ->Good morning President
Batjer and Commissioners.</v>

00:00:22.388 --> 00:00:26.720
And thank you to everyone
who has joined us virtually today.

00:00:26.720 --> 00:00:28.670
The California Public
Utilities Commission

00:00:28.670 --> 00:00:32.160
is hosting this public
workshop to hear from PG and E

00:00:32.160 --> 00:00:34.109
about impacts of trees
that are tall enough

00:00:34.109 --> 00:00:37.620
to fall on electric
overhead distribution lines

00:00:37.620 --> 00:00:40.100
and involve tree Overstrike exposure

00:00:40.100 --> 00:00:41.740
that may increase the necessity

00:00:41.740 --> 00:00:44.390
to call public safety power shutoff.

00:00:44.390 --> 00:00:46.600
We understand that
Commissioners may attend all

00:00:46.600 --> 00:00:49.780
or part of the session
as their schedules allow.

00:00:49.780 --> 00:00:51.770
I am Joyce Steingass, Senior Engineer

00:00:51.770 --> 00:00:54.280
with the CPUC Energy Division.

00:00:54.280 --> 00:00:56.810
I am joined by Tony
Noll, Program Manager

00:00:56.810 --> 00:00:59.060
for the Wildfire Safety
and Enforcement Branch

00:00:59.060 --> 00:01:01.980
of the CPUC Safety and
Enforcement Division.

00:01:01.980 --> 00:01:04.048
Shelby Chaste, Senior
Analyst with Tony's branch

00:01:04.048 --> 00:01:06.370
will join me in moderating the questions

00:01:06.370 --> 00:01:08.700
and answers section today.

00:01:08.700 --> 00:01:12.030
Before we get underway,
let's welcome our colleagues

00:01:12.030 --> 00:01:16.040
from the California office
of Emergency Services

00:01:16.040 --> 00:01:18.610
because we have Mike
Masoni, Director of Response

00:01:18.610 --> 00:01:20.010
for the North region.

00:01:20.010 --> 00:01:22.350
And please welcome from
the California Department

00:01:22.350 --> 00:01:24.670
of Forestry and Fire Protection,

00:01:24.670 --> 00:01:26.800
Cal FIRE Battalion Chief Jeff Fuentes.

00:01:26.800 --> 00:01:28.470
He is affiliated with Cal FIRE's

00:01:28.470 --> 00:01:31.330
Utility Fire Mitigation Unit.

00:01:31.330 --> 00:01:33.560
We welcome Assistant Director, Masoni

00:01:33.560 --> 00:01:35.873
and Battalion Chief
Fuentes to join in the dialogue

00:01:35.873 --> 00:01:38.960
or in the Q and A
segment during the panel

00:01:38.960 --> 00:01:41.460
and we appreciate their
sharing their knowledge

00:01:41.460 --> 00:01:43.380
and expertise today.

00:01:43.380 --> 00:01:46.950
From PG and E they have a
team led by Senior Vice President

00:01:46.950 --> 00:01:49.370
and Chief Risk Officer, Sumeet Singh

00:01:49.370 --> 00:01:51.670
and some of PG and E
presenters will include,

00:01:51.670 --> 00:01:55.330
Scott Strenfel, who's PG
and E's Chief Meteorologist

00:01:55.330 --> 00:01:57.803
and Manager for
Meteorology and Fireside.

00:01:58.700 --> 00:02:00.200
PG and E brought Jake Zigelman

00:02:00.200 --> 00:02:01.890
to speak on customer impacts.

00:02:01.890 --> 00:02:05.130
He's the Senior Director of
local customer experience

00:02:05.130 --> 00:02:07.440
and Tracy Maratukulam is with us.

00:02:07.440 --> 00:02:10.320
She's the director of
public safety power shutoff.

00:02:10.320 --> 00:02:12.990
We appreciate that PG
and E has made available

00:02:12.990 --> 00:02:15.200
their executives and
experts from their company

00:02:15.200 --> 00:02:17.488
who might join during Q and A.

00:02:17.488 --> 00:02:22.390
So, on the agenda slide,
that's inside the deck,

00:02:22.390 --> 00:02:25.700
our agenda for today
begins with some background

00:02:25.700 --> 00:02:28.830
followed by PG and E's
proposal and rationale.

00:02:28.830 --> 00:02:31.890
We'll hear how PG and E
proposes to communicate

00:02:31.890 --> 00:02:35.120
and mitigate the potential
for increased frequency

00:02:35.120 --> 00:02:37.460
of public safety power shutoff,

00:02:37.460 --> 00:02:40.250
about customer impact
and finally discussing

00:02:40.250 --> 00:02:43.800
the reporting or oversight
of these new features.

00:02:43.800 --> 00:02:46.720
On this next slide I'd like to
dive into some background

00:02:46.720 --> 00:02:49.853
about why the Commission
is holding this workshop today.

00:02:50.940 --> 00:02:52.960
So on the background slide,

00:02:52.960 --> 00:02:57.760
PG and E is undergoing
probation stemming from PG and E's

00:02:57.760 --> 00:03:00.400
felony conviction for its involvement

00:03:00.400 --> 00:03:05.280
in the deadly 2010 San
Bruno gas pipeline explosion.

00:03:05.280 --> 00:03:07.362
As a condition of this ongoing probation

00:03:07.362 --> 00:03:10.004
the federal court may order PG and E

00:03:10.004 --> 00:03:12.970
to implement new probation condition.

00:03:12.970 --> 00:03:15.040
Probation conditions, 11 and 12,

00:03:15.040 --> 00:03:17.390
which would require PG and E

00:03:17.390 --> 00:03:19.737
to de energize
additional distribution lines

00:03:19.737 --> 00:03:23.040
during public safety
power shutoff events

00:03:23.040 --> 00:03:25.330
based on the number of trees tall enough

00:03:25.330 --> 00:03:28.090
to fall on the electric
distribution line.

00:03:28.090 --> 00:03:32.070
That's based on the
tree Overstrike exposure.

00:03:32.070 --> 00:03:35.410
So if ordered by the
United States District Court,

00:03:35.410 --> 00:03:39.930
then PG and E would
implement these conditions

00:03:39.930 --> 00:03:44.033
by July 1st for this 2021 fire season.

00:03:44.930 --> 00:03:49.190
The CPUC has notified the
United States District Court

00:03:49.190 --> 00:03:50.830
about the CPUC's concern

00:03:50.830 --> 00:03:53.490
that these probation conditions
would increase the scope

00:03:53.490 --> 00:03:56.970
and frequency of public
safety power shutoff.

00:03:56.970 --> 00:04:00.123
So on the next slide we'll
cover the workshop purpose.

00:04:01.400 --> 00:04:05.130
This workshop is a forum to
present, develop and comment

00:04:05.130 --> 00:04:08.078
on PG and E's proposal
to fulfill probation

00:04:08.078 --> 00:04:10.013
conditions, 11 and 12.

00:04:10.920 --> 00:04:13.000
So these conditions
are currently proposed

00:04:13.000 --> 00:04:15.570
but they're not yet ordered
by the Federal Court.

00:04:15.570 --> 00:04:18.180
PG and E will explain
its proposed methodology,

00:04:18.180 --> 00:04:21.320
they'll also explain the
impacts and the estimated size

00:04:21.320 --> 00:04:22.953
and number of PSPS events.

00:04:24.070 --> 00:04:28.240
So the format for today's
workshop is a moderated panel

00:04:28.240 --> 00:04:31.030
whereby during the agenda
we will have questions

00:04:31.030 --> 00:04:33.120
and answers interspersed.

00:04:33.120 --> 00:04:35.040
The Commissioners may direct questions

00:04:35.040 --> 00:04:38.860
to PG and E followed by other panelists

00:04:38.860 --> 00:04:41.730
such as Calloway and Cal FIRE

00:04:41.730 --> 00:04:44.720
and then by our Safety
Enforcement Division

00:04:44.720 --> 00:04:47.130
and Energy Division staff.

00:04:47.130 --> 00:04:48.960
So PG and E will answer the questions

00:04:48.960 --> 00:04:52.320
and there could be some
dialogue between the panelists.

00:04:52.320 --> 00:04:54.190
These Q and A segments will not be open

00:04:54.190 --> 00:04:56.320
to the public to ask questions.

00:04:56.320 --> 00:04:58.870
At the end of the agenda
the operator will open up

00:04:58.870 --> 00:05:01.580
the phone line and will
take public comment.

00:05:01.580 --> 00:05:04.399
The operator will take
two minute comments

00:05:04.399 --> 00:05:07.010
or statements from the public.

00:05:07.010 --> 00:05:09.530
I wanted to make sure
that everyone knows

00:05:09.530 --> 00:05:12.860
that interested parties
may serve written comments

00:05:12.860 --> 00:05:15.283
five business days
after today's workshop

00:05:15.283 --> 00:05:19.500
through the three service list
noticed about this workshop.

00:05:19.500 --> 00:05:24.500
The deadline for written
comment is April 27th at 5:00p.m.

00:05:25.040 --> 00:05:28.710
And after the workshop, the
CPUC will act appropriately,

00:05:28.710 --> 00:05:31.520
considering the federal
probation proceeding

00:05:31.520 --> 00:05:35.250
and the workshop
information provided today.

00:05:35.250 --> 00:05:39.150
One caveat that I wanted
to offer before we get started

00:05:39.150 --> 00:05:43.780
is that the onscreen presentation
will be minorly different

00:05:44.920 --> 00:05:48.070
from that served to the
service list yesterday.

00:05:48.070 --> 00:05:50.018
A revised version has been uploaded

00:05:50.018 --> 00:05:55.018
just this morning to the
CPUC's PSPS webpage.

00:05:55.760 --> 00:05:59.400
We will send a listing
to the service list

00:05:59.400 --> 00:06:01.210
after the workshop ends

00:06:01.210 --> 00:06:04.133
to make a note to which slides changed.

00:06:06.150 --> 00:06:09.380
So with that, let's turn the mic over

00:06:09.380 --> 00:06:11.980
to Sumeet Singh from PG and E.

00:06:11.980 --> 00:06:15.150
He will provide background
including excerpts

00:06:15.150 --> 00:06:19.110
of the probation conditions
and some overview information

00:06:19.110 --> 00:06:23.470
about the PSPS decision-making
criteria and process

00:06:23.470 --> 00:06:28.470
and about tree related
risks, including tree overstrike.

00:06:28.850 --> 00:06:30.623
So let's turn to that now.

00:06:32.560 --> 00:06:35.860
<v ->Great, good morning, Joyce.</v>

00:06:35.860 --> 00:06:37.770
Just confirming and doing a mic check.

00:06:37.770 --> 00:06:38.603
Can you hear me?

00:06:41.010 --> 00:06:41.843
Excellent.

00:06:41.843 --> 00:06:43.360
All right. Good
morning, President Batjer

00:06:43.360 --> 00:06:44.596
and respect to Commissioners.

00:06:44.596 --> 00:06:46.890
My name is Sumeet Singh
and I have the privilege

00:06:46.890 --> 00:06:49.952
of being PG and E's Chief Risk Officer.

00:06:49.952 --> 00:06:51.928
And we really appreciate
your time in today's forum

00:06:51.928 --> 00:06:56.430
to discuss the 2021 public
safety power shutoff program

00:06:56.430 --> 00:07:00.130
and the proposed updates
to the shutoff criteria

00:07:00.130 --> 00:07:02.270
that are under consideration.

00:07:02.270 --> 00:07:03.103
As we all know,

00:07:03.103 --> 00:07:05.020
California continues to
experience an increase

00:07:05.020 --> 00:07:08.100
in low fire risk and a
longer wildfire season.

00:07:08.100 --> 00:07:10.560
We're meeting with you
today with a shared goal

00:07:10.560 --> 00:07:12.940
of keeping our customers
and our communities

00:07:12.940 --> 00:07:15.480
that we're privileged to serve safe.

00:07:15.480 --> 00:07:17.609
We know that losing power disrupts lives

00:07:17.609 --> 00:07:20.170
and we have been focused on reducing

00:07:20.170 --> 00:07:23.235
the impact of PSPS
events for our customers

00:07:23.235 --> 00:07:25.070
throughout our service territory

00:07:25.070 --> 00:07:27.010
without compromising safety.

00:07:27.010 --> 00:07:28.937
We also know that we need to do more

00:07:28.937 --> 00:07:31.550
and we're committed to doing so.

00:07:31.550 --> 00:07:33.230
Last year was one of the most active

00:07:33.230 --> 00:07:35.050
wildfire seasons on record,

00:07:35.050 --> 00:07:36.200
not just in California,

00:07:36.200 --> 00:07:38.460
but all over the Western United States.

00:07:38.460 --> 00:07:41.530
The effects of climate change are here

00:07:41.530 --> 00:07:45.581
and we have a responsibility
to do everything we can

00:07:45.581 --> 00:07:48.159
to provide electricity
in a way that is safe

00:07:48.159 --> 00:07:49.693
in our new climate.

00:07:50.660 --> 00:07:55.230
After each PSPS event and
after each wildfire season,

00:07:55.230 --> 00:07:57.160
we review the wildfire conditions

00:07:57.160 --> 00:07:59.700
and the damages
experienced to our system

00:07:59.700 --> 00:08:01.668
and incorporate lessons learned

00:08:01.668 --> 00:08:05.620
to continue to evolve our PSPS program.

00:08:05.620 --> 00:08:08.060
We've also been in discussions
with the Federal Court

00:08:08.060 --> 00:08:10.390
providing oversight
over probation conditions

00:08:10.390 --> 00:08:14.780
about additional proposed
criteria for the PSPS program

00:08:14.780 --> 00:08:17.070
that accounts for outstanding pre-work

00:08:17.070 --> 00:08:19.880
and also trees that
are tall enough to strike

00:08:19.880 --> 00:08:21.260
the distribution power lines.

00:08:21.260 --> 00:08:23.580
And that's really at the
heart of the discussion

00:08:23.580 --> 00:08:25.510
that we're gonna have today.

00:08:25.510 --> 00:08:27.530
We look forward to working with you

00:08:27.530 --> 00:08:29.290
on these proposed conditions

00:08:29.290 --> 00:08:31.610
and ensure that we're
taking the appropriate steps

00:08:31.610 --> 00:08:33.090
for the safety of our customers

00:08:33.090 --> 00:08:35.080
and our communities that we serve.

00:08:35.080 --> 00:08:38.690
We understand that the criteria
are still under development

00:08:38.690 --> 00:08:40.947
and we will continue to work
closely with this Commission

00:08:40.947 --> 00:08:43.620
and the Federal Court on a path forward

00:08:43.620 --> 00:08:45.750
as final decisions are made.

00:08:45.750 --> 00:08:47.647
We have presentation
materials that we will review today

00:08:47.647 --> 00:08:50.130
and we look forward to
answering any questions

00:08:50.130 --> 00:08:51.133
that you may have.

00:08:52.080 --> 00:08:55.220
So just a quick recap
of who else is here

00:08:55.220 --> 00:08:56.540
joining me today.

00:08:56.540 --> 00:08:58.910
Scott Strenfel, who is
our chief meteorologist.

00:08:58.910 --> 00:09:03.010
Aaron Johnson, who is our
Vice President of Wildfire Safety,

00:09:03.010 --> 00:09:04.980
Michael Ritter, who's a senior director

00:09:04.980 --> 00:09:08.270
of PG and E's Management Program.

00:09:08.270 --> 00:09:10.880
Jake Zigelman who's
leading our local customer

00:09:10.880 --> 00:09:12.870
experience team and Tracy Maratukulum

00:09:12.870 --> 00:09:14.770
who is the responsible director

00:09:14.770 --> 00:09:16.860
for our PSPS program overall.

00:09:16.860 --> 00:09:19.190
So with that, I will begin
walking through the materials.

00:09:19.190 --> 00:09:21.783
So if we can go to
the next slide, please.

00:09:27.720 --> 00:09:28.623
One more please.

00:09:30.890 --> 00:09:32.600
Perfect. Thank you.

00:09:32.600 --> 00:09:34.830
So the public safety power
shutoff program launched

00:09:34.830 --> 00:09:38.910
in 2018 and every year
the program has evolved

00:09:38.910 --> 00:09:42.090
in important ways to respond
to the increasing wildfire risk

00:09:42.090 --> 00:09:45.060
and lessons learned from the prior year.

00:09:45.060 --> 00:09:48.000
In 2019, following the Camp Fire,

00:09:48.000 --> 00:09:51.390
we expanded the scope
to include transmission lines

00:09:51.390 --> 00:09:54.510
but we failed to
scale our notifications,

00:09:54.510 --> 00:09:56.500
website and customer support

00:09:57.340 --> 00:10:01.710
and our execution required
significant improvements.

00:10:01.710 --> 00:10:04.480
Last year, we improved
on nearly every facet

00:10:04.480 --> 00:10:06.130
of our customer and community support,

00:10:06.130 --> 00:10:09.523
significantly reducing the
number and size of PSPS events.

00:10:10.560 --> 00:10:12.820
After the wildfires we all saw last year

00:10:12.820 --> 00:10:16.298
we know that we have
to be even more diligent

00:10:16.298 --> 00:10:21.040
and vigilant as part of
this year's fire season.

00:10:21.040 --> 00:10:22.690
Given the ongoing drought,

00:10:22.690 --> 00:10:24.400
the lengthening of the fire season

00:10:24.400 --> 00:10:25.940
and ever evolving conditions,

00:10:25.940 --> 00:10:28.763
we will not take any
chances with customer safety.

00:10:30.340 --> 00:10:32.123
If we can go to the next slide, please.

00:10:34.000 --> 00:10:37.320
Judge Alsup, a federal
judge that is overseeing

00:10:37.320 --> 00:10:40.700
our probation is considering
additional conditions

00:10:40.700 --> 00:10:43.000
that would require us to turn off power

00:10:43.000 --> 00:10:45.400
when certain criteria are met

00:10:45.400 --> 00:10:48.780
with regards to outstanding tree work

00:10:48.780 --> 00:10:52.590
and also trees near
distribution power lines.

00:10:52.590 --> 00:10:55.053
The initial proposed conditions,

00:10:56.927 --> 00:10:59.010
in the Judge Alsup conditions referenced

00:10:59.010 --> 00:11:03.360
the nomenclature of none,
few, average and many

00:11:03.360 --> 00:11:05.270
in relationship to the characterization

00:11:05.270 --> 00:11:09.340
of overstrike potential trees
that are in close proximity

00:11:09.340 --> 00:11:11.410
to our distribution power lines.

00:11:11.410 --> 00:11:13.310
The proposed approach
that we're gonna walk through

00:11:13.310 --> 00:11:16.757
in detail is consistent with this intent

00:11:16.757 --> 00:11:19.867
and is based on an objective criteria

00:11:19.867 --> 00:11:22.655
and we'll also discuss
the basis of that criteria

00:11:22.655 --> 00:11:24.663
that enables a consistent

00:11:24.663 --> 00:11:28.250
and repeatable PSPS scoping process.

00:11:28.250 --> 00:11:30.970
While these conditions
are still under consideration

00:11:30.970 --> 00:11:34.480
and not final, we're preparing
now in case we're required

00:11:34.480 --> 00:11:36.920
to change the criteria
of the PSPS program

00:11:36.920 --> 00:11:38.870
heading into this year.

00:11:38.870 --> 00:11:40.770
If we can go to the next slide please?

00:11:43.440 --> 00:11:47.863
Before we get into more detail
regarding these conditions,

00:11:47.863 --> 00:11:51.980
I'll just step back and
provide a quick overview

00:11:51.980 --> 00:11:54.513
of our existing vegetation
management programs.

00:11:55.430 --> 00:11:58.560
In summary, we have
two primary programs.

00:11:58.560 --> 00:12:02.090
One is what we call a routine
vegetation management program

00:12:02.090 --> 00:12:04.500
that is a requirement
for the State of California

00:12:04.500 --> 00:12:07.410
that's covered under General Order 95

00:12:07.410 --> 00:12:09.410
in the public resource code.

00:12:09.410 --> 00:12:11.270
It requires that we maintain

00:12:11.270 --> 00:12:13.510
a minimum of four foot clearance

00:12:13.510 --> 00:12:15.140
around our distribution power lines

00:12:15.140 --> 00:12:17.713
and high fire threat areas year round.

00:12:18.760 --> 00:12:20.930
Our enhanced vegetation
management program

00:12:20.930 --> 00:12:22.470
which is the graphic that
you see on the right-hand side

00:12:22.470 --> 00:12:27.030
of that slide is an extra
safety step that we take

00:12:27.030 --> 00:12:30.140
to clear vegetation
above the power lines

00:12:30.140 --> 00:12:32.010
from the conductor to the sky

00:12:32.010 --> 00:12:36.120
so we minimize any
potential fall vegetation

00:12:36.120 --> 00:12:37.200
that may be overhanging

00:12:37.200 --> 00:12:40.140
on top of our distribution
of overhead lines.

00:12:40.140 --> 00:12:43.980
We also address dead,
dying, deceased trees

00:12:43.980 --> 00:12:47.300
which we've seen uptake of
given the drought conditions

00:12:47.300 --> 00:12:50.120
and the mortality of trees
that are tall enough to fall

00:12:50.120 --> 00:12:53.000
within our overhead distribution lines.

00:12:53.000 --> 00:12:54.980
And then also we assess as part

00:12:54.980 --> 00:12:57.210
of our enhanced vegetation management,

00:12:57.210 --> 00:13:00.020
trees that are tall enough
to strike a distribution line

00:13:00.020 --> 00:13:03.670
that could pose an
increased wildfire risk.

00:13:03.670 --> 00:13:06.770
Although they may be healthy
but have a significant defect

00:13:06.770 --> 00:13:09.510
that deems them to be a higher risk tree

00:13:09.510 --> 00:13:10.860
that needs to be mitigated.

00:13:12.100 --> 00:13:13.230
One clarification

00:13:13.230 --> 00:13:15.290
that enhanced vegetation
management program

00:13:15.290 --> 00:13:19.000
does not mitigate a
potential blow in risk

00:13:19.000 --> 00:13:22.790
where we may have a tree
limb that's 40 or 50 feet away

00:13:22.790 --> 00:13:24.630
from the power line that can break off

00:13:24.630 --> 00:13:27.130
and fly into the line during periods

00:13:27.130 --> 00:13:28.940
of high wind conditions.

00:13:28.940 --> 00:13:31.360
Significant level of focus there for us

00:13:31.360 --> 00:13:33.280
is our system hardening program

00:13:33.280 --> 00:13:36.420
which is the overhead
conductor or undergrounding

00:13:36.420 --> 00:13:39.170
which we've spoken in a similar forum

00:13:39.170 --> 00:13:40.520
with this Commission about.

00:13:41.360 --> 00:13:44.421
I do wanna note that
we will be evaluating

00:13:44.421 --> 00:13:48.290
if excluding circuits,
where we have performed

00:13:48.290 --> 00:13:50.070
the enhancement attrition management

00:13:50.070 --> 00:13:52.635
given the health assessment
of potential fallen trees

00:13:52.635 --> 00:13:57.450
from the proposed three
overstride criteria is appropriate,

00:13:57.450 --> 00:14:00.140
we're still going through
the analysis phase of this

00:14:00.140 --> 00:14:02.060
based on reviewing
the circuit performance

00:14:02.060 --> 00:14:05.640
pre and post EVM mitigation work.

00:14:05.640 --> 00:14:08.160
So just to put things in context,

00:14:08.160 --> 00:14:11.703
out of the 25,500 miles of
overhead distribution lines

00:14:11.703 --> 00:14:15.960
that we have that traversed
our high fire threat districts

00:14:15.960 --> 00:14:18.210
between 2019 and 2020,

00:14:18.210 --> 00:14:21.089
we've completed enhanced
vegetation management work

00:14:21.089 --> 00:14:26.089
of approximately 4,300
miles out of 25,500 miles.

00:14:28.780 --> 00:14:30.580
If we can do the next slide, please?

00:14:33.250 --> 00:14:34.083
Thank you.

00:14:35.030 --> 00:14:38.730
The proposed conditions
requires that we consider trees

00:14:38.730 --> 00:14:40.900
that are further away
from our power lines.

00:14:40.900 --> 00:14:44.520
In essence, any tree that's
tall enough but not far enough

00:14:44.520 --> 00:14:47.950
from our overhead lines that
may be outside our easements

00:14:47.950 --> 00:14:50.290
and our right-of-ways
when making the decision

00:14:50.290 --> 00:14:55.290
to turn off power and
also includes healthy trees

00:14:55.390 --> 00:14:59.240
that could potential
have that fall in risk.

00:14:59.240 --> 00:15:01.277
This means that compared to last year

00:15:01.277 --> 00:15:03.703
under similar weather conditions,

00:15:04.850 --> 00:15:06.903
our customers will live in
areas of the high density

00:15:06.903 --> 00:15:09.300
of trees that are tall enough

00:15:09.300 --> 00:15:10.530
to strike the distribution lines

00:15:10.530 --> 00:15:13.457
may experience more
frequent PSPS events.

00:15:13.457 --> 00:15:16.240
And we're gonna go
through a specific example

00:15:16.240 --> 00:15:18.210
for one of the counties
and we will talk about

00:15:18.210 --> 00:15:22.560
the specific impacts regarding
the frequency of events,

00:15:22.560 --> 00:15:26.120
our estimated impact of
the duration of the events,

00:15:26.120 --> 00:15:29.770
and also the scope on a permanent basis.

00:15:29.770 --> 00:15:33.010
And again, I would like to
reinforce that discussions

00:15:34.370 --> 00:15:37.460
with the court and this
Commission are ongoing.

00:15:37.460 --> 00:15:39.180
We're looking at carefully

00:15:39.180 --> 00:15:42.160
at how this may impact our
customers and our communities

00:15:42.160 --> 00:15:45.290
and we're sharing the
community specific information

00:15:45.290 --> 00:15:46.933
regarding the potential impacts.

00:15:47.880 --> 00:15:49.830
If we can go to the next slide, please?

00:15:55.540 --> 00:15:58.490
This slide shows the
way that we're calculating

00:15:58.490 --> 00:16:02.913
what we call tree over
strike exposure potential.

00:16:04.340 --> 00:16:05.850
When I transition to Scott Strenfel's,

00:16:05.850 --> 00:16:09.919
he will build on this concept
on how we've incorporated this

00:16:09.919 --> 00:16:14.480
as part of our proposed
decision making criteria.

00:16:14.480 --> 00:16:17.940
So the way we calculate this
value is we measure the height

00:16:17.940 --> 00:16:22.700
of the tree and we compare
it to the distance of that tree

00:16:22.700 --> 00:16:27.410
from the line which is what's
referenced as the 3D distance

00:16:29.160 --> 00:16:32.190
and we're able to assess
the overstrike potential

00:16:32.190 --> 00:16:34.030
of individual trees itself.

00:16:34.030 --> 00:16:36.157
So think about height of the tree,

00:16:36.157 --> 00:16:38.140
the distance that it falls,

00:16:38.140 --> 00:16:40.266
and then that remaining
distance of the point of contact

00:16:40.266 --> 00:16:43.620
of the tree to the overhead
line to the top of the height

00:16:43.620 --> 00:16:45.547
of the tree is what's deemed

00:16:45.547 --> 00:16:49.033
as the tree over strike
exposure potential.

00:16:50.870 --> 00:16:53.160
What is shown on the
right-hand side of the slide

00:16:53.160 --> 00:16:55.400
is some elements of the criteria.

00:16:55.400 --> 00:16:58.044
And Scott's gonna
walk through this in detail

00:16:58.044 --> 00:17:03.044
on how we came up with a
threshold of the 70th percentile

00:17:03.780 --> 00:17:06.050
and this really refers to trees

00:17:06.050 --> 00:17:08.250
with the highest overstrike potential

00:17:08.250 --> 00:17:10.420
in a given geographic area.

00:17:10.420 --> 00:17:12.330
And we'll talk about this
in a little bit more detail

00:17:12.330 --> 00:17:14.450
as you build on this concept.

00:17:14.450 --> 00:17:16.980
We're also proposing to consider

00:17:16.980 --> 00:17:20.800
both outstanding priority one trees

00:17:20.800 --> 00:17:24.549
which could potentially
pose an immediate safety risk

00:17:24.549 --> 00:17:29.549
or priority two trees that
require expedited safety work

00:17:29.647 --> 00:17:32.720
as part of the PSPS criteria.

00:17:32.720 --> 00:17:34.689
Now, both priority one
and priority two trees

00:17:34.689 --> 00:17:37.230
are part of our normal course

00:17:37.230 --> 00:17:39.840
of the vegetation
management work that we do

00:17:39.840 --> 00:17:43.440
and we address the priority
one trees within 24 hours

00:17:43.440 --> 00:17:47.240
and priority two trees
within 30 days, respectively.

00:17:47.240 --> 00:17:50.680
As part of the impact

00:17:50.680 --> 00:17:52.970
from priority one
and priority two trees,

00:17:52.970 --> 00:17:56.890
we do not anticipate
the significant impact

00:17:56.890 --> 00:17:58.950
and the reason why I say that

00:17:58.950 --> 00:18:03.210
is because as we
forecast adverse weather,

00:18:03.210 --> 00:18:06.470
that's 72 plus hours
out that could trigger

00:18:06.470 --> 00:18:08.720
a potential PSPS event,

00:18:08.720 --> 00:18:12.830
we have the ability to
overlay our open priority one

00:18:12.830 --> 00:18:15.730
and priority two vegetation
management tags

00:18:15.730 --> 00:18:20.620
and deploy our vegetation
management crews to safely address

00:18:20.620 --> 00:18:25.070
and mitigate and remediate
those open priority one tags

00:18:25.070 --> 00:18:29.600
thereby removing those circuits
from the scope of the work.

00:18:29.600 --> 00:18:32.320
The largest impact that
we're gonna talk about

00:18:32.320 --> 00:18:34.750
is primarily driven by

00:18:34.750 --> 00:18:37.493
the tree overstrike enclosure potential.

00:18:40.339 --> 00:18:42.200
So if you go to the next slide,

00:18:42.200 --> 00:18:46.620
we start to get into the
process that we've used

00:18:46.620 --> 00:18:49.533
by which we have captured the trees

00:18:49.533 --> 00:18:51.440
that are tall enough but not far enough

00:18:51.440 --> 00:18:56.310
from a distribution lines and
we have analyzed that data set

00:18:56.310 --> 00:18:59.390
to help formulate the calculation

00:18:59.390 --> 00:19:00.900
of the tree overstrike potential

00:19:00.900 --> 00:19:03.160
that I discussed in the last slide.

00:19:03.160 --> 00:19:06.240
So in 2019 and 2020,

00:19:06.240 --> 00:19:09.880
as part of our enhanced
vegetation management program,

00:19:09.880 --> 00:19:13.330
we utilized aerial LiDAR imagery,

00:19:13.330 --> 00:19:15.860
a commercially available technology

00:19:15.860 --> 00:19:17.643
that's tried and tested and proven

00:19:17.643 --> 00:19:20.950
to identify trees that
may be tall enough

00:19:20.950 --> 00:19:22.649
to strike our distribution lines

00:19:22.649 --> 00:19:25.750
in the high fire threat areas.

00:19:25.750 --> 00:19:30.310
We conducted the survey over
the entire distribution system

00:19:30.310 --> 00:19:33.690
which covers the 25,500 line miles

00:19:33.690 --> 00:19:38.390
and through the survey we
determined and identified more

00:19:38.390 --> 00:19:42.720
than 5.3 million trees that could strike

00:19:42.720 --> 00:19:46.196
a potential distribution
line if it falls into it

00:19:46.196 --> 00:19:49.827
during severe weather in
the high fire threat districts.

00:19:49.827 --> 00:19:54.580
But that's the process by
which we obtained that data set

00:19:54.580 --> 00:19:57.940
and collected that data
set of strike potential trees

00:19:57.940 --> 00:20:01.500
and through that same
process we analyzed

00:20:01.500 --> 00:20:06.500
and got a third party that
does this work to help analyze

00:20:06.690 --> 00:20:11.270
what that tree strike
overstrike potential distance

00:20:11.270 --> 00:20:14.510
calculation is, that I
just walked through.

00:20:14.510 --> 00:20:18.030
So this was done and this
data set was available middle

00:20:18.030 --> 00:20:20.650
of last year which is the data
set that we're incorporating

00:20:20.650 --> 00:20:24.083
as part of this analysis
in the proposed criteria.

00:20:25.370 --> 00:20:27.230
The last slide I'll cover
and then I'll pause

00:20:27.230 --> 00:20:30.163
for any questions before
I hand it off to Scott.

00:20:31.200 --> 00:20:36.140
Our team has carefully
analyzed the LIDAR data

00:20:36.140 --> 00:20:38.560
that was collected and
we now have a database

00:20:38.560 --> 00:20:39.723
of the approximate number of trees

00:20:39.723 --> 00:20:42.350
that are located near
our distribution lines.

00:20:42.350 --> 00:20:44.830
Like any dataset it's
important to understand

00:20:44.830 --> 00:20:47.500
how the information was collected

00:20:47.500 --> 00:20:50.890
in order to make it
operational and actionable.

00:20:50.890 --> 00:20:53.000
So in the case of our LIDAR data,

00:20:53.000 --> 00:20:55.520
there are certain dense tree canopies

00:20:55.520 --> 00:20:58.980
that can make it challenging
to accurately identify

00:20:58.980 --> 00:21:01.570
where the tree trunks are located.

00:21:01.570 --> 00:21:04.060
That's really how LIDAR works,

00:21:04.060 --> 00:21:08.040
to be able to help identify
the location of the tree trunk,

00:21:08.040 --> 00:21:10.300
the location of the
tree top that provides

00:21:10.300 --> 00:21:14.110
the height measurement
and then the spatial distance

00:21:14.110 --> 00:21:17.940
that's measured on how far a tree is

00:21:17.940 --> 00:21:20.017
from our overhead distribution lines.

00:21:20.017 --> 00:21:23.540
So this means that we
identify the overstrike potential

00:21:23.540 --> 00:21:24.810
through the tree tops.

00:21:24.810 --> 00:21:27.600
In some cases where
there's a tree canopies

00:21:27.600 --> 00:21:28.910
because of that overhang issue,

00:21:28.910 --> 00:21:30.820
that we're on the process of clearing

00:21:30.820 --> 00:21:33.430
as part of our enhancement
vegetation management program,

00:21:33.430 --> 00:21:35.290
and in some of these areas

00:21:35.290 --> 00:21:39.040
there may be overstrike
potential that's overestimated

00:21:39.040 --> 00:21:41.980
or underestimated in our database

00:21:41.980 --> 00:21:46.120
but using the aerial LiDAR
dataset with a sound approach

00:21:46.120 --> 00:21:48.030
to provide a relative comparison

00:21:48.030 --> 00:21:49.780
of the distribution lines

00:21:49.780 --> 00:21:53.370
that have a higher tree
overstrike exposure potential

00:21:53.370 --> 00:21:55.250
than other lines within
our service territory.

00:21:55.250 --> 00:21:58.320
And this does serve as
the best available data set

00:21:58.320 --> 00:22:00.030
to estimate trees that are tall enough

00:22:00.030 --> 00:22:02.910
to potentially strike for
distribution power lines.

00:22:02.910 --> 00:22:05.590
So I'll pause there
to take any questions

00:22:05.590 --> 00:22:09.550
before I transition and
hand it off to Scott Strenfel

00:22:09.550 --> 00:22:14.120
who's gonna build on the
concepts that I just walked through

00:22:14.120 --> 00:22:16.190
and also review how we're
leveraging this data set

00:22:16.190 --> 00:22:18.776
to inform the additions
to our PSPS criteria

00:22:18.776 --> 00:22:21.740
that's consistent with
the proposed conditions

00:22:21.740 --> 00:22:22.850
by the Federal Court.

00:22:22.850 --> 00:22:25.117
So I'll pause here for any questions.

00:22:32.577 --> 00:22:34.043
Commissioner Shiroma.

00:22:35.440 --> 00:22:37.070
<v ->Oh, yes. Thank you.</v>

00:22:37.070 --> 00:22:38.570
Thank you for the presentation

00:22:40.309 --> 00:22:43.220
and you know, all the
efforts towards prevention.

00:22:43.220 --> 00:22:48.220
So does PG and E have
data on past overstrike

00:22:52.027 --> 00:22:56.010
that actually occurred
and the circumstances

00:22:56.010 --> 00:22:57.763
under which they did occur?

00:22:58.780 --> 00:23:02.310
<v ->We do Commissioner
and that's actually</v>

00:23:02.310 --> 00:23:06.230
part of our foundational
PSPS decision making criteria.

00:23:06.230 --> 00:23:08.690
So one of the things that we implemented

00:23:08.690 --> 00:23:10.620
and we further enhanced in 2020

00:23:11.740 --> 00:23:14.960
and Scott Strenfel, our chief
meteorologist and his team

00:23:14.960 --> 00:23:17.540
are responsible for doing this analysis.

00:23:17.540 --> 00:23:20.253
We have taken a rich data history,

00:23:21.180 --> 00:23:24.740
more than 10 years of
data and specifically studying

00:23:24.740 --> 00:23:27.520
the offshore rain
pattern with Diablo winds

00:23:27.520 --> 00:23:30.810
that create the potential
risk of a PSPS event

00:23:30.810 --> 00:23:34.710
and correlated where we
have experienced outages

00:23:34.710 --> 00:23:37.730
to our specific locations in the circuit

00:23:37.730 --> 00:23:39.730
and the drivers of those outages.

00:23:39.730 --> 00:23:43.160
So in some cases it's
caused by equipment,

00:23:43.160 --> 00:23:46.310
in other cases it's caused
by a tree limb that blows

00:23:46.310 --> 00:23:49.350
into the line and in some cases

00:23:49.350 --> 00:23:52.480
it's caused by a potential falling tree.

00:23:52.480 --> 00:23:55.700
So that historical
information is something

00:23:55.700 --> 00:23:59.130
that we call our outage
producing wind probability

00:23:59.130 --> 00:24:02.720
and that's a key input in
regards to our threshold

00:24:02.720 --> 00:24:04.760
for the PSPS decision-making process.

00:24:04.760 --> 00:24:07.037
And we've had that in
place for a couple of years

00:24:07.037 --> 00:24:10.420
and what we're proposing
here, Commissioner is,

00:24:10.420 --> 00:24:13.250
even the circuits that
have not experienced

00:24:13.250 --> 00:24:16.552
that historical outage
but the sheer presence

00:24:16.552 --> 00:24:21.220
of a tree that may be tall
enough could introduce

00:24:21.220 --> 00:24:24.850
that additional exposure risk
from a overstrike perspective.

00:24:24.850 --> 00:24:27.010
So that's really what the focus

00:24:27.010 --> 00:24:28.510
of this proposed condition is.

00:24:30.220 --> 00:24:31.273
<v ->Okay. Thank you.</v>

00:24:31.273 --> 00:24:34.060
So you used historical data,

00:24:34.060 --> 00:24:36.932
looked at the updated weather conditions

00:24:36.932 --> 00:24:41.280
towards the probability
of an overstrike.

00:24:42.295 --> 00:24:43.128
Well, thank you.

00:24:46.976 --> 00:24:49.040
<v ->Any other questions?</v>

00:24:49.040 --> 00:24:51.140
<v ->Yes.</v>
<v ->Yes please.</v>

00:24:51.140 --> 00:24:54.110
<v ->Do you have an
estimate of how many</v>

00:24:54.110 --> 00:24:58.003
of your priority one
and priority two trees,

00:24:59.940 --> 00:25:01.512
maybe it's the inverse actually.

00:25:01.512 --> 00:25:06.512
But what percentage
of the overstrike trees

00:25:07.429 --> 00:25:10.843
are already within your
priority one and priority two?

00:25:12.650 --> 00:25:14.840
<v ->Commissioner, it's a
very small percentage.</v>

00:25:14.840 --> 00:25:16.117
So just to give you...

00:25:16.117 --> 00:25:18.840
And these numbers change
obviously on a daily basis, right?

00:25:18.840 --> 00:25:22.310
Because we have more
than a thousand pre inspectors

00:25:23.217 --> 00:25:26.760
that are on in assessing
our service territory

00:25:26.760 --> 00:25:28.814
as we speak now within
the high fire threat districts

00:25:28.814 --> 00:25:31.319
assessing the condition of vegetation,

00:25:31.319 --> 00:25:33.940
given that that condition
changes in a dynamic way

00:25:33.940 --> 00:25:38.230
but just to put some
numbers and a proxy for you,

00:25:38.230 --> 00:25:42.550
there's less than five
at any given point in time

00:25:42.550 --> 00:25:44.700
priority one open tags,

00:25:44.700 --> 00:25:47.860
given that we address
those within a 24 hour period.

00:25:47.860 --> 00:25:49.840
So it's a very small number

00:25:49.840 --> 00:25:51.880
which is why I mentioned that,

00:25:51.880 --> 00:25:56.030
you know when we forecast
the adverse Diablo wind condition

00:25:56.030 --> 00:25:58.050
as part of a PSPS event,

00:25:58.050 --> 00:25:59.707
you have the ability to
be able to safely mobilize

00:25:59.707 --> 00:26:01.810
the vegetation management teams

00:26:01.810 --> 00:26:04.700
and remediate those
open priority one tags.

00:26:04.700 --> 00:26:07.090
So we take those issues off the table

00:26:07.090 --> 00:26:10.210
as part of consideration
for PSPS criteria.

00:26:10.210 --> 00:26:12.453
In regards to the priority two tags,

00:26:13.320 --> 00:26:16.130
given that that's a 30 day window,

00:26:16.130 --> 00:26:19.990
it's anywhere and in typically
within 900 to a thousand.

00:26:19.990 --> 00:26:21.747
And that number again,
changes on a on a daily basis

00:26:21.747 --> 00:26:25.161
'cause our teams continue
to reduce and identify

00:26:25.161 --> 00:26:27.124
more tags and address these tags.

00:26:27.124 --> 00:26:30.750
It's about 900 to a thousand trees.

00:26:30.750 --> 00:26:33.540
So put that and those numbers

00:26:33.540 --> 00:26:38.540
in context of the 5.3
million strike potential trees.

00:26:39.500 --> 00:26:42.233
So it's a very, very small population.

00:26:44.200 --> 00:26:46.010
<v ->Oh, I missed
that number earlier.</v>

00:26:46.010 --> 00:26:47.530
That is a tremendous...

00:26:49.260 --> 00:26:51.180
That's an astronomical increase.

00:26:51.180 --> 00:26:52.721
Okay.

00:26:52.721 --> 00:26:54.940
And what about in
relation to the circuit?

00:26:54.940 --> 00:26:59.940
So do we have a
proportional (indistinct)

00:27:00.230 --> 00:27:03.033
might be getting to that
in your next presentation.

00:27:06.660 --> 00:27:09.910
Will you be getting into that?
<v ->I'm sorry.</v>

00:27:09.910 --> 00:27:11.620
<v ->What does that translate into?</v>

00:27:11.620 --> 00:27:15.140
Into how many more circuits
will have to be turned off?

00:27:15.140 --> 00:27:18.330
<v ->Yes Commissioner,
that's part of the next step</v>

00:27:18.330 --> 00:27:20.800
in the process so Scott
Strenfel will cover that

00:27:20.800 --> 00:27:22.650
and not only are we gonna discuss

00:27:22.650 --> 00:27:24.830
the potential increase in scope,

00:27:24.830 --> 00:27:29.420
but we will also share the
analysis that we've done looking

00:27:29.420 --> 00:27:34.080
at the last 11 years
of Diablo wind patterns

00:27:34.080 --> 00:27:39.080
from 2010 to 2020 to
identify what the forecast is,

00:27:39.440 --> 00:27:42.860
impact is, to frequency, duration

00:27:42.860 --> 00:27:45.780
and number of customers
in smaller events

00:27:45.780 --> 00:27:47.510
versus larger events.

00:27:47.510 --> 00:27:52.510
And as you can logically
conclude that the impact

00:27:53.900 --> 00:27:56.960
across our service
territory is not uniform.

00:27:56.960 --> 00:27:59.920
So the impact in counties
that have a higher number

00:27:59.920 --> 00:28:01.440
of strike potential trees,

00:28:01.440 --> 00:28:04.190
especially in the Northern
part of our service territory,

00:28:04.190 --> 00:28:05.740
would experience a greater impact.

00:28:05.740 --> 00:28:08.280
And we'll cover that in more detail.

00:28:08.280 --> 00:28:09.223
<v ->Okay. Thank you.</v>

00:28:10.260 --> 00:28:12.730
<v ->And then I have a question.</v>

00:28:12.730 --> 00:28:13.873
This is Marybel.

00:28:15.340 --> 00:28:20.174
Did I hear you say 5.5 million
trees have been identified?

00:28:20.174 --> 00:28:24.244
<v ->Yeah. President Batjer,
we've identified an estimated</v>

00:28:24.244 --> 00:28:29.244
from our aerial LiDAR
data set, 5.3 million trees

00:28:31.450 --> 00:28:33.230
that are tall enough,

00:28:33.230 --> 00:28:36.920
not far enough from our
overhead distribution lines

00:28:36.920 --> 00:28:41.920
and this correlates to 25,500 miles

00:28:42.670 --> 00:28:44.940
of overhead distribution
lines that traverse

00:28:44.940 --> 00:28:46.210
the high fire threat districts.

00:28:46.210 --> 00:28:48.040
And we've provided that information

00:28:48.040 --> 00:28:51.360
on slide six with the materials.

00:28:51.360 --> 00:28:54.623
<v ->These numbers are
inconceivable to me.</v>

00:28:56.450 --> 00:28:59.520
So does that mean
that there's a potential

00:28:59.520 --> 00:29:04.520
of you all removing cutting
down 5.3 million trees?

00:29:06.570 --> 00:29:08.060
<v ->No, it's not President Batjer</v>

00:29:08.060 --> 00:29:11.250
because our enhanced
vegetation management program

00:29:11.250 --> 00:29:13.890
does not do clear cutting.

00:29:13.890 --> 00:29:18.073
We don't cut every single
strike potential tree, right?

00:29:18.073 --> 00:29:21.236
A tree that's tall enough
but not far enough.

00:29:21.236 --> 00:29:24.480
Part of our effort for enhanced
vegetation management,

00:29:24.480 --> 00:29:27.050
and this is why we
have a significant number

00:29:27.050 --> 00:29:30.300
of qualified, registered arborists

00:29:30.300 --> 00:29:33.720
that identify every
single strike potential tree,

00:29:33.720 --> 00:29:37.530
do a 360 hazard assessment,

00:29:37.530 --> 00:29:41.800
and there's a tree assessment
tool that we have deployed

00:29:41.800 --> 00:29:45.170
that's been approved
certified by our arborist

00:29:45.170 --> 00:29:47.265
that gets gets applied in the field

00:29:47.265 --> 00:29:52.265
and they evaluate things
like is that tree on a slope?

00:29:52.970 --> 00:29:56.840
Does that tree have any
kind of a potential defect?

00:29:56.840 --> 00:29:58.850
Is it leaning towards the line?

00:29:58.850 --> 00:30:01.500
What is the species of that tree?

00:30:01.500 --> 00:30:05.210
If you think about trees like
gray pines that are notorious

00:30:05.210 --> 00:30:07.330
for growing at an angle
and if they're growing

00:30:07.330 --> 00:30:09.630
towards a line we know
that as it's gonna mature

00:30:09.630 --> 00:30:11.090
especially on a slope,

00:30:11.090 --> 00:30:14.060
that is gonna pose
a potential higher risk

00:30:14.060 --> 00:30:15.910
than upon the rows of pine

00:30:15.910 --> 00:30:17.840
that may be growing
straight up and down.

00:30:17.840 --> 00:30:21.113
So our professional
arborists go out in the field,

00:30:21.113 --> 00:30:23.083
we have more than a thousand.

00:30:32.040 --> 00:30:33.620
Need to remove that tree

00:30:33.620 --> 00:30:35.090
or do we keep that tree in place

00:30:35.090 --> 00:30:36.640
because it's healthy and green.

00:30:37.830 --> 00:30:41.917
<v ->Okay. So will this
assessment be done by July 1,</v>

00:30:44.410 --> 00:30:47.300
of all these thousands of trees?

00:30:47.300 --> 00:30:49.220
<v ->No, I will not
President Batjer.</v>

00:30:49.220 --> 00:30:51.554
So this is what we call,

00:30:51.554 --> 00:30:53.740
enhanced vegetation management programs

00:30:53.740 --> 00:30:56.860
that we first implemented in 2019.

00:30:56.860 --> 00:31:01.860
And over 2019 and 2020,
we have completed 4,300 miles

00:31:02.950 --> 00:31:05.400
out of the 25,500

00:31:05.400 --> 00:31:09.480
and we're on a pace of
completing 1800 plus miles

00:31:09.480 --> 00:31:13.200
every single year over
the next five plus years

00:31:13.200 --> 00:31:15.720
to be able to do this assessment.

00:31:15.720 --> 00:31:18.100
<v ->And all the while
the trees still will grow</v>

00:31:18.100 --> 00:31:20.100
and they will grow, even the small ones

00:31:20.100 --> 00:31:23.310
that are not within
the 360, they'll grow.

00:31:23.310 --> 00:31:24.143
I mean.

00:31:26.344 --> 00:31:28.420
<v ->So, this is where,
President Batjer,</v>

00:31:28.420 --> 00:31:30.740
where, you know, from
my perspective, right?

00:31:30.740 --> 00:31:33.495
As the work that's
happening we're reducing

00:31:33.495 --> 00:31:38.070
that immediate risk from a
strike potential perspective.

00:31:38.070 --> 00:31:39.600
when you look at the overhang, right?

00:31:39.600 --> 00:31:41.810
Because we're also
removing all the overhang

00:31:41.810 --> 00:31:44.960
and we've had a history
of tree limbs that fall

00:31:44.960 --> 00:31:47.160
into the overhead
lines which is a key part

00:31:47.160 --> 00:31:48.990
of our enhanced vegetation
management program

00:31:48.990 --> 00:31:51.850
and we're also
identifying the weakest link

00:31:51.850 --> 00:31:53.630
of the strike potential trees

00:31:53.630 --> 00:31:57.760
but really the focus
of being able to make

00:31:57.760 --> 00:32:01.683
the system more resilient is
the system hardening program.

00:32:02.610 --> 00:32:06.870
And that's how we engineer
the risk of the system

00:32:06.870 --> 00:32:09.120
to mitigate the fire risk.

00:32:10.124 --> 00:32:10.957
<v ->Sounds far more sensible</v>

00:32:10.957 --> 00:32:12.980
than cutting our way
out of this by the way.

00:32:12.980 --> 00:32:14.063
Just my opinion.

00:32:15.619 --> 00:32:18.270
So, with where you are,

00:32:18.270 --> 00:32:23.240
in terms of enhanced
vegetation management

00:32:23.240 --> 00:32:27.670
and the routine and what we're facing,

00:32:27.670 --> 00:32:29.410
in terms of what you all are facing

00:32:29.410 --> 00:32:32.260
in terms of the court, perhaps

00:32:32.260 --> 00:32:35.393
and the fire season
that's confronting us now,

00:32:36.570 --> 00:32:38.720
will that necessitate,

00:32:38.720 --> 00:32:43.530
will where you have not
been able to identify the trees

00:32:43.530 --> 00:32:46.510
or have the arborist out checking them.

00:32:46.510 --> 00:32:47.550
You're at 43...

00:32:49.180 --> 00:32:53.490
Anyways, you're not at
25,000 miles, for sure.

00:32:53.490 --> 00:32:56.680
So does that mean you
guys are just gonna turn off

00:32:56.680 --> 00:32:57.990
the circuits in those areas

00:32:57.990 --> 00:33:00.383
that you haven't been able to identify?

00:33:01.330 --> 00:33:04.593
When the wind conditions
reach the red flag?

00:33:06.160 --> 00:33:11.160
And is that different than
what you did in 2020 and 2019?

00:33:13.210 --> 00:33:15.403
Will it be different in 2021?

00:33:16.340 --> 00:33:18.810
<v ->It will be, President Batjer</v>

00:33:18.810 --> 00:33:22.010
and you've got that spot on.

00:33:22.010 --> 00:33:26.710
That we're proposing as
part of the proposed conditions

00:33:26.710 --> 00:33:31.710
of the Federal Court is to
de-energize those circuits

00:33:33.230 --> 00:33:37.770
that have a high number
of strike potential trees,

00:33:37.770 --> 00:33:41.410
not at assessed fire and has
vegetation management program

00:33:41.410 --> 00:33:44.110
that's when the minimum
fire potential conditions

00:33:44.110 --> 00:33:45.150
are there, right?

00:33:45.150 --> 00:33:46.920
Meaning a certain level of threshold,

00:33:46.920 --> 00:33:48.560
the live fuel moisture,

00:33:48.560 --> 00:33:51.030
the dead fuel moisture,
red flag warning,

00:33:51.030 --> 00:33:53.710
all the conditions
where a potential ignition

00:33:53.710 --> 00:33:55.801
can turn into a catastrophic wildfire.

00:33:55.801 --> 00:34:00.801
That's the additional scope
that is being proposed in 2021

00:34:01.450 --> 00:34:04.870
which is different than 2020.

00:34:04.870 --> 00:34:07.710
So it's an additional criteria

00:34:07.710 --> 00:34:09.290
compared to what we had in place.

00:34:09.290 --> 00:34:11.753
And as I was explaining previously,

00:34:11.753 --> 00:34:15.150
based on the question that
Commissioner Shiroma asked,

00:34:15.150 --> 00:34:17.303
previously what we've
done is we've evaluated

00:34:17.303 --> 00:34:19.832
the performance of the circuit

00:34:19.832 --> 00:34:22.030
based on a certain wind speed.

00:34:22.030 --> 00:34:24.500
And if that circuit has
experienced an outage

00:34:24.500 --> 00:34:28.160
which is a leading
indicator for a fire ignition,

00:34:28.160 --> 00:34:30.680
that's what we've included
in deactivation scope.

00:34:30.680 --> 00:34:34.110
And what we're proposing going into 2021

00:34:34.110 --> 00:34:35.690
is that even though that circuit

00:34:35.690 --> 00:34:38.690
may not have experienced an outage,

00:34:38.690 --> 00:34:43.690
the sheer presence of
that over strike exposure

00:34:44.050 --> 00:34:45.520
without having the ability,

00:34:45.520 --> 00:34:47.840
given the scale of
trees we're talking about,

00:34:47.840 --> 00:34:51.810
to assess the health of
every single one of those trees

00:34:51.810 --> 00:34:55.140
is what's necessitating
this additional proposal.

00:34:55.140 --> 00:34:58.350
And we'll talk about the
implications of that, that's next.

00:34:58.350 --> 00:35:01.470
<v ->Okay. I look forward to
hearing more about actually</v>

00:35:01.470 --> 00:35:04.083
the lines and the health of the lines.

00:35:05.160 --> 00:35:08.870
We've had public comments
in some of our previous

00:35:08.870 --> 00:35:12.370
perhaps you were, some
of your staff may have heard,

00:35:12.370 --> 00:35:14.800
folks that really question.

00:35:14.800 --> 00:35:19.390
And I don't remember the
gauge of the wire that they said,

00:35:19.390 --> 00:35:22.540
but some of questions that, you know

00:35:22.540 --> 00:35:25.550
it's not the tree, it's the
darn lines that, I mean

00:35:25.550 --> 00:35:29.000
a stick could blow
into some of the lines.

00:35:29.000 --> 00:35:33.082
So public comment has been made to us

00:35:33.082 --> 00:35:37.580
because the lines are
such a minimal gauge.

00:35:37.580 --> 00:35:41.660
That's not the correct
terminology I'm sure,

00:35:41.660 --> 00:35:44.050
but anyway, I look
forward to the presentation

00:35:44.050 --> 00:35:46.020
so we can talk about that

00:35:46.020 --> 00:35:51.010
because I don't know how
you look at 5.3 million trees

00:35:51.880 --> 00:35:54.040
and continually,
continually, continually

00:35:54.040 --> 00:35:56.640
because they grow, thankfully

00:35:56.640 --> 00:35:59.020
and they're dying as you just said

00:35:59.020 --> 00:36:01.780
the mortality rate is increasing

00:36:01.780 --> 00:36:03.397
because of the drought conditions

00:36:03.397 --> 00:36:08.397
and the climate change
that we are experiencing.

00:36:08.480 --> 00:36:13.480
So all of this is becoming
more advanced on us now.

00:36:15.000 --> 00:36:16.780
So I will stop there.

00:36:16.780 --> 00:36:20.640
I'm sorry for going on
so long but thank you.

00:36:20.640 --> 00:36:22.450
<v ->No, President Batjer,
thank you for your comments.</v>

00:36:22.450 --> 00:36:23.900
We're completely aligned.

00:36:23.900 --> 00:36:26.260
We cannot cut our way out of this issue.

00:36:26.260 --> 00:36:28.750
The intent of the enhanced
vegetation management program

00:36:28.750 --> 00:36:32.720
is to have that
additional control in place

00:36:32.720 --> 00:36:35.330
on a more immediate basis
to identify the weakest trees,

00:36:35.330 --> 00:36:36.850
to address the overhang.

00:36:36.850 --> 00:36:40.460
But the focus is for us
to engineer this risk out

00:36:40.460 --> 00:36:43.856
by making the electric
grid more resilient,

00:36:43.856 --> 00:36:45.623
not just based on the conditions

00:36:45.623 --> 00:36:47.500
that we're experiencing now,

00:36:47.500 --> 00:36:50.240
but we know that the conditions
are gonna worsen over time.

00:36:50.240 --> 00:36:53.250
So that's exactly the focus that we have

00:36:53.250 --> 00:36:55.150
as part of this effort.

00:36:55.150 --> 00:36:58.350
In regards to the comment
regarding the small wire, right?

00:36:58.350 --> 00:37:00.290
A comment that was mentioned.

00:37:00.290 --> 00:37:01.890
There's different technical terms.

00:37:01.890 --> 00:37:02.970
I won't go into that.

00:37:02.970 --> 00:37:07.280
And there's also different
material type associated

00:37:07.280 --> 00:37:09.140
with the conductor itself.

00:37:09.140 --> 00:37:11.180
But what I can share
with you President Batjer

00:37:11.180 --> 00:37:16.180
is that even if we had a
bigger or a larger conductor,

00:37:18.340 --> 00:37:23.340
if that conductor is bare
and you have a potential tree

00:37:24.310 --> 00:37:26.740
or branch that comes in contact with it,

00:37:26.740 --> 00:37:29.570
that contact in it and by itself,

00:37:29.570 --> 00:37:33.060
can create a potential arc or spark.

00:37:33.060 --> 00:37:35.260
It does not necessarily have to mean

00:37:35.260 --> 00:37:37.680
that that wire has to hit the ground,

00:37:37.680 --> 00:37:39.560
something called a pitch ground fault

00:37:39.560 --> 00:37:41.570
which creates that ignition

00:37:41.570 --> 00:37:46.000
but that sheer nature of the
impact of that tree or limb,

00:37:46.000 --> 00:37:48.810
yes in some cases, results in,

00:37:48.810 --> 00:37:51.660
when you have the smaller wire

00:37:51.660 --> 00:37:54.840
it can create a potential ignition point

00:37:54.840 --> 00:37:57.010
or an arc or a spark
and that may be enough

00:37:57.010 --> 00:38:00.150
in these conditions to
create that catastrophic fire.

00:38:00.150 --> 00:38:03.130
Hence, the reason why
system hardening includes

00:38:03.130 --> 00:38:05.580
that covered conductor
because it removes

00:38:05.580 --> 00:38:07.860
that bare wire out
of the equation, right?

00:38:07.860 --> 00:38:10.830
When you have that contact
you've got a plastic covering

00:38:10.830 --> 00:38:13.500
on that bare conductor
that does not allow

00:38:13.500 --> 00:38:16.010
for that arcing or sparks to take place.

00:38:16.010 --> 00:38:19.783
So that's the thought
process and intent there.

00:38:21.420 --> 00:38:22.390
<v Joyce>Well, this is Joyce</v>

00:38:22.390 --> 00:38:24.700
and I apologize for interrupting.

00:38:24.700 --> 00:38:27.700
I really love the engagement
and the rich insights

00:38:27.700 --> 00:38:29.750
and perspectives being shared.

00:38:29.750 --> 00:38:31.340
I'd like the urge us to move on

00:38:31.340 --> 00:38:33.960
to Scott Strenfel's presentation

00:38:33.960 --> 00:38:35.989
after which we can
reengage in more questions.

00:38:35.989 --> 00:38:37.600
Thanks again.

00:38:37.600 --> 00:38:38.640
<v ->My apologies.</v>

00:38:38.640 --> 00:38:40.440
Go ahead, Scott. The floor is yours.

00:38:43.350 --> 00:38:44.610
<v ->Great. Yeah. Good
morning, everyone.</v>

00:38:44.610 --> 00:38:46.390
Just wanna do a microphone check.

00:38:46.390 --> 00:38:47.390
Can you all hear me?

00:38:49.380 --> 00:38:51.690
Great. Couple head nods out there.

00:38:51.690 --> 00:38:53.740
So yeah, just to give
you a little background

00:38:53.740 --> 00:38:55.610
about you know, myself and my team.

00:38:55.610 --> 00:38:56.830
My name is Scott Strenfel.

00:38:56.830 --> 00:38:58.350
I don't think I've had the privilege

00:38:58.350 --> 00:38:59.710
of meeting all of you yet

00:38:59.710 --> 00:39:03.620
but my background is, you
know, I'm a meteorologist

00:39:03.620 --> 00:39:05.690
by education and by training

00:39:07.170 --> 00:39:10.350
and received my Master's degree

00:39:10.350 --> 00:39:13.190
from the San Jose State
Fire Weather Research Lab

00:39:13.190 --> 00:39:14.360
over a decade ago.

00:39:14.360 --> 00:39:19.158
So my background is actually
in the fire weather space

00:39:19.158 --> 00:39:23.110
and I'm privileged to be
a part of a strong team

00:39:23.110 --> 00:39:27.070
at PG and E of operational
meteorologists, data scientists,

00:39:27.070 --> 00:39:32.070
data engineers, many of
whom have advanced degrees.

00:39:32.130 --> 00:39:36.030
And so, you know, I wanted to provide

00:39:36.030 --> 00:39:37.600
a little bit of a context

00:39:38.870 --> 00:39:42.270
related to what Sumeet mentioned

00:39:42.270 --> 00:39:44.206
and kind of build upon the concepts

00:39:44.206 --> 00:39:46.540
that he's already outlined.

00:39:46.540 --> 00:39:48.180
And so I just wanna caution

00:39:48.180 --> 00:39:50.200
and just let everybody know

00:39:50.200 --> 00:39:52.180
that it's been only two short months

00:39:52.180 --> 00:39:57.180
since Judge Alsup issued
his proposed conditions

00:39:57.720 --> 00:40:00.060
and my team has been sprinting

00:40:00.060 --> 00:40:03.500
and trying to understand
how to one, operationalize

00:40:03.500 --> 00:40:05.320
those potential proposed conditions

00:40:05.320 --> 00:40:07.740
if they do become conditions,

00:40:07.740 --> 00:40:10.270
as well as understand you
know, what that would mean

00:40:10.270 --> 00:40:12.820
in terms of PSPS impact.

00:40:12.820 --> 00:40:15.340
And I'll talk into, you know,

00:40:15.340 --> 00:40:18.790
part of my presentation
today is I'll go into detail

00:40:18.790 --> 00:40:23.790
about how we analyze
those potential impacts

00:40:24.110 --> 00:40:26.773
to customers by analyzing
events in the past.

00:40:27.870 --> 00:40:29.947
I also wanted to, in my
introductory comments,

00:40:29.947 --> 00:40:33.725
provide some background
of how we actually calculate

00:40:33.725 --> 00:40:36.503
the overstrike feet, if you will,

00:40:39.056 --> 00:40:42.760
and relate it to our weather model grid.

00:40:42.760 --> 00:40:45.430
And I hope I don't lose
anybody along the way

00:40:45.430 --> 00:40:48.670
because a lot of what
we do is very complicated

00:40:48.670 --> 00:40:50.730
in the weather modeling space

00:40:50.730 --> 00:40:53.770
but hopefully it'll
give you enough Intel

00:40:53.770 --> 00:40:56.090
such that you can wrap
your mind around exactly

00:40:56.090 --> 00:40:58.650
how we're operationalizing this

00:40:58.650 --> 00:41:03.650
and exactly how we're
visualizing the risk every day.

00:41:03.840 --> 00:41:07.340
And so from the LiDAR data itself,

00:41:07.340 --> 00:41:09.080
you can imagine that for each tree

00:41:09.080 --> 00:41:10.800
we're getting a point information

00:41:10.800 --> 00:41:14.330
of the overstrike and,
you know, going back

00:41:14.330 --> 00:41:16.420
to some of the Commissioner
comments about, you know

00:41:16.420 --> 00:41:20.200
the 5.3 million trees being, you know,

00:41:20.200 --> 00:41:21.908
a quite staggering number,

00:41:21.908 --> 00:41:26.908
each one of those trees
has an average overstrike feet

00:41:27.300 --> 00:41:29.923
of about 32 to 33 feet.

00:41:30.870 --> 00:41:34.750
And so when you multiply
the average by the total number

00:41:34.750 --> 00:41:37.490
of trees that are out there,

00:41:37.490 --> 00:41:41.843
there's about 170
million feet of overstrike

00:41:41.843 --> 00:41:45.610
as determined from our aerial LiDAR.

00:41:45.610 --> 00:41:47.460
And you can imagine these are, you know

00:41:47.460 --> 00:41:52.460
point data sources
points across our grid.

00:41:53.900 --> 00:41:56.280
And so how did we come
up with 70th percentile?

00:41:56.280 --> 00:42:00.013
Well, we operate a high
resolution weather model,

00:42:00.013 --> 00:42:02.673
very similar to the
National Weather Service,

00:42:02.673 --> 00:42:04.260
similar to other IOUs

00:42:05.690 --> 00:42:09.070
and that weather model is
at two kilometer resolution.

00:42:09.070 --> 00:42:10.293
So what does that mean?

00:42:10.293 --> 00:42:15.200
That the grid itself is
analyzing the weather

00:42:15.200 --> 00:42:18.400
and forecasting weather at
two by two kilometers squares.

00:42:18.400 --> 00:42:21.930
It's the largest across
the state of California.

00:42:21.930 --> 00:42:26.930
Each square's approximately
four kilometers squared areas.

00:42:28.160 --> 00:42:30.950
And so for each of these grid cells

00:42:30.950 --> 00:42:33.940
we aggregated the amount of overstrike

00:42:33.940 --> 00:42:36.600
in each one of these areas.

00:42:36.600 --> 00:42:39.540
We have a little over
10,000 of these boxes,

00:42:39.540 --> 00:42:41.430
these grid cells, if you will

00:42:41.430 --> 00:42:45.230
or where you forecast weather
and also have historical data.

00:42:45.230 --> 00:42:48.633
And out of those 10,000, we now have

00:42:48.633 --> 00:42:52.080
and we understand the
amounts of overstrike feet

00:42:52.080 --> 00:42:53.940
in each one of those.

00:42:53.940 --> 00:42:57.960
And so we simply can
rank them from top to low,

00:42:57.960 --> 00:43:02.687
from top to bottom and
look at it in various ways.

00:43:02.687 --> 00:43:04.950
And we can look at
the outage relationship

00:43:04.950 --> 00:43:07.620
and history compared
to various percentiles.

00:43:07.620 --> 00:43:10.210
And so what we mean today

00:43:10.210 --> 00:43:12.427
when I mentioned 70th percentile

00:43:12.427 --> 00:43:14.520
and that comes up a lot,

00:43:14.520 --> 00:43:16.805
is if we rank those grid cells

00:43:16.805 --> 00:43:21.760
that have overstrike from top to bottom,

00:43:21.760 --> 00:43:26.270
the 70th percentile is
essentially we're looking at the top

00:43:26.270 --> 00:43:30.210
or the 70th percentile and
above of overstrike exposure.

00:43:30.210 --> 00:43:35.210
So that the very top 30%,
if you will, set another way

00:43:35.890 --> 00:43:38.430
of overstrike risk and
what that represents for us

00:43:38.430 --> 00:43:39.660
in our weather model domain

00:43:39.660 --> 00:43:44.660
is a fixed geographic area
where we have the most amounts

00:43:45.030 --> 00:43:48.513
of vegetation overstrike potential.

00:43:49.890 --> 00:43:51.900
And so just wanted
to provide that context.

00:43:51.900 --> 00:43:53.650
I know it's a little bit in the weeds

00:43:53.650 --> 00:43:55.090
a little bit detailed but hopefully

00:43:55.090 --> 00:43:56.470
I didn't lose folks along the way

00:43:56.470 --> 00:43:59.513
and hopefully that
made a little bit of sense.

00:44:00.840 --> 00:44:03.600
So if we go into the next slide.

00:44:03.600 --> 00:44:07.280
Before I get into how we utilize

00:44:07.280 --> 00:44:09.245
that 70th percentile geographic area

00:44:09.245 --> 00:44:11.880
I also wanted to provide some context

00:44:12.730 --> 00:44:16.920
around some of the
models that we utilize now

00:44:16.920 --> 00:44:20.337
and have utilized
and did utilize in 2020

00:44:20.337 --> 00:44:23.110
for public safety power shutoff.

00:44:23.110 --> 00:44:25.900
One of the core models that we use

00:44:25.900 --> 00:44:29.730
is called the Fire
Potential Index Model.

00:44:29.730 --> 00:44:33.980
And I'll probably use the
acronym FPI moving forward

00:44:33.980 --> 00:44:34.960
in this discussion.

00:44:34.960 --> 00:44:37.720
So that's the fire potential index.

00:44:37.720 --> 00:44:42.580
And the FPI model was
developed by my team,

00:44:43.450 --> 00:44:45.540
data scientists working
with fire scientists

00:44:45.540 --> 00:44:50.530
and meteorologists to
tease out the weather

00:44:50.530 --> 00:44:54.530
and feel kind of signals and predictors

00:44:54.530 --> 00:44:58.160
that lead to large
fires across California

00:44:58.160 --> 00:45:01.483
and across the PG and
E territory specifically.

00:45:02.421 --> 00:45:04.933
And in order to do this,

00:45:06.870 --> 00:45:08.760
I have to introduce another concept

00:45:08.760 --> 00:45:12.160
called a historical climatology.

00:45:12.160 --> 00:45:15.420
And essentially what
that is, is, you know,

00:45:15.420 --> 00:45:18.300
we not only forecast the weather

00:45:18.300 --> 00:45:22.760
at that two kilometer resolution
going forward out four days

00:45:22.760 --> 00:45:26.560
so that we can get a sense
of upcoming PSPS events,

00:45:26.560 --> 00:45:29.040
upcoming storm events,

00:45:29.040 --> 00:45:31.970
but what we've also done
is recreate the weather

00:45:32.950 --> 00:45:35.040
going back 30 years,

00:45:35.040 --> 00:45:38.920
hour by hour at that same resolution.

00:45:38.920 --> 00:45:41.630
We have the weather recreated,

00:45:41.630 --> 00:45:44.930
the dead and live fuel moistures

00:45:44.930 --> 00:45:47.670
and a number of different
meteorological parameters

00:45:47.670 --> 00:45:49.481
and parameters around fires

00:45:49.481 --> 00:45:52.360
that I'm not going to get into.

00:45:52.360 --> 00:45:56.960
But essentially we have
this very robust data set

00:45:56.960 --> 00:45:59.363
in order to analyze
events from the past.

00:46:01.440 --> 00:46:04.450
And just to provide
a little bit of context

00:46:04.450 --> 00:46:07.720
and maybe clarity in
some similarities of analysis

00:46:07.720 --> 00:46:08.670
that had been done,

00:46:09.550 --> 00:46:11.440
similar to what we're doing here,

00:46:11.440 --> 00:46:14.390
is that the high fire
threat district map

00:46:14.390 --> 00:46:19.390
that I think we all
know of that was issued

00:46:20.450 --> 00:46:23.470
I believe at the end
of 2017 from the CPUC

00:46:23.470 --> 00:46:25.730
was built on a similar concept.

00:46:25.730 --> 00:46:27.290
One of the core data sets in there

00:46:27.290 --> 00:46:31.210
was a reconstruction using
high resolution weather modeling

00:46:32.240 --> 00:46:34.230
and a 10 year data set to determine

00:46:34.230 --> 00:46:37.400
the highest risk areas
across our landscape

00:46:37.400 --> 00:46:41.623
and where specific, you
know, regulations should apply.

00:46:42.590 --> 00:46:46.610
And so with that historic
dataset what we're able to do is,

00:46:46.610 --> 00:46:49.330
for every fire that's
essentially occurred

00:46:49.330 --> 00:46:52.470
we can analyze it in very great detail.

00:46:52.470 --> 00:46:55.377
Understanding the conditions
that happened around ignition,

00:46:55.377 --> 00:46:58.900
the conditions that lead
to fires spreading rapidly,

00:46:58.900 --> 00:47:01.650
the conditions that lead to
fires not spreading rapidly

00:47:02.670 --> 00:47:03.560
and other things.

00:47:03.560 --> 00:47:06.743
And to that end, we...

00:47:06.743 --> 00:47:08.280
And then fast forward a little bit,

00:47:08.280 --> 00:47:11.750
we essentially constructed
4,000 different fire

00:47:11.750 --> 00:47:13.140
potential index models

00:47:13.140 --> 00:47:17.059
to test various
combinations of parameters

00:47:17.059 --> 00:47:21.000
that would be predictive for large fires

00:47:21.000 --> 00:47:23.390
and essentially selected the one

00:47:23.390 --> 00:47:25.860
that worked best for our territory.

00:47:25.860 --> 00:47:28.703
And at a high level
it's shown at the right.

00:47:30.020 --> 00:47:32.139
And basically what goes

00:47:32.139 --> 00:47:35.310
into our utility fire
potential index model,

00:47:35.310 --> 00:47:37.960
our FPI's weather component,

00:47:37.960 --> 00:47:39.986
wind speed, temperature,
relative humidity.

00:47:39.986 --> 00:47:43.313
A fuel component, we
look at dead fuel moisture,

00:47:44.420 --> 00:47:49.260
as well as live fuel moisture
and a land type components.

00:47:49.260 --> 00:47:52.760
And right now it's broken up
into three specific categories

00:47:52.760 --> 00:47:56.180
forest, shrub brush and grass.

00:47:56.180 --> 00:48:00.730
And we found that that
was a very good predictor

00:48:00.730 --> 00:48:04.117
where you know, it sort
of takes into account the,

00:48:05.670 --> 00:48:10.670
I guess the difficulty or
not of containment, right?

00:48:11.220 --> 00:48:15.130
Like grass fires, we found
are more easily contained.

00:48:15.130 --> 00:48:19.470
Therefore the FPI that's
calculated in grass type lands

00:48:19.470 --> 00:48:22.620
is less than what would
be computed in a forest

00:48:22.620 --> 00:48:24.993
just based on their
characteristics alone.

00:48:26.563 --> 00:48:31.120
And so I hope that gives you
some context of our FPI model.

00:48:31.120 --> 00:48:33.130
And so if we go to the
next slide I'll show you

00:48:33.130 --> 00:48:37.040
how the FPI model, which
is related to the probability

00:48:37.040 --> 00:48:38.620
of large fires is combined

00:48:38.620 --> 00:48:41.270
with our outage producing wind model

00:48:41.270 --> 00:48:46.023
which is related to the
probability of a unplanned,

00:48:46.880 --> 00:48:49.007
sustained and momentary outages,

00:48:49.007 --> 00:48:51.509
which is related to ignitions.

00:48:51.509 --> 00:48:56.509
And here, what we're trying
to accomplish is understand

00:48:57.074 --> 00:49:00.020
the probability of an event.

00:49:00.020 --> 00:49:03.260
Meaning the probability of an outage

00:49:03.260 --> 00:49:08.260
on our distribution network
that is related to wind

00:49:08.320 --> 00:49:11.160
and understand also the
consequence side of things,

00:49:11.160 --> 00:49:12.520
the fire potential index.

00:49:12.520 --> 00:49:15.070
So it's the probability of
an event occurred multiplied

00:49:15.070 --> 00:49:18.713
by the fire potential index.

00:49:19.760 --> 00:49:21.970
And the graph on the right shows

00:49:21.970 --> 00:49:25.290
the conceptual framework of
how the model essentially works.

00:49:25.290 --> 00:49:27.040
When you multiply these two together

00:49:27.040 --> 00:49:31.927
you can imagine that for
every single space in our model,

00:49:34.070 --> 00:49:37.070
we have an output of
outage producing winds,

00:49:37.070 --> 00:49:40.150
an output of the fire potential index

00:49:40.150 --> 00:49:44.570
and areas where the
outage producing a wind index

00:49:44.570 --> 00:49:46.750
is showing a high value,

00:49:46.750 --> 00:49:48.890
maybe there's high wind speeds,

00:49:48.890 --> 00:49:51.233
there's a high probability of an outage,

00:49:53.238 --> 00:49:55.570
that would, you know, on the y-axis

00:49:55.570 --> 00:49:58.880
that would start to
raise the level of OPW.

00:49:58.880 --> 00:50:02.147
And then we also look for
the concurrence in both space

00:50:02.147 --> 00:50:06.570
and time of where we have
a high fire potential index.

00:50:06.570 --> 00:50:08.830
And if you have the
concurrence of both of those

00:50:08.830 --> 00:50:11.430
in the space-time here in
the upper right-hand portion

00:50:11.430 --> 00:50:13.707
of the chart where it's typically

00:50:13.707 --> 00:50:16.360
during a Diablo wind event,

00:50:16.360 --> 00:50:17.573
a dry offshore wind event

00:50:17.573 --> 00:50:22.173
that we see these two
models kind of coming together.

00:50:23.690 --> 00:50:27.430
And essentially we
don't have it plotted here

00:50:27.430 --> 00:50:30.270
but a lot of our large
catastrophic fires

00:50:30.270 --> 00:50:35.270
in the past in California,
Tubs, Nuns, Atlas,

00:50:35.990 --> 00:50:38.121
you know, the the list continues,

00:50:38.121 --> 00:50:41.370
are in that upper right
portion of the chart.

00:50:41.370 --> 00:50:43.340
So we can plot all of our fires kind of

00:50:43.340 --> 00:50:44.713
in this space as well.

00:50:47.340 --> 00:50:51.430
I forgot to mention how
OPW was constructed

00:50:51.430 --> 00:50:54.110
and one thing I also forgot to mention

00:50:54.110 --> 00:50:57.060
which I'll circle back
to is that a discussion

00:50:57.060 --> 00:51:01.090
about these models can also be found

00:51:01.090 --> 00:51:05.250
on our Public 2021
Wildfire Mitigation Plan.

00:51:05.250 --> 00:51:06.610
I believe it's covered in depth

00:51:06.610 --> 00:51:09.900
in Section 4.2.A in that plan.

00:51:09.900 --> 00:51:12.630
So I encourage you
all to, if you don't have...

00:51:12.630 --> 00:51:14.374
If I've not given you
enough information,

00:51:14.374 --> 00:51:16.760
much more information is provided there

00:51:16.760 --> 00:51:19.083
and you can go through
it at your own pace.

00:51:20.905 --> 00:51:24.731
And then stepping into how
the outage producing wind model

00:51:24.731 --> 00:51:27.000
was constructed.

00:51:27.000 --> 00:51:30.190
Essentially, it's also a
machine learning model

00:51:30.190 --> 00:51:35.190
similar to the fire potential
index and going back 10 years

00:51:35.760 --> 00:51:38.930
essentially we can
extract the wind speeds

00:51:38.930 --> 00:51:42.030
from our robust historical dataset

00:51:42.030 --> 00:51:45.873
and upend those to every
single outage that has happened.

00:51:46.710 --> 00:51:51.710
We also supplemented the
model in 2019 with all the damages

00:51:52.140 --> 00:51:54.890
and hazards that happen
during PSPS events

00:51:54.890 --> 00:51:58.660
and so we get a sense and
we can tease out, you know,

00:51:58.660 --> 00:52:02.670
really what is the wind
to outage relationship

00:52:02.670 --> 00:52:04.761
across the PG and E territory.

00:52:04.761 --> 00:52:09.730
And because of the, you know
the uniqueness of California,

00:52:09.730 --> 00:52:13.040
uniqueness of Northern
California specifically,

00:52:13.040 --> 00:52:16.050
those relationships are
heterogeneous across the territory.

00:52:16.050 --> 00:52:18.910
And me and my team, you know every time

00:52:18.910 --> 00:52:22.860
there's a storm event one
of us is up monitoring the...

00:52:22.860 --> 00:52:24.760
And this could be a
winter storm or anything

00:52:24.760 --> 00:52:27.850
but one of us is typically
up monitoring the winds

00:52:27.850 --> 00:52:30.640
and the outage response
'cause we're also responsible

00:52:30.640 --> 00:52:32.900
for our storm outage prediction program

00:52:32.900 --> 00:52:37.480
which forecast outage
activity and get crews out

00:52:37.480 --> 00:52:39.670
in front of storms to mitigate

00:52:39.670 --> 00:52:41.440
the impacts for many unplanned outage

00:52:41.440 --> 00:52:44.320
but we've spent a
lot of time looking at,

00:52:44.320 --> 00:52:49.070
you know, what wind speeds
start to create outage activity

00:52:49.070 --> 00:52:50.533
just across our grid.

00:52:52.660 --> 00:52:56.390
And so, yeah, I hope that
provides some context of how

00:52:56.390 --> 00:53:00.370
these two models come
together and how we utilize them

00:53:00.370 --> 00:53:04.083
in order to form our
public safety power shutoff.

00:53:04.920 --> 00:53:07.015
And the last thing I'll leave
you with is another acronym

00:53:07.015 --> 00:53:10.280
and I apologize for
all the acronyms here,

00:53:10.280 --> 00:53:13.280
but the combination of the two models,

00:53:13.280 --> 00:53:18.160
we call our large fire
probability distribution model.

00:53:18.160 --> 00:53:22.330
So LSP, and you'll see that
on the next slide, I believe.

00:53:22.330 --> 00:53:23.453
So if we go there.

00:53:25.350 --> 00:53:30.350
This slide really talks
about and gives you

00:53:31.240 --> 00:53:34.110
kind of the exact formula
of how we would execute

00:53:34.110 --> 00:53:37.523
a public safety power, shutoff event.

00:53:38.860 --> 00:53:43.460
And one thing I need to start off on

00:53:43.460 --> 00:53:48.460
is that this is essentially
our 2020 PSPS framework

00:53:48.840 --> 00:53:52.810
for the distribution system
and the box that you see

00:53:52.810 --> 00:53:56.530
in blue that says
additional proposed criteria,

00:53:56.530 --> 00:54:00.880
it's kind of in the center
of the plot, bottom center,

00:54:00.880 --> 00:54:05.880
that is the proposed
new criteria to address

00:54:06.870 --> 00:54:11.870
the proposed conditions
from the Federal Court.

00:54:12.200 --> 00:54:14.830
And so that would be the new criteria

00:54:14.830 --> 00:54:16.920
where all the other criteria,

00:54:16.920 --> 00:54:20.000
essentially what we executed to in 2020.

00:54:25.380 --> 00:54:28.660
And so, yeah, let me just
take you through exactly

00:54:29.500 --> 00:54:34.363
how PSPS works and how we
would consider this new criteria.

00:54:35.350 --> 00:54:39.510
And so the first step of
determining whether or not

00:54:39.510 --> 00:54:42.370
we're going to be considering PSPS

00:54:42.370 --> 00:54:46.290
is looking at our minimum
fire potential conditions

00:54:46.290 --> 00:54:49.440
and the exact logic that goes into

00:54:49.440 --> 00:54:51.420
what the minimum fire
potential conditions is,

00:54:51.420 --> 00:54:56.020
has been tabled directly
below that blue box on the left.

00:54:56.020 --> 00:54:58.170
And the way this is done,

00:54:58.170 --> 00:55:01.670
is for every single four
kilometer squared area

00:55:01.670 --> 00:55:05.480
across the entire PG and E network,

00:55:05.480 --> 00:55:07.643
these conditions are assessed hourly,

00:55:08.740 --> 00:55:13.090
going out a little over four
days in our forecast horizon.

00:55:13.090 --> 00:55:17.140
And so we can get a sense
of if there are conditions

00:55:17.140 --> 00:55:21.680
that have historically led to
some of the catastrophic fires

00:55:21.680 --> 00:55:25.270
in California history
present or not present.

00:55:25.270 --> 00:55:29.220
And if so, then we
transition into the middle box.

00:55:29.220 --> 00:55:31.050
So for each one of those areas

00:55:31.050 --> 00:55:33.170
that have minimum
fire potential conditions,

00:55:33.170 --> 00:55:36.373
we consider boxes two, three or four.

00:55:37.920 --> 00:55:42.750
And box two is our large
fire probability model

00:55:42.750 --> 00:55:45.230
which I discussed on the previous slide

00:55:45.230 --> 00:55:48.470
which is again the
probability of an outage

00:55:48.470 --> 00:55:52.380
based on wind speed multiplied
by our fire potential index.

00:55:52.380 --> 00:55:54.983
It's the probability of large fires.

00:55:56.410 --> 00:55:58.410
And then the next box below that,

00:55:58.410 --> 00:56:03.050
is what we call our distribution
black swan conditions.

00:56:03.050 --> 00:56:08.050
And those criteria are in
the bottom right-hand portion

00:56:08.810 --> 00:56:12.020
of the chart there and
they're really meant to capture

00:56:12.020 --> 00:56:15.440
those very low probability

00:56:15.440 --> 00:56:19.030
but potentially high
consequence incidents.

00:56:19.030 --> 00:56:22.360
And it adds a very small addition

00:56:25.040 --> 00:56:28.150
to the overall scope of a PSPS.

00:56:28.150 --> 00:56:31.593
Less than a percent are
identified as a black swan.

00:56:32.440 --> 00:56:36.360
The new proposed criteria to address

00:56:36.360 --> 00:56:41.360
the Federal Courts proposed
condition is in the box below.

00:56:41.680 --> 00:56:45.210
And so if minimum fire
potential conditions are met,

00:56:45.210 --> 00:56:46.310
then we would consider

00:56:46.310 --> 00:56:50.540
that geographic footprint
of where the 70th percentile

00:56:50.540 --> 00:56:54.090
and above overstrike exposure is at,

00:56:54.090 --> 00:56:57.380
as well as the existence of priority one

00:56:57.380 --> 00:57:01.657
or priority two trees to
essentially establish the scope

00:57:04.820 --> 00:57:08.283
of PSPS on our distribution system.

00:57:09.150 --> 00:57:12.530
And so this is the proposal

00:57:12.530 --> 00:57:16.610
and there's a lot of detail.

00:57:16.610 --> 00:57:20.716
I can go into every
single one of these items.

00:57:20.716 --> 00:57:24.070
And I don't wanna go
into that level of detail here.

00:57:24.070 --> 00:57:27.313
A lot of this can be found in
our Wildfire Mitigation Plan.

00:57:28.640 --> 00:57:32.250
Another thing I wanted
to kind of mention

00:57:32.250 --> 00:57:34.690
and into a little bit detail on,

00:57:34.690 --> 00:57:38.090
is, you know, I've been
bringing up the concept

00:57:38.090 --> 00:57:40.970
of our historical climatology.

00:57:40.970 --> 00:57:44.130
That hour by hour historical look back

00:57:44.130 --> 00:57:47.940
that we have of that goes back 30 years.

00:57:47.940 --> 00:57:51.250
And one of the things
that's very powerful

00:57:51.250 --> 00:57:53.890
about that data set
is having the ability

00:57:53.890 --> 00:57:56.600
to run sensitivity analyses

00:57:57.479 --> 00:58:02.479
and understand what
this additional criteria

00:58:03.230 --> 00:58:07.660
to PSPS would mean in terms of the size,

00:58:07.660 --> 00:58:11.060
the scope and the
duration of PSPS events.

00:58:11.060 --> 00:58:14.150
And so what we're able to do

00:58:14.150 --> 00:58:17.910
and what my team is able
to do is take this criteria

00:58:17.910 --> 00:58:21.970
and take this methodology
and run it hour by hour.

00:58:21.970 --> 00:58:24.663
And we did this going
back 11 years to determine

00:58:24.663 --> 00:58:29.148
how many events, if we had a
time machine with this criteria

00:58:29.148 --> 00:58:30.770
what would we have executed on,

00:58:30.770 --> 00:58:33.760
how many catastrophic
fires would we have captured

00:58:33.760 --> 00:58:35.340
or not captured

00:58:35.340 --> 00:58:38.870
and importantly, what does
this mean for our customers?

00:58:38.870 --> 00:58:41.570
And then what can we do to help mitigate

00:58:41.570 --> 00:58:43.180
some of the impact to our customers

00:58:43.180 --> 00:58:46.610
which is coming up
a little bit later today.

00:58:46.610 --> 00:58:49.170
I think Jake Zigelman
is gonna be recording

00:58:49.170 --> 00:58:50.743
out for PG and E on that.

00:58:52.830 --> 00:58:56.100
And so I think the next three slides

00:58:58.690 --> 00:59:02.193
talk about some of the impacts

00:59:02.193 --> 00:59:05.420
that we've been able to determine

00:59:05.420 --> 00:59:08.190
based on that historic look back.

00:59:08.190 --> 00:59:10.248
Taking the proposed conditions,

00:59:10.248 --> 00:59:13.050
running it back through time,

00:59:13.050 --> 00:59:14.510
aggregating the results

00:59:14.510 --> 00:59:18.340
and then comparing it to
what we executed on in 2020.

00:59:20.820 --> 00:59:24.600
And so what we executed to in 2020,

00:59:24.600 --> 00:59:27.960
and if we took our 2020
guidance and ran it back in the past

00:59:27.960 --> 00:59:30.703
that is what we call the baseline.

00:59:31.780 --> 00:59:34.999
And this chart that we're showing now,

00:59:34.999 --> 00:59:38.820
if you look at the baseline column,

00:59:38.820 --> 00:59:43.820
that is essentially the
2020 model run backwards

00:59:45.360 --> 00:59:48.230
over an 11 year period.

00:59:48.230 --> 00:59:49.860
And what we find when we do that

00:59:49.860 --> 00:59:54.000
is we have about three
events per year on average.

00:59:54.000 --> 00:59:58.970
The average event duration
from a weather perspective only

00:59:58.970 --> 01:00:00.683
is about 24 hours.

01:00:01.530 --> 01:00:03.470
The average event customer count

01:00:03.470 --> 01:00:06.200
is almost a hundred thousand

01:00:06.200 --> 01:00:10.500
and the largest event
customer count is about 345,000

01:00:11.710 --> 01:00:15.930
if we take our 2020 model
and run it backward in time.

01:00:15.930 --> 01:00:17.980
One important note here is that

01:00:17.980 --> 01:00:22.980
this is only considering
distribution customers only.

01:00:24.660 --> 01:00:28.450
Now when we, or I guess the next column

01:00:28.450 --> 01:00:31.110
over from the baseline is

01:00:31.110 --> 01:00:34.830
with the additional consideration

01:00:34.830 --> 01:00:39.280
of vegetation overstrike to address

01:00:39.280 --> 01:00:42.790
the potential proposed
conditions from the Federal Court.

01:00:42.790 --> 01:00:47.370
And when we add that criteria in,

01:00:47.370 --> 01:00:49.300
what that could potentially mean

01:00:49.300 --> 01:00:51.507
when we look at that
same historical data set,

01:00:51.507 --> 01:00:55.970
the same exact weather,
just slightly different criteria

01:00:55.970 --> 01:00:59.480
the average number of
events goes from three to five,

01:00:59.480 --> 01:01:02.750
the event duration
goes from 24 hours to 29

01:01:02.750 --> 01:01:03.800
for an average event.

01:01:04.720 --> 01:01:07.600
Which represents an 18%
increase on the duration.

01:01:07.600 --> 01:01:10.513
The increase in
percentage is on the far right.

01:01:11.370 --> 01:01:13.740
The average event size goes up

01:01:15.031 --> 01:01:17.090
and also the largest event goes up.

01:01:17.090 --> 01:01:22.090
The largest events of obviously
is dependent on, you know

01:01:22.350 --> 01:01:24.963
the strongest weather
that we would experience.

01:01:27.100 --> 01:01:28.950
One thing to call out too,

01:01:28.950 --> 01:01:33.950
is that as the events get
stronger in magnitude,

01:01:34.327 --> 01:01:39.327
the percentage of
increase actually goes down

01:01:39.660 --> 01:01:42.643
so that when we get to
the largest event count,

01:01:43.510 --> 01:01:47.373
the size of the event
only grows by about 6%.

01:01:48.410 --> 01:01:50.040
And that's because we start to get

01:01:50.040 --> 01:01:52.730
into a realm where our
outage cruising wind model

01:01:52.730 --> 01:01:56.467
is capturing a lot of
that geographic footprint.

01:01:56.467 --> 01:01:59.050
We're seeing high outage probabilities

01:01:59.050 --> 01:02:03.140
or black swan comes into
play and other kind of criteria

01:02:03.140 --> 01:02:07.043
of our PSPS model are
capturing some of those areas.

01:02:09.110 --> 01:02:10.430
Another thing I can mention

01:02:10.430 --> 01:02:13.010
is that on the event frequency side

01:02:13.900 --> 01:02:18.290
the two events that would
potentially be added per year

01:02:18.290 --> 01:02:22.540
would be of the smaller
to moderate variety

01:02:22.540 --> 01:02:27.540
and so we're not adding, you
know, significant PSPS events

01:02:28.130 --> 01:02:30.095
although, you know, if you're a customer

01:02:30.095 --> 01:02:33.270
that's experiencing a PSPS event,

01:02:33.270 --> 01:02:37.470
we know that any event is significant

01:02:38.660 --> 01:02:41.500
but in terms of the
overall size of the event,

01:02:41.500 --> 01:02:44.860
we're not adding, you know,
some of the larger events

01:02:44.860 --> 01:02:48.660
it's more of the smaller
more moderate type events

01:02:48.660 --> 01:02:52.040
that are ultimately
being added to the scope.

01:02:52.040 --> 01:02:54.370
And I believe the next
slide actually gives

01:02:54.370 --> 01:02:58.210
the year by year impact and changes.

01:02:58.210 --> 01:03:01.300
And so there's a lot of
good information here

01:03:01.300 --> 01:03:02.443
I'll cover now.

01:03:04.575 --> 01:03:09.575
And this really gives, if
we go back to 2010 to 2020

01:03:10.180 --> 01:03:13.920
and run that framework and actually

01:03:13.920 --> 01:03:15.890
there's a couple of frameworks
that we're running here.

01:03:15.890 --> 01:03:19.260
We're running the baseline
model back in the past.

01:03:19.260 --> 01:03:22.860
That is what's covered
in the blue columns.

01:03:22.860 --> 01:03:27.670
So if we took our 2020
criteria without vegetation added

01:03:27.670 --> 01:03:29.260
and we ran it back 10 years,

01:03:29.260 --> 01:03:32.230
that's how many events, PSPS events

01:03:32.230 --> 01:03:33.663
we would have experienced.

01:03:35.650 --> 01:03:38.900
With the vegetation component added

01:03:40.040 --> 01:03:43.760
and that is represented
by the orange bars.

01:03:43.760 --> 01:03:47.650
So you can look at each
year and see how many events

01:03:47.650 --> 01:03:52.296
were added or not added
such like 2014 and 2020.

01:03:52.296 --> 01:03:55.933
And then the gray bars are
are actually what we executed to.

01:03:57.130 --> 01:03:59.760
And one important note there

01:03:59.760 --> 01:04:03.020
because you may be saying, okay, in 2019

01:04:03.020 --> 01:04:06.120
that doesn't make sense why
you executed seven events

01:04:06.120 --> 01:04:10.460
but your 2020 criteria only shows four.

01:04:10.460 --> 01:04:13.160
And the reason being
is that every single year

01:04:13.160 --> 01:04:14.980
since we've had PSPS

01:04:14.980 --> 01:04:17.160
we're on a continuous
improvement journey

01:04:17.160 --> 01:04:22.160
and our criteria is improving each year.

01:04:22.240 --> 01:04:26.470
And we're in that continuous
improvement phase right now.

01:04:26.470 --> 01:04:30.600
So in the off season,
when we're not in, you know

01:04:30.600 --> 01:04:34.030
extreme fire risk, my team works on all

01:04:34.030 --> 01:04:36.230
the identified improvements
that we can make

01:04:36.230 --> 01:04:39.610
to our fire potential index
now decreasing wind model

01:04:39.610 --> 01:04:43.690
such that we can operationalize
those models, you know

01:04:43.690 --> 01:04:45.230
by the upcoming fire season.

01:04:45.230 --> 01:04:49.290
And so every year we've kind of had that

01:04:51.370 --> 01:04:54.660
kind of continuous
improvement cadence, if you will,

01:04:54.660 --> 01:04:55.930
and this year is no different.

01:04:55.930 --> 01:05:00.140
We're working on both
of those core concepts

01:05:00.140 --> 01:05:01.840
of the model as all some other things.

01:05:01.840 --> 01:05:04.920
And I'm very excited about, you know,

01:05:04.920 --> 01:05:08.250
the new developments that
we're making in some of the space.

01:05:08.250 --> 01:05:10.750
And that's a totally
different conversation

01:05:10.750 --> 01:05:13.410
that I hope have soon.

01:05:13.410 --> 01:05:18.410
But that explains why our 2019 model

01:05:20.110 --> 01:05:21.790
and version of PSPS

01:05:21.790 --> 01:05:26.160
over your executing to
that has shown seven events

01:05:26.160 --> 01:05:29.900
and why if we ran our
2020 model now for 2019

01:05:29.900 --> 01:05:32.470
some of the events that
we actually executed on

01:05:32.470 --> 01:05:34.950
would not be PSPS events now.

01:05:34.950 --> 01:05:39.250
I'll give you an example,
like our June 8th PSPS event

01:05:39.250 --> 01:05:42.100
where we had pretty
significant to live fuel moistures

01:05:42.100 --> 01:05:46.750
so present in our territory is
one example of a 2019 event.

01:05:46.750 --> 01:05:49.560
And it's really those
marginal very small events

01:05:49.560 --> 01:05:51.660
that ended up not being events.

01:05:51.660 --> 01:05:54.606
But you know a couple other things

01:05:54.606 --> 01:05:57.400
that kind of stand out to me is that

01:05:58.360 --> 01:06:02.060
there's a lot of year
to year variability

01:06:02.060 --> 01:06:06.270
in the number of PSPS
events that one sees

01:06:06.270 --> 01:06:10.230
when you look at the
weather that you get, right?

01:06:10.230 --> 01:06:14.980
And, you know, I'll
maybe pull this adage

01:06:14.980 --> 01:06:16.750
out of the hat but, you know, climate

01:06:16.750 --> 01:06:19.150
is what you expect every year.

01:06:19.150 --> 01:06:22.970
So the average of the number of events,

01:06:22.970 --> 01:06:26.180
we get 4.8 with the
new vegetation criteria.

01:06:26.180 --> 01:06:28.690
So that's representation of the climate.

01:06:28.690 --> 01:06:30.300
So that's what we expect

01:06:30.300 --> 01:06:33.240
but the weather is what we get, right?

01:06:33.240 --> 01:06:35.930
And so this year's weather,

01:06:35.930 --> 01:06:38.720
we really don't have a sense
of what's going to happen.

01:06:38.720 --> 01:06:40.900
We have a sense that fire
danger is trending worse.

01:06:40.900 --> 01:06:43.440
But one thing that we see going back

01:06:43.440 --> 01:06:46.920
to the significant drought
years, 2012, through 2016

01:06:46.920 --> 01:06:48.800
if you look at that five-year timeframe

01:06:48.800 --> 01:06:50.820
when we were in considerable drought

01:06:50.820 --> 01:06:54.610
the weather was kind of in a
more quiescent, quiet pattern

01:06:54.610 --> 01:06:56.040
and we didn't really see a lot

01:06:56.040 --> 01:06:58.700
of off shore Diablo
wind events occurring

01:06:58.700 --> 01:07:01.983
and so the number of PSPS
events was below average.

01:07:02.965 --> 01:07:05.880
And so anyway this is kind
of like winter storms, right?

01:07:05.880 --> 01:07:08.630
The number of the
amount of precipitation

01:07:08.630 --> 01:07:11.520
each year's highly variable year.

01:07:11.520 --> 01:07:14.380
Right now we're in a bus year,

01:07:14.380 --> 01:07:15.213
a couple of years ago

01:07:15.213 --> 01:07:17.720
we were insignificant
balloon times, if you will,

01:07:17.720 --> 01:07:19.873
from a water perspective.

01:07:21.260 --> 01:07:23.850
and that's what we should
expect moving forward for PSPS.

01:07:23.850 --> 01:07:26.760
Some years we're
gonna have an abnormally

01:07:26.760 --> 01:07:30.990
or abnormal number of
offshore Diablo wind events

01:07:30.990 --> 01:07:35.990
which will lead to more PSPS
some years, hopefully sooner,

01:07:36.770 --> 01:07:39.010
we'll have less offshore wind events

01:07:39.010 --> 01:07:41.080
and quieter years.

01:07:41.080 --> 01:07:44.610
So that's just a kind of a
lesson of what to expect.

01:07:44.610 --> 01:07:47.853
It's very tough when dealing
with operational weather.

01:07:49.460 --> 01:07:53.100
So to tease out a couple
of other things here,

01:07:53.100 --> 01:07:58.100
2014 and 2020 these are
years where the additional criteria

01:08:00.350 --> 01:08:02.080
would not have increased.

01:08:02.080 --> 01:08:05.123
The number of times PSPS is calm.

01:08:06.970 --> 01:08:10.320
However, this is only
looking at the frequency

01:08:10.320 --> 01:08:12.250
of PSPS events.

01:08:12.250 --> 01:08:15.980
It's also important to
consider the duration

01:08:15.980 --> 01:08:17.180
as well as the size.

01:08:17.180 --> 01:08:18.670
How many customers are impacted.

01:08:18.670 --> 01:08:22.930
And from those angles,
from those dimensions,

01:08:22.930 --> 01:08:26.060
you know PSPS is getting larger.

01:08:26.060 --> 01:08:29.620
So I just wanted to also
say that it's important to look

01:08:29.620 --> 01:08:32.640
at PSPS, not just from
a frequency standpoint,

01:08:32.640 --> 01:08:35.450
but also from those other
two dimensions as well.

01:08:35.450 --> 01:08:37.730
And we're looking at those very closely

01:08:37.730 --> 01:08:42.203
when considering any
new criteria to execute on.

01:08:43.360 --> 01:08:45.240
And so if we go to the next slide,

01:08:45.240 --> 01:08:47.190
I believe this is my final slide

01:08:47.190 --> 01:08:50.500
and then I'll stop for questions.

01:08:50.500 --> 01:08:54.390
But we're also trying
to understand, you know

01:08:54.390 --> 01:08:59.390
each County specific
impact from these new criteria.

01:09:00.930 --> 01:09:04.480
And what we're finding
is that some counties

01:09:04.480 --> 01:09:08.350
are going to be impacted
more than other counties

01:09:08.350 --> 01:09:10.360
and the counties that are
gonna be impacted more

01:09:10.360 --> 01:09:12.730
by the implementation
of this new criteria

01:09:12.730 --> 01:09:16.950
are primarily those counties that one,

01:09:16.950 --> 01:09:20.740
have, you know, a high
amount of overstrike exposure

01:09:20.740 --> 01:09:21.600
next to our lines.

01:09:21.600 --> 01:09:24.370
These are heavily forested areas.

01:09:24.370 --> 01:09:29.370
And two, they experience
offshore dry wind events

01:09:29.460 --> 01:09:30.940
more than others.

01:09:30.940 --> 01:09:32.680
And generally these are locations

01:09:32.680 --> 01:09:34.770
that are in the Northern Sierra.

01:09:34.770 --> 01:09:37.510
The kind of Shasta-Trinity area

01:09:37.510 --> 01:09:39.780
where we get those North winds

01:09:39.780 --> 01:09:43.620
as well as the North Bay
in Santa Cruz mountains.

01:09:43.620 --> 01:09:47.450
Primarily the kind of
geographic footprint North

01:09:47.450 --> 01:09:52.443
of generally a moderate to
about a kind of Highway 88 line.

01:09:56.140 --> 01:09:59.320
Areas across farther down in the South,

01:09:59.320 --> 01:10:02.390
they don't experience as
many offshore wind events

01:10:02.390 --> 01:10:04.150
on average, historically, right?

01:10:04.150 --> 01:10:06.935
This is all based on
looking at past weather.

01:10:06.935 --> 01:10:11.410
And so those counties that
are more in Northern California

01:10:11.410 --> 01:10:14.647
are going to be impacted
more with this criteria.

01:10:14.647 --> 01:10:18.440
And this is an example of Butte County's

01:10:19.930 --> 01:10:23.710
kind of history looking
at the 2020 model.

01:10:23.710 --> 01:10:25.990
The 2020 model's plus 70 percentile

01:10:25.990 --> 01:10:29.410
and above overstrike exposure areas

01:10:30.630 --> 01:10:35.523
as well as what was
executed on in 2019 and 2020.

01:10:36.370 --> 01:10:40.300
And it's important to note
that we've created these

01:10:40.300 --> 01:10:42.440
for every single County.

01:10:42.440 --> 01:10:44.770
And I think this is gonna be covered

01:10:44.770 --> 01:10:48.300
in the kind of customer
communication portion

01:10:48.300 --> 01:10:52.910
of today's discussion
but we are in the process

01:10:52.910 --> 01:10:57.100
of communicating these
potential impacts to counties

01:10:57.100 --> 01:10:59.983
should these proposed
conditions be implemented.

01:11:01.930 --> 01:11:06.410
So I believe that's the
totality of my presentation

01:11:06.410 --> 01:11:09.363
and I'll be happy to stop
and take your questions.

01:11:17.610 --> 01:11:20.120
<v ->Yes Scott, this is Jeff
Fuentes with Cal FIRE.</v>

01:11:20.120 --> 01:11:22.380
Thank you for the presentation.

01:11:22.380 --> 01:11:23.640
I did have a question

01:11:24.780 --> 01:11:27.440
and it was kind of a two-part question,

01:11:27.440 --> 01:11:29.690
kind of going back to
the decision-making slide

01:11:29.690 --> 01:11:32.720
and looking at the different
thresholds that were there.

01:11:32.720 --> 01:11:35.430
And it sounded like those
were the same thresholds

01:11:35.430 --> 01:11:40.430
for 2020 with the exception of that new

01:11:40.690 --> 01:11:42.130
potential overstrike data.

01:11:42.130 --> 01:11:43.200
Is that correct?

01:11:43.200 --> 01:11:44.600
And then kind of the second part

01:11:44.600 --> 01:11:47.090
I'm wondering how
you guys are accounting

01:11:47.090 --> 01:11:48.840
for hardened distribution circuits.

01:11:48.840 --> 01:11:52.750
So for example, you know,
circuits with covered conductor

01:11:52.750 --> 01:11:55.890
you know, is there a different
wind threshold for those?

01:11:55.890 --> 01:11:58.940
Are they just completely
removed from scope

01:11:58.940 --> 01:12:01.330
in those areas kind of looking

01:12:01.330 --> 01:12:02.880
at that decision-making slides.

01:12:04.430 --> 01:12:05.263
<v ->Great. Yeah.</v>

01:12:05.263 --> 01:12:06.230
Yeah. Thank you, Jeff.

01:12:07.670 --> 01:12:09.710
Yeah. So going back to
the decision-making slide

01:12:09.710 --> 01:12:11.550
if we can go there, I think it's

01:12:12.500 --> 01:12:16.340
if you advance one
more please on the slide

01:12:17.630 --> 01:12:19.550
and you're talking about this one, Jeff.

01:12:19.550 --> 01:12:23.380
Yeah, there has been one slight change

01:12:23.380 --> 01:12:26.410
from what we actually
executed on in 2020.

01:12:26.410 --> 01:12:29.750
And I believe our minimum
fire potential conditions

01:12:29.750 --> 01:12:33.980
have slightly different
dead fuel moisture

01:12:34.960 --> 01:12:38.630
kind of thresholds and so the
dead fuel moisture thresholds

01:12:38.630 --> 01:12:43.630
were actually adjusted
for use in 2020 and 2021.

01:12:44.000 --> 01:12:46.580
And that's under consideration.

01:12:46.580 --> 01:12:49.440
Essentially everything
with a double asterisk

01:12:49.440 --> 01:12:53.500
is under consideration
based on the update cadence

01:12:53.500 --> 01:12:54.333
that I mentioned.

01:12:54.333 --> 01:12:58.910
So essentially we're
and my team are delving

01:12:58.910 --> 01:13:01.804
through all the data from 2020.

01:13:01.804 --> 01:13:06.804
All the fires that happened,
all the wind patterns

01:13:06.930 --> 01:13:09.850
all the dead fuel
moistures to substantiate

01:13:09.850 --> 01:13:11.978
any adjustments to the criteria.

01:13:11.978 --> 01:13:16.110
We don't expect there to
be any significant changes

01:13:16.110 --> 01:13:17.740
but there might be some.

01:13:17.740 --> 01:13:19.170
For example we're closely looking

01:13:19.170 --> 01:13:21.860
at the dead fuel moisture values to see

01:13:21.860 --> 01:13:24.140
if they can be reduced in some areas

01:13:24.140 --> 01:13:26.150
or the relative humidity to be reduced.

01:13:26.150 --> 01:13:30.260
And we have essentially
for every single fire

01:13:31.220 --> 01:13:32.910
and we have a really good data set now

01:13:32.910 --> 01:13:36.023
that shows the day by
day progression of each fire.

01:13:36.880 --> 01:13:38.900
We can look at the meteorological

01:13:38.900 --> 01:13:40.420
and fuel conditions related to that.

01:13:40.420 --> 01:13:44.080
So that'll support any changes
that we would need to make

01:13:44.080 --> 01:13:46.620
to the minimum fire
potential conditions, if you will.

01:13:46.620 --> 01:13:51.620
But aside from that small adjustment,

01:13:51.880 --> 01:13:56.880
essentially everything
else was the same in 2020

01:13:57.140 --> 01:14:00.150
aside from box four

01:14:00.150 --> 01:14:02.910
that's in the additional
proposed criteria.

01:14:02.910 --> 01:14:04.020
And I'll pause there to see

01:14:04.020 --> 01:14:06.560
if I answered your first question

01:14:06.560 --> 01:14:08.610
before moving on to
your second question.

01:14:09.790 --> 01:14:11.460
<v Jeff>Yes. Thank you.</v>

01:14:11.460 --> 01:14:12.293
<v ->Great.</v>

01:14:12.293 --> 01:14:13.500
Yeah. And your second question

01:14:13.500 --> 01:14:16.540
was related to a system hardening.

01:14:16.540 --> 01:14:19.810
And so a system hardening to date

01:14:19.810 --> 01:14:22.950
has been conducted mostly on segments.

01:14:22.950 --> 01:14:24.730
So we've been focused on

01:14:24.730 --> 01:14:29.360
where we have the
highest overall wildfire risk

01:14:29.360 --> 01:14:34.220
and we've been performing
hardening in those segments.

01:14:34.220 --> 01:14:38.760
And, you know, not
necessarily from this,

01:14:38.760 --> 01:14:40.260
all the way from the substation

01:14:40.260 --> 01:14:43.620
out to the end of the line, if you will.

01:14:43.620 --> 01:14:48.620
And if we wanted to kind
of mitigate a line for PSPS,

01:14:50.140 --> 01:14:53.250
essentially that entire
line would have to have

01:14:53.250 --> 01:14:57.303
a very low risk of causing a ignition.

01:15:01.767 --> 01:15:05.710
And actually in to add some more context

01:15:05.710 --> 01:15:07.470
there's two lines that we identified

01:15:07.470 --> 01:15:11.760
that there are potential pathways

01:15:11.760 --> 01:15:15.610
and methodologies to
maybe adjust our criteria

01:15:15.610 --> 01:15:16.960
such that we can take into account,

01:15:16.960 --> 01:15:18.969
yes, we've done system hardening here,

01:15:18.969 --> 01:15:23.280
how can we adjust our
thresholds to account for, you know

01:15:23.280 --> 01:15:25.010
the system hardening that we've done?

01:15:25.010 --> 01:15:27.660
And so those discussions
are actively taking place.

01:15:27.660 --> 01:15:30.540
I actually have a meeting
at 4:00p.m internally

01:15:30.540 --> 01:15:32.280
to discuss that exact concept.

01:15:32.280 --> 01:15:36.070
So we don't have that
methodology worked out

01:15:36.070 --> 01:15:38.140
but those discussions
are actively happening.

01:15:38.140 --> 01:15:41.610
And one thing that,
that we want to do similar

01:15:41.610 --> 01:15:43.200
to other utilities that we've looked at,

01:15:43.200 --> 01:15:48.200
is collect pre versus post
event system hardening data

01:15:49.950 --> 01:15:51.698
to substantiate any adjustments

01:15:51.698 --> 01:15:53.903
that we made to our criteria.

01:15:55.390 --> 01:15:57.240
And it's important that,
you know, we collect

01:15:57.240 --> 01:16:00.880
that data to validate
performance during wind events

01:16:00.880 --> 01:16:03.050
not just during blue sky events.

01:16:03.050 --> 01:16:05.530
So hopefully I answered your question,

01:16:05.530 --> 01:16:08.423
happy to take another
run at it the possible.

01:16:09.690 --> 01:16:11.450
<v Jeff>No, thank you, Scott.</v>

01:16:16.870 --> 01:16:19.520
<v Joyce>Commissioners, do
you have other questions?</v>

01:16:21.550 --> 01:16:23.240
<v ->Yes. Thank you.</v>

01:16:23.240 --> 01:16:25.465
So if you could go back to the slide

01:16:25.465 --> 01:16:28.183
that shows the expanded duration.

01:16:32.780 --> 01:16:36.700
Are you going to give us
some regional breakout of this?

01:16:36.700 --> 01:16:41.540
I know your example of
view was a frequency example

01:16:41.540 --> 01:16:46.380
and I think based on
what Sumeet said earlier,

01:16:46.380 --> 01:16:50.340
the potential duration is potentially

01:16:50.340 --> 01:16:52.479
an even greater concern.

01:16:52.479 --> 01:16:53.583
Is that correct?

01:16:55.980 --> 01:17:00.420
<v ->Sorry, I didn't catch
your last, last sentence.</v>

01:17:00.420 --> 01:17:02.463
Can you repeat that last portion?

01:17:04.860 --> 01:17:08.720
<v ->I think your slides while
helpful in highlighting</v>

01:17:08.720 --> 01:17:13.720
the potential increase in
frequency dating back to applying

01:17:14.100 --> 01:17:17.700
those in previous
years that we'll likely see

01:17:17.700 --> 01:17:19.850
a trend of frequency.

01:17:19.850 --> 01:17:23.870
However this light and the factoid

01:17:23.870 --> 01:17:28.870
that Sumeet shared with us
earlier on the 5.3 million trees

01:17:31.340 --> 01:17:34.760
leads me to think
that the bigger concern

01:17:34.760 --> 01:17:39.760
is actually the scope and
duration of these events.

01:17:41.760 --> 01:17:44.110
Are you going to give us more detail

01:17:44.110 --> 01:17:48.880
on the geographical
scope that will be impacted

01:17:49.900 --> 01:17:52.333
by adding this additional criteria?

01:17:55.200 --> 01:17:56.420
<v ->Yeah, yeah.</v>

01:17:56.420 --> 01:17:57.640
I believe we can.

01:17:57.640 --> 01:18:00.880
And I think, yeah looking at
all three dimensions, again,

01:18:00.880 --> 01:18:03.340
is very important when considering PSPS,

01:18:03.340 --> 01:18:04.440
not just the frequency.

01:18:04.440 --> 01:18:07.496
So I think you're thinking
about it the right way.

01:18:07.496 --> 01:18:09.584
And for each one of these events,

01:18:09.584 --> 01:18:11.540
it starts to get very dynamic

01:18:11.540 --> 01:18:14.020
because every single
circuit, every single grid cell

01:18:14.020 --> 01:18:16.000
is gonna experience
the event differently.

01:18:16.000 --> 01:18:18.950
And just to give you maybe
a click below the surface

01:18:18.950 --> 01:18:23.023
of how the event was,
the ration was calculated,

01:18:24.340 --> 01:18:28.970
that's looking at it from a
overall view of a PSPS event.

01:18:28.970 --> 01:18:32.980
So when did the event
actually start for the first circuit

01:18:32.980 --> 01:18:35.960
and the when would it
end for the last circuit

01:18:35.960 --> 01:18:39.090
to come out of the weather
risk period, if you will.

01:18:39.090 --> 01:18:41.620
So we're looking at it
from that perspective.

01:18:41.620 --> 01:18:43.600
And there's other ways to look at it

01:18:45.200 --> 01:18:47.850
whether you do it by
County by County specific.

01:18:47.850 --> 01:18:51.370
And so there's almost
an infinite number of ways

01:18:51.370 --> 01:18:53.610
to slice and dice the historic data

01:18:53.610 --> 01:18:55.842
in the way that we've done.

01:18:55.842 --> 01:18:58.850
But I believe if some of that analysis

01:18:58.850 --> 01:19:03.850
is, you know, we can essentially
generate that if needed.

01:19:05.740 --> 01:19:08.870
<v ->Can you go to the slide
that shows the larger event</v>

01:19:08.870 --> 01:19:10.663
versus smaller event?

01:19:15.622 --> 01:19:18.539
Maybe that was larger event, sorry.

01:19:22.280 --> 01:19:24.433
Can you go back to that last slide

01:19:27.970 --> 01:19:29.563
where it has the table?

01:19:30.910 --> 01:19:32.640
<v ->The one before, yeah?</v>

01:19:32.640 --> 01:19:33.473
<v ->Yeah.</v>

01:19:33.473 --> 01:19:36.610
Okay. So here you're showing
that obviously compared

01:19:36.610 --> 01:19:39.060
to a large event, it would be the same

01:19:39.060 --> 01:19:42.890
because we're capturing the large scope

01:19:42.890 --> 01:19:44.110
and average event.

01:19:44.110 --> 01:19:47.770
This is maybe where I'm most
interested in understanding

01:19:47.770 --> 01:19:50.120
the impact of these average events

01:19:50.120 --> 01:19:52.880
because you're saying on average,

01:19:52.880 --> 01:19:55.170
the scope is gonna get bigger.

01:19:55.170 --> 01:19:56.930
And based on what you said before,

01:19:56.930 --> 01:19:59.080
it's gonna get bigger primarily

01:19:59.080 --> 01:20:03.970
in certain counties in the state.

01:20:03.970 --> 01:20:08.250
And so you showed a frequency for Butte.

01:20:08.250 --> 01:20:10.365
Can you show kind of how many customers

01:20:10.365 --> 01:20:12.607
you're talking about there?

01:20:12.607 --> 01:20:14.523
And you can follow up on that.

01:20:15.750 --> 01:20:16.870
<v ->Sure. Yeah.</v>

01:20:16.870 --> 01:20:19.240
There's a couple of
important caveats here

01:20:19.240 --> 01:20:20.993
when we're looking at the average.

01:20:22.230 --> 01:20:26.870
So if we looked at the
average of all events

01:20:26.870 --> 01:20:28.423
with the proposed criteria,

01:20:29.510 --> 01:20:32.020
the average actually goes down

01:20:32.020 --> 01:20:34.040
in terms of the number of customers

01:20:34.040 --> 01:20:35.640
that will experienced a PSPS event

01:20:35.640 --> 01:20:40.000
because we're adding smaller events.

01:20:40.000 --> 01:20:43.640
And so in order to represent an average,

01:20:43.640 --> 01:20:45.920
we wanted to put it on
terms that the baseline.

01:20:45.920 --> 01:20:47.680
So we only took the baseline,

01:20:47.680 --> 01:20:50.160
the average of the events
that are in the baseline,

01:20:50.160 --> 01:20:50.993
if that makes sense,

01:20:50.993 --> 01:20:53.810
to compare the average apples to apples.

01:20:53.810 --> 01:20:55.970
So that hopefully that makes sense

01:20:55.970 --> 01:20:57.950
and gives you some
context because we didn't feel

01:20:57.950 --> 01:21:00.840
like it was representative
to show the average

01:21:00.840 --> 01:21:02.450
of all the events 'cause
they've actually showed

01:21:02.450 --> 01:21:05.580
the average going down
which doesn't really make sense.

01:21:05.580 --> 01:21:09.090
So if that provides some context there.

01:21:09.090 --> 01:21:13.160
But in terms of, yeah, the
customer impacts per County

01:21:13.160 --> 01:21:17.970
don't have that off the top of
my head or in my back pocket

01:21:17.970 --> 01:21:21.196
right now but that's something
that can be generated

01:21:21.196 --> 01:21:23.197
in post analysis if needed..

01:21:24.437 --> 01:21:26.140
<v ->[Smith[ Thank you Scott
and Commissioner Guzman.</v>

01:21:26.140 --> 01:21:26.973
This is Smith.

01:21:26.973 --> 01:21:30.060
We'll take that as a
follow-up for your reference.

01:21:30.060 --> 01:21:33.150
It's gonna be very difficult
to see the resolution

01:21:33.150 --> 01:21:34.190
if you go to the last slide

01:21:34.190 --> 01:21:37.030
but it's in the materials
that were sent out.

01:21:37.030 --> 01:21:38.990
If you actually look at that last slide

01:21:38.990 --> 01:21:40.960
that provides the frequency piece,

01:21:40.960 --> 01:21:44.940
not just for Butte, but all
of the other 47 counties

01:21:44.940 --> 01:21:46.740
within a high fire threat districts.

01:21:46.740 --> 01:21:49.330
It's the last slide in the appendix.

01:21:49.330 --> 01:21:50.760
So that's been distributed

01:21:50.760 --> 01:21:53.880
and what we can add to your
request, Commissioner Guzman,

01:21:53.880 --> 01:21:57.280
is if you go back to that
same table, I'm sorry.

01:21:57.280 --> 01:21:58.440
Of course helping with the slides.

01:21:58.440 --> 01:22:01.520
Yep. We can provide you
with that context by County

01:22:01.520 --> 01:22:04.480
not just the frequency,
but also add the duration

01:22:04.480 --> 01:22:05.857
and average event
customer count increase

01:22:05.857 --> 01:22:07.600
if that's the question you were asking

01:22:07.600 --> 01:22:10.050
so we can take them to
the follow-up, no problem.

01:22:11.690 --> 01:22:12.523
<v ->Thank you.</v>

01:22:12.523 --> 01:22:14.930
<v ->Yeah. And one thing
I wanted to call out</v>

01:22:14.930 --> 01:22:17.283
and apologies for
not doing this is that,

01:22:18.860 --> 01:22:22.800
we don't expect based
on this historical analysis

01:22:22.800 --> 01:22:27.000
to return to 2019 levels of PSPS.

01:22:27.000 --> 01:22:31.510
We don't expect to have
the same customer impact

01:22:31.510 --> 01:22:33.950
that was experienced in 2019.

01:22:33.950 --> 01:22:36.493
So just wanted to call that out as well.

01:22:38.440 --> 01:22:41.430
<v ->I have a question
that sort of follows up</v>

01:22:41.430 --> 01:22:43.978
on Commissioner Guzman Aceves

01:22:43.978 --> 01:22:47.220
and that is several,
Butte being among them,

01:22:47.220 --> 01:22:51.493
but also in the North
Bay counties as well.

01:22:52.380 --> 01:22:56.110
It's not only the scope and the duration

01:22:56.110 --> 01:22:57.133
but it's back to back.

01:22:57.133 --> 01:22:58.480
I mean, there's some folks

01:22:58.480 --> 01:23:00.853
that have had back to back PSPS.

01:23:02.030 --> 01:23:06.750
By the time you guys have
finished the reenergizing

01:23:06.750 --> 01:23:08.970
we're already in the second PSPS.

01:23:08.970 --> 01:23:13.970
So when you look at the
duration, hours they're turned off,

01:23:14.170 --> 01:23:18.130
some folks have been
dead, you know, not, not 24

01:23:18.130 --> 01:23:21.680
which the average, I
forget here, 36, whatever,

01:23:21.680 --> 01:23:23.860
it's like seven, eight days

01:23:23.860 --> 01:23:26.330
because it's not just
the duration of the PS

01:23:26.330 --> 01:23:30.010
it's before you guys do your
patrol and then go back into...

01:23:30.010 --> 01:23:33.420
So it would be helpful
in this information

01:23:33.420 --> 01:23:34.690
maybe if you can do,

01:23:34.690 --> 01:23:36.330
and I don't know if it's possible,

01:23:36.330 --> 01:23:38.270
but showing those counties

01:23:38.270 --> 01:23:40.810
where in terms of
turn on and turning off

01:23:40.810 --> 01:23:43.283
the electricity and turning it back on,

01:23:46.684 --> 01:23:50.740
how many of them had back
to back over the last few years

01:23:50.740 --> 01:23:55.740
especially 19 and 20 and PSPS's

01:23:55.810 --> 01:24:00.810
and would the Federal
Courts proposed new criteria

01:24:04.220 --> 01:24:07.310
escalate that I mean,
given your modeling?

01:24:07.310 --> 01:24:08.470
That might be an impossible...

01:24:08.470 --> 01:24:10.440
The second might be
an impossible question.

01:24:10.440 --> 01:24:11.743
I totally understand that.

01:24:14.860 --> 01:24:16.637
<v ->Yeah, I think with...</v>

01:24:16.637 --> 01:24:17.930
Oh, am I on mute?

01:24:17.930 --> 01:24:18.763
No, I'm good.

01:24:19.700 --> 01:24:21.240
No, thank you for the question

01:24:21.240 --> 01:24:23.550
and I think that's another
important dimension

01:24:23.550 --> 01:24:25.220
to look at as well.

01:24:25.220 --> 01:24:28.380
And, you know, given the two months

01:24:28.380 --> 01:24:31.730
that we've had to produce this
analysis, you know, obviously

01:24:31.730 --> 01:24:36.412
we haven't been able to
turn over every stone here.

01:24:36.412 --> 01:24:39.480
You know, there's one
thing that, and I lived...

01:24:39.480 --> 01:24:42.090
Well, I think we all lived
through the 2019 events

01:24:43.260 --> 01:24:45.800
but you know, in 2019

01:24:45.800 --> 01:24:50.800
I think there was two or
three kind of triple hitters

01:24:50.810 --> 01:24:53.080
that we got where we had, you know

01:24:53.080 --> 01:24:56.200
an event followed by an
event, followed by an event.

01:24:56.200 --> 01:25:00.290
And what's very concerning
to me about those,

01:25:00.290 --> 01:25:05.290
and, you know, Jeff Fuentes
from Cal FIRE, you know,

01:25:05.760 --> 01:25:08.680
can chime in here but
after we get the first event,

01:25:08.680 --> 01:25:11.810
you know, it's dry and
things start to dry out

01:25:11.810 --> 01:25:14.530
and fuels just get drier
and drier with every event.

01:25:14.530 --> 01:25:16.830
So even by the time
we get the third event

01:25:18.860 --> 01:25:22.170
some pretty scary fuel
situations can develop, you know,

01:25:22.170 --> 01:25:23.420
if we're in October and November,

01:25:23.420 --> 01:25:25.160
it hasn't rained in six months.

01:25:25.160 --> 01:25:28.050
And so those in my mind

01:25:28.050 --> 01:25:30.687
are some of the most
dangerous events that we have.

01:25:30.687 --> 01:25:32.760
But we're looking at it.

01:25:32.760 --> 01:25:37.760
But I do think we can
look at it in that lens.

01:25:40.410 --> 01:25:43.260
One thing we haven't
considered in this analysis

01:25:43.260 --> 01:25:47.250
that you've seen today
is the restoration time

01:25:47.250 --> 01:25:48.207
to restore customers.

01:25:48.207 --> 01:25:49.790
And we can make some assumptions

01:25:49.790 --> 01:25:52.810
in the past about you
know, 12 daylight hours

01:25:52.810 --> 01:25:54.730
or something like that
and then look at okay,

01:25:54.730 --> 01:25:58.583
if we add 12 daylight
hours on the last kind of time

01:26:00.380 --> 01:26:01.650
where the weather subsides

01:26:01.650 --> 01:26:04.043
where we would issue traditional clears,

01:26:04.960 --> 01:26:06.994
what does that look like for
events that go back to back?

01:26:06.994 --> 01:26:11.994
And look at the maximum
duration, if you will,

01:26:12.190 --> 01:26:14.179
that might be another
dimension to analyze as well.

01:26:14.179 --> 01:26:16.050
But yeah.

01:26:16.050 --> 01:26:20.110
<v ->Easy to read because
that really shows the impact</v>

01:26:20.110 --> 01:26:24.670
particularly for our
folks, your customers.

01:26:24.670 --> 01:26:27.480
The rate payers who are considered

01:26:27.480 --> 01:26:31.810
part of the medical baseline
and need backup battery

01:26:31.810 --> 01:26:34.490
and when they experienced a PSPS

01:26:34.490 --> 01:26:39.490
that lasts days in terms of
them not having electricity,

01:26:44.310 --> 01:26:46.477
it's just a huge you know,
the impacts are huge.

01:26:46.477 --> 01:26:51.477
Impacts are huge to obviously
food spoilage, et cetera.

01:26:55.410 --> 01:26:58.910
So I think that's a piece of this story

01:26:58.910 --> 01:27:00.680
that we need to be able to tell.

01:27:00.680 --> 01:27:03.300
One of my concerns
is not only the safety

01:27:06.368 --> 01:27:09.170
of the public, of why you call a PSPS,

01:27:10.090 --> 01:27:13.470
of course it's the last resort

01:27:13.470 --> 01:27:15.260
but it's also the safety of people

01:27:15.260 --> 01:27:18.150
who are experiencing a PSPS.

01:27:18.150 --> 01:27:21.130
And it's a huge concern.

01:27:21.130 --> 01:27:24.090
Both sides of that
equation, if you will.

01:27:24.090 --> 01:27:25.540
So, okay, I'll stop there.

01:27:25.540 --> 01:27:28.610
I know we're probably
running a little bit behind now.

01:27:28.610 --> 01:27:30.117
<v ->Scott, this is
Commissioner Rechtschffen</v>

01:27:30.117 --> 01:27:31.683
and I have a question for you.

01:27:32.550 --> 01:27:37.327
You mentioned how much
variability there is about weather

01:27:39.240 --> 01:27:41.374
and I would say climate.

01:27:41.374 --> 01:27:45.340
2020 is a good example
of the fire season

01:27:45.340 --> 01:27:47.160
defied all expectations.

01:27:47.160 --> 01:27:49.280
It's the largest ever.

01:27:49.280 --> 01:27:50.930
You noted we're in a drought

01:27:50.930 --> 01:27:53.367
or in the prior drought
weather conditions

01:27:53.367 --> 01:27:58.343
can been conspire to result
in a lot of PSPS as they could.

01:27:59.590 --> 01:28:03.700
My question is, can you share
with us a sensitivity analysis

01:28:03.700 --> 01:28:08.050
that you've run that show what
happens in some worst case

01:28:08.050 --> 01:28:09.800
or less best worst?

01:28:09.800 --> 01:28:11.810
I don't know if worse is the word

01:28:11.810 --> 01:28:16.110
but in more troubling
circumstances of the scope of PSPS

01:28:16.110 --> 01:28:18.857
is under this new regime in 2021.

01:28:18.857 --> 01:28:21.200
'Cause I'm a little
worried that we're getting,

01:28:21.200 --> 01:28:24.027
I don't know if you've
done that already.

01:28:24.027 --> 01:28:26.580
If it's in the dependencies
this is a range of PSPS

01:28:26.580 --> 01:28:30.350
but I'm very worried about
a worst set of conditions

01:28:30.350 --> 01:28:31.590
will determine what the scope

01:28:31.590 --> 01:28:34.223
and extent would be of the PSPSs.

01:28:36.540 --> 01:28:38.780
<v ->Yeah, I think we could
absolutely take that</v>

01:28:38.780 --> 01:28:42.520
as a follow-up and
part of what we do is run

01:28:42.520 --> 01:28:44.580
a lot of sensitivity studies

01:28:44.580 --> 01:28:49.580
to set our PSPS framework every year.

01:28:50.380 --> 01:28:53.710
And we've done this
for the vegetation criteria.

01:28:53.710 --> 01:28:56.660
We looked at various percentiles

01:28:56.660 --> 01:29:00.190
of the vegetation overstrike percentile

01:29:00.190 --> 01:29:02.625
and I believe it's one of
the slides in the appendix

01:29:02.625 --> 01:29:04.850
and we don't need to go there now.

01:29:04.850 --> 01:29:08.480
I think if folks wanna look
at that information, they can

01:29:08.480 --> 01:29:10.330
but essentially that shows that yeah

01:29:10.330 --> 01:29:14.237
if we expand the geographic
footprint of the percentile

01:29:14.237 --> 01:29:16.150
and above that we're considering

01:29:16.150 --> 01:29:20.100
the amount of risks that
we're capturing increases

01:29:20.100 --> 01:29:22.430
but there's a disproportionate impact

01:29:22.430 --> 01:29:24.973
to a customer's from a PSPS standpoint.

01:29:25.990 --> 01:29:28.570
And then as far as your
comments about the drought,

01:29:28.570 --> 01:29:33.570
yeah, it's very concerning to us

01:29:34.040 --> 01:29:36.810
and we're evaluating that closely.

01:29:36.810 --> 01:29:41.810
However, we do need a Diablo wind event

01:29:42.520 --> 01:29:44.880
or some sort of offshore wind pattern

01:29:44.880 --> 01:29:49.810
or dry winds coupled
with dry conditions,

01:29:49.810 --> 01:29:52.610
basically dry relative
humidity, dry fuels on the ground

01:29:53.550 --> 01:29:55.870
in order to consider PSPS.

01:29:55.870 --> 01:29:59.050
We're not going to be executing PSPS

01:29:59.050 --> 01:30:03.200
on the normal hot and dry
summer days in California

01:30:03.200 --> 01:30:06.253
where large fires are still possible.

01:30:07.280 --> 01:30:10.310
We're not going to be executing
PSPS to capture situations

01:30:10.310 --> 01:30:12.420
around the Butte fire, for example,

01:30:12.420 --> 01:30:15.330
around some of the other
ranch Mendocino type fires

01:30:15.330 --> 01:30:18.470
where they're predominantly,
you know, fuel driven

01:30:18.470 --> 01:30:20.730
they're not wind driven fires.

01:30:20.730 --> 01:30:24.620
And so I think, you know,
you gotta look at PSPS

01:30:24.620 --> 01:30:28.690
through the lens of, you know
we have these fire conditions

01:30:28.690 --> 01:30:29.720
that are out there,

01:30:29.720 --> 01:30:32.730
and then we have an
offshore wind event pattern

01:30:32.730 --> 01:30:34.880
that usually leads
to a red flag warning,

01:30:34.880 --> 01:30:36.000
high risk forecast

01:30:36.000 --> 01:30:38.197
from the Geographic
Area Coordination Center

01:30:38.197 --> 01:30:40.630
and like critical and extreme

01:30:40.630 --> 01:30:43.130
warnings from the
Storm Prediction Center.

01:30:43.130 --> 01:30:45.780
Whereas if we're in a drought situation

01:30:45.780 --> 01:30:50.780
the fuels and other things
are just more receptive

01:30:51.060 --> 01:30:52.590
to large fires in general.

01:30:52.590 --> 01:30:53.905
It's like the baseline.

01:30:53.905 --> 01:30:57.230
We're starting at a higher
baseline if you will, of danger

01:30:57.230 --> 01:31:01.110
but we need that wind
component in order to really

01:31:01.110 --> 01:31:02.947
to necessitate shutting off the power

01:31:02.947 --> 01:31:05.510
'cause that increases the probability

01:31:05.510 --> 01:31:06.960
that we would have an outage.

01:31:09.110 --> 01:31:11.010
So hopefully I answered your question.

01:31:12.480 --> 01:31:14.633
<v ->Well, to the extent,
yeah, thank you.</v>

01:31:14.633 --> 01:31:18.710
To the extent that you can
run more sensitivity analysis

01:31:18.710 --> 01:31:20.738
with all of the updated conditions

01:31:20.738 --> 01:31:23.050
and share them with us.

01:31:23.050 --> 01:31:24.050
That would be great.

01:31:27.610 --> 01:31:28.443
<v ->Yep. Yeah.</v>

01:31:28.443 --> 01:31:29.800
We'll take that as follow up.

01:31:33.180 --> 01:31:34.013
<v Joyce>This is Joyce.</v>

01:31:34.013 --> 01:31:37.080
I think we wanted to turn now.

01:31:37.080 --> 01:31:41.603
I think Sumeet had an update to share?

01:31:45.610 --> 01:31:47.390
<v Sumeet>No, Joyce I think we can</v>

01:31:47.390 --> 01:31:50.983
move on to the next
speaker on the agenda.

01:31:52.870 --> 01:31:54.820
<v Joyce>Oh, that,
wasn't what I meant</v>

01:31:54.820 --> 01:31:59.820
but we can turn now to
some of the staff questions

01:32:00.630 --> 01:32:02.678
unless there was anything
else that you needed

01:32:02.678 --> 01:32:05.830
to share at this point, Sumeet.

01:32:05.830 --> 01:32:08.263
So I was gonna turn it
over to Shelby Chaste.

01:32:11.410 --> 01:32:13.130
<v ->Thank you, Joyce.</v>

01:32:13.130 --> 01:32:15.560
Scott, this is probably
a question for you.

01:32:15.560 --> 01:32:17.400
In a court filing PG and E

01:32:17.400 --> 01:32:20.240
says that the outage
producing winds model

01:32:20.240 --> 01:32:25.240
was based on a sustained
wind speed of 20 miles per hour.

01:32:25.320 --> 01:32:29.110
What was the basis for PG
and E using 20 miles per hour

01:32:29.110 --> 01:32:31.310
as the input sustained wind speed

01:32:31.310 --> 01:32:35.113
when calculating the
tree overstrike percentile?

01:32:37.530 --> 01:32:40.250
<v ->Yeah, that's a great question.</v>

01:32:40.250 --> 01:32:43.830
And so, yes, our minimum,
I just wanna clarify

01:32:43.830 --> 01:32:48.720
that that's not related to our
outage producing wind model.

01:32:48.720 --> 01:32:51.600
It's more related to our
minimum fire potential conditions.

01:32:51.600 --> 01:32:53.780
Those conditions that would be needed

01:32:54.780 --> 01:32:56.850
in order to then consider

01:32:56.850 --> 01:32:59.720
the vegetation overstrike potential.

01:32:59.720 --> 01:33:01.820
And essentially the basis in that,

01:33:01.820 --> 01:33:06.530
is that we've seen historically
catastrophic fires occur

01:33:06.530 --> 01:33:08.820
at that level and
actually below that level.

01:33:08.820 --> 01:33:11.370
Some of the notable
incidents or incidents

01:33:13.040 --> 01:33:17.470
would be Zogg happened
with sustained wind speeds

01:33:17.470 --> 01:33:21.400
around 20 miles per hour
in that geographic area.

01:33:21.400 --> 01:33:23.810
If you look at some of the
weather stations around there,

01:33:23.810 --> 01:33:24.810
the sustained wind speeds

01:33:24.810 --> 01:33:28.000
were actually below 20 miles per hour

01:33:28.000 --> 01:33:29.850
but when you take into account

01:33:29.850 --> 01:33:32.100
high resolution numerical
weather prediction

01:33:32.100 --> 01:33:34.860
and look at the downslope component near

01:33:34.860 --> 01:33:37.923
where this fire happened,
it's closer to 20 miles per hour.

01:33:40.630 --> 01:33:43.890
Another example is the Camp Fire.

01:33:43.890 --> 01:33:45.812
Before the Camp Fire ignited,

01:33:45.812 --> 01:33:50.812
sustained wind speed at
the that Jarbo Gap rose,

01:33:51.740 --> 01:33:53.700
which is kind of a typically

01:33:53.700 --> 01:33:55.680
a notoriously windy weather station

01:33:55.680 --> 01:33:57.680
at the mouth of the Feather River Canyon

01:33:58.600 --> 01:34:02.135
had sustained wind speeds over 20.

01:34:02.135 --> 01:34:04.240
At one point, I think a couple
hours before the ignition

01:34:04.240 --> 01:34:06.130
they were about 30 miles per hour.

01:34:06.130 --> 01:34:08.616
At 6:13 on November 8th,

01:34:08.616 --> 01:34:11.645
the sustained wind speed
was 18 miles per hour

01:34:11.645 --> 01:34:13.810
when the Camp Fire ignited.

01:34:13.810 --> 01:34:16.760
And so, you know, based on looking at

01:34:16.760 --> 01:34:19.400
some of these historical incidents,

01:34:19.400 --> 01:34:21.550
we can have catastrophic fires occurring

01:34:21.550 --> 01:34:23.480
at those levels of wind speeds.

01:34:23.480 --> 01:34:25.930
So that's part of the basis.

01:34:25.930 --> 01:34:30.460
The other part of the
basis is outlined in detail

01:34:30.460 --> 01:34:31.970
in our wildfire mitigation plan.

01:34:31.970 --> 01:34:33.783
I think again, in Section 2.A

01:34:35.840 --> 01:34:39.360
when we look at what agency

01:34:39.360 --> 01:34:41.157
like the National Weather Service

01:34:41.157 --> 01:34:44.170
and the Geographic
Area Coordination Center

01:34:44.170 --> 01:34:45.920
as well as the Storm Prediction Center

01:34:45.920 --> 01:34:50.920
are using to justify their
warnings around red flag warnings

01:34:51.010 --> 01:34:54.040
and high risk of significant fires,

01:34:54.040 --> 01:34:56.060
that's the GAC determination

01:34:57.580 --> 01:35:00.900
or extreme and critical
fire weather warnings

01:35:00.900 --> 01:35:02.670
from the Storm Prediction Center.

01:35:02.670 --> 01:35:05.460
And when you look at all
that data basically congeals

01:35:05.460 --> 01:35:08.610
if everyone's got a
little bit different opinion

01:35:08.610 --> 01:35:11.160
but essentially the take
home message is that

01:35:11.160 --> 01:35:13.290
it's around 20 miles per hour sustained

01:35:13.290 --> 01:35:15.870
where you start to see
these warnings coming out

01:35:15.870 --> 01:35:19.310
from the federal agencies.

01:35:19.310 --> 01:35:21.193
The other components that,

01:35:21.193 --> 01:35:23.580
and the third kind of basis for that

01:35:23.580 --> 01:35:27.720
is looking at when we
start to see an uptick

01:35:27.720 --> 01:35:32.240
in outage activity on
the distribution network.

01:35:32.240 --> 01:35:34.860
And it occurs around that level,

01:35:34.860 --> 01:35:36.840
around that 20 mile per hour level

01:35:36.840 --> 01:35:39.230
when we start to get wind gusts.

01:35:39.230 --> 01:35:42.580
Well, we use sustained
because that's inherently

01:35:42.580 --> 01:35:44.843
what our weather model outputs.

01:35:46.060 --> 01:35:48.640
And so when we get around that level

01:35:48.640 --> 01:35:51.150
that's when we start to
see, we get on the curve

01:35:51.150 --> 01:35:54.270
of having unplanned outage activity.

01:35:54.270 --> 01:35:58.320
And it's, you know,
something that we need to take

01:35:58.320 --> 01:35:59.810
into consideration too,

01:35:59.810 --> 01:36:02.880
is that that curve of when to outages it

01:36:02.880 --> 01:36:06.690
is pretty steep because
when you think about it,

01:36:06.690 --> 01:36:10.830
the force that wind exerts on an object

01:36:10.830 --> 01:36:13.600
is proportional to the
square of the velocity

01:36:13.600 --> 01:36:17.010
meaning that it's not a linear
increase between the wind

01:36:17.010 --> 01:36:19.010
and the outage relationship.

01:36:19.010 --> 01:36:22.793
It's exponential,
essentially a quadratic.

01:36:24.010 --> 01:36:26.290
And we found that relationship.

01:36:26.290 --> 01:36:28.700
We've determined that
based on our historic look

01:36:28.700 --> 01:36:32.120
at wind speeds and outages.

01:36:32.120 --> 01:36:36.510
And so I hope those three
items give you some basis

01:36:36.510 --> 01:36:40.590
of why that's our minimum
fire potential conditions now.

01:36:40.590 --> 01:36:43.380
But as I stated we are evaluating

01:36:43.380 --> 01:36:45.670
those minimum fire potential conditions

01:36:45.670 --> 01:36:49.640
again, as part of our
continuous improvement journey

01:36:49.640 --> 01:36:50.723
and cadence that I mentioned

01:36:50.723 --> 01:36:54.120
that we do every year
to validate and justify

01:36:54.120 --> 01:36:55.670
any adjustments that we would make

01:36:55.670 --> 01:36:59.310
for operationalizing in 2021.

01:36:59.310 --> 01:37:01.463
So I hope I addressed your question.

01:37:03.580 --> 01:37:04.413
<v ->Yes. Thank you.</v>

01:37:04.413 --> 01:37:09.060
My second question is which
tools or enhancements, if any,

01:37:09.060 --> 01:37:12.010
are needed to existing
models for PG and E

01:37:12.010 --> 01:37:14.963
to implement the proposed
probation conditions?

01:37:19.720 --> 01:37:21.700
<v ->Yeah. So thinking about...</v>

01:37:21.700 --> 01:37:23.163
That's a great question.

01:37:24.293 --> 01:37:27.920
So, you know, it's one thing to consider

01:37:27.920 --> 01:37:32.280
the you know, how, or I
guess the methodology

01:37:32.280 --> 01:37:36.630
of how you would consider overstrike.

01:37:36.630 --> 01:37:39.730
One thing that, you know,
I always do is look at it

01:37:39.730 --> 01:37:40.860
from an operational lens.

01:37:40.860 --> 01:37:42.780
How would you actually
operationalize this?

01:37:42.780 --> 01:37:46.110
And I think we've got a very good path

01:37:46.110 --> 01:37:50.240
in order to operationalize this model.

01:37:50.240 --> 01:37:54.020
So I think there are some adjustments

01:37:54.020 --> 01:37:57.680
that my internal team
should we move forward

01:37:57.680 --> 01:37:58.700
with implementing this.

01:37:58.700 --> 01:38:01.610
If these proposed conditions
do become conditions

01:38:01.610 --> 01:38:03.554
we would have to consider

01:38:03.554 --> 01:38:08.250
this in our kind of modeling
framework, if you will.

01:38:08.250 --> 01:38:10.407
So to give you a
little bit of background,

01:38:10.407 --> 01:38:14.210
we are analyzing the weather and fuels

01:38:14.210 --> 01:38:18.270
on a two by two
kilometer basis every hour,

01:38:18.270 --> 01:38:19.300
going out for days.

01:38:19.300 --> 01:38:21.398
And we would simply
need to add in some logic

01:38:21.398 --> 01:38:22.970
that takes into account

01:38:22.970 --> 01:38:25.630
where we have that
70 percentile and above.

01:38:25.630 --> 01:38:27.940
And it's something that
my data science team

01:38:28.780 --> 01:38:31.270
is more than capable of
adding in and making sure

01:38:31.270 --> 01:38:33.083
that we do that in a quality way.

01:38:34.320 --> 01:38:39.320
The other, I think addition
is that we would need to do

01:38:39.560 --> 01:38:43.290
before July 1st, when
we're supposed to execute

01:38:43.290 --> 01:38:44.660
on these proposed conditions,

01:38:44.660 --> 01:38:47.420
is ensuring that we have visibility

01:38:47.420 --> 01:38:50.410
in real time of priority
one, priority two trees

01:38:50.410 --> 01:38:53.920
and we have good visibility
of making that a reality.

01:38:53.920 --> 01:38:56.850
And so I think those are
the two items that I would call

01:38:56.850 --> 01:38:58.250
out to answer your question.

01:39:00.141 --> 01:39:00.974
<v ->Great. Thank you.</v>

01:39:00.974 --> 01:39:04.603
I'll turn it over to Joyce
for other questions.

01:39:09.110 --> 01:39:11.520
<v ->Thank you, Shelby.</v>

01:39:11.520 --> 01:39:13.840
So as of this workshop stakeholders

01:39:13.840 --> 01:39:17.110
have been given multiple
different estimates as

01:39:17.110 --> 01:39:20.400
to what percentage additional PSPS

01:39:21.270 --> 01:39:24.500
these probation conditions might cause.

01:39:24.500 --> 01:39:26.460
Why has there been so much change

01:39:26.460 --> 01:39:29.783
and how is the predicted
figure determined?

01:39:33.072 --> 01:39:34.750
<v ->Yeah, that's a great question.</v>

01:39:34.750 --> 01:39:37.250
Yeah, I think what we've presented today

01:39:37.250 --> 01:39:40.510
is the best available
information we have.

01:39:40.510 --> 01:39:44.030
And I hope through, you
know the conversation

01:39:44.030 --> 01:39:46.768
that we've had today, you know,

01:39:46.768 --> 01:39:50.180
determining the potential
impact by looking at 10 years

01:39:50.180 --> 01:39:54.760
in the past using hourly
data is pretty complicated.

01:39:54.760 --> 01:39:56.840
It's actually very complicated

01:39:56.840 --> 01:39:59.540
and it takes a lot of data science

01:39:59.540 --> 01:40:03.740
and other things in
order to make it happen.

01:40:03.740 --> 01:40:05.890
And in some of the previous,

01:40:05.890 --> 01:40:10.200
I think the information
that was shared earlier

01:40:10.200 --> 01:40:12.550
the numbers might've
been a little bit different.

01:40:12.550 --> 01:40:16.110
We actually found a
data corruption issue

01:40:16.110 --> 01:40:19.840
on one day in January, 2014

01:40:19.840 --> 01:40:23.410
that was disrupting the
inclusion of a couple of events

01:40:23.410 --> 01:40:26.190
and we've since identified
and fixed that issue.

01:40:26.190 --> 01:40:28.030
But that's just some of the things

01:40:28.030 --> 01:40:31.120
when we're working under
very short timelines can happen.

01:40:31.120 --> 01:40:34.080
But we did do believe
now we've corrected

01:40:34.080 --> 01:40:37.270
all of those issues and the information

01:40:37.270 --> 01:40:39.750
that you have in front of you today

01:40:39.750 --> 01:40:43.120
is the best information and
the most accurate information

01:40:43.120 --> 01:40:43.953
we have to date.

01:40:43.953 --> 01:40:46.250
So I would utilize the materials

01:40:46.250 --> 01:40:50.430
that we're reviewing
today as forming the basis

01:40:50.430 --> 01:40:52.830
of your conclusion of
these proposed conditions.

01:40:56.070 --> 01:40:58.560
<v ->Thank you for
that clarification.</v>

01:40:58.560 --> 01:40:59.483
We appreciate it.

01:41:00.460 --> 01:41:04.240
I know you've touched briefly
when you were discussing

01:41:04.240 --> 01:41:09.240
with Shelby about
changing the wind speed.

01:41:09.330 --> 01:41:13.420
So Probation Condition
12 says windstorm.

01:41:13.420 --> 01:41:17.090
So how is PG and E
understanding the applicability

01:41:17.090 --> 01:41:20.550
of that term and is it to be measured

01:41:20.550 --> 01:41:22.230
by sustained wind speed?

01:41:22.230 --> 01:41:23.590
Is it wind gust?

01:41:23.590 --> 01:41:25.990
Is it a wind pressure?

01:41:25.990 --> 01:41:28.490
Can you just articulate a little more

01:41:28.490 --> 01:41:32.460
on this particular issue
regarding how PG and E

01:41:32.460 --> 01:41:36.110
is understanding what
the probation conditions

01:41:36.110 --> 01:41:37.563
call a wind storm?

01:41:38.955 --> 01:41:42.540
<v ->Sure. Yeah. Excellent question.</v>

01:41:42.540 --> 01:41:45.020
And upon reading the language windstorm

01:41:45.020 --> 01:41:49.193
to me as a meteorologist
is a bit nebulous.

01:41:50.760 --> 01:41:53.640
However, we know that
the spirit of this intent

01:41:53.640 --> 01:41:57.750
of the proposed conditions
is not to shut off the power

01:41:57.750 --> 01:42:00.980
during winter wind storms.

01:42:00.980 --> 01:42:05.420
And so, you know, we
believe that this is indicative

01:42:05.420 --> 01:42:09.470
of a dry off shore or dry windstorm

01:42:09.470 --> 01:42:12.520
where typically a red flag warning

01:42:12.520 --> 01:42:16.150
or other high risk indications
from external sources

01:42:16.150 --> 01:42:19.690
and federal agencies
would be present for.

01:42:19.690 --> 01:42:23.840
And, you know, going back to the answer

01:42:23.840 --> 01:42:26.710
around justifying the 20 mile per hour

01:42:26.710 --> 01:42:29.650
sustained minimum fire
potential condition wind speed,

01:42:29.650 --> 01:42:32.070
some of that same
logic applies to, you know

01:42:32.070 --> 01:42:35.910
those are the conditions
that we would typically

01:42:35.910 --> 01:42:38.123
see when there's a
red flag warning issued.

01:42:54.610 --> 01:42:55.770
<v ->Thank you.</v>

01:42:55.770 --> 01:42:59.260
<v ->Yeah, and I realized
I didn't address, sorry</v>

01:42:59.260 --> 01:43:01.940
the wind gusts portion of your comment

01:43:03.870 --> 01:43:07.570
and maybe this is more for a
future kind of parking lot item

01:43:07.570 --> 01:43:12.570
but the reason that we are
utilizing wind speed right now

01:43:12.680 --> 01:43:14.930
is that that is directly output

01:43:14.930 --> 01:43:17.249
from our numerical
weather prediction model.

01:43:17.249 --> 01:43:22.249
We also evaluate wind gusts
too and we continue to do so.

01:43:22.660 --> 01:43:25.770
In fact, in our 2021
wildfire mitigation plan

01:43:25.770 --> 01:43:29.710
you could read, I think
it's in Section 7.3.2

01:43:32.320 --> 01:43:35.060
and another sub bullet,
another sub number

01:43:35.060 --> 01:43:38.100
about some of the
improvements that we're executing

01:43:38.100 --> 01:43:39.490
in that space this year

01:43:39.490 --> 01:43:41.220
which I'm very excited about.

01:43:41.220 --> 01:43:44.880
A couple of those is
developing machine learning

01:43:44.880 --> 01:43:48.588
wind gust models that take the output

01:43:48.588 --> 01:43:53.380
from our high resolution
weather prediction model

01:43:53.380 --> 01:43:56.240
that is outputting
generally a sustained wind

01:43:56.240 --> 01:44:00.030
and translating it into a
wind gust for weather stations

01:44:01.140 --> 01:44:04.610
and doing it in a way that
takes into account, you know,

01:44:04.610 --> 01:44:06.677
upper level winds of the atmosphere,

01:44:06.677 --> 01:44:09.810
the terrain that that
weather station is around

01:44:09.810 --> 01:44:12.060
and other components
that are kind of feeding

01:44:12.060 --> 01:44:13.490
into the machine learning model.

01:44:13.490 --> 01:44:18.490
And so we're making some large strides

01:44:19.110 --> 01:44:20.580
I believe this year in translating

01:44:20.580 --> 01:44:23.350
from when sustained
wind speeds or wind gusts

01:44:23.350 --> 01:44:28.037
and whatever we feel
more confident in forecasting,

01:44:28.037 --> 01:44:30.900
that's what we'll use to form the basis

01:44:30.900 --> 01:44:32.950
of our minimum fire
potential conditions.

01:44:34.000 --> 01:44:36.410
So I hope that addresses the wind gusts

01:44:36.410 --> 01:44:38.260
versus sustained wind speed question.

01:44:40.720 --> 01:44:41.553
<v ->Oh yes. Thank you.</v>

01:44:41.553 --> 01:44:42.920
I think it does, Scott.

01:44:42.920 --> 01:44:45.290
Thanks for elaborating on that.

01:44:45.290 --> 01:44:50.290
So what is the impact of
using 2019 or 2020 LiDAR data

01:44:50.680 --> 01:44:54.070
and what are PG and E plans
for the future use of LiDAR

01:44:54.070 --> 01:44:57.523
and it's vegetation management programs?

01:45:00.350 --> 01:45:04.250
<v ->Great. Yeah, that one's a
little outside my swim lane.</v>

01:45:04.250 --> 01:45:07.260
Sumeet, do you mind taking that one?

01:45:07.260 --> 01:45:09.000
<v ->Yup. I was gonna
jump right in, man.</v>

01:45:09.000 --> 01:45:11.280
So, thank you Joyce for that question.

01:45:11.280 --> 01:45:15.160
So we have a different
frequency between transmission

01:45:15.160 --> 01:45:17.760
and distribution so as part
of our transmission vegetation

01:45:17.760 --> 01:45:20.120
management program, Joyce,

01:45:20.120 --> 01:45:23.350
we are capturing LiDAR information

01:45:23.350 --> 01:45:26.570
on a much much more
frequent cadence every year

01:45:26.570 --> 01:45:28.510
or once every two years.

01:45:28.510 --> 01:45:30.940
And we use the strike potential trees

01:45:30.940 --> 01:45:33.910
that are identified coming
out of LiDAR on the trends

01:45:35.150 --> 01:45:38.620
as the mechanism by
which we evaluate the health

01:45:38.620 --> 01:45:40.400
of all of those strike potential trees

01:45:40.400 --> 01:45:43.930
but the density of
strike potential trees

01:45:43.930 --> 01:45:47.410
between our distribution
is much different

01:45:48.285 --> 01:45:49.740
than transmission.

01:45:49.740 --> 01:45:51.310
So when we look at transmission

01:45:52.200 --> 01:45:54.450
we have 500 hundred
miles roughly of overhang

01:45:55.517 --> 01:45:57.350
by far throughout districts

01:45:57.350 --> 01:46:01.647
and we have about 365,000
strike potential trees, right?

01:46:01.647 --> 01:46:04.010
So you do that quick
math, if the density

01:46:04.010 --> 01:46:08.290
of about 65 to 66 trees
on average per mile.

01:46:08.290 --> 01:46:12.530
When you look at the
distribution LiDAR data,

01:46:12.530 --> 01:46:17.530
25,500, 5.3 million you do that math

01:46:17.540 --> 01:46:22.540
it's more than 205
to 207 trees for miles

01:46:22.870 --> 01:46:26.963
three on distribution as
opposed to transmission.

01:46:26.963 --> 01:46:29.500
So our intent on transmission
is to continue to use LiDAR

01:46:29.500 --> 01:46:32.290
on a much more frequent
cadence for distribution.

01:46:32.290 --> 01:46:35.830
The first time we ever
captured that data was in 2019

01:46:35.830 --> 01:46:37.730
and it took quite a bit of time

01:46:37.730 --> 01:46:41.220
to analyze all of that LiDAR data

01:46:41.220 --> 01:46:43.286
because it's not a quick analysis

01:46:43.286 --> 01:46:45.750
especially when we
talk about that scale.

01:46:45.750 --> 01:46:48.877
So that data became
available middle of 2020

01:46:48.877 --> 01:46:51.200
and we anticipate to establish

01:46:51.200 --> 01:46:54.530
what the right frequency
is going forward

01:46:54.530 --> 01:46:57.840
because part of this is that
we still have a lot of areas

01:46:57.840 --> 01:47:00.250
with tree canopy and as we remove

01:47:00.250 --> 01:47:01.940
that overhang and tree canopy and have

01:47:01.940 --> 01:47:04.360
the enhanced vegetation
management program,

01:47:04.360 --> 01:47:08.640
the intent is for us to
evolve our distribution

01:47:08.640 --> 01:47:10.540
vegetation management program,

01:47:10.540 --> 01:47:12.850
to look a lot more like transition.

01:47:12.850 --> 01:47:13.940
We're just not there yet.

01:47:13.940 --> 01:47:17.754
So our intent would be to capture LIDAR.

01:47:17.754 --> 01:47:19.310
We don't have plans to do that in 2021.

01:47:19.310 --> 01:47:22.530
We think the data that
we have is pretty robust

01:47:22.530 --> 01:47:25.300
based on what we captured
and then going into 2022

01:47:25.300 --> 01:47:27.140
and beyond we will set
that established frequency

01:47:27.140 --> 01:47:28.427
for distribution.

01:47:34.013 --> 01:47:34.846
That help?

01:47:37.200 --> 01:47:38.033
<v ->That helped a lot.</v>

01:47:38.033 --> 01:47:39.019
Thank you.

01:47:39.019 --> 01:47:40.060
<v ->Most welcome.</v>

01:47:40.060 --> 01:47:42.600
<v ->I think it's already in
some of your materials</v>

01:47:42.600 --> 01:47:47.600
where you discuss the accuracy
of the LiDAR measurements.

01:47:48.530 --> 01:47:53.530
I think it mentioned that
you not only use LiDAR

01:47:54.110 --> 01:47:57.080
but you did a certain
amount of field verification

01:47:57.080 --> 01:47:58.620
on the accuracy of LiDAR.

01:47:58.620 --> 01:48:00.573
Can you just speak to that briefly?

01:48:02.710 --> 01:48:06.288
<v ->Yeah Joyce, so when
you look at the accuracy</v>

01:48:06.288 --> 01:48:11.288
of the aerial LiDAR, it's one
of the best available methods

01:48:13.730 --> 01:48:16.010
that are available commercially

01:48:16.010 --> 01:48:19.393
to be able to leverage
this data set up scale.

01:48:20.300 --> 01:48:23.960
You know, we've also
looked at additional technology

01:48:23.960 --> 01:48:25.670
through satellite

01:48:25.670 --> 01:48:27.890
and there's been
several different entities

01:48:27.890 --> 01:48:30.316
that have approached
us in that capacity.

01:48:30.316 --> 01:48:31.930
We're open to those discussions

01:48:31.930 --> 01:48:36.447
but we have not yet quite
seen the same level of accuracy.

01:48:36.447 --> 01:48:39.440
You know, the one thing
that we have identified

01:48:39.440 --> 01:48:44.180
is as we go out and have
our professional arborists

01:48:44.180 --> 01:48:46.440
that put boots on the ground

01:48:46.440 --> 01:48:49.540
as part of our enhanced
vegetation management program,

01:48:49.540 --> 01:48:53.589
where they're identifying
the strike potential trees

01:48:53.589 --> 01:48:58.589
on a overall aggregate
basis for the 4,300 miles.

01:48:58.910 --> 01:49:01.390
And we've looked at a
subset of that dataset,

01:49:01.390 --> 01:49:04.795
roughly 1500 to 1800 miles.

01:49:04.795 --> 01:49:08.590
You know, we have
identified that the aerial LiDAR

01:49:08.590 --> 01:49:13.000
is in certain cases has
underestimated the number of trees

01:49:13.000 --> 01:49:16.120
and that happens in one of the slides

01:49:16.120 --> 01:49:19.130
that I was discussing previously.

01:49:19.130 --> 01:49:23.660
I think it was slide nine, I believe,

01:49:23.660 --> 01:49:25.859
which shows the canopy and the challenge

01:49:25.859 --> 01:49:28.395
of the canopy is the LiDAR
doesn't have the ability

01:49:28.395 --> 01:49:31.210
to be able to see the tree trunk

01:49:31.210 --> 01:49:33.320
and capture that data point.

01:49:33.320 --> 01:49:36.550
So there's a over and under estimation

01:49:36.550 --> 01:49:39.330
and that occurs as a result of that.

01:49:39.330 --> 01:49:43.450
So we have found in
some parts of the circuit

01:49:43.450 --> 01:49:46.970
where the aerial LiDAR
could have underestimated

01:49:46.970 --> 01:49:50.393
the strike potential trees by 15 to 20%.

01:49:51.760 --> 01:49:54.300
But on a relative basis when you look at

01:49:54.300 --> 01:49:58.090
the overall aggregate 25,500

01:49:58.090 --> 01:50:02.470
it's a fairly good data set to compare

01:50:02.470 --> 01:50:06.280
which circuit has a
higher density of trees

01:50:06.280 --> 01:50:07.940
versus those that have
the medium density

01:50:07.940 --> 01:50:09.030
versus a lower density.

01:50:09.030 --> 01:50:11.145
So it's a very effective means

01:50:11.145 --> 01:50:14.330
to be able to do a relative comparison.

01:50:14.330 --> 01:50:17.028
When you do an absolute comparison

01:50:17.028 --> 01:50:19.005
that's where there's
additional opportunities

01:50:19.005 --> 01:50:21.833
to further improve on that dataset.

01:50:24.990 --> 01:50:25.823
I apologize.

01:50:25.823 --> 01:50:28.550
That slide was slide nine on my version

01:50:28.550 --> 01:50:33.550
but I think if you go three
more, four more slides forward

01:50:34.583 --> 01:50:36.560
that's the slide I was talking about.

01:50:36.560 --> 01:50:37.713
I'm sorry about that.

01:50:39.440 --> 01:50:40.273
One more.

01:50:42.473 --> 01:50:43.306
That's it.

01:50:49.440 --> 01:50:51.390
<v ->Did you have a
question Commissioner?</v>

01:50:53.870 --> 01:50:55.740
<v ->I did. I wanted to make
sure that you finished</v>

01:50:55.740 --> 01:50:57.340
your line of questioning though.

01:51:02.420 --> 01:51:04.380
<v ->The only remaining
question I had</v>

01:51:09.016 --> 01:51:12.570
was about residual
tree overstrike exposure.

01:51:12.570 --> 01:51:15.610
So on slide 30, which is in the appendix

01:51:17.850 --> 01:51:19.320
it would help to have more clarity

01:51:19.320 --> 01:51:22.323
on what overstrike
means in this context.

01:51:23.250 --> 01:51:28.250
And maybe just describe
how the residual risk is defined.

01:51:30.890 --> 01:51:35.440
I think as stakeholders read that

01:51:38.840 --> 01:51:40.840
the 10% can mean different things.

01:51:40.840 --> 01:51:44.520
Is it 10% risk of an overstrike outage

01:51:44.520 --> 01:51:47.520
or 10% risk of an
overstrike cause wildfire

01:51:47.520 --> 01:51:50.033
maybe just give us
some context on that slide.

01:51:53.670 --> 01:51:54.767
<v ->Sure. Yes, Scott.</v>

01:51:54.767 --> 01:51:55.880
And this is Scott.

01:51:55.880 --> 01:51:57.300
Yeah, I can address this.

01:51:57.300 --> 01:52:00.330
So, you know, one of the
things that we wanted to do

01:52:00.330 --> 01:52:05.330
when looking at overstrike
is, you know, determine,

01:52:05.790 --> 01:52:08.654
you know, one thing is
looking at the increase

01:52:08.654 --> 01:52:11.480
in potential impact to customers.

01:52:11.480 --> 01:52:15.660
And that's what the orange
line represents when we move

01:52:15.660 --> 01:52:19.620
from the 2020 10 year baseline

01:52:19.620 --> 01:52:23.680
which is on the far left
portion of the chart to looking

01:52:23.680 --> 01:52:28.480
at considering all the
way to the 50th percentile

01:52:31.180 --> 01:52:35.960
above tree overstrike risk
and what that would mean

01:52:35.960 --> 01:52:40.513
in terms of increase in customer
hours relative to baseline.

01:52:41.680 --> 01:52:44.800
And so I'll explain
the orange line first

01:52:44.800 --> 01:52:48.070
and I'll come back to the
blue line which is your question.

01:52:48.070 --> 01:52:50.030
But the orange line,
essentially, when you get

01:52:50.030 --> 01:52:53.000
to the 50th percentile,
we're almost doubling

01:52:53.000 --> 01:52:58.000
the customer, our dimension
of public safety power shutoff.

01:52:59.670 --> 01:53:02.840
This is just a one dimension of of PSPS

01:53:02.840 --> 01:53:04.573
and there's many to digest here.

01:53:06.040 --> 01:53:08.870
However, you know,
we want to also look at

01:53:08.870 --> 01:53:13.230
how much risk reduction that
we're gaining by doing that.

01:53:13.230 --> 01:53:16.770
And one way is by evaluating

01:53:16.770 --> 01:53:18.880
the amount of outage
activity that's occurring

01:53:18.880 --> 01:53:20.960
in that geographic footprint

01:53:20.960 --> 01:53:24.373
that's represented by the percentile.

01:53:26.670 --> 01:53:29.950
And in order to calculate this,

01:53:29.950 --> 01:53:34.950
is essentially we're
looking at the number of,

01:53:35.940 --> 01:53:39.350
going back over the 10 year period,

01:53:39.350 --> 01:53:42.730
the number of vegetation caused outages

01:53:42.730 --> 01:53:47.530
within that geographic
footprint that's representative

01:53:47.530 --> 01:53:50.310
of that percentile and above value.

01:53:50.310 --> 01:53:53.020
So for example, our baseline model

01:53:53.020 --> 01:53:55.250
we believe that didn't take

01:53:55.250 --> 01:53:57.070
into account vegetation directly

01:53:57.070 --> 01:53:59.160
but considered outage producing wind

01:53:59.160 --> 01:54:00.713
and fire potential index.

01:54:01.940 --> 01:54:05.820
Essentially 70% of vegetation
cause outages are happening

01:54:05.820 --> 01:54:07.590
within that geographic footprint

01:54:07.590 --> 01:54:10.823
that's covered by the model.

01:54:11.820 --> 01:54:13.003
The inverse of that is that

01:54:13.003 --> 01:54:16.610
there's 30% of vegetation caused outages

01:54:16.610 --> 01:54:18.702
that are happening outside
of that geographic footprint

01:54:18.702 --> 01:54:23.702
which we call the residual
tree overstrike risk here.

01:54:25.190 --> 01:54:29.710
And so this is one
way to try to estimate

01:54:31.730 --> 01:54:35.510
you know, with PSPS, how
much risk reduction we're seeing.

01:54:35.510 --> 01:54:38.380
There's multiple other
ways to calculate this

01:54:38.380 --> 01:54:41.610
but this is one way
that we've looked at it.

01:54:41.610 --> 01:54:43.865
And so when we start
to go down the chart,

01:54:43.865 --> 01:54:47.660
essentially, you know, all
the way down to 50th percent

01:54:47.660 --> 01:54:51.920
because we're expanding
the geographic area, if you will

01:54:54.200 --> 01:54:56.400
overstrike we're essentially
capturing more risks,

01:54:56.400 --> 01:54:59.770
we're capturing a larger geographic area

01:54:59.770 --> 01:55:02.843
where vegetation outages are happening.

01:55:04.080 --> 01:55:09.080
And only 3% of outages
vegetation related

01:55:10.410 --> 01:55:15.410
are not happening in
the bottom 50th percentile

01:55:15.880 --> 01:55:20.880
of geographic area or
geographic overstrike risk

01:55:20.910 --> 01:55:24.940
where the majority 97% of
vegetation cause outages

01:55:24.940 --> 01:55:27.740
are happening in the
top 50th percentile.

01:55:27.740 --> 01:55:30.680
And so that's what the 10
percentile essentially means

01:55:30.680 --> 01:55:34.922
if we hone in on 70,
that's what the 10 means

01:55:34.922 --> 01:55:37.670
is then we hone in
on the 70th percentile

01:55:37.670 --> 01:55:41.873
that 70 percentile and
above geographic area.

01:55:42.800 --> 01:55:46.280
And that again is hopefully more simply

01:55:47.660 --> 01:55:49.340
that's the area where we have more trees

01:55:49.340 --> 01:55:51.530
that can strike our lines.

01:55:51.530 --> 01:55:56.530
90% of vegetation caused
outages are occurring

01:55:56.830 --> 01:55:59.700
within the 70th percentile and above,

01:55:59.700 --> 01:56:02.350
meaning that there's a 10%

01:56:05.600 --> 01:56:08.020
that is not going to
be captured directly

01:56:08.020 --> 01:56:10.453
by the current framework.

01:56:12.320 --> 01:56:16.940
And so hopefully with my
explanation of percentiles

01:56:16.940 --> 01:56:18.960
and other things I
didn't muddy the waters

01:56:18.960 --> 01:56:20.070
but hopefully that gives you a sense

01:56:20.070 --> 01:56:22.223
of how it was calculated.

01:56:24.680 --> 01:56:25.910
<v Joyce>Thank you for
walking through that.</v>

01:56:25.910 --> 01:56:27.050
Appreciate it.

01:56:27.050 --> 01:56:28.400
Commissioner Rechtschaffen.

01:56:30.673 --> 01:56:34.630
<v ->I had a question which
may be review or clarification</v>

01:56:34.630 --> 01:56:36.690
or maybe I just don't
understand it exactly

01:56:36.690 --> 01:56:38.747
but I wanted to go back Scott

01:56:38.747 --> 01:56:43.747
and Sumeet commented about
this slide 17 or 17 in my deck,

01:56:45.190 --> 01:56:49.510
which is implementation
of the proposed PSPS 21

01:56:51.840 --> 01:56:53.423
decision-making process.

01:56:54.390 --> 01:56:58.070
And I just wanna drill
down on the new box,

01:56:58.070 --> 01:57:01.910
which is an or as opposed to put aside

01:57:01.910 --> 01:57:03.810
the black foreign conditions

01:57:03.810 --> 01:57:05.930
your current practices you calculate

01:57:05.930 --> 01:57:09.140
this distribution
large fire probability.

01:57:09.140 --> 01:57:11.260
And that encompasses a number of factors

01:57:11.260 --> 01:57:15.140
that go beyond an area
meeting a minimum fire potential,

01:57:15.140 --> 01:57:16.020
that's the baseline

01:57:16.020 --> 01:57:17.460
but then you look at the probability

01:57:17.460 --> 01:57:22.460
of whether fuels land
use types and wind speed

01:57:24.800 --> 01:57:26.330
and that's the first box.

01:57:26.330 --> 01:57:28.535
And then the fourth box is in the or

01:57:28.535 --> 01:57:32.730
the box in the blue
at the bottom is in or,

01:57:32.730 --> 01:57:36.380
the question I have and
Sumeet touched on this a little bit

01:57:36.380 --> 01:57:39.710
is to what extent are
those other risk factors

01:57:39.710 --> 01:57:44.637
being used in combination
with the overstrike criteria

01:57:47.330 --> 01:57:49.330
to inform the PSPS.

01:57:49.330 --> 01:57:53.990
As I heard Sumeet talk about
the narrowing the universe

01:57:53.990 --> 01:57:57.910
of the 5.3 million trees
with overstrike capability

01:57:57.910 --> 01:58:00.050
on the distribution network

01:58:00.050 --> 01:58:04.360
but I'm not quite sure how
these other risk factors merged

01:58:04.360 --> 01:58:09.360
with the overstrike
considerations in box four.

01:58:10.760 --> 01:58:13.262
So may I apologize
if this is already been

01:58:13.262 --> 01:58:15.197
sort of gone over this already

01:58:15.197 --> 01:58:17.447
but maybe you could
walk us through it again.

01:58:18.870 --> 01:58:20.430
<v Scott>Yeah, absolutely.</v>

01:58:20.430 --> 01:58:23.030
And I think it would
actually add a lot of value

01:58:23.030 --> 01:58:25.850
to walk through this again.

01:58:25.850 --> 01:58:30.220
And yeah, so essentially I
think you're thinking about

01:58:30.220 --> 01:58:34.100
the operator, the OR
operator exactly right.

01:58:34.100 --> 01:58:38.460
It's after minimum fire
potential conditions are met,

01:58:38.460 --> 01:58:41.486
it's either one of these
things that can bring

01:58:41.486 --> 01:58:44.083
a distribution line into scope.

01:58:45.790 --> 01:58:49.670
The core model, the thing
that's going to bring most lines

01:58:49.670 --> 01:58:51.330
into scope will continue

01:58:51.330 --> 01:58:55.460
to be our large fire probability
model for distribution.

01:58:55.460 --> 01:58:57.700
And we use a value of six

01:58:57.700 --> 01:59:01.080
and that is the fire potential
index multiplied by OBW.

01:59:01.080 --> 01:59:03.395
And so if we have any
values and forecasts

01:59:03.395 --> 01:59:06.733
that are greater than a value of six

01:59:06.733 --> 01:59:08.810
then those lines are gonna
be considered a scope,

01:59:08.810 --> 01:59:11.660
we're gonna start
communication with customers.

01:59:11.660 --> 01:59:14.600
Or we look at distribution Black Swan.

01:59:14.600 --> 01:59:19.600
And so that's not dependent
on meeting or not meeting

01:59:20.370 --> 01:59:22.437
the box two.

01:59:22.437 --> 01:59:25.380
So if we're meeting
distribution Black Swan only

01:59:25.380 --> 01:59:28.780
then that would be considered in scope

01:59:28.780 --> 01:59:31.443
or if we're meeting direct vegetation

01:59:31.443 --> 01:59:33.380
then that would be considered.

01:59:33.380 --> 01:59:37.080
And you'll see that there's
or's inside of that box too

01:59:37.080 --> 01:59:39.410
where if we're meeting

01:59:39.410 --> 01:59:42.010
the minimum fire
potential conditions only

01:59:43.610 --> 01:59:47.470
and let's say only direct
vegetation consideration

01:59:47.470 --> 01:59:49.950
we would have to consider
what's actually driving it

01:59:49.950 --> 01:59:52.700
is it the 70th percentile and above,

01:59:52.700 --> 01:59:55.640
the priority one or the priority two.

01:59:55.640 --> 01:59:57.763
So either one of those things,

01:59:59.250 --> 02:00:01.830
either one of those three things

02:00:01.830 --> 02:00:05.100
is the proposed 2021 criteria.

02:00:05.100 --> 02:00:08.230
And it's activated, it's
flipped on, if you will

02:00:08.230 --> 02:00:11.510
if minimum fire potential
conditions are met

02:00:11.510 --> 02:00:14.210
regardless of what's happening

02:00:14.210 --> 02:00:17.973
in the other two boxes
box two and box three.

02:00:19.510 --> 02:00:23.970
Now, one of the other things
that we're doing this year

02:00:23.970 --> 02:00:27.243
that we can and
to Sumeet's point,

02:00:28.540 --> 02:00:33.540
we can identify those
areas that are being identified

02:00:33.920 --> 02:00:37.280
for in scope or PSPS
under this methodology

02:00:37.280 --> 02:00:39.261
that are only being pulled in,

02:00:39.261 --> 02:00:40.920
basically identified for scope

02:00:40.920 --> 02:00:43.880
for priority one and priority two trees.

02:00:43.880 --> 02:00:47.070
And we can prioritize
those such that we can

02:00:47.070 --> 02:00:49.220
send vegetation crews out

02:00:49.220 --> 02:00:53.660
before the PSPS event
arrives to mitigate those trees

02:00:53.660 --> 02:00:57.810
such that we can keep
those lines hopefully energized

02:00:57.810 --> 02:01:01.210
during a PSPS event
that would only be meeting

02:01:01.210 --> 02:01:04.453
that priority one and
priority two classification

02:01:04.453 --> 02:01:05.833
or threshold.

02:01:07.880 --> 02:01:11.857
And I'll stop there and
see how I did my answer.

02:01:15.782 --> 02:01:17.536
<v ->Okay, thank
you. That's helpful.</v>

02:01:17.536 --> 02:01:21.700
You obviously can't
mitigate all the potential

02:01:21.700 --> 02:01:25.077
over the trees with
potential overstride capacity

02:01:25.077 --> 02:01:28.740
given the volume of those
in the same way you can do

02:01:28.740 --> 02:01:30.883
with priority one and priority two.

02:01:31.750 --> 02:01:34.280
So there's a large universe of trees

02:01:34.280 --> 02:01:37.020
that could trigger this other category.

02:01:37.020 --> 02:01:42.020
And if I'm just reducing
this to an oversimplification,

02:01:42.643 --> 02:01:47.643
it's a much cruder criteria
than your highly sophisticated

02:01:47.850 --> 02:01:51.470
large distribution fire
profitability methodology

02:01:51.470 --> 02:01:54.860
which relies on tasks, climate
events and machine learning.

02:01:54.860 --> 02:01:58.370
And this does to some
extent to get you into the door

02:01:58.370 --> 02:02:00.525
but then once you
add a minimum criteria,

02:02:00.525 --> 02:02:05.525
it's a much more simplistic trigger.

02:02:05.810 --> 02:02:08.003
Is that a fair way of thinking about it?

02:02:09.320 --> 02:02:12.410
<v ->Yeah, I would say
it's a simpler way to...</v>

02:02:13.540 --> 02:02:15.130
Yeah, it's more simple

02:02:15.130 --> 02:02:18.330
than our large fire probability model.

02:02:18.330 --> 02:02:19.300
That is correct.

02:02:19.300 --> 02:02:21.425
And just to put in
context, the 70 percentile

02:02:21.425 --> 02:02:24.650
and the comment around the volume

02:02:25.730 --> 02:02:27.670
I can't remember if I mentioned this

02:02:27.670 --> 02:02:28.940
or if Sumeet mentioned it or not

02:02:28.940 --> 02:02:31.580
but at the 70th
percentile of overstrike,

02:02:32.710 --> 02:02:35.130
the number, the absolute
number of overstrike

02:02:35.130 --> 02:02:39.980
that's calculated at the 70th
percentile is up 10,000 feet

02:02:39.980 --> 02:02:41.610
of overstrike,

02:02:41.610 --> 02:02:46.610
which is a little under
two miles of tree length

02:02:47.910 --> 02:02:49.770
that can strike our line, essentially.

02:02:49.770 --> 02:02:54.770
So yes, the number
is still quite staggering

02:02:54.940 --> 02:02:59.348
and I don't think it's...

02:02:59.348 --> 02:03:01.600
Well, maybe I'll leave it there

02:03:03.020 --> 02:03:05.910
<v ->If I just add onto that
Scott and Commissioner</v>

02:03:05.910 --> 02:03:07.760
you're thinking about
the right way, right?

02:03:07.760 --> 02:03:12.200
Which is step one is the
minimum gating criteria, right?

02:03:12.200 --> 02:03:14.670
Those conditions have to exist

02:03:14.670 --> 02:03:19.550
to get to box two, three or four.

02:03:19.550 --> 02:03:23.480
So once those minimum
conditions are met, as it starts

02:03:23.480 --> 02:03:28.290
you know, that Scott articulated
the overstrike potential,

02:03:28.290 --> 02:03:31.680
I mean, think about that
as if a tree is tall enough

02:03:31.680 --> 02:03:33.160
but not far enough

02:03:33.160 --> 02:03:38.160
and just by the sheer
fact that that tree exists

02:03:39.650 --> 02:03:41.150
poses a potential risk.

02:03:41.150 --> 02:03:42.280
So you're absolutely right.

02:03:42.280 --> 02:03:45.980
It is kind of more of
that bright line approach.

02:03:45.980 --> 02:03:49.160
Now, the next place for us to evolve to

02:03:49.160 --> 02:03:51.270
and this is a comment I was making about

02:03:51.270 --> 02:03:53.940
the use of LiDAR for distribution,

02:03:53.940 --> 02:03:56.160
for example, on transmission

02:03:56.160 --> 02:03:58.890
we also take that a step further

02:03:58.890 --> 02:04:00.430
for the strike potential tree

02:04:00.430 --> 02:04:05.430
and start to evaluate what's
the slope, how steep is it?

02:04:07.522 --> 02:04:11.670
Is the tree up slope or down
slope of the transmission line?

02:04:11.670 --> 02:04:12.770
What's the proximity?

02:04:12.770 --> 02:04:16.550
And what's the path
of the line of the tree?

02:04:16.550 --> 02:04:18.230
Does it have any
other trees in front of it,

02:04:18.230 --> 02:04:20.430
something called the front row factor.

02:04:20.430 --> 02:04:23.180
So we can take the
sheer existence of the tree

02:04:23.180 --> 02:04:25.360
and then add additional
factors to determine

02:04:25.360 --> 02:04:27.950
the probability of failure.

02:04:27.950 --> 02:04:29.920
And that's what gets
it to that next level

02:04:29.920 --> 02:04:31.740
of sophistication.

02:04:31.740 --> 02:04:33.215
We have that in transmission,

02:04:33.215 --> 02:04:35.400
we're not there yet for distribution

02:04:35.400 --> 02:04:36.310
and the reason we're not there

02:04:36.310 --> 02:04:38.097
is because of the
sheer volume of the data

02:04:38.097 --> 02:04:40.390
that's being captured

02:04:40.390 --> 02:04:45.180
and the tree canopy,
the overhang that exists

02:04:45.180 --> 02:04:46.770
are things that have to be addressed,

02:04:46.770 --> 02:04:48.900
which is why we're
addressing them proactively

02:04:48.900 --> 02:04:52.440
as part of our enhanced
vegetation management program

02:04:52.440 --> 02:04:55.170
that goes beyond the
regulatory requirements

02:04:55.170 --> 02:04:56.650
to be able to do exactly that.

02:04:56.650 --> 02:04:58.750
So we can get to that place Commissioner

02:04:58.750 --> 02:04:59.710
that you're articulating.

02:04:59.710 --> 02:05:02.742
So we go from just the
sheer fact that it exists

02:05:02.742 --> 02:05:06.690
now also calculating
the probability of failure

02:05:06.690 --> 02:05:08.260
on a tree by tree basis.

02:05:08.260 --> 02:05:10.210
'Cause that's really where we wanna go.

02:05:12.070 --> 02:05:15.010
<v ->When do you imagine
you would be able to do that</v>

02:05:15.010 --> 02:05:16.643
for the distribution system?

02:05:18.290 --> 02:05:21.450
<v ->Well, we're
working through that.</v>

02:05:21.450 --> 02:05:24.590
I think it's a couple of year effort

02:05:24.590 --> 02:05:27.100
and the reason why I say that

02:05:27.100 --> 02:05:31.000
is because we're gonna have the ability

02:05:31.000 --> 02:05:34.110
to be able to do this on
a portion of our system

02:05:34.110 --> 02:05:35.550
as compared to the entire system

02:05:35.550 --> 02:05:38.450
because until we do that base level work

02:05:38.450 --> 02:05:41.340
to be able to inventory all
of the strike potential trees

02:05:41.340 --> 02:05:43.760
with enhanced vegetation
management, remove that overhang

02:05:43.760 --> 02:05:46.950
because those are key
foundational steps and elements

02:05:46.950 --> 02:05:49.910
to be able to get further accurate data,

02:05:49.910 --> 02:05:52.530
to be able to start
getting angles of slopes

02:05:52.530 --> 02:05:54.240
coming from LiDAR,

02:05:54.240 --> 02:05:56.150
looking at the front row factors.

02:05:56.150 --> 02:05:57.730
And those are some of the things

02:05:57.730 --> 02:06:00.667
that we have in transmission
just by the sheer virtue

02:06:00.667 --> 02:06:02.420
of the lower density of trees.

02:06:02.420 --> 02:06:04.560
So it's a multi-year effort

02:06:04.560 --> 02:06:05.770
from our perspective, Commissioner

02:06:05.770 --> 02:06:08.700
but that's exactly where
we're headed with all of this

02:06:08.700 --> 02:06:10.930
because ultimately we're managing

02:06:10.930 --> 02:06:12.660
and Scott will tell you this, billions

02:06:12.660 --> 02:06:17.660
if not more of pieces of data
around hourly weather forecast

02:06:18.090 --> 02:06:21.750
over 30 years, 5.3 million trees.

02:06:21.750 --> 02:06:24.070
So the only way we're
doing this and a lot of this

02:06:24.070 --> 02:06:26.370
is through AI and machine
learning capabilities

02:06:26.370 --> 02:06:31.370
but we have to be able to get
that remote sensing capability

02:06:31.400 --> 02:06:33.530
to a far enough advancement

02:06:33.530 --> 02:06:35.800
for accurate data capture purposes.

02:06:35.800 --> 02:06:36.943
And that's some of the
work that we have to do

02:06:36.943 --> 02:06:40.390
to be able to remove
some of this vegetation

02:06:40.390 --> 02:06:42.993
that's in and around our overhead lines.

02:06:44.690 --> 02:06:46.130
<v Joyce>I'd like to stop us there</v>

02:06:46.130 --> 02:06:47.790
and I apologize for interrupting

02:06:47.790 --> 02:06:51.070
because this has been some
very, very valuable information.

02:06:51.070 --> 02:06:53.353
And thanks for carrying
us to those points.

02:06:54.530 --> 02:06:56.390
Thank you, Scott, for your presentation.

02:06:56.390 --> 02:06:59.580
I think we need to move
next to Jake Zigelman

02:06:59.580 --> 02:07:02.353
and hear more about
the customer impacts.

02:07:06.340 --> 02:07:07.930
<v ->Okay. Good morning, everyone.</v>

02:07:07.930 --> 02:07:10.163
Mic check, can you hear me?

02:07:11.890 --> 02:07:14.180
Okay. Thanks guys.
<v ->We got you dude.</v>

02:07:14.180 --> 02:07:16.840
<v ->All right, thank
you. Appreciate that.</v>

02:07:16.840 --> 02:07:18.090
My name is Jake Zigelman

02:07:18.090 --> 02:07:22.330
and I oversee our local
customer experience organization

02:07:22.330 --> 02:07:24.900
which does include a number
of our customer programs

02:07:24.900 --> 02:07:27.340
related to PSPS.

02:07:27.340 --> 02:07:29.310
I know we're running
a little bit late here

02:07:29.310 --> 02:07:33.600
so I will do my best to keep
this section relatively brief

02:07:34.670 --> 02:07:37.980
because our overall
plan is to incorporate

02:07:37.980 --> 02:07:41.740
these proposed conditions
into our customer education

02:07:41.740 --> 02:07:43.410
and outreach campaigns

02:07:43.410 --> 02:07:46.200
and where appropriate
continue to refine and augment

02:07:46.200 --> 02:07:48.560
our customer support offerings

02:07:48.560 --> 02:07:52.010
related to the proposed
conditions from the Federal Court.

02:07:52.010 --> 02:07:57.010
So this slide shows a
number of the many different

02:07:57.200 --> 02:08:00.010
menus and channels that we
already use to communicate

02:08:00.010 --> 02:08:03.363
with our customers, our agency
partners and our communities.

02:08:04.450 --> 02:08:06.720
Again, our plan is to
incorporate the messages

02:08:06.720 --> 02:08:09.423
you're hearing today
into all of these forums.

02:08:10.420 --> 02:08:12.980
It's important to note that
that most of the customers

02:08:12.980 --> 02:08:16.100
agencies and tribes who
would have been impacted

02:08:16.100 --> 02:08:17.837
by these proposed conditions

02:08:17.837 --> 02:08:21.390
in that 10 year historical
analysis that looked back

02:08:21.390 --> 02:08:23.580
that Scott was talking about,

02:08:23.580 --> 02:08:25.920
those are primarily the same customers

02:08:25.920 --> 02:08:28.670
that we would be communicating
with early and often

02:08:28.670 --> 02:08:31.377
to help raise awareness
and share support services

02:08:31.377 --> 02:08:35.640
and resources under
the previous conditions

02:08:35.640 --> 02:08:37.920
or the previous scope and criteria.

02:08:37.920 --> 02:08:41.490
So while these outreach
programs are already in place,

02:08:41.490 --> 02:08:43.450
they do give us a
number of opportunities

02:08:43.450 --> 02:08:46.880
to share this new information
through a variety of channels,

02:08:46.880 --> 02:08:48.153
which you can see here.

02:08:49.665 --> 02:08:53.340
So just to touch on a few
for customers, you know

02:08:53.340 --> 02:08:56.010
these are our community
wildfire webinars

02:08:56.010 --> 02:08:59.450
our Statewide access and
functional needs council meetings,

02:08:59.450 --> 02:09:00.590
social media channels,

02:09:00.590 --> 02:09:03.550
things of that nature for
our agency and tribes,

02:09:03.550 --> 02:09:06.110
we have our regular
regional working groups,

02:09:06.110 --> 02:09:09.390
our coordination meetings
with emergency managers

02:09:09.390 --> 02:09:11.960
and of course, a number
of one-on-one meetings

02:09:11.960 --> 02:09:14.270
with cities, counties,
tribal governments

02:09:14.270 --> 02:09:17.140
and critical customer groups.

02:09:17.140 --> 02:09:20.630
And in fact, on that last
point later this afternoon,

02:09:20.630 --> 02:09:24.230
we'll be hosting a meeting
focused on resiliency and PSPS

02:09:24.230 --> 02:09:26.237
with our telecommunications partners,

02:09:26.237 --> 02:09:30.000
where we will be highlighting
some of the same content

02:09:30.000 --> 02:09:32.483
that's gonna be discussed here today.

02:09:33.640 --> 02:09:35.913
So you can go to the next slide, please.

02:09:38.710 --> 02:09:40.000
Okay. Thank you.

02:09:40.000 --> 02:09:42.050
So this slide shows
the customer programs

02:09:42.050 --> 02:09:44.220
that we have available
to support customers

02:09:44.220 --> 02:09:46.481
impacted by PSPS events.

02:09:46.481 --> 02:09:51.159
Again, more than more than
90% of our 5.4 million customers

02:09:51.159 --> 02:09:53.810
don't live in the areas that are a focus

02:09:53.810 --> 02:09:55.712
of our overall PSPS program

02:09:55.712 --> 02:09:58.390
and are less likely to be impacted

02:09:58.390 --> 02:10:01.310
by these additional proposed conditions.

02:10:01.310 --> 02:10:02.870
That means that our support programs

02:10:02.870 --> 02:10:06.173
were really already focused
on the customers that were

02:10:06.173 --> 02:10:09.595
and will continue to be
or will likely continue to be

02:10:09.595 --> 02:10:13.040
most impacted by PSPS events.

02:10:13.040 --> 02:10:15.820
For many of our programs,
like our partnerships

02:10:15.820 --> 02:10:19.320
with community-based
organizations and local food banks,

02:10:19.320 --> 02:10:21.334
we're working to partner
with additional organizations

02:10:21.334 --> 02:10:25.230
in those areas that are
most likely to be impacted.

02:10:25.230 --> 02:10:27.110
And we're also preparing our resources

02:10:27.110 --> 02:10:29.750
to potentially handle the
increased event frequency

02:10:29.750 --> 02:10:31.967
that Scott referenced earlier.

02:10:31.967 --> 02:10:36.620
Most notably with respect
to these proposed conditions

02:10:36.620 --> 02:10:38.380
where we're preparing to mobilize

02:10:38.380 --> 02:10:41.080
our community resource
centers more frequently

02:10:41.080 --> 02:10:42.810
and we're working with our CBO partners

02:10:42.810 --> 02:10:45.630
to prepare for the
possible need to support

02:10:45.630 --> 02:10:48.540
additional customers and events.

02:10:48.540 --> 02:10:50.119
We're also in the process of assessing

02:10:50.119 --> 02:10:53.574
if the proposed conditions
create additional,

02:10:53.574 --> 02:10:56.578
I'd call it small geographical pockets

02:10:56.578 --> 02:11:01.578
that might benefit from a CRC
location being located nearby.

02:11:01.602 --> 02:11:04.040
And we'll continue to
coordinate those potential

02:11:04.040 --> 02:11:07.070
CRC locations with our
county and tribal partners

02:11:07.070 --> 02:11:11.090
which we've been doing
for the last couple of years.

02:11:11.090 --> 02:11:14.870
So our overall focus
remains on supporting

02:11:14.870 --> 02:11:17.415
our most vulnerable and
frequently impacted customers.

02:11:17.415 --> 02:11:20.730
We'll continue to
refine those strategies

02:11:20.730 --> 02:11:24.060
as we understand more
regarding the actual implementation

02:11:24.060 --> 02:11:25.763
of the proposed conditions.

02:11:26.920 --> 02:11:28.592
And that is all I had.

02:11:28.592 --> 02:11:30.493
So I will pause there.

02:11:34.040 --> 02:11:34.873
<v Joyce>Thank you, Jake.</v>

02:11:34.873 --> 02:11:36.760
Commissioners, did
you have any questions?

02:11:39.910 --> 02:11:42.523
<v ->I do Joyce, if I may.</v>

02:11:44.580 --> 02:11:46.010
Thanks Jake.

02:11:46.010 --> 02:11:50.720
I was wondering, it's a question
we frequently ask you all.

02:11:50.720 --> 02:11:52.971
And that's your portable batteries,

02:11:52.971 --> 02:11:57.971
is that 11,500 more than the
count we've been given lately?

02:11:59.670 --> 02:12:03.541
I mean, I remember
in one of the estimates,

02:12:03.541 --> 02:12:07.090
you all were counting when
you included medical baseline

02:12:07.090 --> 02:12:12.090
and all of the critical needs

02:12:13.410 --> 02:12:16.370
that it was up to almost
20,000, I thought?

02:12:16.370 --> 02:12:18.330
But maybe my memory is wrong on that.

02:12:18.330 --> 02:12:23.183
So I just wanna know in the
big a universe of the batteries

02:12:23.183 --> 02:12:27.940
that right now are
needed, let alone those...

02:12:27.940 --> 02:12:32.940
Yeah, is this an add on to
what's currently needed?

02:12:33.640 --> 02:12:34.473
<v ->Good question.</v>

02:12:34.473 --> 02:12:36.430
Thank you for the
question, President Batjer

02:12:38.460 --> 02:12:41.530
No, this is the same number
that we have been planning

02:12:41.530 --> 02:12:42.760
to deploy.

02:12:42.760 --> 02:12:45.667
The total reflect the
combination from last year

02:12:45.667 --> 02:12:48.573
and the planned
deployments for this year.

02:12:49.880 --> 02:12:52.040
This program, the
portable battery program,

02:12:52.040 --> 02:12:53.230
as a reminder for everyone,

02:12:53.230 --> 02:12:55.450
is targeted towards our most vulnerable

02:12:55.450 --> 02:12:57.750
and frequently impacted
customers for PSPS.

02:12:57.750 --> 02:13:00.339
So these programs are,

02:13:00.339 --> 02:13:02.380
or these these batteries I should say,

02:13:02.380 --> 02:13:07.290
are deployed to our low-income
medical baseline customers

02:13:07.290 --> 02:13:09.187
in either a high fire threat district

02:13:09.187 --> 02:13:13.670
or those customers who
have experienced two or more

02:13:13.670 --> 02:13:15.640
PSPS events in the past.

02:13:15.640 --> 02:13:17.800
And that population
of customers is around

02:13:17.800 --> 02:13:20.479
10,000 customers and change.

02:13:20.479 --> 02:13:24.720
And so the total combined
battery deployments

02:13:24.720 --> 02:13:26.650
from last year and this year

02:13:26.650 --> 02:13:29.620
is going to be that roughly 11,500

02:13:29.620 --> 02:13:31.713
that you see on the screen.

02:13:33.180 --> 02:13:34.730
Does that answer your question?

02:13:38.350 --> 02:13:39.263
<v ->Yes, it does.</v>

02:13:41.365 --> 02:13:44.244
<v Jeff>President Batjer?</v>

02:13:44.244 --> 02:13:46.661
(indistinct)

02:13:47.670 --> 02:13:48.503
No, you go ahead.

02:13:48.503 --> 02:13:50.762
I'm sure yours is
probably richer than mine.

02:13:50.762 --> 02:13:52.860
<v ->No, it's just the follow up.</v>

02:13:52.860 --> 02:13:54.730
How many have you deployed already,

02:13:54.730 --> 02:13:56.050
that's the first question, Jake.

02:13:56.050 --> 02:14:00.700
And the second is, if you
add the additional criteria

02:14:00.700 --> 02:14:01.533
that you're targeting,

02:14:01.533 --> 02:14:06.073
what's the target number beyond 11,500?

02:14:07.550 --> 02:14:09.163
<v ->Yeah, good question.</v>

02:14:10.070 --> 02:14:12.300
Yeah, I will start with the second part

02:14:12.300 --> 02:14:16.040
because the target remains
the same at the 11,500

02:14:16.040 --> 02:14:18.560
and I'll provide a little
bit more context on that

02:14:18.560 --> 02:14:19.463
in a second.

02:14:20.320 --> 02:14:25.320
We have deployed, it's
around, approaching 7,000

02:14:25.780 --> 02:14:28.870
I believe is the number
that we've deployed so far.

02:14:28.870 --> 02:14:31.660
So the rest are planned to be deployed

02:14:31.660 --> 02:14:32.823
for this fire season.

02:14:33.950 --> 02:14:37.320
And the additional context
from the second part

02:14:37.320 --> 02:14:38.600
of your question is that

02:14:39.580 --> 02:14:41.310
and Scott touched
on this a little bit earlier

02:14:41.310 --> 02:14:44.740
but based on the preliminary
analysis that we've done

02:14:44.740 --> 02:14:47.173
of the impacts of this scoping criteria,

02:14:48.070 --> 02:14:53.070
the population of customers
who would not have historically

02:14:54.520 --> 02:14:56.720
been impacted at all

02:14:56.720 --> 02:15:01.270
but for the new conditions
proposed by the Federal Court

02:15:01.270 --> 02:15:03.000
is very, very small.

02:15:03.000 --> 02:15:04.840
It appears to be on the order

02:15:04.840 --> 02:15:07.790
of between one and one and
a half percent of our customers.

02:15:08.810 --> 02:15:13.340
And so the vast
majority of our customers

02:15:13.340 --> 02:15:17.070
would have already
experienced a PSPS event

02:15:17.070 --> 02:15:19.750
just based on the baseline criteria.

02:15:19.750 --> 02:15:23.770
And so that would include
the same population,

02:15:23.770 --> 02:15:26.160
generally speaking of vulnerable

02:15:26.160 --> 02:15:27.860
and frequently impacted customers

02:15:27.860 --> 02:15:30.771
that we were already planning to support

02:15:30.771 --> 02:15:32.377
through all of these programs

02:15:32.377 --> 02:15:34.850
and our education and
outreach campaigns.

02:15:34.850 --> 02:15:38.350
And so that's why we're
looking at where are those places

02:15:38.350 --> 02:15:39.750
on the margin

02:15:39.750 --> 02:15:42.510
that we might need to
continue to augment things

02:15:42.510 --> 02:15:44.489
but by and large, it's the same group

02:15:44.489 --> 02:15:48.570
of vulnerable customers that
we really need to work hard

02:15:48.570 --> 02:15:50.780
on educating and
outreach with our partners

02:15:50.780 --> 02:15:55.780
to be prepared for a higher
frequency of possible events

02:15:56.460 --> 02:15:58.310
based on this new scope and criteria.

02:15:59.620 --> 02:16:00.453
<v ->Thank you.</v>

02:16:03.010 --> 02:16:05.870
<v ->And just to remind
folks that are listening</v>

02:16:05.870 --> 02:16:09.420
and these batteries are
how much of a backup,

02:16:09.420 --> 02:16:10.823
how many hours?

02:16:13.702 --> 02:16:16.691
<v ->It varies based on their needs</v>

02:16:16.691 --> 02:16:19.380
but it's going to be on
the order of magnitude

02:16:19.380 --> 02:16:20.770
of a few hours

02:16:20.770 --> 02:16:22.660
but it really does vary
based on their needs

02:16:22.660 --> 02:16:25.370
and President Batjer
to your question earlier

02:16:25.370 --> 02:16:28.904
about the possibility
of back-to-back events,

02:16:28.904 --> 02:16:32.498
as we engage with these
vulnerable customers

02:16:32.498 --> 02:16:34.660
and go through the assessment

02:16:34.660 --> 02:16:37.560
of what's the right
solution to meet their need,

02:16:37.560 --> 02:16:42.300
we typically see about 25%
to a third of those customers

02:16:42.300 --> 02:16:44.060
are the folks who
actually need a battery

02:16:44.060 --> 02:16:46.340
and who could benefit from a battery.

02:16:46.340 --> 02:16:48.610
Many others might
need a different solution

02:16:48.610 --> 02:16:51.819
like lodging or meal
replacement or something else.

02:16:51.819 --> 02:16:53.980
But as we go through that assessment,

02:16:53.980 --> 02:16:56.399
we do work with those customers

02:16:56.399 --> 02:16:59.800
to understand the possibilities
of a back-to-back event.

02:16:59.800 --> 02:17:03.470
And what those would put
that back to back events period

02:17:03.470 --> 02:17:05.374
would mean for them in terms of,

02:17:05.374 --> 02:17:09.060
you know, the need
for medical device usage

02:17:09.060 --> 02:17:10.210
or things like that.

02:17:10.210 --> 02:17:13.054
And so, as those portable
batteries are deployed,

02:17:13.054 --> 02:17:18.054
someone who who
would really be disrupted

02:17:18.870 --> 02:17:21.400
by back-to-back events
in a more material way

02:17:21.400 --> 02:17:23.723
might get a larger battery, for example.

02:17:24.850 --> 02:17:26.935
<v ->I really appreciate
that further explanation</v>

02:17:26.935 --> 02:17:31.250
'cause it's a real concern
and it's not, as I said earlier,

02:17:31.250 --> 02:17:33.227
it's not just the PSPS events,

02:17:33.227 --> 02:17:36.820
it's the electricity on, electricity off

02:17:36.820 --> 02:17:38.853
and when are they re-energized?

02:17:40.063 --> 02:17:42.690
'Cause we've had a lot
of testimony from folks

02:17:42.690 --> 02:17:47.690
that correct us or correct
you when they say,

02:17:47.890 --> 02:17:51.175
well, the PSPS was 48 hours

02:17:51.175 --> 02:17:56.175
and they said, well, I didn't
get re-energized for 72 hours.

02:17:58.164 --> 02:18:00.760
So it's a real concern.

02:18:00.760 --> 02:18:04.320
So the full calculation of when folks

02:18:04.320 --> 02:18:08.380
are without electricity
over the period of time

02:18:08.380 --> 02:18:11.700
and then the further complication

02:18:11.700 --> 02:18:14.880
of back-to-back PSPS as well.

02:18:14.880 --> 02:18:15.823
Okay, thank you.

02:18:20.180 --> 02:18:22.990
<v ->I had a question
about whether PG and E</v>

02:18:22.990 --> 02:18:25.740
will be able to identify the circuits

02:18:25.740 --> 02:18:29.810
that are in the top 70 percentile

02:18:29.810 --> 02:18:33.640
and can you speak to PG and E plans

02:18:33.640 --> 02:18:36.940
to communicate those
to public safety partners

02:18:36.940 --> 02:18:39.173
and local and tribal government?

02:18:41.250 --> 02:18:42.520
<v ->Yes, thank you
for the question.</v>

02:18:42.520 --> 02:18:45.770
The team, we do have
those circuits identified.

02:18:45.770 --> 02:18:48.460
What we're in the
process of doing right now

02:18:48.460 --> 02:18:50.940
is really translating that data down

02:18:50.940 --> 02:18:52.250
to a more granular level

02:18:52.250 --> 02:18:54.850
to better understand the
specific customer impacts

02:18:54.850 --> 02:18:56.298
to your point around

02:18:56.298 --> 02:19:00.180
who are the potentially
increment incrementally

02:19:00.180 --> 02:19:03.303
impacted customers who
might be a critical facility?

02:19:04.600 --> 02:19:07.680
So we're in the process
of distilling that data down

02:19:07.680 --> 02:19:09.300
to a more granular level.

02:19:09.300 --> 02:19:11.940
And I mentioned the
Telekom meeting this afternoon

02:19:11.940 --> 02:19:14.420
over the next several
weeks, we will be going out,

02:19:14.420 --> 02:19:16.390
our customer account
reps will be going out

02:19:16.390 --> 02:19:19.220
and having these conversations
with these customers

02:19:19.220 --> 02:19:20.765
about the possible impacts

02:19:20.765 --> 02:19:24.563
of this additional proposed criteria.

02:19:28.450 --> 02:19:29.370
<v ->Thank you.</v>

02:19:29.370 --> 02:19:31.293
Were there any other questions

02:19:31.293 --> 02:19:34.143
before we turn to our final speaker?

02:19:41.650 --> 02:19:43.210
I'm seeing none.

02:19:43.210 --> 02:19:44.770
Thank you, Jake for your presentation.

02:19:44.770 --> 02:19:47.423
And let's now turn to Tracy.

02:19:48.900 --> 02:19:50.440
<v ->Hello, just as a mic check.</v>

02:19:50.440 --> 02:19:51.513
Can everyone hear me?

02:19:55.470 --> 02:19:57.000
<v Joyce>Yes.</v>

02:19:57.000 --> 02:19:58.660
<v ->Great.</v>

02:19:58.660 --> 02:20:00.620
So my name is Tracy Maratukulam.

02:20:00.620 --> 02:20:04.920
I'll be covering how we
plan to share the results

02:20:04.920 --> 02:20:09.920
of these proposed conditions
on our 2021 PSPS season.

02:20:10.930 --> 02:20:13.697
So to aid in gauging the effectiveness

02:20:13.697 --> 02:20:17.775
of the proposed condition
and our implementation of them.

02:20:17.775 --> 02:20:21.383
PG and E plans, if you
can go to the next slide.

02:20:22.252 --> 02:20:26.560
PG and E will share in
our postseason report

02:20:26.560 --> 02:20:30.730
an accounting of the following
for any circuit segments

02:20:30.730 --> 02:20:35.730
that is holed into scope
due to the proposed condition

02:20:36.290 --> 02:20:38.093
of the event overstrike criteria.

02:20:39.000 --> 02:20:42.270
This includes the number
of customers impacted

02:20:42.270 --> 02:20:45.050
due to that circuit segment
being pulled into scope.

02:20:45.050 --> 02:20:47.830
Similarly, the customer impact frequency

02:20:47.830 --> 02:20:51.760
and duration of the PSPS
outage that they experienced

02:20:51.760 --> 02:20:53.340
over the season.

02:20:53.340 --> 02:20:55.785
And then in accounting
of any damages or hazards

02:20:55.785 --> 02:20:58.942
that are found on those circuit segments

02:20:58.942 --> 02:21:01.903
that are pulled in due to that criteria.

02:21:02.870 --> 02:21:07.870
We plan to share an
accounting notes these staff

02:21:08.720 --> 02:21:13.260
on the full seasons
impacts of PSPS events

02:21:13.260 --> 02:21:16.930
in our post-season report
which is currently being proposed

02:21:16.930 --> 02:21:20.360
and staff proposal to
the things three OYR

02:21:20.360 --> 02:21:22.377
in that proceeding.

02:21:22.377 --> 02:21:24.750
We'd like to work with the Commission on

02:21:24.750 --> 02:21:27.800
if there's any other appropriate metrics

02:21:27.800 --> 02:21:32.410
that they would like to see
as part of our measurement

02:21:32.410 --> 02:21:34.620
of what the impact of implementing

02:21:34.620 --> 02:21:36.273
these proposed conditions are.

02:21:40.030 --> 02:21:42.140
That is the bulk of our proposal.

02:21:42.140 --> 02:21:45.204
So I'd like to open it up to
questions, if there are any

02:21:45.204 --> 02:21:47.603
on anything else that
should be measured.

02:21:53.780 --> 02:21:57.730
<v Joyce>I believe Shelby
has a question to pose.</v>

02:21:57.730 --> 02:21:59.280
Why don't you go ahead, Shelby?

02:22:03.720 --> 02:22:04.553
<v ->Thanks Joyce.</v>

02:22:05.680 --> 02:22:08.645
We would like to see
in the post event reports

02:22:08.645 --> 02:22:12.910
a comparison of how many
customers were de-energized,

02:22:12.910 --> 02:22:15.623
how many customers were de-energized

02:22:16.573 --> 02:22:17.957
due to 2021 or 2020 baseline conditions.

02:22:20.270 --> 02:22:23.990
And then how many customers
were de-energized specifically

02:22:23.990 --> 02:22:25.883
due to the probation condition.

02:22:28.380 --> 02:22:30.383
<v ->Excellent. That is
what we're proposing</v>

02:22:30.383 --> 02:22:32.960
for circuit segments
that are pulled into scope

02:22:32.960 --> 02:22:36.523
for the proposed per that
conditions to get that account.

02:22:38.500 --> 02:22:39.450
<v ->Great. Thank you.</v>

02:22:46.150 --> 02:22:48.763
<v Joyce>Do any of the
Commissioners have any questions?</v>

02:22:58.710 --> 02:23:01.733
And Cliff, do you have
any other questions?

02:23:05.295 --> 02:23:09.570
<v Jeff>I do not have a question
on the event reporting.</v>

02:23:09.570 --> 02:23:11.298
However, I do have a general question.

02:23:11.298 --> 02:23:13.620
I don't know if I should
wait until after this

02:23:13.620 --> 02:23:14.823
or address that now?

02:23:17.540 --> 02:23:20.423
<v Joyce>Oh please go
ahead now, Chief Fuentes.</v>

02:23:20.423 --> 02:23:23.970
<v ->Okay, so I was wondering kind
of what PG and E needs doing</v>

02:23:23.970 --> 02:23:25.940
in the emerging technology

02:23:26.880 --> 02:23:31.070
in this with you know,
anticipation, fault detection,

02:23:31.070 --> 02:23:35.240
early detection, things like that.

02:23:35.240 --> 02:23:40.240
You know, it seems like that
technology might be helpful

02:23:44.470 --> 02:23:45.640
for this type of risk

02:23:45.640 --> 02:23:48.080
but I don't know, I know
you guys were piloting

02:23:48.080 --> 02:23:49.253
some of that technology.

02:23:49.253 --> 02:23:52.180
So I was curious what the
effectiveness of that was

02:23:52.180 --> 02:23:55.340
and if looking at the WMP this year,

02:23:55.340 --> 02:23:57.540
you looked like you
were deploying additional

02:23:57.540 --> 02:23:58.980
emerging technologies

02:23:58.980 --> 02:24:03.980
and are they in these areas
if this proposed credence

02:24:04.055 --> 02:24:04.888
accounted for it,

02:24:04.888 --> 02:24:07.313
there's gonna be some
technology that's gonna be.

02:24:10.410 --> 02:24:11.830
<v ->Yep, yeah. Chief Fuentes.</v>

02:24:11.830 --> 02:24:13.250
Thank you for that question,

02:24:13.250 --> 02:24:15.290
this is Sumeet, I'm happy to take that.

02:24:15.290 --> 02:24:17.028
So there's a number of breakthrough

02:24:17.028 --> 02:24:21.070
and emerging technologies
that we're piloting.

02:24:21.070 --> 02:24:24.210
So the one you mentioned
in regards to REFCL,

02:24:24.210 --> 02:24:26.710
Rapid Earth Fault Current Limiter

02:24:26.710 --> 02:24:28.820
and it comes from Australia.

02:24:28.820 --> 02:24:32.170
I personally spent some time
with the operators in Australia

02:24:32.170 --> 02:24:36.370
to understand how they're
implementing that technology.

02:24:36.370 --> 02:24:40.462
And we actually have
upgraded one of our circuits

02:24:40.462 --> 02:24:44.371
in the Napa Sonoma County area

02:24:44.371 --> 02:24:49.371
within the high parts but
district roughly 150 miles

02:24:49.380 --> 02:24:53.522
that has the rapid earth
fault current limiting capability.

02:24:53.522 --> 02:24:56.790
Now, you know, the
intent of that technology

02:24:56.790 --> 02:25:01.790
is if there's a potential
wires down type of a situation

02:25:03.810 --> 02:25:07.140
it puts equal and opposite
energy onto the line

02:25:07.140 --> 02:25:10.890
so that it basically
neutralizes the electricity flow

02:25:10.890 --> 02:25:12.180
and you don't have enough energy

02:25:12.180 --> 02:25:14.850
to create a potential fire ignition.

02:25:14.850 --> 02:25:18.660
And that's really focusing
on one of three different types

02:25:18.660 --> 02:25:20.700
of faults that we see within our system.

02:25:20.700 --> 02:25:23.960
Something called a
Phase to Ground Fault.

02:25:23.960 --> 02:25:27.810
One of the things that the
rapid earth fault current limiter

02:25:27.810 --> 02:25:29.704
right now does not necessarily have

02:25:29.704 --> 02:25:32.230
the technology to address is something

02:25:32.230 --> 02:25:34.330
called a Phase-to-Phase Fault,

02:25:34.330 --> 02:25:37.700
which would be two
different phases of a line

02:25:37.700 --> 02:25:40.280
that may come together
during periods of high wind

02:25:40.280 --> 02:25:43.031
and create something
called line slopping.

02:25:43.031 --> 02:25:46.530
Another element is the third category

02:25:46.530 --> 02:25:47.910
is called a high impedance fault,

02:25:47.910 --> 02:25:51.560
where you may have
a tree, a branch of tree

02:25:51.560 --> 02:25:54.311
that traverses two different phases.

02:25:54.311 --> 02:25:56.950
And at the moment that technology

02:25:56.950 --> 02:25:58.800
does not mitigate those defaults

02:25:58.800 --> 02:26:01.510
but it is effective in this space.

02:26:01.510 --> 02:26:06.500
And we are in the process of evaluating

02:26:06.500 --> 02:26:09.500
the operational use cases

02:26:09.500 --> 02:26:12.010
to be able to understand the limitations

02:26:12.010 --> 02:26:14.861
and to understand
where within our blueprint

02:26:14.861 --> 02:26:17.957
we can expand and
implement this capability.

02:26:17.957 --> 02:26:21.410
And so that is absolutely
a tool within our toolkit

02:26:21.410 --> 02:26:23.580
that we're very optimistic about.

02:26:23.580 --> 02:26:26.090
But again, it's not a silver bullet.

02:26:26.090 --> 02:26:29.280
Another technology that
we actually filed a patent for

02:26:29.280 --> 02:26:32.861
we've described it within
the wildfire mitigation plan,

02:26:32.861 --> 02:26:35.840
something called a DTS-Fast.

02:26:35.840 --> 02:26:39.199
It's a fast acting scheme in essence

02:26:39.199 --> 02:26:41.296
and we're piloting
another transmission line.

02:26:41.296 --> 02:26:46.010
And in essence, going
back to the discussion

02:26:46.010 --> 02:26:47.550
that President Batjer and I were having,

02:26:47.550 --> 02:26:48.810
one of the things we're looking to do

02:26:48.810 --> 02:26:50.370
is engineer the risk out

02:26:50.370 --> 02:26:53.430
so that for our overhead electric system

02:26:53.430 --> 02:26:57.050
if the system fails, it fails safely

02:26:57.050 --> 02:27:00.006
and has the capacity to feel safe.

02:27:00.006 --> 02:27:02.250
So what we're basically
doing is in this instance

02:27:02.250 --> 02:27:06.370
we're outfitting some of our
towers with laser technology.

02:27:06.370 --> 02:27:10.370
And these are lasers that
are mounted on our towers

02:27:10.370 --> 02:27:13.730
no different than lasers use
in self autonomous vehicles

02:27:13.730 --> 02:27:18.600
and the intent is that
creates a laser field around,

02:27:18.600 --> 02:27:20.480
an invisible laser field,

02:27:20.480 --> 02:27:22.160
around our overhead conductors

02:27:22.160 --> 02:27:25.480
and if there's any breach
within that laser field,

02:27:25.480 --> 02:27:28.470
that specific section of
the system automatically

02:27:28.470 --> 02:27:31.420
re-energizes in less than a millisecond.

02:27:31.420 --> 02:27:34.970
It's the hardware that enables
that software capabilities.

02:27:34.970 --> 02:27:36.440
So we've filed a patent for that.

02:27:36.440 --> 02:27:38.520
And actually we've proved that out

02:27:38.520 --> 02:27:41.030
from a field viability perspective

02:27:41.030 --> 02:27:43.610
and we're doing the
operational assessment

02:27:43.610 --> 02:27:46.250
of that technology as well.

02:27:46.250 --> 02:27:48.960
So that's another
tool within our toolkit.

02:27:48.960 --> 02:27:51.870
And then the last piece
I'll share with you is that

02:27:51.870 --> 02:27:54.840
you know, obviously
we're one of the first movers

02:27:54.840 --> 02:27:58.070
across the nation to
implement smart meters.

02:27:58.070 --> 02:27:59.930
So one of the things
we're doing is working

02:27:59.930 --> 02:28:01.820
with the smart meter service provider

02:28:01.820 --> 02:28:05.910
to be able to outfit that
with additional sensors,

02:28:05.910 --> 02:28:07.580
it's called Sensor IQ

02:28:07.580 --> 02:28:10.270
that gives us the ability
to be able to measure

02:28:10.270 --> 02:28:14.240
not just the traditional
volume of electricity

02:28:14.240 --> 02:28:16.880
and gas being used, which
is what's been in operations

02:28:16.880 --> 02:28:19.070
for more than a decade
with smart meters,

02:28:19.070 --> 02:28:20.980
but also the ability
to be able to detect

02:28:20.980 --> 02:28:22.940
things like partial voltage.

02:28:22.940 --> 02:28:24.340
So that if there's a wires down

02:28:24.340 --> 02:28:29.340
we have instant detection
back within our control center

02:28:29.625 --> 02:28:32.710
which is staffed 24/7 365 days a year.

02:28:32.710 --> 02:28:36.070
And we can dispatch
an appropriate qualified

02:28:36.070 --> 02:28:39.650
electrical worker to be
able to do the remediation.

02:28:39.650 --> 02:28:43.250
So early detection is one category

02:28:43.250 --> 02:28:45.117
and then the other two
fall into that category

02:28:45.117 --> 02:28:47.280
of engineering the risk out

02:28:47.280 --> 02:28:50.650
and providing additional
safety margin within our system.

02:28:50.650 --> 02:28:52.960
So when it does fail, that
does fail in a safe manner.

02:28:52.960 --> 02:28:56.484
So those are some of the
technologies that we have teed up.

02:28:56.484 --> 02:28:58.810
And there's a whole
bunch of additional ones

02:28:58.810 --> 02:29:01.150
that I didn't touch with
the essence of time

02:29:01.150 --> 02:29:02.520
that we have included in the WMP.

02:29:02.520 --> 02:29:05.410
So we're pretty excited
about what needs to happen

02:29:05.410 --> 02:29:08.260
and I'm very encouraged
by what I'm also seeing

02:29:08.260 --> 02:29:11.330
the other IOUs in California doing

02:29:11.330 --> 02:29:14.570
and us working as the collective us

02:29:14.570 --> 02:29:17.683
to really move the needle
forward in the technology space.

02:29:19.550 --> 02:29:20.530
<v ->Thank you for that.</v>

02:29:20.530 --> 02:29:23.940
(indistinct) to hear that and
look forward to hearing more

02:29:23.940 --> 02:29:26.260
about the pilots outcomes.

02:29:26.260 --> 02:29:27.340
Thanks.

02:29:27.340 --> 02:29:28.173
<v ->Our pleasure</v>

02:29:30.900 --> 02:29:32.040
<v ->Sumeet, this is Joyce</v>

02:29:32.040 --> 02:29:34.910
and the scope of our workshop today

02:29:34.910 --> 02:29:36.160
hasn't really touched on this

02:29:36.160 --> 02:29:40.520
but are there any other legal
or regulatory solutions here

02:29:40.520 --> 02:29:42.040
where we're dealing with trees

02:29:42.040 --> 02:29:44.370
that are beyond utility easements

02:29:44.370 --> 02:29:46.760
and beyond utility rights of way?

02:29:46.760 --> 02:29:50.510
Are there other solutions
that we should be looking at

02:29:50.510 --> 02:29:54.140
as far as the planting
and replacement of trees

02:29:54.140 --> 02:29:56.393
that impact power line?

02:29:59.280 --> 02:30:01.027
<v ->That's a great question, Joyce</v>

02:30:01.027 --> 02:30:04.195
and I think one of the things that...

02:30:04.195 --> 02:30:06.423
And I appreciate you opening
the door on that question.

02:30:06.423 --> 02:30:08.760
I think it's probably a
separate follow-up deep dive

02:30:08.760 --> 02:30:09.593
we can have.

02:30:09.593 --> 02:30:14.593
I think one of the challenges
that obviously we face a times

02:30:14.916 --> 02:30:16.930
and we're very mindful,

02:30:16.930 --> 02:30:20.224
we understand the importance
of trees to the climate as well

02:30:20.224 --> 02:30:23.730
but obviously as we do identify trees

02:30:23.730 --> 02:30:26.390
as part of our enhanced
vegetation management program,

02:30:26.390 --> 02:30:30.760
you know, for removal because
they do pose that higher risk

02:30:30.760 --> 02:30:33.530
but at times, you
know, we're not aligned

02:30:33.530 --> 02:30:37.760
with the viewpoints
that may exist locally,

02:30:37.760 --> 02:30:38.670
you know with our customers.

02:30:38.670 --> 02:30:40.400
And we're very, very respectful of that

02:30:40.400 --> 02:30:42.749
and insensitive to some of these trees

02:30:42.749 --> 02:30:44.420
because some of these
trees at one point in time

02:30:44.420 --> 02:30:46.600
were not a threat or a risk

02:30:46.600 --> 02:30:49.617
but now given the change of
condition in and around the tree

02:30:49.617 --> 02:30:52.820
and the power line
has created that risk.

02:30:52.820 --> 02:30:55.200
And I think there's
opportunities choice, right?

02:30:55.200 --> 02:30:57.060
Not necessarily to problem solve here

02:30:57.060 --> 02:31:00.468
but we'll be happy to engage
with you in that discussion

02:31:00.468 --> 02:31:03.660
with our team on what
are some of the additional

02:31:03.660 --> 02:31:06.103
legal regulatory opportunities exist

02:31:06.103 --> 02:31:10.388
to be able to do the right
thing in a very prudent manner

02:31:10.388 --> 02:31:14.330
and mitigate that risk in an
expeditious manner as well

02:31:14.330 --> 02:31:17.290
because there are
instances where it takes us

02:31:17.290 --> 02:31:22.048
12, 18, 24 months to be able
to work through the processes

02:31:22.048 --> 02:31:25.500
we have today to be
able to mitigate that risk.

02:31:25.500 --> 02:31:29.110
And in those instances,
when we talk about

02:31:29.110 --> 02:31:32.960
some of these higher priority
trees and higher risk trees

02:31:32.960 --> 02:31:35.632
and now obviously that
has an adverse impact

02:31:35.632 --> 02:31:38.730
on when a potential PSPS may be called.

02:31:38.730 --> 02:31:42.040
So there is an
interdependency there, Joyce

02:31:42.040 --> 02:31:44.030
I don't think it's a silver bullet

02:31:44.030 --> 02:31:46.980
but there's absolutely
an opportunity, I think

02:31:46.980 --> 02:31:51.140
across the board and working
on multi jurisdiction areas

02:31:51.140 --> 02:31:56.140
of between the local
government, the respective CPUC

02:31:56.429 --> 02:31:59.640
to be able to help
establish some mechanism

02:31:59.640 --> 02:32:03.110
by which we can streamline
some of the risk reduction work

02:32:03.110 --> 02:32:05.031
that all the IOUs are
doing not just PG and E

02:32:05.031 --> 02:32:06.581
within the state of California.

02:32:10.830 --> 02:32:13.457
<v ->Well, thank you very much
for PG and E presentations.</v>

02:32:13.457 --> 02:32:17.500
Unless there's any other
questions from Commissioners,

02:32:17.500 --> 02:32:20.440
I see Commissioner Shiroma
would like to pose the question.

02:32:20.440 --> 02:32:21.590
Go ahead, Commissioner.

02:32:29.230 --> 02:32:32.713
So we are unable to hear
you Commissioner Shiroma.

02:32:49.877 --> 02:32:54.127
<v ->Do you wanna type in your
question, Commissioner?</v>

02:33:12.620 --> 02:33:15.540
<v ->Immediately after the
Commissioner's question,</v>

02:33:15.540 --> 02:33:19.853
we'll likely be moving into
the public comment mode.

02:33:20.700 --> 02:33:25.570
So I would say that that's
what's going to happen next

02:33:26.470 --> 02:33:28.170
after the Commissioner's question.

02:33:42.250 --> 02:33:43.830
<v ->So the question is,</v>

02:33:43.830 --> 02:33:47.440
are you poised to
update your PSPS portal

02:33:47.440 --> 02:33:50.093
should the additional
criteria be approved?

02:33:51.010 --> 02:33:52.220
Absolutely.

02:33:52.220 --> 02:33:53.870
We've gotten a lot of feedback,

02:33:53.870 --> 02:33:56.560
you know, Commissioner,
as part of our listing sessions

02:33:56.560 --> 02:34:01.440
that we've done both
with the local agencies

02:34:01.440 --> 02:34:03.850
as well as with their emergency managers

02:34:03.850 --> 02:34:06.120
as well as at the state level

02:34:06.120 --> 02:34:09.250
with both the respected
Calloways and Cal FIRE

02:34:09.250 --> 02:34:12.300
and our intent is absolutely
you have to continue

02:34:12.300 --> 02:34:14.293
to make improvements on our PSPS portal

02:34:14.293 --> 02:34:18.700
so that we're able to
provide timely information

02:34:18.700 --> 02:34:23.490
that's relevant to the local
community and make it clear

02:34:23.490 --> 02:34:27.010
as changes happen to that information,

02:34:27.010 --> 02:34:29.900
given the changes in
the weather scenario

02:34:29.900 --> 02:34:31.698
that we make it very clear

02:34:31.698 --> 02:34:35.010
for all of the interested stakeholders

02:34:35.010 --> 02:34:39.410
and impacted stakeholders
on the situational awareness.

02:34:39.410 --> 02:34:41.204
So that's absolutely something
that we're committed to.

02:34:41.204 --> 02:34:43.530
I know we've got Erin Johnson,

02:34:43.530 --> 02:34:46.079
who's leading that
effort up from our side

02:34:46.079 --> 02:34:46.912
on the call as well.

02:34:46.912 --> 02:34:49.462
And I don't know if Erin
will add anything to that?

02:34:56.880 --> 02:34:59.520
<v ->No, I think you've
covered it well, Sumeet</v>

02:34:59.520 --> 02:35:02.730
the only thing I would add is,

02:35:02.730 --> 02:35:04.858
that as we begin our outreach

02:35:04.858 --> 02:35:07.570
that starts a week from today

02:35:07.570 --> 02:35:12.390
in Santa Clara County
with counties and tribes,

02:35:12.390 --> 02:35:16.730
we will be sharing enhanced
information about the locations

02:35:16.730 --> 02:35:19.740
and the frequency of
these potential criteria

02:35:19.740 --> 02:35:21.260
even though they are not yet final.

02:35:21.260 --> 02:35:25.380
And we started previewing
that with counties and tribes

02:35:25.380 --> 02:35:27.079
over the last couple of weeks

02:35:27.079 --> 02:35:30.140
as there was more and
more local discussion

02:35:30.140 --> 02:35:31.510
and these matters have been covered

02:35:31.510 --> 02:35:33.560
in the newspapers and
we're raising to awareness.

02:35:33.560 --> 02:35:36.070
We were hoping to
have a little more certainty

02:35:36.070 --> 02:35:39.250
for those jurisdictions
before we started speaking

02:35:39.250 --> 02:35:40.083
about those issues

02:35:40.083 --> 02:35:42.700
but we were getting
questions from a few of them,

02:35:42.700 --> 02:35:44.420
so we have proactively reached out

02:35:44.420 --> 02:35:45.950
to all counties and tribes to make sure

02:35:45.950 --> 02:35:47.880
they're aware of these
potential developments.

02:35:47.880 --> 02:35:50.930
And we'll certainly let
them know as they finalize

02:35:50.930 --> 02:35:54.770
and be incorporating the
impacts of that into all the tools

02:35:54.770 --> 02:35:55.870
that we're developing.

02:35:57.310 --> 02:35:58.143
Thank you.

02:36:00.100 --> 02:36:02.350
<v ->Thank you, Erin.</v>

02:36:02.350 --> 02:36:03.300
Joyce, back to you.

02:36:05.553 --> 02:36:07.410
<v ->Thank you.</v>
<v ->Thank you.</v>

02:36:07.410 --> 02:36:11.500
<v ->We'll now move on to
the public comment portion</v>

02:36:11.500 --> 02:36:12.430
of the proceedings,

02:36:12.430 --> 02:36:14.973
so I will turn it over to the operator.

02:36:17.180 --> 02:36:18.073
<v ->Thank you.</v>

02:36:19.120 --> 02:36:21.500
The first public comment on the line

02:36:21.500 --> 02:36:26.160
is coming from Katherine Sandoval.

02:36:26.160 --> 02:36:27.550
Please state your organization.

02:36:27.550 --> 02:36:28.523
Your line is open.

02:36:29.900 --> 02:36:30.880
<v Katherine>Yes. Thank you.</v>

02:36:30.880 --> 02:36:33.070
This is professor and
former Commissioner,

02:36:33.070 --> 02:36:34.190
Katherine Sandoval.

02:36:34.190 --> 02:36:37.700
I'm the director of the
Insurance law Institute

02:36:37.700 --> 02:36:39.640
at Santa Clara University.

02:36:39.640 --> 02:36:40.473
Can you hear me?

02:36:42.550 --> 02:36:43.383
<v Joyce>Yes.</v>

02:36:44.780 --> 02:36:47.350
<v Katherine>So I wanted to
make a couple of comments.</v>

02:36:47.350 --> 02:36:50.270
First of all, thank you so
much for having this workshop.

02:36:50.270 --> 02:36:51.983
It's been very informative.

02:36:52.950 --> 02:36:56.410
One question I think that
we haven't asked is that

02:36:56.410 --> 02:37:01.410
when you apply the PG and
E's model to years prior to 2018

02:37:01.910 --> 02:37:03.510
it raises the question of really

02:37:03.510 --> 02:37:05.260
how predictive those models are

02:37:05.260 --> 02:37:08.370
since the vegetation management criteria

02:37:08.370 --> 02:37:10.569
and wildfire mitigation requirements

02:37:10.569 --> 02:37:14.550
changed dramatically after 2018.

02:37:14.550 --> 02:37:18.528
And so thus my question is
really whether or not the data

02:37:18.528 --> 02:37:22.480
where the model indicates
2019 and 2020 data

02:37:22.480 --> 02:37:24.309
really are the best
predictors of the impact

02:37:24.309 --> 02:37:27.630
of potential PSPS on the application

02:37:27.630 --> 02:37:29.731
of probation conditions, 11 and 12

02:37:29.731 --> 02:37:33.050
and where we see for
example, in 2018, 2020,

02:37:33.050 --> 02:37:35.443
no additional PSPS?

02:37:35.443 --> 02:37:38.750
I would also emphasize
that PG and E was saying that

02:37:38.750 --> 02:37:43.330
this would affect 1%
to 1.5% more customers

02:37:43.330 --> 02:37:47.421
and they didn't provide the
detailed County by County data

02:37:47.421 --> 02:37:49.660
in this analysis.

02:37:49.660 --> 02:37:51.140
But as stated previously,

02:37:51.140 --> 02:37:53.460
the court can also order PG and E

02:37:53.460 --> 02:37:55.430
to provide more power backup

02:37:55.430 --> 02:37:59.960
and other appropriate
resources in the affected areas.

02:37:59.960 --> 02:38:02.860
So what really this indicates is that

02:38:02.860 --> 02:38:05.420
we need to think about
two different things.

02:38:05.420 --> 02:38:08.490
One, whether or not,
if in fact there were

02:38:08.490 --> 02:38:11.350
unaddressed tree overstrikes

02:38:12.540 --> 02:38:16.730
and overhanging
vegetation that hit the line,

02:38:16.730 --> 02:38:18.340
whether that would, for example,

02:38:18.340 --> 02:38:22.683
violate California
Public Utilities Code 451

02:38:22.683 --> 02:38:27.000
indicating that PG and
E is not operating safely.

02:38:27.000 --> 02:38:30.860
So the judge is trying
to address this risk

02:38:30.860 --> 02:38:32.457
and unaddressed risks

02:38:32.457 --> 02:38:34.530
and for example, what
caused the Zogg fire

02:38:34.530 --> 02:38:36.363
through these probation conditions?

02:38:37.290 --> 02:38:39.620
So the Insurance Law Institute

02:38:39.620 --> 02:38:41.768
of California at Santa
Clara University believes that

02:38:41.768 --> 02:38:46.768
these probation conditions
are well calculated

02:38:46.920 --> 02:38:48.960
to protect public safety.

02:38:48.960 --> 02:38:52.010
And Commissioners I
would urge you to support

02:38:52.010 --> 02:38:54.950
these probation conditions,
if you can make comments

02:38:54.950 --> 02:38:58.820
to the court suggesting
any appropriate modifications

02:38:58.820 --> 02:39:00.330
to the probation conditions,

02:39:00.330 --> 02:39:03.340
such as the addition of
requirement to PG and E

02:39:03.340 --> 02:39:04.510
provide power backup

02:39:04.510 --> 02:39:06.561
and other resources
to effective customers.

02:39:06.561 --> 02:39:09.110
And what's really important

02:39:09.110 --> 02:39:11.790
and what these probation
conditions are trying to achieve

02:39:11.790 --> 02:39:13.768
is the same thing that the
Commission is trying to achieve,

02:39:13.768 --> 02:39:18.768
which is to save lives, save
lungs, safeguard property

02:39:19.720 --> 02:39:20.910
and the environment

02:39:20.910 --> 02:39:24.420
and also forestal climate
change for more wildfires.

02:39:24.420 --> 02:39:26.410
So thank you very much for this workshop

02:39:26.410 --> 02:39:29.930
and I encourage your support
for these probation conditions.

02:39:29.930 --> 02:39:30.763
Thank you.

02:39:34.510 --> 02:39:35.920
<v Shelby>Thank you, our
next public comment</v>

02:39:35.920 --> 02:39:37.824
comes from Richard Scaff.

02:39:37.824 --> 02:39:38.810
Please state your organization.

02:39:38.810 --> 02:39:39.710
Your line is open.

02:39:42.200 --> 02:39:43.700
<v Richard>My name is Richard Skaff.</v>

02:39:43.700 --> 02:39:47.220
I am the Executive Director
of a nonprofit organization

02:39:47.220 --> 02:39:49.550
called Designing Accessible Communities.

02:39:49.550 --> 02:39:50.750
Are you able to hear me?

02:39:53.540 --> 02:39:54.373
Hello.

02:39:55.827 --> 02:39:58.071
<v Shelby>You go ahead, Mr. Skaff.</v>

02:39:58.071 --> 02:40:00.119
We can hear you, go ahead.

02:40:00.119 --> 02:40:03.000
<v Richard>Okay. Thank you.</v>

02:40:03.000 --> 02:40:06.040
A number of things first, PG and E

02:40:06.040 --> 02:40:08.053
is only listening to those,

02:40:09.380 --> 02:40:13.612
the groups that had described
during his presentation today

02:40:13.612 --> 02:40:17.490
that agree with its inadequate
mitigation measures.

02:40:17.490 --> 02:40:19.710
And I say that because as the director

02:40:19.710 --> 02:40:23.740
of a nonprofit organization
who deals with the rights

02:40:23.740 --> 02:40:26.490
of people with disabilities
and the protection of those

02:40:28.000 --> 02:40:31.850
those folks in communities
throughout the state

02:40:33.160 --> 02:40:38.160
that are affected by this
condition that was created

02:40:38.460 --> 02:40:41.940
by the three electric utilities,

02:40:41.940 --> 02:40:43.230
they have made it clear

02:40:43.230 --> 02:40:45.666
that they don't wanna hear anything

02:40:45.666 --> 02:40:49.340
unless it is in support
of what they propose

02:40:49.340 --> 02:40:50.910
and what they're doing.

02:40:50.910 --> 02:40:55.730
Not all right that should
be on the medical baseline

02:40:55.730 --> 02:40:57.570
have joined that program.

02:40:57.570 --> 02:41:00.500
I know that PG and E
has made some effort

02:41:00.500 --> 02:41:05.360
to educate their rate
payers about the program

02:41:05.360 --> 02:41:09.390
but it still has not been successful

02:41:09.390 --> 02:41:12.200
in getting all that should
be in that program,

02:41:12.200 --> 02:41:13.223
into the program.

02:41:14.059 --> 02:41:18.773
And to date, there is inadequate.

02:41:20.090 --> 02:41:22.493
There's a lack of adequate
mitigation measures.

02:41:23.420 --> 02:41:27.160
Presently, one of the
major mitigation measures

02:41:27.160 --> 02:41:32.160
that they have touted the
Yeti 3000 battery generators

02:41:33.600 --> 02:41:37.840
that have been distributed
by the California Foundation

02:41:37.840 --> 02:41:39.120
for Independent Living Centers.

02:41:39.120 --> 02:41:41.783
They've got a $5 million
grant from PG and E.

02:41:43.409 --> 02:41:48.409
They are the least
supported battery generator

02:41:50.660 --> 02:41:53.730
of all of those that
are available today.

02:41:53.730 --> 02:41:56.290
One of their major issues is that ,

02:41:56.290 --> 02:42:00.483
of all of the most visible

02:42:00.483 --> 02:42:05.483
and major battery generators available,

02:42:06.830 --> 02:42:11.350
this one only is able to have
500 recharging capabilities.

02:42:11.350 --> 02:42:15.580
That's when it gets the power
within the battery reduced,

02:42:15.580 --> 02:42:17.620
it is recharged.

02:42:17.620 --> 02:42:22.620
It can only have 500 recharges
when most battery generators

02:42:23.280 --> 02:42:27.370
that are produced for
the type of mitigation

02:42:27.370 --> 02:42:30.410
that we're talking
about can be recharged

02:42:30.410 --> 02:42:34.260
between 1500 and 2500 times,

02:42:34.260 --> 02:42:35.960
a substantial difference.

02:42:35.960 --> 02:42:40.960
I don't know why PG and E
and the California Foundation

02:42:41.160 --> 02:42:44.100
for Independent Living
centers decided on that one.

02:42:44.100 --> 02:42:46.185
There was no discussion with anybody

02:42:46.185 --> 02:42:51.185
other than the two organizations,
PG and E and CFILC.

02:42:52.470 --> 02:42:53.720
And that's another issue.

02:42:54.580 --> 02:42:57.120
During that first development,

02:42:57.120 --> 02:43:02.120
there was a meeting created
between PG and E and CFILC.

02:43:02.800 --> 02:43:05.363
No one else was
included in that meeting.

02:43:06.410 --> 02:43:11.410
And I have a number of
other issues I'd like to speak to.

02:43:11.850 --> 02:43:13.959
We don't have transportation for people

02:43:13.959 --> 02:43:16.550
that don't have their own transportation

02:43:16.550 --> 02:43:21.210
to get to the charging
stations that PG and E opens

02:43:21.210 --> 02:43:23.303
so that we can recharge equipment.

02:43:25.720 --> 02:43:28.230
Most of the counties, including Sonoma,

02:43:28.230 --> 02:43:31.750
I'm talking to them
next month about this

02:43:31.750 --> 02:43:33.860
don't provide transportation

02:43:33.860 --> 02:43:36.930
and unlike Southern California Edison

02:43:36.930 --> 02:43:39.220
in a report that I just read

02:43:39.220 --> 02:43:43.480
apparently they are providing vehicles.

02:43:43.480 --> 02:43:48.480
They have vans that either
bring equipment to a person

02:43:48.840 --> 02:43:50.190
who is home bound

02:43:50.190 --> 02:43:55.190
or they take a person in a
wheelchair accessible vehicle

02:43:59.780 --> 02:44:01.483
to the charging stations.

02:44:02.550 --> 02:44:04.972
That is not happening
throughout the state

02:44:04.972 --> 02:44:09.593
and especially in the
PG and E grid locations.

02:44:11.610 --> 02:44:16.610
So I would ask the
Commission to consider the need

02:44:17.710 --> 02:44:22.710
to require PG and E to
have input from those of us

02:44:24.030 --> 02:44:26.780
that don't necessarily
agree with what they're doing

02:44:26.780 --> 02:44:28.370
as far as mitigation.

02:44:28.370 --> 02:44:32.190
I would ask the Commission
to consider requiring all

02:44:32.190 --> 02:44:34.770
of the electric
utilities they'll receive

02:44:34.770 --> 02:44:36.697
during the energization events

02:44:36.697 --> 02:44:41.601
providing wheelchair
accessible transportation

02:44:41.601 --> 02:44:46.601
to charging stations and
hotels in Sonoma County,

02:44:46.880 --> 02:44:50.700
for example, there
are no accessible cabs

02:44:50.700 --> 02:44:54.670
even though the County
oversees and gives permits for cabs.

02:44:54.670 --> 02:44:56.940
There are no wheelchair accessible cabs.

02:44:56.940 --> 02:44:59.317
So there is virtually no
wheelchair accessible

02:44:59.317 --> 02:45:03.900
transportation available
for immediate transportation

02:45:03.900 --> 02:45:07.060
to either the charging
stations or to a hotel

02:45:07.060 --> 02:45:08.513
or to go pick up food.

02:45:09.370 --> 02:45:13.510
And lastly, we need mitigation measures

02:45:13.510 --> 02:45:16.800
that are going to be able to handle

02:45:18.050 --> 02:45:22.080
running a refrigerator
for 24 hours or 48 hours.

02:45:22.080 --> 02:45:24.560
The Yeti 3000 will not do that.

02:45:24.560 --> 02:45:27.670
In fact, when I picked the one I have up

02:45:27.670 --> 02:45:31.500
from the local independent
living center, I asked,

02:45:31.500 --> 02:45:34.290
what happens if I need
to run my refrigerator

02:45:34.290 --> 02:45:35.123
during this time?

02:45:35.123 --> 02:45:38.290
And they said, Oh, don't
plug the refrigerator in

02:45:38.290 --> 02:45:41.700
because it will reduce
the power so quickly

02:45:41.700 --> 02:45:45.560
that you won't have
adequate power for the rest

02:45:45.560 --> 02:45:49.430
of the period of the
de-energization event.

02:45:49.430 --> 02:45:54.430
So there are some
substantial mitigation measures

02:45:54.830 --> 02:45:56.423
that are still lacking.

02:45:58.371 --> 02:46:01.470
And we as a community
of vulnerable seniors

02:46:01.470 --> 02:46:02.720
and people with disabilities

02:46:02.720 --> 02:46:06.270
are still being put in jeopardy

02:46:06.270 --> 02:46:09.200
because of this lack of mitigation.

02:46:09.200 --> 02:46:13.810
And last I would ask that
you ask the electric utilities

02:46:13.810 --> 02:46:18.810
whether we as representatives
of the communities we serve,

02:46:19.900 --> 02:46:21.300
agree or don't agree,

02:46:21.300 --> 02:46:24.233
we should be part of
that process of discussion.

02:46:25.680 --> 02:46:26.610
So thank you very much

02:46:26.610 --> 02:46:29.030
for allowing me to
speak completely today.

02:46:29.030 --> 02:46:30.253
I appreciate the time.

02:46:35.420 --> 02:46:37.780
<v Shelby>Our next public
comment comes from Will Abrams.</v>

02:46:37.780 --> 02:46:39.160
Your line is open.

02:46:39.160 --> 02:46:41.246
Please state your organization.

02:46:41.246 --> 02:46:43.236
<v Will>Thanks very much.</v>

02:46:43.236 --> 02:46:44.620
Good morning Commissioners

02:46:44.620 --> 02:46:47.990
and thank you for holding
this important proceeding.

02:46:47.990 --> 02:46:51.500
The presentations here today
seemed perfectly plausible.

02:46:51.500 --> 02:46:54.480
If you don't consider prior
comments from PG and E.

02:46:54.480 --> 02:46:57.730
In 2019 PG and E relied and parsed out

02:46:57.730 --> 02:46:58.990
substantial compliance

02:46:58.990 --> 02:47:02.110
from actual vegetation
management compliance.

02:47:02.110 --> 02:47:05.470
In 2020 they excluded
clauses of recent fires

02:47:05.470 --> 02:47:10.090
from their fire protection
index but rely on it here today.

02:47:10.090 --> 02:47:14.490
Now in 2021, PG and E
misappropriates the black Swan term

02:47:14.490 --> 02:47:16.610
to explain away failures.

02:47:16.610 --> 02:47:19.740
No a black Swan is not a low probability

02:47:19.740 --> 02:47:21.960
but high consequence event.

02:47:21.960 --> 02:47:22.860
This is wrong.

02:47:22.860 --> 02:47:25.840
Black swans are only
unpredictable events

02:47:25.840 --> 02:47:28.730
PG and E is taking fires
like Kincade and Zogg

02:47:28.730 --> 02:47:30.360
and calling them black swans

02:47:30.360 --> 02:47:34.310
to avoid accountability and liability.

02:47:34.310 --> 02:47:36.316
PG and E changes
the goalposts every time

02:47:36.316 --> 02:47:40.080
there are failures detected
by a court or this Commission.

02:47:40.080 --> 02:47:43.900
In one hour, PG and E is
being arraigned about 10 minutes

02:47:43.900 --> 02:47:45.100
from my burned down house

02:47:45.100 --> 02:47:47.410
and where I have
evacuated three other times

02:47:47.410 --> 02:47:49.130
due to PG and E fires.

02:47:49.130 --> 02:47:52.290
And I expect a similar range
of excuses will be leveraged

02:47:52.290 --> 02:47:53.810
in that proceeding.

02:47:53.810 --> 02:47:57.420
If the Commission or Judge
Alsup or interveners like me,

02:47:57.420 --> 02:47:59.330
micromanage PG and E,

02:47:59.330 --> 02:48:01.807
I believe we are in
a lose lose situation.

02:48:01.807 --> 02:48:04.820
Let PG and E call it
substantial compliance

02:48:04.820 --> 02:48:08.060
or a black Swan or
Turkey on Thanksgiving,

02:48:08.060 --> 02:48:10.650
the Commission shouldn't
care or try to parse out

02:48:10.650 --> 02:48:13.310
fact from fiction and
PG and E statements.

02:48:13.310 --> 02:48:18.290
Results, results, results,
nothing else matters.

02:48:18.290 --> 02:48:20.955
One last point, the fact
that these trees fall outside

02:48:20.955 --> 02:48:22.640
their right of way

02:48:22.640 --> 02:48:24.453
means that they need to tie their plans

02:48:24.453 --> 02:48:27.610
to the community
wildfire protection plans.

02:48:27.610 --> 02:48:31.760
And PG and E has
made no effort to do that.

02:48:31.760 --> 02:48:33.710
Please take these under consideration.

02:48:33.710 --> 02:48:35.410
Thank you very much for your time.

02:48:40.000 --> 02:48:40.833
<v Shelby>Thank you.</v>

02:48:40.833 --> 02:48:44.760
Our next public comment
comes from Michael Agury.

02:48:44.760 --> 02:48:46.550
Please state your organization.

02:48:46.550 --> 02:48:47.453
Your line is open.

02:48:48.370 --> 02:48:49.430
<v Michael>Good morning.</v>

02:48:49.430 --> 02:48:53.493
I'm an attorney for Amigi
appearing before Judge Alsup.

02:48:54.410 --> 02:48:56.070
I wanna remind the listeners

02:48:56.980 --> 02:49:01.980
that the reason that PG
and E has to shut off power

02:49:02.050 --> 02:49:06.230
is because it hasn't obeyed
fire safety rules and laws

02:49:06.230 --> 02:49:07.153
for years.

02:49:08.040 --> 02:49:11.533
And the CPUC has let
them get away with that.

02:49:12.810 --> 02:49:15.723
That's left us with two choices.

02:49:16.670 --> 02:49:20.030
We can have electricity with fires

02:49:20.030 --> 02:49:23.093
or no electricity without fires.

02:49:24.010 --> 02:49:28.290
Your response has been to
issue PG and E licenses to burn

02:49:28.290 --> 02:49:29.923
called safety certificates.

02:49:30.890 --> 02:49:33.260
Your response to Judge Alsup's efforts

02:49:33.260 --> 02:49:35.870
to make PG and E improve safety

02:49:35.870 --> 02:49:39.200
is the forum you provided PG and E today

02:49:39.200 --> 02:49:44.160
to make a self-serving
presentation with no sworn testimony,

02:49:44.160 --> 02:49:47.763
no cross examination,
no evidence-based record.

02:49:48.640 --> 02:49:53.393
Instead of charades
like what went on today,

02:49:54.300 --> 02:49:58.710
make safety certificates
subject to evidence based

02:49:58.710 --> 02:50:02.090
administrative hearings with full rights

02:50:02.090 --> 02:50:03.453
of cross examination.

02:50:04.810 --> 02:50:07.390
I hope the Judge Alsup has watched

02:50:07.390 --> 02:50:10.240
this absurd exercise today

02:50:10.240 --> 02:50:13.060
and I hope that he will learn from it

02:50:13.060 --> 02:50:18.060
that you cannot trust the
CPUC to step up and to do its job.

02:50:19.940 --> 02:50:20.773
Thank you.

02:50:26.240 --> 02:50:27.073
<v Shelby>Thank you.</v>

02:50:27.073 --> 02:50:28.860
Our next public comment
comes from Dan Courtney.

02:50:28.860 --> 02:50:30.210
Please state your organization.

02:50:30.210 --> 02:50:31.133
Your line is open.

02:50:31.980 --> 02:50:34.513
<v Dan>I'm a member of
the Sierra Club wildfire.</v>

02:50:35.410 --> 02:50:38.395
Sorry, Sierra Club Utility
Wildfire Prevention Task Force

02:50:38.395 --> 02:50:41.160
but I'm speaking today
strictly as a property owner

02:50:41.160 --> 02:50:43.600
in Alameda County.

02:50:43.600 --> 02:50:47.060
We have a family
property on the outskirts

02:50:47.060 --> 02:50:48.370
of Yosemite National Park

02:50:48.370 --> 02:50:50.830
surrounded by a
Stanislaus National Forest

02:50:50.830 --> 02:50:55.803
with many old growth trees
are 400 or 500 years old.

02:50:58.390 --> 02:51:02.470
So I've been paying
attention to what's going on

02:51:02.470 --> 02:51:04.450
you know, for the past year or two

02:51:04.450 --> 02:51:08.390
since we had hundreds
of trees on our properties

02:51:08.390 --> 02:51:10.490
marked for removal during

02:51:10.490 --> 02:51:14.380
the enhanced vegetation
management markings inspections

02:51:14.380 --> 02:51:17.097
that happened in fall of 2019

02:51:17.097 --> 02:51:20.110
and what I've learned so
far with doing a lot of research

02:51:20.110 --> 02:51:21.820
and participating a lot of meetings

02:51:21.820 --> 02:51:25.570
and reading a lot of
information is that...

02:51:25.570 --> 02:51:30.570
Because I wondered, why are
trees that are healthy and green

02:51:30.590 --> 02:51:34.142
and 150 feet away from a power line,

02:51:34.142 --> 02:51:36.690
how there was a threat to start a fire?

02:51:36.690 --> 02:51:39.383
And what I learned is
it's not because the trees

02:51:39.383 --> 02:51:42.110
it's because they have these old wires

02:51:42.110 --> 02:51:44.650
like in our case there's 70 years old

02:51:44.650 --> 02:51:45.900
and they're uninsulated,

02:51:45.900 --> 02:51:50.400
they have like 14 splices,
for example along the span,

02:51:50.400 --> 02:51:52.193
that's closest to our cabin.

02:51:53.570 --> 02:51:56.470
The power poles are
short, they're wooden,

02:51:56.470 --> 02:51:58.560
they're burned, badly burned.

02:51:58.560 --> 02:52:02.170
They were burned in The Rim
Fire, which was eight years ago

02:52:02.170 --> 02:52:04.310
and still not been replaced.

02:52:04.310 --> 02:52:05.760
They're looking now to replace them

02:52:05.760 --> 02:52:06.880
but they're gonna replace them

02:52:06.880 --> 02:52:09.810
with the same short end power poles.

02:52:09.810 --> 02:52:12.750
And they're not gonna change the wires,

02:52:12.750 --> 02:52:15.160
instead they're gonna put up bare wires.

02:52:15.160 --> 02:52:18.100
And so obviously that's the issue.

02:52:18.100 --> 02:52:19.557
The issue is the old equipment,

02:52:19.557 --> 02:52:24.550
the decades and decades of
deferred maintenance by PG and E

02:52:24.550 --> 02:52:27.400
and my family has been
a shareholder for 50 years

02:52:27.400 --> 02:52:29.254
and we appreciate the dividends

02:52:29.254 --> 02:52:32.730
but now really don't
appreciate them as much

02:52:32.730 --> 02:52:35.020
knowing that they were earned

02:52:35.020 --> 02:52:38.810
at the cost of making virtually

02:52:38.810 --> 02:52:41.460
all parts of Northern
California extremely dangerous.

02:52:42.420 --> 02:52:46.690
And so the focus is all
centered on trees, County trees

02:52:48.170 --> 02:52:51.973
and in response to Judge
Alsup's proposed order.

02:52:54.809 --> 02:52:57.659
So what's the time limit or
how much time do I have left?

02:53:02.200 --> 02:53:03.300
Hello, I heard a beep.

02:53:04.183 --> 02:53:06.760
<v Shelby>You have two minutes sir.</v>

02:53:06.760 --> 02:53:09.580
<v Dan>Sorry, how much time left?</v>

02:53:09.580 --> 02:53:11.240
<v Shelby>No, your time is up.</v>

02:53:11.240 --> 02:53:14.550
The bell sounded at the two minute mark.

02:53:14.550 --> 02:53:15.920
<v Dan>Oh I didn't realize
it was two minutes.</v>

02:53:15.920 --> 02:53:18.560
I would just like to
close with one sentence

02:53:18.560 --> 02:53:23.380
and that is, please start
focusing on ordering PG and E

02:53:23.380 --> 02:53:26.580
to modernize and upgrade its equipment.

02:53:26.580 --> 02:53:28.333
And also I think there
should be a program

02:53:28.333 --> 02:53:31.400
to look at cost sharing
between property owners

02:53:31.400 --> 02:53:33.384
who are willing to pay
for under grounding

02:53:33.384 --> 02:53:35.860
but don't wanna foot the whole cost.

02:53:35.860 --> 02:53:38.070
And that would be beneficial to everyone

02:53:38.070 --> 02:53:40.260
in terms of accelerating the speed

02:53:40.260 --> 02:53:43.610
at which we have safe
electricity through the mountains.

02:53:43.610 --> 02:53:45.708
PG and E should do
at least a 50, 50 split

02:53:45.708 --> 02:53:47.634
with property owners.

02:53:47.634 --> 02:53:50.800
And then we could get
some of these areas improved.

02:53:50.800 --> 02:53:51.990
Thank you for your time

02:53:51.990 --> 02:53:53.990
and for your attention to these matters.

02:53:57.000 --> 02:53:58.000
<v Shelby>I currently have no other</v>

02:53:58.000 --> 02:53:59.353
public comments in queue.

02:54:12.830 --> 02:54:13.835
<v Joyce>Okay, well,
we could go back</v>

02:54:13.835 --> 02:54:17.450
to the presentation slides

02:54:17.450 --> 02:54:21.550
and there's a closing slide at the end

02:54:21.550 --> 02:54:22.993
right before the appendix.

02:54:37.731 --> 02:54:42.398
I think you need to advance
to another couple of slides.

02:54:44.610 --> 02:54:45.920
Maybe go to the end.

02:54:55.266 --> 02:54:57.220
There we go, yeah. Thank you.

02:54:57.220 --> 02:55:01.730
I wanted to thank everyone
who participated today

02:55:01.730 --> 02:55:03.830
and provided their
insights and perspectives

02:55:03.830 --> 02:55:05.053
during public comment.

02:55:06.790 --> 02:55:09.800
The Commission and its staff
will consider the information

02:55:09.800 --> 02:55:13.300
and act appropriately in
particular, given the circumstances

02:55:14.240 --> 02:55:16.207
and considering the
Federal Probation Proceeding

02:55:16.207 --> 02:55:19.640
and the workshop information provided.

02:55:19.640 --> 02:55:24.240
I wanted to reinforce
that if parties, stakeholders

02:55:24.240 --> 02:55:27.730
and members of the public
wish to provide written comments

02:55:27.730 --> 02:55:28.900
then please provide them.

02:55:28.900 --> 02:55:31.370
And in the next five business days

02:55:31.370 --> 02:55:33.976
by April 27th at five o'clock,

02:55:33.976 --> 02:55:37.830
please serve the written
comments to the three proceedings

02:55:37.830 --> 02:55:40.490
that were given notice of the workshop.

02:55:40.490 --> 02:55:42.470
And this final slide provides a link

02:55:42.470 --> 02:55:45.293
to the Commission
webpage related to service list.

02:55:48.750 --> 02:55:53.750
I think, unless there's
any other closing remarks,

02:55:55.549 --> 02:55:59.513
we can conclude today's workshop.

02:56:05.140 --> 02:56:09.223
And thank you all again
for your participation.