WEBVTT

00:00:00.100 --> 00:00:02.240
<v Announcer>To you
by adminmonitor.com.</v>

00:00:02.240 --> 00:00:03.770
We'll begin momentarily.

00:00:03.770 --> 00:00:05.170
Thank you for your patience.

00:00:16.450 --> 00:00:17.283
<v Operator>Welcome</v>

00:00:17.283 --> 00:00:19.370
to the California Public
Utilities Commission.

00:00:19.370 --> 00:00:23.500
This is the Remote
Participation Joint IOUs Workshop

00:00:23.500 --> 00:00:27.040
on the 2021 Public Safety
Power Shutoff Events.

00:00:27.040 --> 00:00:28.290
Thank you, you may begin.

00:00:31.330 --> 00:00:32.163
<v ->All right.</v>

00:00:32.163 --> 00:00:36.550
We're about 1:09, so let's
go ahead and get started.

00:00:36.550 --> 00:00:39.360
Thank you for joining us
on this Friday afternoon.

00:00:39.360 --> 00:00:40.760
My name is Steven Klaiber.

00:00:40.760 --> 00:00:42.580
I'm a Senior Regulatory Analyst

00:00:42.580 --> 00:00:45.820
in SED Wildfire Safety
Enforcement Branch,

00:00:45.820 --> 00:00:48.200
and I will be your facilitator today.

00:00:48.200 --> 00:00:49.470
This will be day two

00:00:49.470 --> 00:00:52.260
of the Public Briefings
on Utility Execution

00:00:52.260 --> 00:00:55.040
of 2021 PSPS Events.

00:00:55.040 --> 00:00:58.280
In addition to looking back
at the 2021 PSPS Events,

00:00:58.280 --> 00:01:01.190
the utilities will also present
on the lessons learned

00:01:01.190 --> 00:01:02.790
and improvements planned

00:01:02.790 --> 00:01:06.400
in preparation of the
2022 Wildfire Season.

00:01:06.400 --> 00:01:07.700
To recap day one,

00:01:07.700 --> 00:01:11.720
we heard presentations
from PG&amp;E, Liberty Utilities

00:01:11.720 --> 00:01:13.340
and the Civic Court,

00:01:13.340 --> 00:01:16.003
as well as public comments
at the end of the session.

00:01:16.880 --> 00:01:17.940
Reviewing the agenda,

00:01:17.940 --> 00:01:21.520
we will start with opening
remarks from the virtual Dias.

00:01:21.520 --> 00:01:24.630
You will hear remarks from
CPUC President Reynolds,

00:01:24.630 --> 00:01:27.780
Commissioner Houck,
Commissioner Jon Reynolds,

00:01:27.780 --> 00:01:31.020
Commissioner Shiroma and
Commissioner Rechtschaffen.

00:01:31.020 --> 00:01:34.260
Additionally, we have Mike
Massone from Cal OES,

00:01:34.260 --> 00:01:36.570
Daniel Berlant from Cal Fire

00:01:36.570 --> 00:01:40.010
and Caroline Thomas
Jacobs from Energy Safety.

00:01:40.010 --> 00:01:41.750
Our first presentation will be held

00:01:41.750 --> 00:01:45.460
by SCE and led by VP Jill Anderson.

00:01:45.460 --> 00:01:48.617
Our second and last
presentation of the workshop

00:01:48.617 --> 00:01:50.967
will be held by SDG&amp;E
and led by Vice President

00:01:52.264 --> 00:01:53.660
of Electric Operations, Kevin Geraghty.

00:01:53.660 --> 00:01:55.417
Each utility will be allotted an hour,

00:01:55.417 --> 00:01:58.700
and this will account for
questions asked by our panel.

00:01:58.700 --> 00:02:01.170
We open the phone line
and allow for public comments

00:02:01.170 --> 00:02:03.341
after both utilities have presented.

00:02:03.341 --> 00:02:06.780
We will end with closing
remarks from our panel.

00:02:06.780 --> 00:02:07.613
That being said,

00:02:07.613 --> 00:02:09.010
I will hand it over to
President Reynolds

00:02:09.010 --> 00:02:10.053
for opening remarks.

00:02:12.280 --> 00:02:13.910
<v ->Thank you, Steven.</v>

00:02:13.910 --> 00:02:17.460
I did wanna welcome
everyone here today to day two

00:02:17.460 --> 00:02:21.273
of our two-day workshop on
Public Safety Power Shutoffs,

00:02:22.325 --> 00:02:24.670
and I'm very pleased
to share the virtual Dias

00:02:24.670 --> 00:02:27.530
with CPUC's sister agencies.

00:02:27.530 --> 00:02:29.613
It's an honor to be
here with all of you.

00:02:30.530 --> 00:02:33.720
And then I also wanted to
recognize that this is our time

00:02:33.720 --> 00:02:38.720
to hear a report from our
IOUs on their efforts to improve

00:02:40.450 --> 00:02:43.320
the performance of PSPS events.

00:02:43.320 --> 00:02:46.463
So this is a very
important workshop to us.

00:02:46.463 --> 00:02:51.463
It's critical to hear
efforts to recognize both

00:02:52.730 --> 00:02:55.820
the effectiveness of PSPS as a tool,

00:02:55.820 --> 00:02:57.950
but also maybe even more importantly,

00:02:57.950 --> 00:03:01.340
the impact the tool has
on customers and efforts

00:03:01.340 --> 00:03:03.203
to mitigate those impacts.

00:03:04.320 --> 00:03:09.260
We have been working with
the utilities and emphasizing

00:03:09.260 --> 00:03:12.140
that PSPS should
be a tool of last resort.

00:03:12.140 --> 00:03:17.140
We continue to look forward
to hearing reporting on efforts

00:03:17.750 --> 00:03:21.610
to make sure the tool is made smaller,

00:03:21.610 --> 00:03:25.490
smaller scope, smaller
scale, less on impacts.

00:03:25.490 --> 00:03:29.130
And so we'll be listening
very carefully for those actions

00:03:29.130 --> 00:03:31.420
that the utilities have taken.

00:03:31.420 --> 00:03:33.970
I'm really hopeful
that through this event

00:03:33.970 --> 00:03:35.440
and follow-up events,

00:03:35.440 --> 00:03:39.730
we can hear that the utilities
are working hard to get

00:03:39.730 --> 00:03:42.271
the protections of customers right,

00:03:42.271 --> 00:03:47.271
to move towards a day when
hopefully PSPS will not be a tool

00:03:47.670 --> 00:03:52.670
in our toolbox, and that
we can use today to share

00:03:52.950 --> 00:03:54.850
the lessons learned, what's working,

00:03:54.850 --> 00:03:58.950
what's not working, and a
critique of current practices.

00:03:58.950 --> 00:04:01.680
We can improve of
oversight and accountability,

00:04:01.680 --> 00:04:04.900
and also lead to stronger
lines of communication

00:04:04.900 --> 00:04:08.010
and improvement of
joint operations of utilities,

00:04:08.010 --> 00:04:09.824
government entities,

00:04:09.824 --> 00:04:12.720
community-based
organizations, and others.

00:04:12.720 --> 00:04:16.050
I did wanna also thank Commission staff,

00:04:16.050 --> 00:04:18.950
Kevin Klaiber, our moderator today,

00:04:18.950 --> 00:04:20.640
as well as Tony Noel,

00:04:20.640 --> 00:04:23.880
who did a lot of work to
put this workshop together.

00:04:23.880 --> 00:04:25.225
Thanks.

00:04:25.225 --> 00:04:26.395
Thanks to both of them

00:04:26.395 --> 00:04:28.860
for their efforts in
organizing this workshop.

00:04:28.860 --> 00:04:29.760
And with that,

00:04:29.760 --> 00:04:32.960
I will turn it over to my
fellow Commissioners

00:04:32.960 --> 00:04:34.580
for opening statements.

00:04:45.247 --> 00:04:48.060
Commissioner
Rechtschaffen, would you like?

00:04:48.060 --> 00:04:49.460
<v ->I have no opening remarks.</v>

00:04:50.600 --> 00:04:52.360
<v ->And I have no
opening remarks either.</v>

00:04:52.360 --> 00:04:53.710
This is Commissioner Houck.

00:04:56.640 --> 00:04:57.720
<v ->This is Shiroma.</v>

00:04:57.720 --> 00:05:02.530
I just wanted to say that it was in 2019

00:05:03.938 --> 00:05:04.810
that I had a chance to visit

00:05:04.810 --> 00:05:09.663
the San Diego Gas
Electric Emergency Center

00:05:10.610 --> 00:05:14.630
from which it operates

00:05:14.630 --> 00:05:19.620
its Public Safety Power Shutoff efforts.

00:05:19.620 --> 00:05:24.290
It was very insightful to hear
what they have been doing

00:05:25.881 --> 00:05:30.173
and lessons learned
over the years for them.

00:05:31.053 --> 00:05:31.886
And then (clears throat)

00:05:31.886 --> 00:05:35.820
through the Southern California
Edison General Rate Case,

00:05:35.820 --> 00:05:40.820
I learned many details about
what Southern California Edison

00:05:42.400 --> 00:05:43.730
is doing and of course

00:05:43.730 --> 00:05:45.960
through their wildfire mitigation plans.

00:05:45.960 --> 00:05:48.920
So I look forward to
hearing this update today

00:05:48.920 --> 00:05:52.540
on how last year
went for these utilities

00:05:52.540 --> 00:05:55.010
and what they foresee for the future.

00:05:55.010 --> 00:05:55.843
Thank you.

00:05:59.549 --> 00:06:02.077
<v ->And I have no
opening remarks as well.</v>

00:06:02.077 --> 00:06:02.910
Thank you.

00:06:05.592 --> 00:06:06.560
<v ->I wanted to check
with Frank and Caroline,</v>

00:06:06.560 --> 00:06:08.653
did you guys have any opening remarks?

00:06:10.980 --> 00:06:11.813
<v ->This is Caroline.</v>

00:06:11.813 --> 00:06:13.047
I just had a few things,.

00:06:14.900 --> 00:06:17.510
So well, thank you, President
Reynolds and Commissioners.

00:06:17.510 --> 00:06:20.270
Really appreciate the
opportunity to join the Commission,

00:06:20.270 --> 00:06:22.610
Cal OES and Cal Fire today

00:06:22.610 --> 00:06:25.350
to hear from San Diego and
Southern California Edison

00:06:25.350 --> 00:06:28.670
on PSPS, both their execution
in 2021 and their plans

00:06:28.670 --> 00:06:30.343
for 2022 and improvement.

00:06:31.390 --> 00:06:33.371
As President Reynold said,

00:06:33.371 --> 00:06:35.540
while PSPS has been used to
reduce the risk of fires caused

00:06:35.540 --> 00:06:36.910
by utility infrastructure,

00:06:36.910 --> 00:06:39.120
we know it comes that
high price to customers

00:06:39.120 --> 00:06:40.740
and community members.

00:06:40.740 --> 00:06:44.040
Each use of PSPS poses
serious risk to life safety

00:06:44.040 --> 00:06:46.540
for those at-risk and
vulnerable community members,

00:06:46.540 --> 00:06:49.630
as well as significant
impacts on quality of life.

00:06:49.630 --> 00:06:52.550
For these reasons, PSPS
must continue to be a use

00:06:52.550 --> 00:06:54.890
of the mitigation of last for resorts.

00:06:54.890 --> 00:06:56.450
Through the wildfire mitigation plans,

00:06:56.450 --> 00:06:59.310
Energy Safety remains
focused on how each of you

00:06:59.310 --> 00:07:02.057
are taking action to reduce the scale,

00:07:02.057 --> 00:07:03.990
scope and frequency of its use.

00:07:03.990 --> 00:07:06.440
It's our expectation that
each of you will continue

00:07:06.440 --> 00:07:08.100
to reimagine how you build,

00:07:08.100 --> 00:07:10.130
operate and maintain the infrastructure

00:07:10.130 --> 00:07:13.737
so is not to be reliant
on PSPS as a future

00:07:13.737 --> 00:07:15.303
for mitigation tactic.

00:07:17.162 --> 00:07:18.380
And while it is a short-term tactic,

00:07:18.380 --> 00:07:21.890
it should and cannot be
considered a long-term strategy.

00:07:21.890 --> 00:07:24.980
In our 2021 wildfire
mitigation plan evaluations,

00:07:24.980 --> 00:07:26.823
we focused on a few critical areas,

00:07:28.076 --> 00:07:30.130
how your wildfire mitigation initiatives

00:07:30.130 --> 00:07:33.820
were driving towards the
elimination of use of PSPS,

00:07:33.820 --> 00:07:36.510
how you were doing what you
were doing to reduce the scale,

00:07:36.510 --> 00:07:39.200
scope and frequency with
an emphasis on frequency

00:07:39.200 --> 00:07:43.630
of PSPS events and how
you're improving your forecasting

00:07:43.630 --> 00:07:46.640
for improving the accuracy
of the number of times

00:07:46.640 --> 00:07:49.560
you're doing PSPS and the need for PSPS.

00:07:49.560 --> 00:07:53.480
So in 2022, we will be
following up on all these areas

00:07:53.480 --> 00:07:56.366
in our wild fire
mitigation plan evaluation

00:07:56.366 --> 00:07:58.833
with particular attention

00:07:58.833 --> 00:08:00.640
to the frequently, impacted and circuit.

00:08:00.640 --> 00:08:02.310
I look forward to today's briefing

00:08:02.310 --> 00:08:04.863
from San Diego and
Southern California Edison.

00:08:06.040 --> 00:08:07.610
And I would, I do wanna just call out,

00:08:07.610 --> 00:08:10.138
I'm gonna have to
step out at two o'clock

00:08:10.138 --> 00:08:11.590
for a very short
meeting that I must take,

00:08:11.590 --> 00:08:13.580
but I did wanna let you know
I have reviewed the materials

00:08:13.580 --> 00:08:15.750
and I'll just catch back
up wherever you are

00:08:15.750 --> 00:08:16.970
in the presentation.

00:08:16.970 --> 00:08:18.220
So look forward to today.

00:08:19.150 --> 00:08:20.900
Thank you, President.

00:08:23.220 --> 00:08:24.690
<v ->Thank you, Director Jacobs.</v>

00:08:24.690 --> 00:08:25.853
With that being said,

00:08:27.159 --> 00:08:31.713
let's open up the line to SCE
Vice President, Jill Anderson.

00:08:33.320 --> 00:08:34.170
<v ->Thank you so much.</v>

00:08:34.170 --> 00:08:35.620
I'm happy to get us started.

00:08:35.620 --> 00:08:38.952
So I know we provided some material,

00:08:38.952 --> 00:08:41.030
and I'll be sharing that as we go.

00:08:41.030 --> 00:08:43.150
Let me first just say, good afternoon,

00:08:43.150 --> 00:08:45.850
President Reynolds
and other Commissioners

00:08:45.850 --> 00:08:49.280
along with Director Thomas
Jacobs and the other leadership

00:08:49.280 --> 00:08:52.540
that we have here from OES and Cal Fire

00:08:52.540 --> 00:08:55.283
and our community members and customers.

00:08:55.283 --> 00:08:58.350
So we appreciate the invitation
and the opportunity today

00:08:58.350 --> 00:09:01.450
to share what we have
been doing directly in line

00:09:01.450 --> 00:09:03.250
with the opening
remarks that we just heard

00:09:03.250 --> 00:09:05.750
from President Reynolds
and Director Thomas Jacobs

00:09:06.856 --> 00:09:09.430
around what we are doing
to reduce the frequency

00:09:09.430 --> 00:09:11.710
and the impacts of PSPS,

00:09:11.710 --> 00:09:13.180
how we performed last year

00:09:13.180 --> 00:09:14.560
and what we're doing going forward.

00:09:14.560 --> 00:09:17.120
So I think you're gonna
hear all of that from us today.

00:09:17.120 --> 00:09:19.330
Let me also introduce
the other people from SCE

00:09:19.330 --> 00:09:20.630
who are with me.

00:09:20.630 --> 00:09:23.100
You're also gonna
hear from Erik Takayesu,

00:09:23.100 --> 00:09:26.200
who's our Vice President of
Asset Strategy and Planning.

00:09:26.200 --> 00:09:28.880
You'll hear from Katie Sloan,
who's our Vice President

00:09:28.880 --> 00:09:31.730
of Customer Programs and Services,

00:09:31.730 --> 00:09:34.870
Tom Brady, who leads
our PSPS Readiness Group,

00:09:34.870 --> 00:09:36.210
and he's a Principal Manager

00:09:36.210 --> 00:09:38.295
in our Emergency
Operations Organization,

00:09:38.295 --> 00:09:41.790
and Michael B. Williams, who
is a Principal Manager for us

00:09:41.790 --> 00:09:43.430
in our business Customer Division.

00:09:43.430 --> 00:09:46.524
So we've really brought the experts here

00:09:46.524 --> 00:09:48.410
and we're looking
forward to sharing with you

00:09:48.410 --> 00:09:51.310
our progress and our
opportunities for improvement.

00:09:51.310 --> 00:09:54.700
Additionally, we have Terry
Ohanian, who's our Director

00:09:54.700 --> 00:09:56.660
of the Southeast
Distribution Construction

00:09:56.660 --> 00:09:57.650
and Maintenance Group,

00:09:57.650 --> 00:10:00.230
who I know that has spoken
to many of these events

00:10:00.230 --> 00:10:03.380
in the past, and Scott Scudder,
who's our Senior Manager

00:10:03.380 --> 00:10:07.172
of Business Process Improvement
in our PSPS Readiness Team.

00:10:07.172 --> 00:10:09.242
They are standing by
with us to make sure

00:10:09.242 --> 00:10:10.700
we can get the direct
answers to any questions

00:10:10.700 --> 00:10:12.050
that you wanna cover today.

00:10:13.110 --> 00:10:15.440
I'm just gonna start out
really by acknowledging

00:10:15.440 --> 00:10:19.140
that PSPS is very
difficult for our customers.

00:10:19.140 --> 00:10:21.990
I think President
Reynolds, you explained that

00:10:22.935 --> 00:10:27.890
as you did your introductory remarks,

00:10:27.890 --> 00:10:31.810
not, especially difficult
for vulnerable customers,

00:10:31.810 --> 00:10:34.060
but it is difficult for
all of our customers.

00:10:35.450 --> 00:10:37.767
I staff these events myself.

00:10:37.767 --> 00:10:40.667
We, Commissioner Shiroma,

00:10:40.667 --> 00:10:41.500
you mentioned the
Energy Operations Center,

00:10:41.500 --> 00:10:42.740
that's actually where I'm at today

00:10:43.720 --> 00:10:46.460
for, I had other meetings
here this morning, and so,

00:10:46.460 --> 00:10:50.400
but during these PSPS events,
I go out into the community.

00:10:50.400 --> 00:10:54.010
I was out on Thanksgiving at
our community crew vehicles

00:10:54.010 --> 00:10:56.170
where I'm interacting
directly with customers

00:10:56.170 --> 00:11:00.593
and I heard for first hand
the frustration, the anger,

00:11:02.905 --> 00:11:03.738
and we understand it, we understand

00:11:04.717 --> 00:11:06.350
it's certainly very
real for our customers.

00:11:06.350 --> 00:11:10.540
We are only doing PSPS
to reduce the wildfire risk

00:11:10.540 --> 00:11:14.420
to the communities, but to our
customers who are impacted,

00:11:14.420 --> 00:11:16.920
they feel the extended outage,

00:11:16.920 --> 00:11:19.650
the extreme personal hardship,

00:11:19.650 --> 00:11:23.040
and they're not, us telling
them it's a last resort tool

00:11:23.040 --> 00:11:27.240
is usually not sufficient for
us to satisfy their concerns.

00:11:27.240 --> 00:11:32.070
So we continue to make sure
that anytime we're using PSPS,

00:11:32.070 --> 00:11:34.470
it is only at a time of last resort.

00:11:34.470 --> 00:11:37.530
And I'm gonna show
some statistics with you

00:11:37.530 --> 00:11:39.580
this afternoon and
where you'll see that.

00:11:40.557 --> 00:11:42.601
But while we're talking briefly here

00:11:42.601 --> 00:11:43.848
about Thanksgiving Event,

00:11:43.848 --> 00:11:46.258
and I'm sure we'll talk more
about that in our remarks,

00:11:46.258 --> 00:11:47.640
'cause it was our
largest event last year,

00:11:47.640 --> 00:11:50.682
I also wanna acknowledge all of you,

00:11:50.682 --> 00:11:53.620
the CPUC, OES, Cal OES, Cal Fire,

00:11:53.620 --> 00:11:57.657
all the local government,
when we initiate event,

00:11:57.657 --> 00:12:01.050
we very much realize and
appreciate that it creates work

00:12:01.050 --> 00:12:04.220
and activity for many
other organizations.

00:12:04.220 --> 00:12:06.740
And many of your team
members had to also give up

00:12:06.740 --> 00:12:09.610
your holiday and time with
your families in order to support

00:12:09.610 --> 00:12:11.430
your communities and
the role you play with this,

00:12:11.430 --> 00:12:14.280
and we're very grateful for that.

00:12:14.280 --> 00:12:18.140
So we are gonna talk through
some of our accomplishments,

00:12:18.140 --> 00:12:21.070
and some of the things that
we've been able to improve

00:12:21.070 --> 00:12:22.790
and things that we're proud of.

00:12:22.790 --> 00:12:24.740
We're also gonna talk
about upcoming work we have

00:12:24.740 --> 00:12:28.000
because we know that
we have more work to do.

00:12:28.000 --> 00:12:30.600
And we're also gonna be very
transparent and share some

00:12:30.600 --> 00:12:34.320
of the lessons learned, some
of the areas where we missed.

00:12:34.320 --> 00:12:39.320
We, as I said, we are only
using PSPS when we know

00:12:39.650 --> 00:12:41.810
that it's necessary to
protect public safety,

00:12:41.810 --> 00:12:42.660
when we're talking

00:12:42.660 --> 00:12:46.170
about being in a very dangerous
environmental condition

00:12:46.170 --> 00:12:48.480
posing significant risks to wildfire,

00:12:48.480 --> 00:12:53.270
but our goal is to make sure
that we are reducing the use

00:12:53.270 --> 00:12:56.110
of PSPS year over year,

00:12:56.110 --> 00:12:58.868
we're continuing to improve
our management of it,

00:12:58.868 --> 00:13:01.640
that we continue to treat our
customers with transparency,

00:13:01.640 --> 00:13:05.690
with respect to appreciate
that any outage of any length

00:13:05.690 --> 00:13:08.540
is too long for most customers.

00:13:08.540 --> 00:13:10.510
And we wanna make sure that
we're providing them the tools

00:13:10.510 --> 00:13:12.490
they need to manage through those.

00:13:12.490 --> 00:13:14.803
So with that, I know we
shared a some material

00:13:14.803 --> 00:13:18.430
and I think it'd probably be
helpful if we could display it

00:13:18.430 --> 00:13:20.933
so that I could talk through
a couple of the numbers.

00:13:22.470 --> 00:13:23.842
Thank you.

00:13:23.842 --> 00:13:25.333
So if you wanna go to the next slide.

00:13:26.790 --> 00:13:28.282
Okay.

00:13:28.282 --> 00:13:31.160
So Erik is gonna speak
after me and he's gonna talk

00:13:31.160 --> 00:13:34.250
a little bit about the grid
hardening that we've done,

00:13:34.250 --> 00:13:36.630
but I start out by emphasizing some

00:13:36.630 --> 00:13:38.260
of these top line numbers.

00:13:38.260 --> 00:13:42.010
If we look at the top
left here, you see 45%.

00:13:42.010 --> 00:13:47.010
This is a number that we see
that we reduced in PSPS usage,

00:13:48.690 --> 00:13:51.480
that reduction of the duration in 2021

00:13:51.480 --> 00:13:54.730
based on all the mitigations
that we put in place.

00:13:54.730 --> 00:13:57.010
Because of the work
that we did that year,

00:13:58.711 --> 00:14:02.427
that last year, we saw there
were 45% fewer customer minutes

00:14:03.594 --> 00:14:05.790
of outage than there would've been

00:14:05.790 --> 00:14:07.320
if we hadn't done the
grid hardening work.

00:14:07.320 --> 00:14:10.200
We also looked at specific
locations that we're targeting,

00:14:10.200 --> 00:14:12.310
and I heard Director Thomas Jacobs,

00:14:12.310 --> 00:14:14.410
you talked about
frequently impacted circuits.

00:14:14.410 --> 00:14:18.190
So when looked specifically
at frequently impacted circuits,

00:14:18.190 --> 00:14:21.620
we reduced the customer
minutes of interruption

00:14:21.620 --> 00:14:26.010
by the number on the
bottom left there, 73%.

00:14:26.010 --> 00:14:29.530
We also reduced the
scope of the interruptions.

00:14:29.530 --> 00:14:32.640
And so looking at 72%,

00:14:32.640 --> 00:14:37.080
which is the frequency
on the circuits themselves,

00:14:37.080 --> 00:14:40.621
and instrumental to all this reduction,

00:14:40.621 --> 00:14:42.020
as I talked about, was grid hardening.

00:14:42.020 --> 00:14:43.883
And so right there in the top middle,

00:14:45.287 --> 00:14:47.670
we installed more than 1,500
miles of covered conductor,

00:14:47.670 --> 00:14:48.840
and almost half of that,

00:14:48.840 --> 00:14:51.470
we deployed on
frequently impacted circuits.

00:14:51.470 --> 00:14:55.460
And we're able to look at
event by event and demonstrate

00:14:55.460 --> 00:14:57.470
that if not for cover conductor,

00:14:57.470 --> 00:15:00.200
additional customers would have been out

00:15:00.200 --> 00:15:01.500
during those wind storms.

00:15:01.500 --> 00:15:05.500
So we're very pleased with
the progress that we've seen.

00:15:05.500 --> 00:15:08.563
And I think the numbers
here tell a very positive story.

00:15:09.640 --> 00:15:14.640
Most significant when I think
about 2021 is the outcome

00:15:14.800 --> 00:15:16.360
of keeping our communities safe.

00:15:16.360 --> 00:15:19.890
So we did not have any
significant utility-caused ignitions

00:15:19.890 --> 00:15:21.723
in our service area in 2021.

00:15:23.250 --> 00:15:27.993
The next thing I'd like to
review is on the next slide,

00:15:28.960 --> 00:15:31.280
and here's some of
our top line achievement

00:15:31.280 --> 00:15:35.400
when we think about how we
are working with our customers

00:15:35.400 --> 00:15:36.790
and helping inform our customers,

00:15:36.790 --> 00:15:39.061
helping get our customers ready

00:15:39.061 --> 00:15:40.747
for extreme weather events and outages.

00:15:40.747 --> 00:15:42.900
And you're gonna hear a little
more from Katie and Michael

00:15:42.900 --> 00:15:44.840
who are gonna break
down these in more detail,

00:15:44.840 --> 00:15:47.550
but the overarching message is that this

00:15:47.550 --> 00:15:49.810
has been a tremendous
area of focus for us.

00:15:49.810 --> 00:15:52.020
It's something we work on year round.

00:15:52.020 --> 00:15:55.040
Not only are we trying
to mitigate the use

00:15:55.040 --> 00:15:58.060
of the PSPS themselves,

00:15:58.060 --> 00:16:02.760
but also looking at the breadth
of our efforts in connecting

00:16:02.760 --> 00:16:06.150
with customers, making sure
that our customers are prepared.

00:16:06.150 --> 00:16:08.200
Some of the stats we
have here is that we held

00:16:08.200 --> 00:16:12.170
over 100 meetings with our
local government and customers.

00:16:12.170 --> 00:16:15.871
We, all of these are attended
by people like me in roles

00:16:15.871 --> 00:16:18.420
like I have in other executives.

00:16:18.420 --> 00:16:22.020
We also had more than 2,700 visitors

00:16:22.020 --> 00:16:25.250
to our community care resource centers.

00:16:25.250 --> 00:16:28.860
And we surveyed these
customers after they joined one

00:16:28.860 --> 00:16:30.870
of their either community crew vehicle

00:16:30.870 --> 00:16:32.820
or one of our resource centers,

00:16:32.820 --> 00:16:36.010
and though, and I told
you, I meet with them myself.

00:16:36.010 --> 00:16:38.490
I go out to these locations regularly,

00:16:38.490 --> 00:16:40.300
and as frustrated as they are,

00:16:40.300 --> 00:16:43.390
in the surveys that we've
received back from customers,

00:16:43.390 --> 00:16:46.860
we got an overall
rating of 8.8 out of 10.

00:16:46.860 --> 00:16:51.520
And I can attest that what we
hear firsthand from verbatims

00:16:51.520 --> 00:16:55.220
is definite chow that
are presented by PSPS,

00:16:55.220 --> 00:16:58.750
but appreciation for the
services that are being provided

00:16:58.750 --> 00:17:00.330
at these customer care locations.

00:17:00.330 --> 00:17:03.530
So I think the investment
that we've done in partnership

00:17:03.530 --> 00:17:05.490
with the CPUC and that we're seeing

00:17:05.490 --> 00:17:08.610
working on with our other
sister utilities really pays off

00:17:08.610 --> 00:17:11.413
in the customer care that
goes on during these events.

00:17:13.925 --> 00:17:17.247
In the bottom right, you
see another metric here

00:17:18.390 --> 00:17:23.390
where we're talking about
our public safety partners

00:17:23.410 --> 00:17:27.150
and the readiness and
work that we did in 2021

00:17:27.150 --> 00:17:28.780
for making sure that we can work

00:17:28.780 --> 00:17:30.940
to manage emergencies together.

00:17:30.940 --> 00:17:34.160
And this is not just something
that is PSPS-related.

00:17:34.160 --> 00:17:36.510
When we think about the
outreach we do with customers,

00:17:36.510 --> 00:17:39.450
the work we're doing with
other public safety partners,

00:17:39.450 --> 00:17:40.970
we're thinking about all hazards.

00:17:40.970 --> 00:17:42.620
And so that's earthquakes

00:17:42.620 --> 00:17:46.150
or other climate
change-related extreme weather.

00:17:46.150 --> 00:17:47.310
And we are really,

00:17:47.310 --> 00:17:50.650
really gratified that we've
had such positive engagement

00:17:50.650 --> 00:17:51.900
throughout the last year.

00:17:53.081 --> 00:17:54.950
And so I'm gonna ask
Erik to pick up and walk you

00:17:54.950 --> 00:17:58.570
through a little more about
2021 in our action plan.

00:17:58.570 --> 00:18:01.510
And then I'm gonna come back at the end

00:18:01.510 --> 00:18:05.090
and add a little bit more
and be then be happy

00:18:05.090 --> 00:18:06.993
to beyond to take any questions.

00:18:09.810 --> 00:18:13.093
<v ->Thank you, Jill, and
good afternoon, everyone.</v>

00:18:14.233 --> 00:18:16.603
I think I'm gonna start off here.

00:18:18.493 --> 00:18:19.900
PSPS action plan
that we filed last year.

00:18:19.900 --> 00:18:22.663
So if you wouldn't mind
going to the next slide.

00:18:24.630 --> 00:18:26.100
So the action plan we filed,

00:18:26.100 --> 00:18:28.720
you'll see the five
sort of areas of focus

00:18:28.720 --> 00:18:29.780
in our work stream.

00:18:29.780 --> 00:18:33.280
And there was 132 steps altogether.

00:18:33.280 --> 00:18:35.040
We're nearly complete with the plan.

00:18:35.040 --> 00:18:37.690
We have one milestone left
that will be finished at the end

00:18:37.690 --> 00:18:41.120
of March, but this is in a way,

00:18:41.120 --> 00:18:44.190
the way we're gonna talk
through both the lessons learned

00:18:44.190 --> 00:18:49.190
and our sort of plans for how
we're getting ready for 2022.

00:18:49.720 --> 00:18:52.850
So I'll cover a number of
things around grid hardening

00:18:52.850 --> 00:18:55.800
and some of the issues
that happen in our events.

00:18:55.800 --> 00:18:57.970
And then we're gonna go
through in a lot more detail

00:18:57.970 --> 00:19:01.680
around just the very specific
lessons learned across each

00:19:01.680 --> 00:19:03.890
of these five categories.

00:19:03.890 --> 00:19:05.440
So we can go to the next slide.

00:19:07.980 --> 00:19:11.970
So this table is our
customer outage statistics

00:19:11.970 --> 00:19:14.363
when we compare 2020 to 2021.

00:19:15.260 --> 00:19:17.690
So last year we had the nine PSPS events

00:19:18.580 --> 00:19:20.687
that was down from
the 13th of previous year,

00:19:20.687 --> 00:19:22.498
and you can see the difference

00:19:22.498 --> 00:19:26.240
in the member of customers impacted.

00:19:26.240 --> 00:19:29.290
Now, part of the
reductions here were due

00:19:29.290 --> 00:19:32.080
to the grid hardening
efforts, which I'll talk about

00:19:32.080 --> 00:19:32.913
in more detail,

00:19:32.913 --> 00:19:35.363
but the other part of it
was also driven by weather.

00:19:36.380 --> 00:19:40.430
We had a, somewhat of
a more mild PSPS season.

00:19:40.430 --> 00:19:41.870
We had a bit of moisture moisture

00:19:41.870 --> 00:19:43.600
that came in in the summer,

00:19:43.600 --> 00:19:46.990
but then really what
defined most of 2021

00:19:46.990 --> 00:19:49.560
was that one really large
event over Thanksgiving,

00:19:49.560 --> 00:19:51.000
which I'll talk about,

00:19:51.000 --> 00:19:53.760
but we did have have
nine events overall,

00:19:53.760 --> 00:19:56.875
and these are, when we add it all up,

00:19:56.875 --> 00:19:59.085
this is the primary difference
between what you see here

00:19:59.085 --> 00:20:03.531
between 2020 and 2021.

00:20:03.531 --> 00:20:06.750
Now, one thing I do wanna
note here is when we look

00:20:06.750 --> 00:20:10.410
at these kinds of statistics,
it's important to note here,

00:20:10.410 --> 00:20:12.390
I think, that our events

00:20:12.390 --> 00:20:15.400
are very distribution system-centric.

00:20:15.400 --> 00:20:18.413
So when we de-energize customers,

00:20:19.260 --> 00:20:22.010
this is not something that
we've seen yet since 2019,

00:20:22.010 --> 00:20:26.570
or actually ever since
we've had PSPS in place,

00:20:26.570 --> 00:20:29.560
we have not instituted any
large scale de-energizations

00:20:29.560 --> 00:20:32.290
from our bulk power system.

00:20:32.290 --> 00:20:34.020
These are segment by segment

00:20:34.020 --> 00:20:36.610
and circuit-by-circuit de-energizations

00:20:36.610 --> 00:20:38.023
that make up these numbers.

00:20:38.970 --> 00:20:40.320
Let's go to the next slide.

00:20:43.171 --> 00:20:44.004
Okay, thank you.

00:20:44.004 --> 00:20:46.260
So our, again, our most
significant event occurring here

00:20:46.260 --> 00:20:49.670
in Thanksgiving, so
different from other events,

00:20:49.670 --> 00:20:53.530
and I've been involved in PSPS
events since we started this.

00:20:53.530 --> 00:20:57.140
And one thing I think that
sort of differentiates this event

00:20:57.140 --> 00:21:00.820
from others is really the
size, scale and really the speed

00:21:00.820 --> 00:21:04.210
of this event as it escalated
from where we started

00:21:04.210 --> 00:21:08.690
on June, or November 22nd,
leading up to November 25th.

00:21:08.690 --> 00:21:12.210
So, and the challenges that
we experienced during this event

00:21:13.895 --> 00:21:16.920
are really the basis for
our focus areas in 2022.

00:21:16.920 --> 00:21:18.910
Now, before I get into the details

00:21:18.910 --> 00:21:21.020
about these very specific circumstances,

00:21:21.020 --> 00:21:24.230
I will say that while there
were significant improvements,

00:21:24.230 --> 00:21:25.780
as we've been highlighting,

00:21:25.780 --> 00:21:27.770
we could have done better
in this particular event.

00:21:27.770 --> 00:21:31.300
And while our dedicated
team was on the job

00:21:31.300 --> 00:21:35.545
throughout the whole weekend,
everybody was on board,

00:21:35.545 --> 00:21:39.000
there were gaps and we
have room for improvement

00:21:39.000 --> 00:21:40.820
in several areas.

00:21:40.820 --> 00:21:41.810
And the team is gonna go

00:21:41.810 --> 00:21:44.613
through the subsequent
actions in the next three slides.

00:21:46.752 --> 00:21:47.585
So back on this event,

00:21:47.585 --> 00:21:50.080
our Wednesday forecasts
were continually increasing

00:21:50.080 --> 00:21:52.271
and expanding to more areas.

00:21:52.271 --> 00:21:55.160
More and more circuits
were being added to scope.

00:21:55.160 --> 00:21:58.340
The forecast of our wind
speeds were climbing.

00:21:58.340 --> 00:22:02.390
And what we weren't anticipating
is the day that we started

00:22:02.390 --> 00:22:05.570
to de-energize, that we
saw wind speed gust up

00:22:05.570 --> 00:22:09.320
to 89 miles an hour in a
number of different locations.

00:22:09.320 --> 00:22:12.461
Just just one way to
put that in a perspective,

00:22:12.461 --> 00:22:17.383
several of the weather stations
in the Malibu area recorded

00:22:17.383 --> 00:22:19.290
their highest wind peak
gust in the four years

00:22:19.290 --> 00:22:20.740
since they've been installed.

00:22:21.600 --> 00:22:25.280
So we didn't see throughout that event,

00:22:25.280 --> 00:22:26.820
the difference in the numbers,

00:22:26.820 --> 00:22:30.750
so between how many circuits
and customers were in scope

00:22:30.750 --> 00:22:33.363
for that de-energization versus those

00:22:33.363 --> 00:22:36.150
that were actually de-energized.

00:22:36.150 --> 00:22:38.523
But one of the significant
challenges though,

00:22:38.523 --> 00:22:41.074
what we saw with this
very rapid escalation

00:22:41.074 --> 00:22:45.070
was really the inability to
get out notifications and time

00:22:45.070 --> 00:22:47.300
to all of our customers.

00:22:47.300 --> 00:22:49.400
Additionally, one thing
I wanna point out here

00:22:49.400 --> 00:22:53.630
is that we recently identified
that we under-reported

00:22:53.630 --> 00:22:56.713
the number of mist notifications
in the post-event report.

00:22:58.347 --> 00:22:59.850
We're assessing the data issues,

00:22:59.850 --> 00:23:03.300
we're aided by, here,
who we use to convert

00:23:03.300 --> 00:23:06.150
our manual system to an automated one,

00:23:06.150 --> 00:23:08.230
and we'll be filing updated information

00:23:08.230 --> 00:23:10.460
as soon as that review is complete.

00:23:10.460 --> 00:23:13.030
We have advised the
Safety Enforcement Division

00:23:13.030 --> 00:23:15.660
and we'll be discussing
those findings in further detail

00:23:15.660 --> 00:23:18.310
at the next monthly meeting in March.

00:23:18.310 --> 00:23:22.190
So we do these bi-week
or now monthly check-ins

00:23:22.190 --> 00:23:24.797
with the SED on the action plan itself.

00:23:26.500 --> 00:23:29.680
But near the end of
December, we implemented

00:23:29.680 --> 00:23:32.180
an automated solution
that we placed a number

00:23:32.180 --> 00:23:33.650
of our manual processes

00:23:34.550 --> 00:23:37.070
that we had in place
previously for notifications,

00:23:37.070 --> 00:23:39.364
and unfortunately, that
system was not in place in time

00:23:39.364 --> 00:23:41.150
for this Thanksgiving Event.

00:23:41.150 --> 00:23:45.690
The systems are in place
now, they've been tested.

00:23:45.690 --> 00:23:47.630
We'll walk through those later,

00:23:47.630 --> 00:23:50.540
but this is really gonna
be a game changer for us

00:23:50.540 --> 00:23:53.483
and the accuracy and
timeliness of those notifications.

00:23:56.074 --> 00:23:57.150
Besides the notifications,

00:23:57.150 --> 00:23:59.300
other things that we are focusing on

00:23:59.300 --> 00:24:03.463
is, as you saw in the chart
here, the escalating wind feeds.

00:24:04.440 --> 00:24:07.190
We're gonna have to continue
to increase the accuracy

00:24:07.190 --> 00:24:10.320
and precision of our forecasting.

00:24:10.320 --> 00:24:13.780
We had started putting in
machine learning models

00:24:13.780 --> 00:24:14.980
on our weather stations,

00:24:15.842 --> 00:24:17.764
particularly because we had some areas

00:24:17.764 --> 00:24:19.970
that have been historically
difficult to forecast.

00:24:19.970 --> 00:24:23.270
We have some very
encouraging results from that,

00:24:23.270 --> 00:24:25.294
and so we're gonna be expanding that

00:24:25.294 --> 00:24:26.673
to 500 locations this year.

00:24:27.830 --> 00:24:30.450
Restoration time is
another issue that we saw

00:24:30.450 --> 00:24:34.040
with this kind of wide
scale long duration of that.

00:24:34.040 --> 00:24:36.390
So we're gonna be taking
a number steps to continue

00:24:36.390 --> 00:24:38.230
to improve the restoration time

00:24:39.430 --> 00:24:42.210
regardless of the size and scale,

00:24:42.210 --> 00:24:44.510
but all of this is also gonna require

00:24:44.510 --> 00:24:46.510
more training and drilling,

00:24:46.510 --> 00:24:49.800
especially as we implement
new tools to ensure

00:24:49.800 --> 00:24:52.613
that we're gonna be better
prepared for this season.

00:24:53.890 --> 00:24:58.580
And finally, we're further
automating to improve consistency

00:24:58.580 --> 00:25:01.500
across our data sources
and methodologies

00:25:01.500 --> 00:25:03.800
and our post, reporting to ensure

00:25:03.800 --> 00:25:06.620
that they're more accurately reflective,

00:25:06.620 --> 00:25:10.123
using the automation systems
that are now put in place.

00:25:10.960 --> 00:25:14.450
So we did significantly
reduce the need for PSPS,

00:25:14.450 --> 00:25:16.460
but because of the grid hardening,

00:25:16.460 --> 00:25:19.750
and I'm gonna go ahead and,
if there are no other questions,

00:25:19.750 --> 00:25:22.300
I'm gonna go and more specifically

00:25:22.300 --> 00:25:24.550
into those grid hardening
steps that we took.

00:25:28.286 --> 00:25:29.513
You can go to the next slide.

00:25:32.260 --> 00:25:33.662
Okay.

00:25:33.662 --> 00:25:35.680
So in last year we focused,

00:25:35.680 --> 00:25:38.470
we defined as frequently
impacted circuits.

00:25:38.470 --> 00:25:42.460
So Director Thomas Jacobs
appropriately identified

00:25:42.460 --> 00:25:44.731
the term frequently impacted circuits,

00:25:44.731 --> 00:25:46.550
and the way we defined it last year,

00:25:46.550 --> 00:25:49.050
it was any circuit that
had experienced four

00:25:49.050 --> 00:25:53.970
or more de-energizations from
2019 through January of 2021.

00:25:54.960 --> 00:25:57.110
So that represents two fire seasons,

00:25:57.110 --> 00:26:00.287
the fire season of 2020
and 2019, 2020 being defined

00:26:02.970 --> 00:26:05.033
all the way through January of 2021.

00:26:06.270 --> 00:26:09.560
This population was
seven in two circuits,

00:26:09.560 --> 00:26:12.770
and altogether they experienced

00:26:12.770 --> 00:26:16.690
nearly 160 million customer
outage minutes in 2020,

00:26:16.690 --> 00:26:17.983
just due to PSPS.

00:26:19.170 --> 00:26:21.280
Now, one of the advantages we have

00:26:21.280 --> 00:26:22.790
with our cover conductor plan

00:26:23.785 --> 00:26:25.710
is we performed risk modeling on those.

00:26:25.710 --> 00:26:30.170
And what we found out is we
had already put in the scope

00:26:31.030 --> 00:26:33.720
a significant number of miles
that we were already planning

00:26:33.720 --> 00:26:36.553
to do now, all they weren't
necessarily planned to be done

00:26:36.553 --> 00:26:41.130
in the timeframe that we needed to,

00:26:41.130 --> 00:26:44.140
so we accelerated grid hardening efforts

00:26:44.140 --> 00:26:47.227
with all attempts to get
everything done by October 1st,

00:26:48.365 --> 00:26:50.215
and time for the peak, and an season.

00:26:51.051 --> 00:26:55.350
But we accelerated 685
miles of cover conductor.

00:26:55.350 --> 00:26:58.030
That allowed us to
raise wind thresholds,

00:26:58.030 --> 00:27:00.594
and hence that's where
we get the benefits

00:27:00.594 --> 00:27:04.863
from the grid hardening to
avoid or minimize damages.

00:27:06.400 --> 00:27:09.520
Now, we also took
other measures as well.

00:27:09.520 --> 00:27:11.263
You see some of those listed here.

00:27:12.520 --> 00:27:14.910
On one of the slides Joe had,

00:27:14.910 --> 00:27:17.220
there were 81,000 customers

00:27:17.220 --> 00:27:20.663
that we more permanently
removed from PSPS.

00:27:21.499 --> 00:27:22.680
And we took a much closer look

00:27:22.680 --> 00:27:26.610
at all the different areas
that circuits were reversing.

00:27:26.610 --> 00:27:29.130
There's different topologies
or places where fuel

00:27:29.130 --> 00:27:32.230
is really not existing
'cause maybe circuits start

00:27:32.230 --> 00:27:34.863
in the rural, they go
through communities

00:27:34.863 --> 00:27:36.128
when they come out.

00:27:36.128 --> 00:27:39.120
So we also leveraged the
flexibility in our system to do

00:27:39.120 --> 00:27:42.550
the best we can to remove
customers in the first place.

00:27:42.550 --> 00:27:44.610
But all these measures,

00:27:44.610 --> 00:27:47.290
we did everything we could,
and even where cover conductor

00:27:47.290 --> 00:27:50.490
was delayed, we
accelerated other mitigation.

00:27:50.490 --> 00:27:54.800
So we're really happy
to say that communities

00:27:54.800 --> 00:27:58.436
like Acton did not get de-energized

00:27:58.436 --> 00:28:00.083
during that November event.

00:28:02.435 --> 00:28:03.920
What we're also saying
is the cover conductor

00:28:03.920 --> 00:28:05.650
is providing benefits year around.

00:28:05.650 --> 00:28:07.590
So not just in high fire conditions,

00:28:07.590 --> 00:28:09.490
they're helping us to avoid outages

00:28:09.490 --> 00:28:11.133
under normal storm conditions,

00:28:12.626 --> 00:28:15.570
and when other things come
into contact with their lives.

00:28:15.570 --> 00:28:19.863
So raise one speed thresholds,
reduce the frequency of PSPS.

00:28:20.780 --> 00:28:25.130
There are areas that still
exceeded our thresholds

00:28:25.130 --> 00:28:29.170
because of the extreme wind
speeds that I had talked about.

00:28:29.170 --> 00:28:32.420
And that's gonna be the breeding
ground for additional views

00:28:32.420 --> 00:28:35.513
on mitigations, on what
additional things could we do?

00:28:37.360 --> 00:28:42.360
I'll say that Our 2022 grid
hardening plans will focus

00:28:43.100 --> 00:28:47.140
on the circuit that have been
accumulating here in terms

00:28:47.140 --> 00:28:49.340
of being frequently impacted.

00:28:49.340 --> 00:28:51.690
We're also gonna put special emphasis

00:28:51.690 --> 00:28:56.690
on the Thanksgiving Event to
see what other circuits we need

00:28:57.300 --> 00:29:00.250
to address that may have
even showed up for the first time.

00:29:01.740 --> 00:29:05.530
So with that, that's
the end of my section,

00:29:05.530 --> 00:29:09.200
and what we're gonna do
is dive much more deeply,

00:29:09.200 --> 00:29:12.120
and so all these other
areas around notification,

00:29:12.120 --> 00:29:15.110
customer programs,
our emergency response

00:29:16.333 --> 00:29:18.713
over the next few speakers here.

00:29:19.880 --> 00:29:21.730
So with that, I'm gonna
go ahead and hand it off

00:29:21.730 --> 00:29:23.193
to Mr. Tom Brady.

00:29:25.680 --> 00:29:29.420
<v ->Hey, thanks Erik, and
good afternoon, everyone.</v>

00:29:29.420 --> 00:29:32.660
So I wanna kick things off
here this afternoon by sharing

00:29:32.660 --> 00:29:34.030
some of the work that was completed

00:29:34.030 --> 00:29:37.800
by our Fire Science and
Meteorology teams last year,

00:29:37.800 --> 00:29:40.880
really to improve both the
precision and the granularity

00:29:40.880 --> 00:29:43.360
of our weather and fuel
modeling capabilities.

00:29:43.360 --> 00:29:46.400
And I think it builds nicely on
some of the opening comments

00:29:46.400 --> 00:29:49.000
that we heard as well as
what Jill and Erik shared

00:29:49.000 --> 00:29:53.380
around really improving
the precision of our forecast.

00:29:53.380 --> 00:29:55.520
And the reason is, as we all know,

00:29:55.520 --> 00:29:59.000
PSPS execution relies
on access to timely

00:29:59.000 --> 00:30:00.840
and accurate forecast data.

00:30:00.840 --> 00:30:03.230
It starts at the very
beginning of the event.

00:30:03.230 --> 00:30:06.270
Forecast data informs
which circuits are expected

00:30:06.270 --> 00:30:09.550
to meet PSPS criteria,
and that drives a lot

00:30:09.550 --> 00:30:12.490
of our pre-event processes
around notifications,

00:30:12.490 --> 00:30:14.320
pre-patrols, et cetera.

00:30:14.320 --> 00:30:17.360
These same forecasts are
also critical for determining

00:30:17.360 --> 00:30:19.780
when those dangerous conditions debates,

00:30:19.780 --> 00:30:22.970
and the data informs when
we can start restoration patrols

00:30:22.970 --> 00:30:26.490
to get the lights back
on as quickly as possible.

00:30:26.490 --> 00:30:30.000
So as you've heard the
previous speakers mention,

00:30:30.000 --> 00:30:33.490
we have made substantial
upgrades to our in-house weather

00:30:33.490 --> 00:30:37.200
and fuel modeling
capabilities throughout 2021,

00:30:37.200 --> 00:30:39.767
and it's really enabled us
to increase that precision

00:30:39.767 --> 00:30:42.810
and that granularity
that we all talked about.

00:30:42.810 --> 00:30:46.500
So first, we added two additional
super computers last year,

00:30:46.500 --> 00:30:50.130
and it's allowed us to
double our forecast resolution.

00:30:50.130 --> 00:30:52.880
Prior to having those
additional super computers,

00:30:52.880 --> 00:30:54.980
we were at a two kilometer resolution,

00:30:54.980 --> 00:30:56.994
and since we've installed them,

00:30:56.994 --> 00:30:57.970
we're now down to one kilometer.

00:30:57.970 --> 00:31:02.140
And so what factor here is
really that greater granularity

00:31:02.140 --> 00:31:05.328
helps our meteorologist
more precisely determine some

00:31:05.328 --> 00:31:10.080
of the details around event
scope and also event timing.

00:31:10.080 --> 00:31:13.220
We're also using machine
learning technology to improve

00:31:13.220 --> 00:31:17.030
our wind speed forecast
at point-specific locations

00:31:17.030 --> 00:31:19.560
where PSPS has occurred most frequently

00:31:19.560 --> 00:31:23.160
in prior PSPS or wildfire years.

00:31:23.160 --> 00:31:23.993
Early last season,

00:31:23.993 --> 00:31:26.300
we saw the benefits
of this new technology.

00:31:26.300 --> 00:31:28.430
These models actually picked up a threat

00:31:28.430 --> 00:31:30.219
on one of our circuits,

00:31:30.219 --> 00:31:32.920
the Sam Canyon Circuit, that
may have been otherwise missed

00:31:32.920 --> 00:31:35.050
using our legacy models.

00:31:35.050 --> 00:31:38.130
So early on indication that
these machine learning models

00:31:38.130 --> 00:31:40.430
are really moving the needle for us

00:31:40.430 --> 00:31:42.930
in the forecasting space.

00:31:42.930 --> 00:31:45.910
Lastly, we added an
entirely new weather model

00:31:45.910 --> 00:31:47.530
to our setup forecasting tools,

00:31:47.530 --> 00:31:49.400
and that's the European weather model.

00:31:49.400 --> 00:31:51.080
And this provides two main benefits.

00:31:51.080 --> 00:31:54.930
Number one, if our existing
legacy models become unavailable

00:31:54.930 --> 00:31:57.530
for whatever reason,
we have redundancy now

00:31:57.530 --> 00:32:00.200
because we can get data
from this European model

00:32:00.200 --> 00:32:01.890
to develop our forecast,

00:32:01.890 --> 00:32:03.510
but also it gives our meteorologists

00:32:03.510 --> 00:32:08.300
with an entirely incremental
set of forecast scenarios

00:32:08.300 --> 00:32:13.023
from which to consider and
evaluate the PSPS forecast list.

00:32:13.910 --> 00:32:16.860
So I guess the summary here
is these three enhancements

00:32:16.860 --> 00:32:20.870
really help us identify
where, when and how long

00:32:20.870 --> 00:32:24.240
these potentialization
de-energization events may last,

00:32:24.240 --> 00:32:26.520
improving precision in notification,

00:32:26.520 --> 00:32:29.533
and really just overall event execution.

00:32:30.520 --> 00:32:33.260
We also updated our fire
potential index thresholds.

00:32:33.260 --> 00:32:35.360
or FPI, and what FPI is

00:32:35.360 --> 00:32:38.580
is it's an index that
estimates the likelihood

00:32:38.580 --> 00:32:41.550
of a spark turning
into a major wildfire.

00:32:41.550 --> 00:32:46.550
It has a range of one to 17,
with 17 being the most extreme.

00:32:47.950 --> 00:32:51.990
So in 2020, we set our
thresholds for FPI to 12.

00:32:51.990 --> 00:32:54.730
However, based on additional
data that we had available

00:32:54.730 --> 00:32:58.950
in 2021, we were able to
go back and look at 26 years

00:32:58.950 --> 00:33:03.350
of historical fuel and
FPI data and determine

00:33:03.350 --> 00:33:05.700
where these larger fires tend to occur.

00:33:05.700 --> 00:33:08.142
The outcome of this
study was an increase

00:33:08.142 --> 00:33:11.000
in our fire potential index
threshold from a 12 to 13

00:33:11.000 --> 00:33:14.700
in most fire climate zones
subject to some exceptions.

00:33:14.700 --> 00:33:17.560
So what's in the plans for 2022?

00:33:17.560 --> 00:33:19.670
Really leaning into
continuing developing

00:33:19.670 --> 00:33:21.670
those machine learning models.

00:33:21.670 --> 00:33:23.240
I talked about one of the main benefits

00:33:23.240 --> 00:33:25.650
we're seeing some really
promising early results

00:33:25.650 --> 00:33:28.470
into how useful these
are for our meteorologist.

00:33:28.470 --> 00:33:31.400
It's gonna help us reduce the
variance between the customers

00:33:31.400 --> 00:33:33.800
who are notified of
potential de-energization

00:33:33.800 --> 00:33:36.480
and the customers who
are actually de-energized.

00:33:36.480 --> 00:33:40.170
Additionally, it's also
gonna help us improve timing

00:33:40.170 --> 00:33:43.410
or the number of customers
who are de-energized

00:33:43.410 --> 00:33:45.140
with no notice at all.

00:33:45.140 --> 00:33:46.770
So that's a quick flyover of some

00:33:46.770 --> 00:33:49.000
of our weather and field
modeling capabilities.

00:33:49.000 --> 00:33:51.780
I wanna pause briefly and
then I'll go into more detail

00:33:51.780 --> 00:33:52.913
on our execution.

00:33:57.110 --> 00:33:58.610
All right, next slide, please.

00:33:59.990 --> 00:34:01.470
<v ->Right, quick question.</v>

00:34:01.470 --> 00:34:02.350
<v ->So you've heard
Jill and Erik talk a lot</v>

00:34:02.350 --> 00:34:06.240
about the Thanksgiving
activation, the largest event

00:34:06.240 --> 00:34:09.270
that occurred for SCE in 2021.

00:34:09.270 --> 00:34:10.880
And it really strange.

00:34:10.880 --> 00:34:13.370
<v ->Tom, I think we
had a quick question.</v>

00:34:13.370 --> 00:34:14.654
<v ->Oh, I'm sorry.</v>

00:34:14.654 --> 00:34:16.097
Absolutely.

00:34:16.097 --> 00:34:16.994
Yes, please.

00:34:16.994 --> 00:34:17.827
<v ->Sorry, I missed this.</v>

00:34:17.827 --> 00:34:20.740
What is this European modeling?

00:34:20.740 --> 00:34:22.330
I'm sorry, what is that?

00:34:23.975 --> 00:34:25.570
<v ->So there's the North
American weather model</v>

00:34:25.570 --> 00:34:28.120
and then there's also another model

00:34:28.120 --> 00:34:29.510
that is in Europe

00:34:29.510 --> 00:34:33.000
and we previously
didn't have access to it.

00:34:33.000 --> 00:34:35.603
It's, the acronym is ECMWS.

00:34:37.715 --> 00:34:39.530
And this model provides
our meteorologist

00:34:39.530 --> 00:34:43.130
with an entirely incremental
set of forecast outcomes

00:34:43.130 --> 00:34:47.020
for which they base their
PSPS decisions on in terms

00:34:47.020 --> 00:34:48.970
of what circuits are on scope,

00:34:48.970 --> 00:34:51.560
what circuits are not in scope.

00:34:51.560 --> 00:34:53.920
So it's essentially what we
have the North American model,

00:34:53.920 --> 00:34:55.543
but it's the European model.

00:34:57.520 --> 00:34:58.353
<v ->Okay.</v>

00:34:58.353 --> 00:35:01.860
Have you included
that in your most recent

00:35:01.860 --> 00:35:04.983
wildfire mitigation plan
application to OEIS?

00:35:07.320 --> 00:35:09.860
<v ->I'd have to take that as a
follow-up just to make sure</v>

00:35:09.860 --> 00:35:11.289
that it's in there.

00:35:11.289 --> 00:35:12.450
I do believe it's in the
wildfire mitigation plan,

00:35:12.450 --> 00:35:13.860
but I would want to check and confirm

00:35:13.860 --> 00:35:18.800
before making a final statement on that.

00:35:18.800 --> 00:35:20.124
<v ->Okay.</v>

00:35:20.124 --> 00:35:21.037
All right.

00:35:21.037 --> 00:35:21.937
Thank you.

00:35:21.937 --> 00:35:22.770
<v ->You're welcome.</v>

00:35:22.770 --> 00:35:24.190
<v ->I'll coordinate with you
on getting the answer to that</v>

00:35:24.190 --> 00:35:25.780
and then getting the answer over

00:35:25.780 --> 00:35:27.530
to the Commissioner's post-meeting.

00:35:28.450 --> 00:35:29.873
Sounds good.

00:35:29.873 --> 00:35:31.571
And I suspect that we'll
hear back from the team here,

00:35:31.571 --> 00:35:33.288
and we may be able to
close it out here on the call

00:35:33.288 --> 00:35:34.121
in a little bit as well.

00:35:37.440 --> 00:35:38.921
All right.

00:35:38.921 --> 00:35:40.110
So shifting back into this slide,

00:35:40.110 --> 00:35:43.790
we talked about the size and complexity,

00:35:43.790 --> 00:35:47.690
really straining our
pre-automation processes resulting

00:35:47.690 --> 00:35:48.890
in, like Erik said,

00:35:48.890 --> 00:35:52.040
delays in processing our
weather forecast and sending some

00:35:52.040 --> 00:35:54.390
of those pre-event notifications.

00:35:54.390 --> 00:35:57.500
And in many cases, these
processing delays were made worse

00:35:57.500 --> 00:36:01.100
or exacerbated by our
efforts to send notifications

00:36:01.100 --> 00:36:03.830
at the segment level for pre-event.

00:36:03.830 --> 00:36:07.760
And the reason that this is
important is because in part

00:36:07.760 --> 00:36:10.060
of the grid, or in the
grid hardening activities

00:36:10.060 --> 00:36:11.720
that Erik described earlier,

00:36:11.720 --> 00:36:16.560
we now have higher threshold
for fully isolatable segments

00:36:16.560 --> 00:36:18.490
of circuit with covered conductor.

00:36:18.490 --> 00:36:22.380
And so the team is
always trying to filter

00:36:22.380 --> 00:36:25.140
those notifications so that
we only notify the customers

00:36:25.140 --> 00:36:27.180
that are most likely to be de-energized.

00:36:27.180 --> 00:36:29.380
Well, by doing this, it
added an additional layer

00:36:29.380 --> 00:36:31.930
of complexity, which
made it more difficult

00:36:31.930 --> 00:36:34.420
to get through those updated forecast

00:36:34.420 --> 00:36:37.760
and get those notifications
out to customers.

00:36:37.760 --> 00:36:41.060
Additionally, during
the period of concern,

00:36:41.060 --> 00:36:43.800
this event rapidly intensified in terms

00:36:43.800 --> 00:36:48.800
of the span or the boundary
of the weather condition,

00:36:49.030 --> 00:36:51.060
which pulled more circus in the scope.

00:36:51.060 --> 00:36:54.400
And this also made it
difficult to support some

00:36:54.400 --> 00:36:57.420
of those pre-event
notifications, but also in event,

00:36:57.420 --> 00:37:00.450
seeing rapid increases
in wind speeds and having

00:37:00.450 --> 00:37:01.403
to move quickly.

00:37:02.744 --> 00:37:04.920
So just these convergence
of complexity factors

00:37:04.920 --> 00:37:08.177
making it hard to
dispatch those notifications.

00:37:08.177 --> 00:37:10.650
So I think that takes us nicely

00:37:10.650 --> 00:37:14.340
to the work we're doing to
help improve automation.

00:37:14.340 --> 00:37:17.010
We've heard us speak
a lot about it specifically

00:37:17.010 --> 00:37:19.840
about, which is a tool
that was developed

00:37:20.794 --> 00:37:23.250
by the talent here,
and as Erik mentioned,

00:37:23.250 --> 00:37:26.020
some of these capabilities
or all of these capabilities

00:37:26.020 --> 00:37:27.940
that would've helped in this situation

00:37:27.940 --> 00:37:29.630
were not operationalized at the time

00:37:29.630 --> 00:37:31.400
of the Thanksgiving Event,

00:37:31.400 --> 00:37:34.830
since we've operationalized
several core processes

00:37:34.830 --> 00:37:36.700
around the PSPS workflow,

00:37:36.700 --> 00:37:38.790
and they're really gonna
be game changers in terms

00:37:38.790 --> 00:37:41.930
of reducing processing
time and minimizing

00:37:41.930 --> 00:37:43.650
the potential for error.

00:37:43.650 --> 00:37:45.430
So I'm gonna go
through a couple of those,

00:37:45.430 --> 00:37:48.210
and then we'll talk about
some other learnings

00:37:48.210 --> 00:37:49.800
from the Thanksgiving Event.

00:37:49.800 --> 00:37:53.080
So the first of which is
we developed automation

00:37:53.080 --> 00:37:56.800
to help our Meteorology
Team intake and synthesize all

00:37:56.800 --> 00:37:58.850
of these weather model inputs, right?

00:37:58.850 --> 00:38:00.770
To inform the
development of what we call

00:38:00.770 --> 00:38:02.420
our PSPS circuit list,

00:38:02.420 --> 00:38:05.910
which is essentially the list
of circuits that our forecast

00:38:05.910 --> 00:38:08.180
to meet or exceed criteria.

00:38:08.180 --> 00:38:10.440
We also automated the
processes that are used

00:38:10.440 --> 00:38:13.900
by our Outage Notifications
team to dispatch

00:38:13.900 --> 00:38:16.800
and inform Notification, Team.

00:38:16.800 --> 00:38:20.000
This is again, really gonna
reduce that processing time

00:38:20.000 --> 00:38:23.233
and increased accuracy
in the notification space.

00:38:24.210 --> 00:38:27.248
An additional use case
that I do wanna share

00:38:27.248 --> 00:38:29.880
is publishing information

00:38:29.880 --> 00:38:32.060
to the Public Safety Partner Portal,

00:38:32.060 --> 00:38:34.800
the process of going in
and determining what circuits

00:38:34.800 --> 00:38:37.620
are impacted and how
many customers are impacted

00:38:37.620 --> 00:38:38.700
on those circuits.

00:38:38.700 --> 00:38:43.540
Now, that has been automated
to help us support timely

00:38:43.540 --> 00:38:46.830
and event updates to our
Public Safety Partner Portal

00:38:46.830 --> 00:38:48.623
and to sce.com.

00:38:49.550 --> 00:38:53.830
So in 2022, we look to continue
to build on the automation

00:38:53.830 --> 00:38:55.920
to further and increase and optimize

00:38:55.920 --> 00:39:00.750
our event management
practices, and wanting to, again,

00:39:00.750 --> 00:39:03.550
provide some examples of
where we're gonna do that.

00:39:03.550 --> 00:39:06.720
So in-event situational
awareness is critical.

00:39:06.720 --> 00:39:08.430
It supports our external reporting

00:39:08.430 --> 00:39:10.040
and briefing requirements.

00:39:10.040 --> 00:39:12.990
And so we're building our
new situational awareness tool

00:39:12.990 --> 00:39:15.020
that will provide us with better access

00:39:15.020 --> 00:39:18.647
to near realtime data on
circuit that are in scope

00:39:18.647 --> 00:39:20.420
and the customers that are impacted.

00:39:20.420 --> 00:39:23.670
We're also automating the
process for how we populate

00:39:23.670 --> 00:39:25.730
our in-event risk calculator.

00:39:25.730 --> 00:39:27.940
Legacy process is highly manual.

00:39:27.940 --> 00:39:30.010
Some of this new automation
will make that quicker

00:39:30.010 --> 00:39:31.020
and more efficient,

00:39:31.020 --> 00:39:33.250
so we can get that
important data in front

00:39:33.250 --> 00:39:35.870
of our incident commanders
for decision-making

00:39:37.020 --> 00:39:39.000
And then you also heard
earlier in the discussion

00:39:39.000 --> 00:39:40.450
about our post-event reports,

00:39:41.540 --> 00:39:43.540
we're applying expensive automation

00:39:45.167 --> 00:39:46.440
and energy around automation

00:39:46.440 --> 00:39:49.330
that's gonna help increase
the accuracy by integrating all

00:39:49.330 --> 00:39:51.900
of the disparate data sources that exist

00:39:51.900 --> 00:39:55.480
across our response
operation and standardizing

00:39:55.480 --> 00:39:58.743
the methodology that
we use to query that data.

00:39:59.720 --> 00:40:02.230
So that's a quick play
over of automation,

00:40:02.230 --> 00:40:03.960
and now I wanna
shift gears and talk a bit

00:40:03.960 --> 00:40:06.060
about our restoration process.

00:40:06.060 --> 00:40:09.350
Erik mentioned previously
that we had some learnings

00:40:09.350 --> 00:40:10.830
in this space too,

00:40:10.830 --> 00:40:14.764
and so wanted to note that
in the Thanksgiving Event,

00:40:14.764 --> 00:40:17.400
we saw our average restoration time

00:40:17.400 --> 00:40:19.260
right at about nine hours.

00:40:19.260 --> 00:40:21.896
And this is outside of the
typical restoration range

00:40:21.896 --> 00:40:25.770
that we share with customers,
which is three to eight hours.

00:40:25.770 --> 00:40:26.990
So why was that?

00:40:26.990 --> 00:40:28.280
In this particular event,

00:40:28.280 --> 00:40:32.020
restoration was complicated
by a late breaking shift

00:40:32.020 --> 00:40:35.010
in the weather that resulted
in the period of concern

00:40:35.010 --> 00:40:38.230
ending earlier than we
had initially expected,

00:40:38.230 --> 00:40:40.590
and it was also late in the evening.

00:40:40.590 --> 00:40:44.180
So this change required us to
adjust our resourcing strategy

00:40:44.180 --> 00:40:45.960
extremely late in the game.

00:40:45.960 --> 00:40:49.720
And then to complicate
factors further, in many cases,

00:40:49.720 --> 00:40:53.900
restoration couldn't be
performed until daylight hours

00:40:53.900 --> 00:40:56.110
for circuits that required air patrol,

00:40:56.110 --> 00:40:58.820
as well as some other
circuits where we have visibility

00:40:58.820 --> 00:41:00.640
and access issues.

00:41:00.640 --> 00:41:04.040
So for 2022, we look to codify the use

00:41:04.040 --> 00:41:05.670
of a dedicated representative

00:41:05.670 --> 00:41:07.450
on our incident management team

00:41:07.450 --> 00:41:12.140
who's sole purpose on the
response operation is to lead

00:41:12.140 --> 00:41:15.260
the overall restoration
planning and staffing efforts,

00:41:15.260 --> 00:41:18.660
and this really includes
refining our operational protocol

00:41:18.660 --> 00:41:19.493
for many things,

00:41:19.493 --> 00:41:23.540
including making sure we
get our helicopters in the air

00:41:23.540 --> 00:41:25.140
as soon as it's safely possible.

00:41:26.510 --> 00:41:29.300
So with that, I'm gonna go
ahead and close, but before I do,

00:41:29.300 --> 00:41:32.580
I wanna echo what
both Jill and Erik said.

00:41:32.580 --> 00:41:34.720
We've obviously come a long way in terms

00:41:34.720 --> 00:41:38.630
of our PSPS execution,
impacting fewer customers,

00:41:38.630 --> 00:41:40.750
expanding our mitigation efforts,

00:41:40.750 --> 00:41:42.910
but based on what I just shared,

00:41:42.910 --> 00:41:45.030
we know that our performance
in November left room

00:41:45.030 --> 00:41:46.910
for improvement, and so wanted

00:41:46.910 --> 00:41:48.520
to share some of our learnings

00:41:48.520 --> 00:41:51.873
on how we're going
about tackling those issues.

00:41:53.900 --> 00:41:54.733
I see a hand.

00:41:57.440 --> 00:41:59.143
<v ->This is Commissioner
Rechtschaffen.</v>

00:42:00.658 --> 00:42:02.581
So I wanna ask you a little bit more

00:42:02.581 --> 00:42:04.010
about the Thanksgiving Event

00:42:05.070 --> 00:42:07.540
and sort of learnings going forward.

00:42:07.540 --> 00:42:10.090
Are you, so the first question

00:42:10.090 --> 00:42:13.240
is, are you now including
those sets of circuits

00:42:13.240 --> 00:42:15.570
in the most frequently impacted circuits

00:42:15.570 --> 00:42:19.130
that get priority for remediation work

00:42:19.130 --> 00:42:21.080
like coverage conductors?

00:42:21.080 --> 00:42:22.833
That that's the first question.

00:42:23.670 --> 00:42:26.810
And then it just strikes me that all

00:42:26.810 --> 00:42:31.810
of the automation
improvements that you're making

00:42:32.250 --> 00:42:36.380
still will leave you with a
judgment of how inclusive

00:42:36.380 --> 00:42:40.410
or broad you're gonna be
in a situation where things

00:42:40.410 --> 00:42:41.660
are rapidly changing.

00:42:41.660 --> 00:42:46.160
And of course, rapidly-changing
climate is now the norm,

00:42:46.160 --> 00:42:48.332
not the exception, and I know

00:42:48.332 --> 00:42:49.270
you've got two new
super computers trying

00:42:49.270 --> 00:42:51.060
to figure that out.

00:42:51.060 --> 00:42:56.060
So I guess what I'm looking
for is your assessment

00:42:56.580 --> 00:42:58.550
about whether you
think you drew the line

00:42:58.550 --> 00:43:01.710
in the wrong place, and would
you draw the line differently?

00:43:01.710 --> 00:43:06.660
Would you be more inclusive
in notifying people sooner,

00:43:06.660 --> 00:43:10.370
even though there's a probability

00:43:10.370 --> 00:43:11.840
that they wouldn't be de-energized,

00:43:11.840 --> 00:43:14.190
given the experience
you had last Thanksgiving?

00:43:15.510 --> 00:43:16.894
<v ->Okay.</v>

00:43:16.894 --> 00:43:18.000
So let me take those in order.

00:43:18.000 --> 00:43:20.680
And then I also welcome the
voices of my SDE colleagues

00:43:20.680 --> 00:43:23.550
who are on the phone to
help expand on the answers.

00:43:23.550 --> 00:43:24.500
So the first one I think

00:43:24.500 --> 00:43:27.120
was about prioritizing
grid hardening efforts

00:43:27.120 --> 00:43:29.500
based on the outcomes
of the Thanksgiving Event.

00:43:29.500 --> 00:43:30.333
Is that right?

00:43:32.180 --> 00:43:33.700
<v ->Correct.</v>

00:43:33.700 --> 00:43:34.533
<v ->Okay.</v>

00:43:34.533 --> 00:43:35.940
And the answer to that is yes.

00:43:35.940 --> 00:43:38.962
We're currently going
through and assessing

00:43:38.962 --> 00:43:42.090
the circuit de-energizations
that did take place

00:43:42.090 --> 00:43:44.040
during the Thanksgiving
Event and looking

00:43:44.040 --> 00:43:47.320
at how frequently those
circuits were impacted previously.

00:43:47.320 --> 00:43:49.160
That event was a bit atypical,

00:43:49.160 --> 00:43:52.480
like Erik stated, in terms
of those sheer wind speeds,

00:43:52.480 --> 00:43:55.440
seeing levels on some
of our weather stations

00:43:55.440 --> 00:43:57.760
that we haven't seen
since they've been installed.

00:43:57.760 --> 00:44:01.060
So like a, think about
like a four-year history.

00:44:01.060 --> 00:44:03.490
So we wanted to take
that into consideration

00:44:03.490 --> 00:44:06.450
as we look to understand
how frequently those circuits

00:44:06.450 --> 00:44:10.420
are impacted and if accelerated
grid hardening is warranted

00:44:10.420 --> 00:44:11.830
for those locations.

00:44:11.830 --> 00:44:14.330
And I'll pause there briefly
to see if Erik or anybody else

00:44:14.330 --> 00:44:15.320
has anything to add,

00:44:15.320 --> 00:44:17.320
and then I'll take your second question.

00:44:18.630 --> 00:44:20.640
<v ->Yeah, Tom, I'll go ahead
and add a few things.</v>

00:44:20.640 --> 00:44:24.090
So thank you for the question,
Commissioner Rechtschaffen.

00:44:24.090 --> 00:44:28.930
When we started and we
identified those 72 circuits,

00:44:28.930 --> 00:44:32.660
we did draw that line at four
or more de-energizations,

00:44:32.660 --> 00:44:37.660
and we knew that at that time
that there was another subset

00:44:38.980 --> 00:44:41.200
of those that we called them sort

00:44:41.200 --> 00:44:43.680
of near frequently impacted circuits,

00:44:43.680 --> 00:44:47.180
ones that maybe energized
three or more times,

00:44:47.180 --> 00:44:50.000
or had other circumstances.

00:44:50.000 --> 00:44:52.946
So the grid hardening

00:44:52.946 --> 00:44:56.960
that's in our longterm
mitigation plan is associated

00:44:56.960 --> 00:45:01.080
with extending out more
circuits below that line,

00:45:01.080 --> 00:45:04.610
knowing that's a potential
likelihood that those circuits

00:45:04.610 --> 00:45:06.433
can come into the picture.

00:45:07.780 --> 00:45:10.117
What's interesting about the
Thanksgiving Event though,

00:45:10.117 --> 00:45:14.104
and if we compare to even
the events that occurred in 2021,

00:45:14.104 --> 00:45:17.380
this one was more or less dominated

00:45:17.380 --> 00:45:20.290
by non-frequently impacted circuits.

00:45:20.290 --> 00:45:22.750
And this is where we saw wind speeds

00:45:22.750 --> 00:45:25.440
that we hadn't seen historically.

00:45:25.440 --> 00:45:28.150
So that's why we're
also adding into the scope

00:45:28.990 --> 00:45:33.020
those circuits that, we
start to look at mitigations

00:45:33.020 --> 00:45:34.930
and other circuits, but
we're gonna be accelerating

00:45:34.930 --> 00:45:37.472
those efforts to really
try to understand

00:45:37.472 --> 00:45:41.450
what that particular Thanksgiving
Event, what it brought,

00:45:41.450 --> 00:45:44.220
and what's the likelihood
that those things

00:45:44.220 --> 00:45:46.120
are gonna show up down the road?

00:45:46.120 --> 00:45:47.750
I think you make a great point here,

00:45:47.750 --> 00:45:49.669
that with climate change,

00:45:49.669 --> 00:45:53.000
there is gonna be sort
of an upward trajectory

00:45:53.000 --> 00:45:56.980
of uncertainty and more
difficult things to predict.

00:45:56.980 --> 00:46:01.680
So I think that the goal
for us is to continue driving

00:46:01.680 --> 00:46:04.480
these sort of grid hardening mitigation

00:46:05.888 --> 00:46:09.800
that align both with
mitigating the risk of ignitions,

00:46:09.800 --> 00:46:14.192
but also mitigating and
reducing the need for PSPS.

00:46:14.192 --> 00:46:16.400
So the short answer, just to summarize,

00:46:16.400 --> 00:46:18.520
we are looking at that next level down

00:46:18.520 --> 00:46:21.080
that that was the basis of
our grid hardening plans,

00:46:21.080 --> 00:46:23.630
and we're adding two
with additional circuits

00:46:23.630 --> 00:46:26.180
and considerations based
on the Thanksgiving Event.

00:46:28.455 --> 00:46:30.370
<v ->Thanks, Erik.</v>

00:46:30.370 --> 00:46:32.600
And now I can shift gears
to the second question

00:46:32.600 --> 00:46:35.513
if there's no further
questions on that topic.

00:46:38.330 --> 00:46:40.960
But I think the second
question was in terms

00:46:40.960 --> 00:46:42.900
of notifications, I had
mentioned how we tried

00:46:42.900 --> 00:46:45.730
to filter notifications for the circuit

00:46:45.730 --> 00:46:48.010
that were most likely
to be de-energized,

00:46:48.010 --> 00:46:50.380
and what comes to mind
for me on that question

00:46:50.380 --> 00:46:52.650
is we're always trying to
strike that right balance.

00:46:52.650 --> 00:46:55.160
We don't wanna over notify
customers who are likely

00:46:55.160 --> 00:46:57.670
to be de-energized,
but at the same time,

00:46:57.670 --> 00:46:58.971
we wanna make sure

00:46:58.971 --> 00:47:01.190
that we're providing
sufficient notifications

00:47:01.190 --> 00:47:04.150
when there is a probability
of that happening.

00:47:04.150 --> 00:47:06.709
And so I think what we
learned in Thanksgiving,

00:47:06.709 --> 00:47:07.542
and it's an excellent question,

00:47:07.542 --> 00:47:10.000
is what's that
appropriate balance, right?

00:47:10.000 --> 00:47:13.060
And so as part of our
2022 planning efforts,

00:47:13.060 --> 00:47:15.970
we're going back and
determining what the at right level

00:47:15.970 --> 00:47:18.140
of buffer is to put in place.

00:47:18.140 --> 00:47:20.410
So if a forecast is coming
in and it's indicating

00:47:20.410 --> 00:47:23.810
that we're not gonna
breach those thresholds,

00:47:23.810 --> 00:47:25.260
we need to make sure
that we're accounting

00:47:25.260 --> 00:47:26.527
for margin of error.

00:47:26.527 --> 00:47:29.943
And so that is definitely
a priority for 2022.

00:47:32.560 --> 00:47:33.393
<v ->Thank you.</v>

00:47:33.393 --> 00:47:36.405
<v ->I have a follow
question for that.</v>

00:47:36.405 --> 00:47:39.340
On customer notifications,

00:47:39.340 --> 00:47:43.530
I know you had slides that
show statistics on reduction

00:47:43.530 --> 00:47:45.363
of the total number of events.

00:47:46.480 --> 00:47:50.320
Do you have metrics on a
events that were notified?

00:47:50.320 --> 00:47:53.920
So how many events were
notified through the years

00:47:53.920 --> 00:47:55.693
as you've been doing this?

00:47:55.693 --> 00:47:58.400
Has there been a
downward trajectory of that,

00:47:58.400 --> 00:48:02.350
or are you still kind of
notifying more events

00:48:02.350 --> 00:48:05.900
that you're calling and have
you been able to reduce that?

00:48:05.900 --> 00:48:07.417
I agree.

00:48:07.417 --> 00:48:10.100
I think there is an effect of notifying,

00:48:10.100 --> 00:48:12.410
even if you don't call an event,

00:48:12.410 --> 00:48:14.530
it has an effect on
customers who have to plan,

00:48:14.530 --> 00:48:17.160
local responders have to get organized,

00:48:17.160 --> 00:48:20.520
you maybe experience
a crying wolf syndrome

00:48:20.520 --> 00:48:22.060
if you do it too much.

00:48:22.060 --> 00:48:24.810
So just was wondering how
your numbers are looking in terms

00:48:24.810 --> 00:48:29.810
of notification of events
versus, so that larger number

00:48:30.110 --> 00:48:31.550
of total events notified,

00:48:31.550 --> 00:48:33.863
and have you been able to reduce that?

00:48:35.660 --> 00:48:37.080
<v ->So to kind of
restate the question,</v>

00:48:37.080 --> 00:48:39.780
just to make sure I understand
it correctly, my question

00:48:39.780 --> 00:48:43.580
is are we seeing any changes
in that false positive rate?

00:48:43.580 --> 00:48:45.083
Is that a good way to put it?

00:48:46.080 --> 00:48:46.913
<v ->I think it is.</v>

00:48:46.913 --> 00:48:48.650
That's a coming at it
a little bit differently,

00:48:48.650 --> 00:48:51.513
but I think we would
get to the same result.

00:48:52.490 --> 00:48:54.420
<v ->Okay, well, excellent question.</v>

00:48:54.420 --> 00:48:56.370
I think, again, that Thanksgiving Event

00:48:57.267 --> 00:48:58.656
was a great example, right?

00:48:58.656 --> 00:49:00.820
Where we looked to try
to minimize notifications

00:49:00.820 --> 00:49:03.640
to customers who weren't
likely to get de-energized.

00:49:03.640 --> 00:49:05.100
And of course, the
flip side of doing that

00:49:05.100 --> 00:49:08.320
is if you cut it too close,
then you run into the issue

00:49:08.320 --> 00:49:11.200
where folks don't get
enough advanced notice.

00:49:11.200 --> 00:49:13.250
I don't have the
metrics with me in terms

00:49:13.250 --> 00:49:17.080
of false positive rates
over the seasons,

00:49:17.080 --> 00:49:18.670
or even over the events within a season.

00:49:18.670 --> 00:49:21.582
So if you're okay with it,

00:49:21.582 --> 00:49:23.360
I'd like to take an action item
and commit to getting back

00:49:23.360 --> 00:49:24.460
to you with that data,

00:49:25.556 --> 00:49:26.926
unless somebody else on the SDE Team

00:49:26.926 --> 00:49:28.087
has that readily available.

00:49:31.270 --> 00:49:32.631
<v ->Thank you.</v>

00:49:32.631 --> 00:49:35.214
I appreciate at that follow-up.

00:49:39.319 --> 00:49:42.590
<v ->And I did want to confirm
as well that the question</v>

00:49:42.590 --> 00:49:43.980
about the European weather model

00:49:43.980 --> 00:49:45.980
and whether or not it was in the WMP,

00:49:45.980 --> 00:49:50.650
team confirmed that it is,
it's on page 284, table 531

00:49:50.650 --> 00:49:51.483
in the WMP.

00:49:51.483 --> 00:49:53.680
So just wanted to
close the loop on as well.

00:49:55.660 --> 00:49:56.493
<v ->Thank you.</v>

00:49:57.610 --> 00:50:01.260
<v ->You said page 284 of WMP?</v>

00:50:01.260 --> 00:50:03.673
Page 284 of the WMP.

00:50:05.140 --> 00:50:05.973
<v ->Gotcha.</v>

00:50:10.980 --> 00:50:12.323
<v ->I wanna ask the
panel one more time,</v>

00:50:12.323 --> 00:50:14.118
so they have any questions

00:50:14.118 --> 00:50:16.833
regarding the SCE presentation today?

00:50:19.350 --> 00:50:21.175
And we still have
additional slides as well.

00:50:21.175 --> 00:50:22.750
I'm about to hand
over to Katie to talk a bit

00:50:22.750 --> 00:50:25.810
about how we're mitigating
the impact of PSPS

00:50:25.810 --> 00:50:28.270
through our customer care programs.

00:50:28.270 --> 00:50:29.408
But let me pause briefly to see

00:50:29.408 --> 00:50:31.858
if there there's no additional
follow-up, and then if not,

00:50:31.858 --> 00:50:32.953
I'll go ahead and hand over to her.

00:50:36.950 --> 00:50:37.800
All right, Katie.

00:50:40.260 --> 00:50:41.093
<v ->Great.</v>

00:50:41.093 --> 00:50:42.553
Thank you.

00:50:42.553 --> 00:50:44.310
And we can go to the next page.

00:50:44.310 --> 00:50:45.163
Thanks, Tom.

00:50:46.946 --> 00:50:49.120
Good afternoon.

00:50:49.120 --> 00:50:51.443
First, I just really would
like to start by saying

00:50:51.443 --> 00:50:53.400
that I can't overstate how important

00:50:54.251 --> 00:50:57.990
our various PSPS mitigations are to SCE.

00:50:57.990 --> 00:51:01.010
And as long as we continue
to need to use PSPS,

00:51:01.010 --> 00:51:03.870
it's our highest priority
to minimize impacts

00:51:03.870 --> 00:51:05.793
in our communities for all customers,

00:51:06.795 --> 00:51:08.920
and especially those with
Access and Functional Needs

00:51:08.920 --> 00:51:10.070
who are at higher risk.

00:51:11.200 --> 00:51:12.890
In the 2021 fire season,

00:51:12.890 --> 00:51:17.340
we activated on 33
occasions for a total of 67 days.

00:51:17.340 --> 00:51:19.280
And this year, our added services

00:51:19.280 --> 00:51:22.870
included onsite language
translation for customers

00:51:22.870 --> 00:51:25.730
for whom spoken English
is not their primary language,

00:51:25.730 --> 00:51:28.373
and this also includes
American Sign Language.

00:51:29.520 --> 00:51:34.020
In the 2021 fire season, we
had more than 2,700 visitors

00:51:34.020 --> 00:51:35.890
to our community resource centers

00:51:35.890 --> 00:51:37.920
and community crew vehicles,

00:51:37.920 --> 00:51:39.710
including more than 2,000 visitors

00:51:39.710 --> 00:51:41.860
during the Thanksgiving Event.

00:51:41.860 --> 00:51:43.840
As Jill mentioned in
her opening remarks,

00:51:43.840 --> 00:51:45.880
you can see her here
in our picture with one

00:51:45.880 --> 00:51:47.260
of our employee volunteers

00:51:47.260 --> 00:51:50.090
at the Silverado
Community crew vehicles.

00:51:50.090 --> 00:51:52.290
Many of our executives went
out to be with our customers

00:51:52.290 --> 00:51:54.900
and team members over
the Thanksgiving activation

00:51:54.900 --> 00:51:56.483
to hear directly from them.

00:51:57.990 --> 00:52:00.530
In 2021, we also completed construction

00:52:00.530 --> 00:52:02.540
of manual transfer switch equipment,

00:52:02.540 --> 00:52:04.490
six resiliency zone sites,

00:52:04.490 --> 00:52:06.510
and now have seven resiliency zone sites

00:52:06.510 --> 00:52:09.960
in remote communities
impacted by PSPS events

00:52:09.960 --> 00:52:11.773
in 2019 and 2020.

00:52:12.630 --> 00:52:15.010
These are customer sites
where we entered into a contract

00:52:15.010 --> 00:52:17.350
to install generators-switching
equipment,

00:52:17.350 --> 00:52:20.200
and deploy backup
generation during an event.

00:52:20.200 --> 00:52:22.170
For example, during
our Thanksgiving Event,

00:52:22.170 --> 00:52:24.820
we deployed a generator
to the Cabazon Fuel Center

00:52:24.820 --> 00:52:26.173
as part of this program.

00:52:27.010 --> 00:52:29.560
Separately, we provided
community resource centers

00:52:29.560 --> 00:52:33.800
in Actan and Cabazon with
manual transfer switch equipment

00:52:33.800 --> 00:52:36.110
and deployed backup
generation to both sites

00:52:36.110 --> 00:52:37.610
during the Thanksgiving Event.

00:52:39.210 --> 00:52:40.610
Over the Thanksgiving Event,

00:52:40.610 --> 00:52:43.440
we were resource-constrained
and had some logistical issues

00:52:43.440 --> 00:52:46.400
that affected the delivery
of resiliency materials.

00:52:46.400 --> 00:52:47.920
We are currently expanding our pool

00:52:47.920 --> 00:52:49.940
of customer care team
members and looking

00:52:49.940 --> 00:52:52.170
at ways to smooth
those logistical issues

00:52:53.144 --> 00:52:53.977
that we experienced.

00:52:53.977 --> 00:52:56.540
We will also be continuing
to listen to our customers

00:52:56.540 --> 00:52:59.370
through onsite customer
research focus groups

00:52:59.370 --> 00:53:02.410
and through our working
group and community meetings.

00:53:02.410 --> 00:53:05.200
To increase feedback,
we added a QR code option

00:53:05.200 --> 00:53:08.693
to our onsite survey to
increase customer usability.

00:53:09.950 --> 00:53:14.950
In 2021, we deployed 6,021
critical care battery backup.

00:53:16.180 --> 00:53:18.490
Our 2022 goal will be to target

00:53:19.785 --> 00:53:21.440
an additional 2,750 batteries,

00:53:21.440 --> 00:53:25.193
which is about 35% of
remaining eligible customers.

00:53:26.400 --> 00:53:28.619
We acknowledge that not all customers

00:53:28.619 --> 00:53:30.790
who use a medical device
or assistive technology

00:53:30.790 --> 00:53:33.430
for independence,
health or safety are eligible

00:53:33.430 --> 00:53:36.534
for critical care battery
backup programs.

00:53:36.534 --> 00:53:40.110
In 2022, to further assist
customers with access

00:53:40.110 --> 00:53:42.640
and functional needs, we are piloting

00:53:42.640 --> 00:53:45.130
an in-event battery loan program

00:53:45.130 --> 00:53:48.540
to provide a portable
battery backup to customers

00:53:48.540 --> 00:53:51.780
who are notified of the
potential for de-energization

00:53:51.780 --> 00:53:53.810
as part of PSPS.

00:53:53.810 --> 00:53:54.790
We will be partnering

00:53:54.790 --> 00:53:56.960
with various
community-based organizations

00:53:56.960 --> 00:53:59.080
who serve customers disabilities

00:53:59.080 --> 00:54:02.870
and faith-based organizations
for implementation.

00:54:02.870 --> 00:54:04.610
I'll go ahead and pause here and see

00:54:04.610 --> 00:54:06.500
if there's any questions before we talk

00:54:06.500 --> 00:54:10.723
about some of our other
community customer care programs.

00:54:14.110 --> 00:54:18.170
Yes, I see Commissioner Rechtschaffen.

00:54:18.170 --> 00:54:19.575
<v ->Thanks.</v>

00:54:19.575 --> 00:54:22.310
Could you just clarify what
you said your target for 2022

00:54:22.310 --> 00:54:27.310
is 35% of remaining eligible customers?

00:54:27.478 --> 00:54:28.311
Is that right?

00:54:28.311 --> 00:54:32.100
<v ->Yes, exactly, of the
remaining eligible customers.</v>

00:54:32.100 --> 00:54:35.930
To date we've deployed batteries for 48%

00:54:35.930 --> 00:54:38.070
of total customers that are eligible.

00:54:38.070 --> 00:54:40.950
<v ->And what, and just remind us</v>

00:54:40.950 --> 00:54:43.080
what the universe is
that you're describing.

00:54:43.080 --> 00:54:45.400
Are these all critical-care customers

00:54:45.400 --> 00:54:47.610
or Medical Baselines customers,

00:54:47.610 --> 00:54:49.690
and are they in highly impacted circuits

00:54:49.690 --> 00:54:54.510
or what is the universe,
the 48% and the 35%?

00:54:54.510 --> 00:54:58.260
If you've done that 48
and you have targeting 35,

00:54:58.260 --> 00:55:00.960
how many will be
remaining in the numerator?

00:55:00.960 --> 00:55:04.310
If I could ask you a
compound question like that.

00:55:04.310 --> 00:55:08.270
<v ->So, yeah, no, and trust me,
I'm always asking for the map.</v>

00:55:08.270 --> 00:55:11.030
So I'll start with the denominator.

00:55:11.030 --> 00:55:14.520
The denominator is
14,000 eligible customers,

00:55:14.520 --> 00:55:17.950
and we define those as
customers that are enrolled

00:55:17.950 --> 00:55:21.620
in Medical Baseline for
our care fair programs,

00:55:21.620 --> 00:55:24.420
which are income-qualified
rate programs,

00:55:24.420 --> 00:55:27.580
and that also live in a high fire zone.

00:55:27.580 --> 00:55:29.483
So that's the total.

00:55:30.596 --> 00:55:35.207
In total, we've deployed
to 6,741 customers.

00:55:36.170 --> 00:55:40.760
And in 2022, we'll be
adding to that 2,750.

00:55:42.360 --> 00:55:43.590
So the numerator,

00:55:43.590 --> 00:55:48.313
to answer your questions, is 9,491.

00:55:56.924 --> 00:55:59.680
<v ->Well, you have another
four to 5,000 that you still need</v>

00:55:59.680 --> 00:56:04.030
to reach over that, after 2022.

00:56:04.030 --> 00:56:05.410
And some of them you're targeting

00:56:05.410 --> 00:56:07.820
with this in-event battery loan pilot,

00:56:07.820 --> 00:56:10.640
but otherwise you just
you're are still trying

00:56:10.640 --> 00:56:14.910
to get those customers
backup batteries, basically.

00:56:14.910 --> 00:56:15.743
<v ->Yes.</v>

00:56:15.743 --> 00:56:20.743
And just to elaborate
on that, SCE notifies

00:56:20.903 --> 00:56:22.690
the customers that are eligible,

00:56:22.690 --> 00:56:25.160
and we actually have
additional customers

00:56:25.160 --> 00:56:29.060
that are eligible each month,

00:56:29.060 --> 00:56:30.740
we add them to the list of customers

00:56:30.740 --> 00:56:32.240
that we're reaching out to.

00:56:32.240 --> 00:56:35.730
And we attempt to reach
out to those customers

00:56:35.730 --> 00:56:39.310
through direct mail
and letters and emails.

00:56:39.310 --> 00:56:41.050
We try up to three times,

00:56:41.050 --> 00:56:44.490
and then the vendor that
we work with will conduct

00:56:44.490 --> 00:56:48.380
up to six outbound calls
to eligible customers,

00:56:48.380 --> 00:56:51.030
and we're doing this on a monthly basis.

00:56:51.030 --> 00:56:54.130
In addition, we're providing
information and education

00:56:54.130 --> 00:56:57.370
to community-based organizations,

00:56:57.370 --> 00:56:59.350
and we're using social media platforms

00:56:59.350 --> 00:57:03.900
like Nextdoor and Twitter
in order to reach customers.

00:57:03.900 --> 00:57:07.055
In addition, we're
actually going in-person

00:57:07.055 --> 00:57:10.510
and knocking on doors to
try to reach more people.

00:57:10.510 --> 00:57:13.480
and we actually just
got an update last night

00:57:13.480 --> 00:57:16.140
that last year, just
through knocking on doors,

00:57:16.140 --> 00:57:17.910
not just calling or emailing,

00:57:17.910 --> 00:57:22.260
we've delivered batteries to
an additional, 106, excuse me,

00:57:22.260 --> 00:57:26.103
106 batteries to an additional
amount of customers.

00:57:30.910 --> 00:57:34.320
<v ->And do you know how
many are, what percentage</v>

00:57:34.320 --> 00:57:39.320
of the relative share
of those 14,000 have

00:57:39.410 --> 00:57:41.120
that are in highly impacted

00:57:41.120 --> 00:57:43.650
or frequently impacted
circuits have you been able

00:57:43.650 --> 00:57:44.853
to get batteries to?

00:57:48.730 --> 00:57:50.630
<v ->Could you state
that question again?</v>

00:57:51.900 --> 00:57:55.360
<v ->I was asking you for the
frequently impacted circuits,</v>

00:57:55.360 --> 00:57:57.483
which is a lower number

00:57:57.483 --> 00:58:00.231
than all your high-fire threat areas,

00:58:00.231 --> 00:58:03.507
so I'm curious if you have
any idea of the percentage

00:58:03.507 --> 00:58:07.630
of customers, eligible
customers that you've reached

00:58:07.630 --> 00:58:10.500
in those frequently impacted circuits

00:58:10.500 --> 00:58:15.500
as opposed to the entire
universe of high-fire threat areas?

00:58:17.780 --> 00:58:18.980
<v ->Thank you for clarifying.</v>

00:58:18.980 --> 00:58:20.418
Right.

00:58:20.418 --> 00:58:21.442
And as we've been talking about,

00:58:21.442 --> 00:58:24.605
the 14,000 is in the
high-fire threat area.

00:58:24.605 --> 00:58:26.087
I don't have the statistic

00:58:26.087 --> 00:58:28.047
on the frequently impacted customers,

00:58:28.047 --> 00:58:30.873
but we can get that
number and get back to you.

00:58:32.340 --> 00:58:34.160
<v ->Thank you very much.</v>

00:58:34.160 --> 00:58:35.750
<v ->Thank you.</v>

00:58:35.750 --> 00:58:37.050
And Commissioner Reynolds.

00:58:39.630 --> 00:58:42.180
<v ->Just as a follow-up
on the battery question,</v>

00:58:42.180 --> 00:58:45.040
can you explain a little
bit more about what types

00:58:45.040 --> 00:58:46.500
of batteries these are?

00:58:46.500 --> 00:58:48.563
It sounds like they're not portable

00:58:48.563 --> 00:58:50.281
because that's a separate program.

00:58:50.281 --> 00:58:51.114
Are they whole house batteries?

00:58:51.114 --> 00:58:55.560
And are there batteries that
work in multifamily buildings

00:58:55.560 --> 00:58:57.240
as well as single family buildings?

00:58:57.240 --> 00:58:59.461
If you could just give me
some more detail on that,

00:58:59.461 --> 00:59:00.840
that would be great.

00:59:00.840 --> 00:59:01.673
<v ->Sure.</v>

00:59:01.673 --> 00:59:05.160
The batteries are, they are portable

00:59:05.160 --> 00:59:06.870
in that they can move around,

00:59:06.870 --> 00:59:11.870
and the larger ones actually
are on a cart that have wheels.

00:59:12.440 --> 00:59:15.820
So they're not like a
power wall, for example.

00:59:15.820 --> 00:59:18.900
And they come in
multiple different sizes.

00:59:18.900 --> 00:59:23.900
We have 1,500 watt-hour
battery up to 6,000 watt battery,

00:59:26.500 --> 00:59:29.310
and they can, we talk to customers

00:59:29.310 --> 00:59:31.880
about what medical devices they have

00:59:31.880 --> 00:59:34.880
and then we help to size
the type battery that they get

00:59:34.880 --> 00:59:37.543
based on the medical
equipment that they're running.

00:59:40.060 --> 00:59:40.893
<v ->Thank you.</v>

00:59:42.939 --> 00:59:45.020
<v ->I have a question also.</v>

00:59:45.020 --> 00:59:48.870
Oh, sorry, Commissioner
Houck, I jump ahead of you.

00:59:48.870 --> 00:59:51.100
<v ->Oh no, no, I think raised
your hand before me,</v>

00:59:51.100 --> 00:59:53.863
but I either way, you wanna go first or?

00:59:54.990 --> 00:59:56.320
<v ->Okay, sure.</v>

00:59:56.320 --> 01:00:00.900
So, and for that
Thanksgiving Event, okay?

01:00:00.900 --> 01:00:03.490
Describe a little bit of what kind

01:00:03.490 --> 01:00:06.740
of customer care resources were deployed

01:00:07.610 --> 01:00:09.033
for that Thanksgiving Event.

01:00:10.290 --> 01:00:13.670
<v ->Yes, I'm happy to discuss that.</v>

01:00:13.670 --> 01:00:15.730
So during this Thanksgiving Event,

01:00:15.730 --> 01:00:20.300
we activated 13
community resource centers

01:00:20.300 --> 01:00:23.100
and community crew vehicles.

01:00:23.100 --> 01:00:25.012
So breaking that down,

01:00:25.012 --> 01:00:28.060
we had five community crew
vehicles throughout Los Angeles,

01:00:28.060 --> 01:00:31.123
Ventura, Orange and San Bernardino,

01:00:32.000 --> 01:00:35.220
and eight of the
community resource centers.

01:00:35.220 --> 01:00:37.120
And just as a reminder,

01:00:37.120 --> 01:00:39.010
I'm not sure if the different utilities

01:00:39.010 --> 01:00:41.443
use different terminology, but for us,

01:00:42.343 --> 01:00:43.240
the community crew vehicles

01:00:43.240 --> 01:00:46.077
are vehicles that can be moved

01:00:46.077 --> 01:00:46.950
throughout our service area

01:00:46.950 --> 01:00:50.253
depending on need and our
community resource centers,

01:00:51.584 --> 01:00:55.700
our locations, like community
centers, police departments,

01:00:55.700 --> 01:00:58.240
sometimes hotels or motels,

01:00:58.240 --> 01:01:00.430
that our actual physical locations.

01:01:00.430 --> 01:01:01.830
And so during Thanksgiving,

01:01:01.830 --> 01:01:05.470
we had eight of those
community resource centers

01:01:05.470 --> 01:01:08.340
that were open and
available to customers.

01:01:08.340 --> 01:01:10.410
In addition to some of the things

01:01:10.410 --> 01:01:12.120
that we were doing over Thanksgiving

01:01:12.120 --> 01:01:17.120
is that we distributed
2,818 $25 grocery gift cards.

01:01:18.440 --> 01:01:21.080
And that was for a
total of about $70,000

01:01:21.080 --> 01:01:23.100
through these various locations.

01:01:23.100 --> 01:01:24.640
We distributed snacks,

01:01:24.640 --> 01:01:29.130
water, resiliency kits that
included phone chargers

01:01:29.130 --> 01:01:33.520
and LED lights in addition to
personal protective equipment

01:01:34.864 --> 01:01:36.650
and additional program
and resource information

01:01:36.650 --> 01:01:37.623
to our customers.

01:01:40.220 --> 01:01:41.614
Thank you.

01:01:41.614 --> 01:01:42.447
<v ->Did that answer the question?</v>

01:01:42.447 --> 01:01:43.280
<v ->Yes.</v>

01:01:43.280 --> 01:01:44.113
Yes, thank you.

01:01:48.050 --> 01:01:50.030
<v ->I just wanted to get a
little more information</v>

01:01:50.030 --> 01:01:51.200
about your coordination

01:01:51.200 --> 01:01:53.190
with the community-based organizations.

01:01:53.190 --> 01:01:58.010
I think the earlier slide
referenced 1,600 organizations.

01:01:58.010 --> 01:01:59.340
And if you could just talk a little bit

01:01:59.340 --> 01:02:01.250
about how you're engaging with them

01:02:02.329 --> 01:02:04.070
and how they're engaging

01:02:04.070 --> 01:02:07.987
with of customers,
and then also the local

01:02:07.987 --> 01:02:09.390
and tribal engagements.

01:02:09.390 --> 01:02:11.420
I think it said there was 134,

01:02:11.420 --> 01:02:13.978
and if you could
give a little more detail

01:02:13.978 --> 01:02:15.560
about how you're working with
local and tribal governments,

01:02:15.560 --> 01:02:17.210
that would be really appreciated.

01:02:18.740 --> 01:02:19.573
<v ->Great, thank you.</v>

01:02:19.573 --> 01:02:23.453
Yeah, we work with over
1,600 different nonprofits,

01:02:24.437 --> 01:02:28.220
and they're community-based
organizations

01:02:28.220 --> 01:02:30.320
that serve all various
types of customers,

01:02:30.320 --> 01:02:33.140
including those with Access
and Functional Needs.

01:02:33.140 --> 01:02:36.670
We partner with them by
providing them with information

01:02:36.670 --> 01:02:39.330
on the various services that we offer,

01:02:39.330 --> 01:02:41.730
and they distribute that
through their channels

01:02:41.730 --> 01:02:44.850
to the communities that they serve.

01:02:44.850 --> 01:02:48.890
We're actually this year looking
into working with new types

01:02:48.890 --> 01:02:52.014
of community organizations,
like independent living centers,

01:02:52.014 --> 01:02:57.014
area agencies on aging, food
banks and nutritional programs,

01:02:57.910 --> 01:03:01.886
and we're looking to
distribute more battery backup

01:03:01.886 --> 01:03:04.603
through those projects.

01:03:05.500 --> 01:03:08.130
We also use those
community-based organizations.

01:03:08.130 --> 01:03:09.990
They have various social media channels

01:03:09.990 --> 01:03:13.390
that they can provide
information to their constituents on.

01:03:13.390 --> 01:03:14.610
So we do that.

01:03:14.610 --> 01:03:17.700
We really are working
with them very regularly

01:03:17.700 --> 01:03:21.230
and we also have instituted

01:03:21.230 --> 01:03:23.370
an Access and Functional Needs Liaison

01:03:23.370 --> 01:03:28.050
that's dedicated during our
PSPS events to do coordination

01:03:28.050 --> 01:03:30.853
specifically with our
community-based organizations.

01:03:33.580 --> 01:03:36.121
And could you, I think
there was a second part

01:03:36.121 --> 01:03:36.954
of that question.

01:03:37.901 --> 01:03:40.482
Could you repeat that?

01:03:40.482 --> 01:03:41.315
I think it was on tribal
and local communication.

01:03:41.315 --> 01:03:42.786
<v ->Yes.</v>

01:03:42.786 --> 01:03:44.330
Could you give a little more
detail about your coordination

01:03:44.330 --> 01:03:47.063
and engagement with
tribal and local government?

01:03:49.104 --> 01:03:50.180
<v ->Great.</v>

01:03:50.180 --> 01:03:53.300
On that one, I'm going to see

01:03:53.300 --> 01:03:58.300
if I have another speaker that
can speak to that from SCE.

01:04:03.920 --> 01:04:05.870
<v ->Okay, Katie, I
think I can take that.</v>

01:04:07.160 --> 01:04:09.470
<v ->Thank you.</v>
<v ->So we're actually,</v>

01:04:09.470 --> 01:04:12.873
we're actually engaging with
a number of tribes in our area.

01:04:14.197 --> 01:04:16.610
There's 13 tribes in
SCE's service territory,

01:04:16.610 --> 01:04:20.040
nine are located in
high fire risk areas.

01:04:20.040 --> 01:04:22.930
And so we engage with
them on a regular basis.

01:04:22.930 --> 01:04:26.290
We've got SCE representatives
that are assigned to each

01:04:26.290 --> 01:04:29.771
of the tribal governments
and regularly engage them.

01:04:29.771 --> 01:04:33.120
We've held several workshops in 2021

01:04:33.120 --> 01:04:36.480
specifically for the tribes
where SCE provided updates

01:04:36.480 --> 01:04:38.760
on our wildfire mitigation efforts,

01:04:38.760 --> 01:04:42.226
PSPS Public Safety Power portal,

01:04:42.226 --> 01:04:45.440
as well as information on
customer care programs,

01:04:45.440 --> 01:04:47.671
resiliency opportunities

01:04:47.671 --> 01:04:50.233
such as self-generation
incentive program

01:04:50.233 --> 01:04:51.283
and resiliency zones.

01:04:52.903 --> 01:04:55.303
And so that engagement
will continue in 2022,

01:04:56.680 --> 01:05:00.370
and yeah, we'll continue
promoting those engagements

01:05:00.370 --> 01:05:03.773
with each of those tribes as
we move into the new year.

01:05:07.490 --> 01:05:09.927
<v ->Thank you, and are you.</v>
<v ->Did that</v>

01:05:09.927 --> 01:05:10.825
answer your question?

01:05:10.825 --> 01:05:12.380
<v ->And then do you have similar
engagement that you described</v>

01:05:12.380 --> 01:05:15.490
with the tribes with the
local governments as well?

01:05:15.490 --> 01:05:16.550
<v ->Yes, we do.</v>

01:05:16.550 --> 01:05:19.400
Very similarly, we engage
with local governments

01:05:19.400 --> 01:05:23.960
as well as with our critical
infrastructure customers.

01:05:23.960 --> 01:05:28.860
We handle, we get together
with them in workshops,

01:05:28.860 --> 01:05:32.620
resiliency workshops, PSPS updates,

01:05:32.620 --> 01:05:35.640
making sure that they've
got information on the latest

01:05:35.640 --> 01:05:38.513
and greatest that were
working on in the PSPS space,

01:05:40.354 --> 01:05:43.543
and hosting similar
workshops with them as well.

01:05:45.520 --> 01:05:46.940
<v ->Thank you.</v>

01:05:46.940 --> 01:05:48.760
<v ->Hey Michael, just one
thing that I wanted to share</v>

01:05:48.760 --> 01:05:49.727
to build on that

01:05:51.012 --> 01:05:53.740
with an emergency
management engagement angle,

01:05:53.740 --> 01:05:57.200
also both prior to
events and during events,

01:05:57.200 --> 01:05:58.860
lots of engagement with our county

01:05:58.860 --> 01:06:01.890
and state emergency
management officials county

01:06:01.890 --> 01:06:03.520
at the operational area level,

01:06:03.520 --> 01:06:04.790
really getting in and out and meeting

01:06:04.790 --> 01:06:07.540
with those emergency
management directors

01:06:07.540 --> 01:06:09.730
to close the feedback,
to help improve and refine

01:06:09.730 --> 01:06:11.480
our engagement protocols.

01:06:11.480 --> 01:06:14.160
And then the same thing with Cal OES,

01:06:14.160 --> 01:06:16.000
the California State Warning Center,

01:06:16.000 --> 01:06:19.080
also looking to standardize
some create consistency

01:06:19.080 --> 01:06:23.160
in how we respond and
handle in-event engagement

01:06:23.160 --> 01:06:24.140
with our state partners.

01:06:24.140 --> 01:06:26.303
So just wanted to
add that briefly as well.

01:06:28.650 --> 01:06:29.483
<v ->Thank you.</v>

01:06:33.520 --> 01:06:34.955
<v ->Great.</v>

01:06:34.955 --> 01:06:37.190
And I'm happy to, slide 11.

01:06:37.190 --> 01:06:40.060
I did want to do a quick, and make sure

01:06:40.060 --> 01:06:42.293
we still have some time here.

01:06:44.464 --> 01:06:45.350
I think we're at about one hour,

01:06:45.350 --> 01:06:48.690
but we, I still have
some functional needs

01:06:48.690 --> 01:06:51.190
and then we have upcoming
after that notification.

01:06:59.520 --> 01:07:02.870
So I'll go ahead and
con continue on that

01:07:02.870 --> 01:07:05.870
because I'm not seeing
anyone telling me to stop.

01:07:05.870 --> 01:07:06.983
Thank you for that.

01:07:07.860 --> 01:07:11.550
So moving on to slide 11,

01:07:11.550 --> 01:07:12.810
we've made some good strides

01:07:12.810 --> 01:07:16.160
in our Access and Functional
Needs Program in 2021,

01:07:16.160 --> 01:07:19.231
and I really just wanna take
the opportunity to call two

01:07:19.231 --> 01:07:20.064
of our team members.

01:07:20.064 --> 01:07:21.960
You can see here Dani Anderson pictured

01:07:21.960 --> 01:07:24.160
on our Government Relations Team,

01:07:24.160 --> 01:07:27.720
and also Jennifer Ocampo
on our Customer Care Team.

01:07:27.720 --> 01:07:29.820
Danny and Jennifer
have been both internal

01:07:29.820 --> 01:07:31.300
and external advisors for us,

01:07:31.300 --> 01:07:33.490
and Jennifer led a team that activated

01:07:33.490 --> 01:07:35.630
an Access and
Functionally Needs Liaisons

01:07:35.630 --> 01:07:36.680
that I mentioned earlier

01:07:36.680 --> 01:07:40.800
for every single one of
our activations in 2021.

01:07:40.800 --> 01:07:43.300
Jennifer's team engaged
community-based organizations

01:07:43.300 --> 01:07:44.520
like we've been talking about

01:07:44.520 --> 01:07:47.420
and resolved urgent
escalation issues from customers

01:07:47.420 --> 01:07:49.490
with access and functional needs.

01:07:49.490 --> 01:07:52.783
She was supported by
our partnership with 211

01:07:52.783 --> 01:07:56.040
to expand education and
connect customers to resources

01:07:56.040 --> 01:07:57.510
such as transportation,

01:07:57.510 --> 01:08:00.723
meal delivery and shelter
during PSPS events.

01:08:01.840 --> 01:08:03.540
We've also expanded our customers

01:08:03.540 --> 01:08:05.840
who receive escalated
notification attempts

01:08:05.840 --> 01:08:09.100
to all Medical Baseline
customers and customers

01:08:09.100 --> 01:08:12.360
who self-certify as sensitive
while also expanding

01:08:12.360 --> 01:08:16.460
customer enrollment in
Medical Baseline by close to 9%.

01:08:16.460 --> 01:08:19.550
We did this increase in
Medical Baseline enrollment

01:08:19.550 --> 01:08:22.680
through email outreach
to 420,000 customers

01:08:22.680 --> 01:08:24.933
and also digital advertising.

01:08:25.970 --> 01:08:27.739
We still have some gaps,

01:08:27.739 --> 01:08:29.670
and these are also addressed

01:08:29.670 --> 01:08:32.530
in the AFN plan that
we filed last month.

01:08:32.530 --> 01:08:34.750
But in particular, we are contracting

01:08:34.750 --> 01:08:36.700
with third-party vendors to prepare

01:08:36.700 --> 01:08:38.900
and send PSPS notifications

01:08:38.900 --> 01:08:42.730
and educational outreach
materials in American Sign Language

01:08:42.730 --> 01:08:46.380
and with English voice and
text-accessible communications

01:08:46.380 --> 01:08:48.100
for individuals who are deaf,

01:08:48.100 --> 01:08:51.610
blind, deaf-blind and heart of hearing.

01:08:51.610 --> 01:08:54.990
We are also continuing our
efforts to increase medical base

01:08:54.990 --> 01:08:57.530
even further CARE DERA enrollment,

01:08:57.530 --> 01:08:59.450
which are our rate discount programs,

01:08:59.450 --> 01:09:02.460
in addition to enhancing
other service offerings.

01:09:02.460 --> 01:09:05.122
So I will stop here for questions

01:09:05.122 --> 01:09:07.493
before I hand it over
to Michael William.

01:09:13.900 --> 01:09:15.273
Okay.

01:09:15.273 --> 01:09:17.020
I think we got most of the
questions from the last slide.

01:09:17.020 --> 01:09:20.420
So I will go ahead and
hand this over to Michael

01:09:20.420 --> 01:09:23.200
to discuss how we're informing
partners and customers.

01:09:23.200 --> 01:09:24.090
Thank you, all.

01:09:39.230 --> 01:09:40.665
<v ->Sorry about that.</v>

01:09:40.665 --> 01:09:41.500
I think that was on mute.

01:09:41.500 --> 01:09:42.410
Thank you for that, Katie.

01:09:42.410 --> 01:09:45.508
And if you wouldn't mind
moving to the next slide, please,

01:09:45.508 --> 01:09:46.341
that would be great.

01:09:47.210 --> 01:09:49.470
So thanks for the question early on,

01:09:49.470 --> 01:09:52.474
because I think that provided
a terrific segue into some

01:09:52.474 --> 01:09:54.850
of the things that we're doing

01:09:54.850 --> 01:09:57.420
based on our learnings in 2021.

01:09:57.420 --> 01:09:59.600
First thing that I wanted
to stress is we did do

01:09:59.600 --> 01:10:02.050
a major overhaul of
our notification process

01:10:02.050 --> 01:10:03.770
and our content.

01:10:03.770 --> 01:10:06.700
Turns out that we've
done quite a bit of research,

01:10:06.700 --> 01:10:09.470
and the research that
we have done suggests

01:10:09.470 --> 01:10:12.640
that the notifications that
we've, the modifications

01:10:12.640 --> 01:10:16.960
on our notifications
have been better received.

01:10:16.960 --> 01:10:18.530
And actually customer are saying

01:10:18.530 --> 01:10:21.421
that they understand them
better than what we had

01:10:21.421 --> 01:10:22.254
in the prior duration.

01:10:22.254 --> 01:10:23.087
So we'll be doing more research.

01:10:23.087 --> 01:10:26.250
We wanna make sure we stay
connected with our customers,

01:10:26.250 --> 01:10:29.420
and we'll continue, if required,
to optimize our messaging

01:10:29.420 --> 01:10:32.190
as we get that feedback
from our customers.

01:10:32.190 --> 01:10:33.370
That's the good news,

01:10:33.370 --> 01:10:36.230
but now I wanna discuss
the room for improvement,

01:10:36.230 --> 01:10:38.262
as Erik mentioned earlier,

01:10:38.262 --> 01:10:40.695
that Thanksgiving period event,

01:10:40.695 --> 01:10:42.600
it taught us quite a bit.

01:10:42.600 --> 01:10:44.530
We didn't provide, it
turns out we didn't provide

01:10:44.530 --> 01:10:49.430
advanced notice to a number
of customers of de-energization

01:10:49.430 --> 01:10:50.540
to a number of customers.

01:10:50.540 --> 01:10:53.850
And so we're gonna be
providing revised numbers to that.

01:10:53.850 --> 01:10:56.440
And frankly, neither
the lack of notification

01:10:56.440 --> 01:11:00.260
nor the data errors requiring
revision were acceptable

01:11:00.260 --> 01:11:01.553
to us or our leaders.

01:11:03.030 --> 01:11:06.310
Given our approach to
de-energization that is to continue

01:11:06.310 --> 01:11:09.830
to de-energize as few
customers as possible,

01:11:09.830 --> 01:11:12.330
and only when it's absolutely necessary,

01:11:12.330 --> 01:11:15.387
we don't pre-schedule
the de-energization.

01:11:15.387 --> 01:11:16.670
And that makes it a
little bit more complex

01:11:16.670 --> 01:11:20.120
to manage as Tom mentioned earlier.

01:11:20.120 --> 01:11:21.900
Over Thanksgiving, as Erik mentioned,

01:11:21.900 --> 01:11:24.639
we faced a lot of
changing weather patterns,

01:11:24.639 --> 01:11:28.010
and some that were totally anticipated.

01:11:28.010 --> 01:11:30.200
So we had some data issues as well,

01:11:30.200 --> 01:11:33.010
and we were working with
our legacy notification system.

01:11:33.010 --> 01:11:35.778
That slowed down the
transfer of information.

01:11:35.778 --> 01:11:38.120
The completion of the
Foundry automation,

01:11:38.120 --> 01:11:41.510
which we're very excited
about, promises to support faster

01:11:41.510 --> 01:11:44.450
and more accurate
notifications going forward.

01:11:44.450 --> 01:11:46.801
So we're looking forward
to the full deployment

01:11:46.801 --> 01:11:49.083
of that system and being
able to use that this year.

01:11:50.220 --> 01:11:51.880
The second issue,

01:11:51.880 --> 01:11:54.870
which is the issue of the
accurate post-event reporting

01:11:54.870 --> 01:11:58.000
will also be addressed
because we're gonna be codifying

01:11:58.000 --> 01:11:59.842
the data sources.

01:11:59.842 --> 01:12:02.730
Instead of having disparate
data sources that we use

01:12:02.730 --> 01:12:06.620
during the reporting process,
information in the event

01:12:06.620 --> 01:12:09.820
will flow directly into
our operational system

01:12:09.820 --> 01:12:12.440
and into our post-event
reporting, which means

01:12:12.440 --> 01:12:14.230
we'll have a single source truth,

01:12:14.230 --> 01:12:16.310
and it means that we'll
be able to generate

01:12:16.310 --> 01:12:19.380
that information much more quickly.

01:12:19.380 --> 01:12:21.680
One additional area that
continues to be a challenge

01:12:21.680 --> 01:12:24.460
in notifications, and
also the web content,

01:12:24.460 --> 01:12:29.130
is providing more specific
estimated restoration times,

01:12:29.130 --> 01:12:31.540
due to the time required
for line inspections mainly.

01:12:31.540 --> 01:12:33.686
And I think Tom
touched on this a little bit

01:12:33.686 --> 01:12:34.607
previously as well.

01:12:34.607 --> 01:12:38.038
There are a lot of
variables to consider in that.

01:12:38.038 --> 01:12:40.170
We need to understand
whether we're using truck patrols,

01:12:40.170 --> 01:12:45.030
air patrols, or even occasionally
hiking, on-foot patrols.

01:12:45.030 --> 01:12:47.150
If it's late in the day,
we've gotta evaluate

01:12:47.150 --> 01:12:48.850
whether the patrol can be safely

01:12:48.850 --> 01:12:52.200
and efficient, effectively
done overnight.

01:12:52.200 --> 01:12:54.960
And as many of you know,
we don't fly helicopter routes

01:12:54.960 --> 01:12:59.200
at night, and winds may
subside at night enough to end

01:12:59.200 --> 01:13:01.500
the event, but it could
still be too windy to fly

01:13:01.500 --> 01:13:02.393
in some areas.

01:13:03.830 --> 01:13:05.670
We're looking at a
variety of ways to increase

01:13:05.670 --> 01:13:08.530
the specificity of our
restoration estimates.

01:13:08.530 --> 01:13:10.010
Based on historical data,

01:13:10.010 --> 01:13:13.300
I think Tom mentioned some
of the modeling capabilities

01:13:13.300 --> 01:13:14.360
that we have,

01:13:14.360 --> 01:13:17.280
but also looking at historical
data and the frequency

01:13:17.280 --> 01:13:19.870
of impacts to certain
circuits should give us

01:13:19.870 --> 01:13:22.875
better information
on how to look forward

01:13:22.875 --> 01:13:25.700
to where restoration times might be,

01:13:25.700 --> 01:13:27.920
and to be able to deliver
those more dynamically

01:13:27.920 --> 01:13:31.540
so that they can be updated
as the situation requires.

01:13:31.540 --> 01:13:34.030
So we've been benchmarking
quite a bit with SDG&amp;E

01:13:34.030 --> 01:13:36.810
on this, and we hope
understand if their approach,

01:13:36.810 --> 01:13:39.210
which is to focus on
publishing information

01:13:39.210 --> 01:13:42.530
to their outage page
will work for us as well.

01:13:42.530 --> 01:13:45.130
So let me stop for questions
here for just a second.

01:13:51.150 --> 01:13:52.820
Yes, Commissioner.

01:13:52.820 --> 01:13:53.853
<v ->I have a question.</v>

01:13:55.530 --> 01:13:58.210
Can you describe in just simple terms

01:13:58.210 --> 01:14:02.283
how you changed your
message to be clearer or better?

01:14:04.010 --> 01:14:04.843
<v ->Yes.</v>

01:14:05.935 --> 01:14:06.780
<v ->You got that feedback too.</v>

01:14:06.780 --> 01:14:09.120
An example of language you're using now

01:14:09.120 --> 01:14:11.473
that made the notification better.

01:14:13.430 --> 01:14:15.450
<v ->Well, in the simplest
terms possible,</v>

01:14:15.450 --> 01:14:17.380
let me just say that what we were doing

01:14:17.380 --> 01:14:20.230
was, in our notifications,

01:14:20.230 --> 01:14:23.760
we were telling customers
that they could be de-energized

01:14:24.796 --> 01:14:28.090
and not explaining that
because weather patterns

01:14:28.090 --> 01:14:31.510
could shift, well, we let them know it

01:14:31.510 --> 01:14:32.920
because weather patterns do shift.

01:14:32.920 --> 01:14:35.950
There was a possibility that
they would not be de-energized.

01:14:35.950 --> 01:14:39.510
So they were a little bit
more rigid, if you will, prior.

01:14:39.510 --> 01:14:42.220
We actually hired a
third party to come in

01:14:42.220 --> 01:14:44.380
and help us evaluate that messaging

01:14:44.380 --> 01:14:47.680
and evaluate customer
feedback on that messaging

01:14:47.680 --> 01:14:50.560
so that we could speak a
little bit more plainly to them.

01:14:50.560 --> 01:14:54.940
So an example that might
help with this is for customers

01:14:54.940 --> 01:14:58.100
who are re-energized, but where we know

01:14:58.100 --> 01:15:00.413
there may still be a
risk of weather patterns,

01:15:00.413 --> 01:15:04.570
that could necessitate de-energization.

01:15:04.570 --> 01:15:08.095
We put in additional language
to help them understand

01:15:08.095 --> 01:15:09.020
that we're trying to mitigate risks,

01:15:09.020 --> 01:15:14.020
but we wanna also just
keep them aware of the fact

01:15:14.190 --> 01:15:15.940
that although they're re-energized,

01:15:15.940 --> 01:15:18.400
they may be de-energized again.

01:15:18.400 --> 01:15:21.780
But we created language that
was a little bit more palatable

01:15:21.780 --> 01:15:22.820
and better received.

01:15:22.820 --> 01:15:25.377
And I think that's what
created the improvement

01:15:25.377 --> 01:15:28.800
and customer favorability
to the messaging

01:15:28.800 --> 01:15:31.253
that we've deployed going forward.

01:15:33.940 --> 01:15:34.773
<v ->Thank you.</v>

01:15:43.660 --> 01:15:44.493
<v ->All right.</v>

01:15:44.493 --> 01:15:46.183
So if we can move to the next slide.

01:15:49.240 --> 01:15:51.860
So we talked a little
bit about our outreach,

01:15:51.860 --> 01:15:56.860
and I was excited that we
focus quite a bit on the question

01:15:57.260 --> 01:15:58.590
that was asked earlier.

01:15:58.590 --> 01:16:01.080
We focused quite a bit
on increasing customer

01:16:01.080 --> 01:16:02.780
and community resiliency.

01:16:02.780 --> 01:16:05.330
So we ended up hosting
eight resiliency workshops

01:16:05.330 --> 01:16:06.520
for critical facilities

01:16:06.520 --> 01:16:09.320
and critical infrastructure
customers on topics

01:16:09.320 --> 01:16:12.990
such as PSPS, emergency
preparedness as well,

01:16:12.990 --> 01:16:14.853
and Public Safety Partner Portal.

01:16:15.896 --> 01:16:18.450
To assist the carriers in deployment

01:16:18.450 --> 01:16:19.920
of their backup power resources,

01:16:19.920 --> 01:16:22.960
we held one-on-one resiliency meetings

01:16:22.960 --> 01:16:26.423
with the major telecommunication
providers in our area.

01:16:27.310 --> 01:16:28.830
This helped to identify circuits

01:16:28.830 --> 01:16:33.500
and equipment locations that
are at risk for PSPS outages.

01:16:33.500 --> 01:16:36.130
Now, we realized this
is an ongoing discussion.

01:16:36.130 --> 01:16:38.000
and our commitment to
them to the Commission

01:16:38.000 --> 01:16:41.100
is that we're gonna continue
to meet with them in 2022

01:16:41.100 --> 01:16:43.913
to support their
PSPS resiliency efforts.

01:16:45.310 --> 01:16:48.591
We sent a targeted newsletter
also to all of our customers,

01:16:48.591 --> 01:16:51.440
who each received one of two additions.

01:16:51.440 --> 01:16:54.070
For some customers
in high fire risk areas,

01:16:54.070 --> 01:16:58.290
the content focused on PSPS
resiliency and information,

01:16:58.290 --> 01:17:00.132
while for the rest of our customers,

01:17:00.132 --> 01:17:02.840
it was more generally focused
on emergency preparedness.

01:17:02.840 --> 01:17:06.200
We'll be sending out our
2022 editions of the newsletter

01:17:06.200 --> 01:17:07.970
later this spring.

01:17:07.970 --> 01:17:10.210
Our advertising and
digital marketing efforts

01:17:10.210 --> 01:17:12.870
reflected this focus as well
and directed our customers

01:17:12.870 --> 01:17:15.263
to our website for
additional information.

01:17:16.690 --> 01:17:17.993
As Jill mentioned earlier,

01:17:19.060 --> 01:17:21.542
we also held more than 100 meetings

01:17:21.542 --> 01:17:23.890
with community members,
partners and jurisdictions.

01:17:23.890 --> 01:17:25.268
This included

01:17:25.268 --> 01:17:27.390
11 wildfire safety community
livestream meetings

01:17:27.390 --> 01:17:32.210
with 865 attendees, 15
power talk meetings attended

01:17:32.210 --> 01:17:35.430
by more than 500
customers, and 13 meetings

01:17:35.430 --> 01:17:39.290
with county operational
areas in our service territory.

01:17:39.290 --> 01:17:42.240
Additionally, our Local
Public Affairs Team briefed

01:17:42.240 --> 01:17:45.820
or communicated with
125 local governments

01:17:45.820 --> 01:17:48.510
and nine tribal governments
and made presentations

01:17:48.510 --> 01:17:50.770
to government and business associations

01:17:50.770 --> 01:17:53.140
on SCE's wildfire mitigation efforts

01:17:53.140 --> 01:17:56.133
and updates to help
them prepare for PSPS.

01:17:57.010 --> 01:17:59.810
So I'll pause there for just
a second for any questions.

01:18:08.580 --> 01:18:09.946
All right.

01:18:09.946 --> 01:18:11.546
Seeing none, next slide, please.

01:18:14.130 --> 01:18:17.100
So we've made pretty significant strides

01:18:17.100 --> 01:18:19.023
in our website in 2021,

01:18:20.077 --> 01:18:22.730
and I think the most significant
is that we consolidated

01:18:22.730 --> 01:18:25.470
our PSPS maintenance repair

01:18:25.470 --> 01:18:28.560
and rotating outage maps into one.

01:18:28.560 --> 01:18:30.990
Now, I like this because this simplifies

01:18:30.990 --> 01:18:34.660
how people find the status
of power at any location.

01:18:34.660 --> 01:18:37.650
If I go into a map, I wanna
be able to distinguish

01:18:37.650 --> 01:18:40.680
between PSPS or other types of outages

01:18:40.680 --> 01:18:42.692
that might be impacting me.

01:18:42.692 --> 01:18:43.630
It's easy to get these things confused.

01:18:43.630 --> 01:18:46.650
So we've tried to simplify this
for our customers, that way,

01:18:46.650 --> 01:18:50.330
they can make that
distinction on the map.

01:18:50.330 --> 01:18:53.320
We're gonna continue to
enhance this, and in 2022,

01:18:53.320 --> 01:18:57.050
we'll add the ability the
search for PSPS online maps

01:18:57.050 --> 01:18:59.370
and alerts using a meter number

01:18:59.370 --> 01:19:02.060
and also to sign up for PSPS alerts

01:19:02.060 --> 01:19:04.130
while turning on new service.

01:19:04.130 --> 01:19:07.470
So we're undergoing a
larger review and an update

01:19:07.470 --> 01:19:10.765
to the sce.com PSPS
pages with an outside agency.

01:19:10.765 --> 01:19:14.060
This should also help
with overall navigation

01:19:14.060 --> 01:19:14.900
for our customers,

01:19:14.900 --> 01:19:17.760
trying to make it a little
bit more user-friendly.

01:19:17.760 --> 01:19:21.150
Our weather awareness
map was introduced in 2021

01:19:21.150 --> 01:19:24.300
and currently shows a
seven-day extended forecast

01:19:24.300 --> 01:19:27.870
for PSPS weather by
county, and this map allows

01:19:27.870 --> 01:19:29.450
some pre-planning for customers

01:19:29.450 --> 01:19:32.170
and partners by letting them
know whether their county

01:19:32.170 --> 01:19:35.350
will be in PSPS watch or warning status.

01:19:35.350 --> 01:19:37.880
We still direct customers
to the PSPS map

01:19:37.880 --> 01:19:39.300
for more granular information

01:19:39.300 --> 01:19:41.270
as we get closer to the event,

01:19:41.270 --> 01:19:43.823
where we can provide
information at a circuit level.

01:19:44.920 --> 01:19:47.990
And then we'll also be
tying our GIS data flow

01:19:47.990 --> 01:19:49.730
into the Foundry automation product

01:19:49.730 --> 01:19:51.580
that's been talked about so much.

01:19:51.580 --> 01:19:53.780
This is gonna help to
improve the flow of information

01:19:53.780 --> 01:19:56.772
to the map and remove
some of the manual steps

01:19:56.772 --> 01:20:00.280
that are required to update our maps.

01:20:00.280 --> 01:20:01.623
So any questions on that?

01:20:03.690 --> 01:20:04.940
<v ->I just have a question.</v>

01:20:05.931 --> 01:20:07.500
A lot of the information
you're talking about seems

01:20:07.500 --> 01:20:09.470
to be web-based

01:20:09.470 --> 01:20:14.300
or is being given to
customers through some sort

01:20:14.300 --> 01:20:15.490
of electronic means.

01:20:15.490 --> 01:20:18.837
If they're in an outage
and they need information,

01:20:18.837 --> 01:20:23.837
how are they going to be
able to get that information?

01:20:24.290 --> 01:20:29.290
And are you, I guess they
would be looking at relying

01:20:30.120 --> 01:20:31.830
on cell phones potentially.

01:20:31.830 --> 01:20:34.920
So just maybe go into a little
more detail about your work

01:20:34.920 --> 01:20:37.880
with some of the telco
providers and just ensuring

01:20:37.880 --> 01:20:41.259
that there's access
to emergency services

01:20:41.259 --> 01:20:42.920
if somebody is in an outage
and isn't gonna be able

01:20:42.920 --> 01:20:45.693
to access some of the online material.

01:20:48.390 --> 01:20:50.898
<v ->So that's, I think
that's a really good point,</v>

01:20:50.898 --> 01:20:51.849
and it's something

01:20:51.849 --> 01:20:55.375
that we've talked quite a bit about,

01:20:55.375 --> 01:20:59.673
recognizing that a lot of
people are not accessing

01:20:59.673 --> 01:21:02.080
their computers during an outage event.

01:21:02.080 --> 01:21:04.130
We do take for granted

01:21:04.130 --> 01:21:07.660
that they are probably
in the cell phone space,

01:21:07.660 --> 01:21:11.357
although we have
additional outreach efforts

01:21:11.357 --> 01:21:12.300
through our Consumer Affairs Group,

01:21:12.300 --> 01:21:16.080
which will make sure that
certain customers are contacted.

01:21:16.080 --> 01:21:19.150
But I think what we're
trying to do is address

01:21:19.150 --> 01:21:23.910
and make as user-friendly
the mobile platforms

01:21:23.910 --> 01:21:26.870
that are available so that customers

01:21:26.870 --> 01:21:30.580
who have access to their
cell phones have got the ability

01:21:30.580 --> 01:21:32.170
to get regular updates.

01:21:32.170 --> 01:21:35.040
And then of course providing information

01:21:35.040 --> 01:21:38.040
on where we can keep those
cell phones charged up and ready

01:21:38.040 --> 01:21:40.550
through our community resource centers.

01:21:40.550 --> 01:21:43.960
Also the CCD vehicles that we dispatch.

01:21:43.960 --> 01:21:45.640
So the customers have some longevity

01:21:45.640 --> 01:21:47.503
with those resources.

01:21:48.681 --> 01:21:52.040
And I wanna make sure
I'm not missing anything.

01:21:52.040 --> 01:21:57.030
So we are continuing to
engage with our telco customers,

01:21:57.030 --> 01:21:58.670
as I mentioned earlier,

01:21:58.670 --> 01:22:02.320
and we are conducting engagement
meetings focused on telco,

01:22:02.320 --> 01:22:07.320
such as in our Public
Safety Partner Portal,

01:22:07.620 --> 01:22:09.360
critical infrastructure workshops

01:22:09.360 --> 01:22:11.920
and including and the
functional exercises to a system

01:22:11.920 --> 01:22:14.370
in their resiliency efforts.

01:22:14.370 --> 01:22:17.207
So I think those meetings
are gonna continue

01:22:17.207 --> 01:22:22.190
to provide ample information
on the notification process,

01:22:22.190 --> 01:22:25.140
the messaging types
as well as addressing

01:22:25.140 --> 01:22:26.970
public safety resiliency plans

01:22:26.970 --> 01:22:31.762
and Rural Communities Public
Safety Partner Portal training

01:22:31.762 --> 01:22:35.141
and enhancements, and
we also conduct simulations

01:22:35.141 --> 01:22:36.970
with our telco partners as well.

01:22:36.970 --> 01:22:40.200
And we invite them to be a
part of those engagements,

01:22:40.200 --> 01:22:42.966
so that we're ready and
we can address some

01:22:42.966 --> 01:22:45.570
of these challenges that
you might be mentioning.

01:22:45.570 --> 01:22:49.690
So these are good opportunities
for them to provide feedback

01:22:49.690 --> 01:22:51.010
and help us to shape the way

01:22:51.010 --> 01:22:54.410
that we approach these situations.

01:22:54.410 --> 01:22:55.243
And in addition,

01:22:55.243 --> 01:22:58.810
it provides an opportunity for
proactive engagement efforts

01:22:58.810 --> 01:23:00.960
for our account
managers that are available

01:23:01.930 --> 01:23:04.280
during and before an event

01:23:04.280 --> 01:23:06.847
and after the event to provide support

01:23:06.847 --> 01:23:08.900
and to answer questions.

01:23:08.900 --> 01:23:11.350
But there's a whole
lot going on out there

01:23:11.350 --> 01:23:14.290
and I like to say, we
can cover every base,

01:23:14.290 --> 01:23:16.610
and I think we're gonna
continue finding ways and looking

01:23:16.610 --> 01:23:18.240
for ways that we can make sure customers

01:23:18.240 --> 01:23:20.243
get the right information in hand.

01:23:22.450 --> 01:23:24.117
<v ->I'm just gonna add</v>

01:23:25.229 --> 01:23:30.229
on how customers are
using some of this information,

01:23:30.460 --> 01:23:33.140
'cause I think as Commissioner
Rechtschaffen commented

01:23:33.140 --> 01:23:34.730
on our earlier meeting this week.

01:23:34.730 --> 01:23:38.460
Most people are worried
about when that outage goes out

01:23:38.460 --> 01:23:43.330
and may not be doing the
research into some of these things.

01:23:43.330 --> 01:23:45.150
So any further information you have

01:23:45.150 --> 01:23:48.560
on and how you're assisting
customers and making sure

01:23:48.560 --> 01:23:51.447
they have what they need
through the notifications

01:23:51.447 --> 01:23:55.303
and during the outages,
we'll greatly appreciate it.

01:23:56.258 --> 01:23:57.290
And so thank you.

01:23:57.290 --> 01:23:58.140
<v ->Oh, absolutely.</v>

01:24:00.590 --> 01:24:01.690
<v ->And I just wanna tag</v>

01:24:01.690 --> 01:24:06.150
onto that (clears throat) for example,

01:24:06.150 --> 01:24:10.390
senior citizens who
maybe their only contact

01:24:10.390 --> 01:24:14.053
might be someone who's delivering
a meals on wheels package,

01:24:17.540 --> 01:24:21.223
no internet acumen.

01:24:22.058 --> 01:24:24.280
Maybe they have a wire line phone

01:24:25.120 --> 01:24:29.900
as far as what Edison is doing

01:24:29.900 --> 01:24:34.253
to reach those, kinds of customer.

01:24:35.900 --> 01:24:37.000
<v ->So-</v>
<v ->It'd be very.</v>

01:24:39.080 --> 01:24:41.460
<v ->Thank you for that question.</v>

01:24:41.460 --> 01:24:43.190
And in my experience,

01:24:43.190 --> 01:24:45.960
and I'm not responsible
for this particular area,

01:24:45.960 --> 01:24:48.770
so I may ask, I think Katie
probably has some insights

01:24:48.770 --> 01:24:51.900
on this, but I know that
we are engaging quite a bit

01:24:51.900 --> 01:24:56.250
with the counties and
coordinating efforts in conjunction

01:24:56.250 --> 01:24:59.960
with the counties so that
we can identify these types

01:24:59.960 --> 01:25:03.040
of customers to make
sure that we are conducting

01:25:03.040 --> 01:25:06.840
or supporting the efforts to
conduct in-person outreach

01:25:06.840 --> 01:25:09.713
where we know that those
vulnerable customers are at.

01:25:11.090 --> 01:25:14.510
I know that through our Access
and Functional Needs Program,

01:25:14.510 --> 01:25:16.700
we're taking a more proactive approach

01:25:16.700 --> 01:25:19.960
to identify these
customers, encouraging them

01:25:19.960 --> 01:25:23.970
to self-identify, but also
engaging in that outreach

01:25:23.970 --> 01:25:27.770
to make sure that we can
cover those where necessary.

01:25:27.770 --> 01:25:30.063
Katie, I don't know if you
want to add anything to that.

01:25:35.340 --> 01:25:36.755
<v ->Yes.</v>

01:25:36.755 --> 01:25:37.655
Thank you.

01:25:37.655 --> 01:25:39.800
Thanks for that.

01:25:39.800 --> 01:25:44.800
We are reaching out to
customers in different ways

01:25:45.320 --> 01:25:46.533
through our call center.

01:25:48.699 --> 01:25:49.532
We actually have been
working with customers

01:25:50.542 --> 01:25:52.070
that call using the California, Service,

01:25:52.070 --> 01:25:55.210
which is a sign language interpreter,

01:25:55.210 --> 01:25:58.343
and we're using that in order
to talk to other customers,

01:25:59.577 --> 01:26:04.577
for customers that can't use
some of those normal services.

01:26:06.150 --> 01:26:09.596
Additionally, we do have
a partnership with 211,

01:26:09.596 --> 01:26:12.410
and those customers, customers

01:26:12.410 --> 01:26:16.950
are being, for food,
transportation and shelter.

01:26:16.950 --> 01:26:18.900
And 211 is something that can be called

01:26:19.910 --> 01:26:20.743
with a landline.

01:26:20.743 --> 01:26:23.130
We do know that this is
an area for improvement

01:26:23.130 --> 01:26:27.480
and we are looking at other
ways to communicate and talk

01:26:27.480 --> 01:26:30.210
to various customers with
different types of needs.

01:26:30.210 --> 01:26:32.460
So I appreciate the
question and the concern.

01:26:36.110 --> 01:26:36.943
<v ->Thank you.</v>

01:26:41.120 --> 01:26:42.160
<v ->Hey, Katie and team,</v>

01:26:42.160 --> 01:26:43.830
I thought it'd be helpful
to provide a couple

01:26:43.830 --> 01:26:44.760
of case studies too

01:26:44.760 --> 01:26:48.430
based on the Thanksgiving
activation that we had.

01:26:48.430 --> 01:26:52.580
So I was the Lead Coach on
the Incident Management Team.

01:26:52.580 --> 01:26:56.210
And just one example that I
thought was worthwhile to share

01:26:56.210 --> 01:26:59.960
was working with the
independent living centers

01:26:59.960 --> 01:27:04.880
to triage escalated requests
for different types of things.

01:27:04.880 --> 01:27:09.180
So having medically,
customers reach out for example,

01:27:09.180 --> 01:27:11.330
and ask for access to backup batteries.

01:27:11.330 --> 01:27:13.060
I remember getting on phone calls

01:27:13.060 --> 01:27:16.340
with the County Emergency
Management Entities,

01:27:16.340 --> 01:27:19.610
as well as with our Access
and Functional Needs expert

01:27:19.610 --> 01:27:22.200
on the Incident Management
Team, to really triage and see

01:27:22.200 --> 01:27:25.860
what we can do to help
provide additional support

01:27:25.860 --> 01:27:26.693
to those folks.

01:27:26.693 --> 01:27:28.910
And in one case, we ended up dispatching

01:27:28.910 --> 01:27:32.130
a vacuum generator out to
that location so that that person

01:27:32.130 --> 01:27:33.240
could have continued power

01:27:33.240 --> 01:27:35.290
because relocation wasn't possible.

01:27:35.290 --> 01:27:36.770
So I just thought that quick case study

01:27:36.770 --> 01:27:38.120
would be a helpful example.

01:27:43.480 --> 01:27:44.380
<v ->Yeah, thank you.</v>

01:27:45.447 --> 01:27:47.030
Thank you for that.

01:27:48.380 --> 01:27:51.412
<v ->That's great input, Tom,
and thank you for that.</v>

01:27:51.412 --> 01:27:52.245
And thanks, Katie.

01:27:52.245 --> 01:27:53.078
Appreciate the question.

01:27:53.078 --> 01:27:55.498
I know we need to kind of move it along.

01:27:55.498 --> 01:27:56.970
So let me ask that
we go to the next slide.

01:27:56.970 --> 01:27:57.920
I'll talk a little bit

01:27:57.920 --> 01:28:00.023
about our Public Safety Partner Portal.

01:28:01.320 --> 01:28:05.080
So our portal was actually
launched in mid 2021,

01:28:05.080 --> 01:28:06.270
as many of you know,

01:28:06.270 --> 01:28:09.570
and was used on PSPS
events starting in June.

01:28:09.570 --> 01:28:12.250
So this secure
password-protected site is intended

01:28:12.250 --> 01:28:15.470
to be a one-stop shop for
our public safety partners

01:28:15.470 --> 01:28:17.800
and critical infrastructure customers.

01:28:17.800 --> 01:28:19.760
And we've been gradually
increasing its features

01:28:19.760 --> 01:28:23.060
and functionality as well
as its enrollment to the site.

01:28:23.060 --> 01:28:26.080
To date, we have 600-plus users.

01:28:26.080 --> 01:28:29.321
For reference, we have
approximately 40 users

01:28:29.321 --> 01:28:31.010
on our legacy GIS-based platform.

01:28:31.010 --> 01:28:33.950
So this is a pretty significant
increase in utilization,

01:28:33.950 --> 01:28:36.010
and we're really excited about that.

01:28:36.010 --> 01:28:39.671
After a benchmarking session
with PG&amp;E and SDG&amp;E to discuss

01:28:39.671 --> 01:28:42.480
some of the key
features and capabilities,

01:28:42.480 --> 01:28:45.730
we added a weekly user
group session to identify

01:28:45.730 --> 01:28:48.040
and triage issues and get feedback

01:28:48.040 --> 01:28:49.450
for future portal enhancements.

01:28:49.450 --> 01:28:51.050
We wanna continue to develop this

01:28:51.050 --> 01:28:54.150
and make sure that it's
useful to our partners.

01:28:54.150 --> 01:28:57.320
So for 2022, we're gonna
continue to enhance the portal

01:28:58.180 --> 01:29:02.780
by making in-event
information more on the site

01:29:02.780 --> 01:29:06.320
after the events have concluded
and prior to being archived.

01:29:06.320 --> 01:29:09.260
We also want to provide
additional functionality to mimic

01:29:09.260 --> 01:29:12.330
the previous legacy GIS-based platform

01:29:12.330 --> 01:29:15.653
for telecom providers
and public safety partners.

01:29:16.550 --> 01:29:18.000
And based on feedback, we're starting

01:29:18.000 --> 01:29:19.620
to introduce, feature

01:29:19.620 --> 01:29:22.543
to reduce unwanted
portal email notifications.

01:29:23.750 --> 01:29:26.540
Lastly, we're doing some
exploratory research to understand

01:29:26.540 --> 01:29:29.320
how and if we should be
expanding the portal to be available

01:29:29.320 --> 01:29:33.030
for major all-hazard events as well.

01:29:33.030 --> 01:29:36.810
So let me stop and I'll
ask the questions there,

01:29:36.810 --> 01:29:40.503
and if not, then we can move to close.

01:29:47.401 --> 01:29:48.870
<v ->Okay, why don't I pick
it up from here, Michael?</v>

01:29:48.870 --> 01:29:50.623
So thank you very much.

01:29:51.769 --> 01:29:56.420
If you could go to our last
slide, I wanna wrap, oh, sorry.

01:29:56.420 --> 01:30:00.140
Back a back a little
bit, one more, back.

01:30:00.140 --> 01:30:00.973
There we go.

01:30:00.973 --> 01:30:02.430
Thanks.

01:30:02.430 --> 01:30:03.263
There we go.

01:30:03.263 --> 01:30:05.510
So I wanna end really where we started,

01:30:05.510 --> 01:30:07.450
which is just talking
about our commitment

01:30:07.450 --> 01:30:11.490
and very much our alignment
with what President Reynolds

01:30:11.490 --> 01:30:13.320
and Director Thomas Jacob laid out right

01:30:13.320 --> 01:30:18.090
from the very beginning that
our objective is to make sure

01:30:18.090 --> 01:30:21.890
we are using PSPS only
as a last resort to make sure

01:30:21.890 --> 01:30:24.420
that we are keeping our customers,

01:30:24.420 --> 01:30:25.893
all of our customers,

01:30:27.301 --> 01:30:28.134
and especially our vulnerable customers,

01:30:29.731 --> 01:30:31.048
front of mind, that we are deploying

01:30:31.048 --> 01:30:32.360
every mitigation possible
to us through partnerships,

01:30:32.360 --> 01:30:34.230
through the tools we have,
through the interactions

01:30:34.230 --> 01:30:37.150
that we have with customers
year round to make sure

01:30:37.150 --> 01:30:40.010
that we are minimizing
any kind of impacts

01:30:40.010 --> 01:30:44.340
that last resort use of PSPS
might have on our customers.

01:30:44.340 --> 01:30:49.300
We at the same time are
very realistic about the problem

01:30:50.159 --> 01:30:52.353
that we are confronting,
and I think it was brought up

01:30:52.353 --> 01:30:54.790
in one of the earlier
comments about climate change

01:30:54.790 --> 01:30:57.620
and how extreme weather
is here with us to stay.

01:30:57.620 --> 01:31:00.850
It was just reported that we're in one

01:31:00.850 --> 01:31:03.460
of the worst drought
periods of, I don't remember

01:31:04.495 --> 01:31:06.043
what it was, something like 1,000 years.

01:31:06.043 --> 01:31:08.930
So we know we have to be
very thoughtful about the realities

01:31:08.930 --> 01:31:12.151
of the environment that we're
operating in and make sure

01:31:12.151 --> 01:31:16.000
that we are moving appropriately
to manage and mitigate

01:31:16.000 --> 01:31:20.500
the risks to all of our customers
that comes from wildfire,

01:31:20.500 --> 01:31:23.920
while every time we
are using any of the tools

01:31:23.920 --> 01:31:26.570
in our tool belt, that we
are think being thoughtful

01:31:26.570 --> 01:31:29.640
of the customers that
are being impacted.

01:31:29.640 --> 01:31:32.960
So that's why we really look
at this as a year-round effort,

01:31:32.960 --> 01:31:35.947
a year-round
relationship-building with partners,

01:31:35.947 --> 01:31:37.620
a year-round education
effort with our customers,

01:31:37.620 --> 01:31:40.140
to make sure that they're
ready, and as Michael just said,

01:31:40.140 --> 01:31:41.930
for all hazards.

01:31:41.930 --> 01:31:43.610
I think we've made a lot of strides.

01:31:43.610 --> 01:31:48.450
If you just look in from '21
to compared to '20 or go back

01:31:48.450 --> 01:31:51.140
even another year from
there, but as you heard

01:31:51.140 --> 01:31:53.660
from, I think every single
speaker, we recognize

01:31:53.660 --> 01:31:56.140
we still have a lot of
opportunity for improvement.

01:31:56.140 --> 01:31:59.030
And so I'll give you my
commitment that we know

01:31:59.030 --> 01:32:01.710
what we can do better, and
we know that we will do better

01:32:01.710 --> 01:32:05.070
in our execution, and
we are completely aligned

01:32:05.070 --> 01:32:10.070
with the objectives to keep
PSPS on a declining use

01:32:10.360 --> 01:32:13.320
year over year and
to a very targeted way

01:32:13.320 --> 01:32:16.670
in the case where it is
really focused on keeping

01:32:16.670 --> 01:32:18.560
the community safe
when that's the only tool

01:32:18.560 --> 01:32:20.454
that's left to us.

01:32:20.454 --> 01:32:23.170
So with that, I'll close
up the SCE portion.

01:32:23.170 --> 01:32:25.440
Thank you for allowing
us to go a little bit over,

01:32:25.440 --> 01:32:28.820
and myself and our
entire team will be available

01:32:28.820 --> 01:32:32.191
through the end of this
program to answer any questions

01:32:32.191 --> 01:32:33.103
that might come up later.

01:32:37.949 --> 01:32:39.270
<v ->I wanted to thank
the folks over at SCE.</v>

01:32:39.270 --> 01:32:41.352
I wanted to check with the panel,

01:32:41.352 --> 01:32:43.500
do we have any
additional question for SCE

01:32:43.500 --> 01:32:44.653
in their presentation?

01:32:49.660 --> 01:32:51.060
All right.

01:32:51.060 --> 01:32:52.689
Hearing none, I would like

01:32:52.689 --> 01:32:54.550
to turn it over to SDG&amp;E.

01:32:54.550 --> 01:32:58.813
Operator, can you give
the folks at SDG&amp;E access?

01:33:00.190 --> 01:33:02.423
I think we're gonna start
off with Kevin Geraghty.

01:33:05.500 --> 01:33:06.787
<v ->I just wanna make sure.</v>

01:33:08.070 --> 01:33:09.604
Oops!

01:33:09.604 --> 01:33:10.499
Hello.

01:33:10.499 --> 01:33:11.332
Just wanna make sure I'm
coming across loud and clear.

01:33:18.340 --> 01:33:19.736
<v ->You sound great.</v>

01:33:19.736 --> 01:33:20.840
Thank you.

01:33:20.840 --> 01:33:22.860
<v ->I'm sorry, can you hear me?</v>

01:33:22.860 --> 01:33:25.201
<v ->We can hear you.</v>
<v ->I can hear you.</v>

01:33:25.201 --> 01:33:26.100
<v ->Okay.</v>

01:33:26.100 --> 01:33:26.993
Thank you.

01:33:26.993 --> 01:33:28.140
So sorry for the confusion.

01:33:28.140 --> 01:33:29.600
Hey, good afternoon.

01:33:29.600 --> 01:33:33.890
Hey, thank you for having
the time to get together today.

01:33:33.890 --> 01:33:36.990
Thank you, President Reynolds
and respective Commissioners,

01:33:36.990 --> 01:33:40.810
Cal Fire Chiefs and
Director Thomas Jacobs.

01:33:40.810 --> 01:33:42.740
My name is Kevin Geraghty.

01:33:42.740 --> 01:33:46.120
I am SDG&amp;E Senior Vice
President for Electric Operations,

01:33:46.120 --> 01:33:49.600
and I also serve as
its Chief Safety Officer.

01:33:49.600 --> 01:33:52.390
My remarks will be brief
as we have quite a bit

01:33:52.390 --> 01:33:54.710
of information to share and discuss.

01:33:54.710 --> 01:33:59.710
Joining me today to share
SDG&amp;E's 2021 PSPS Experiences

01:34:00.712 --> 01:34:03.000
is our team of leaders
who I'm honored everyday

01:34:03.000 --> 01:34:05.280
to serve with, and who are focused

01:34:05.280 --> 01:34:09.680
on improving Public Safety
Power Shutoff at SDG&amp;E.

01:34:09.680 --> 01:34:12.249
You'll first hear from Brian D'Agostino,

01:34:12.249 --> 01:34:15.690
SDG&amp;E's Director of Fire
Science and Climate Adaptation.

01:34:15.690 --> 01:34:18.290
He'll present on forecasting.

01:34:18.290 --> 01:34:21.610
Zoraya Griffin, SDG&amp;E's
Senior Communications Manager,

01:34:21.610 --> 01:34:25.180
will present on notifications
to communications.

01:34:25.180 --> 01:34:28.100
Danielle Kyd, SDG&amp;E's Access

01:34:28.100 --> 01:34:30.630
and Functional Needs Customer
Strategy Manager, will present

01:34:30.630 --> 01:34:33.880
on access and functional
needs, including Medical Baseline

01:34:33.880 --> 01:34:36.790
and tribal relationships and service.

01:34:36.790 --> 01:34:40.640
Jon Kochik, SDG&amp;E's Customer
Integrated Solutions Manager,

01:34:40.640 --> 01:34:43.270
will present backup battery programs.

01:34:43.270 --> 01:34:47.210
Mona Freels, SDG&amp;E's Emergency
Operations Services Manager,

01:34:47.210 --> 01:34:50.160
will discuss lessons learned from 2021.

01:34:50.160 --> 01:34:52.676
And finally, Jonathan Woldemariam,

01:34:52.676 --> 01:34:56.860
SDG&amp;E's Director of
Wildfire Mitigation, will discuss

01:34:56.860 --> 01:34:59.100
our ongoing mitigations.

01:34:59.100 --> 01:35:00.440
We're excited to be here today

01:35:00.440 --> 01:35:04.500
and to share our 2021 Public
Safety Power Shutoff experience

01:35:04.500 --> 01:35:08.070
and what also will expect
from SDG&amp;E in 2022.

01:35:08.070 --> 01:35:13.070
We did improve Public Safety
Power Shutoff Programs in 2021.

01:35:13.390 --> 01:35:16.190
We advanced our
situational awareness continue

01:35:16.190 --> 01:35:18.850
to make infrastructure
more climate-resilient.

01:35:18.850 --> 01:35:20.660
We integrated renewable
energy solutions,

01:35:20.660 --> 01:35:23.450
such as microgrids and
batteries, and most importantly,

01:35:23.450 --> 01:35:25.980
we continue to grow our
partnerships with stakeholders

01:35:25.980 --> 01:35:29.660
who serve our communities
in high-fire threat districts.

01:35:29.660 --> 01:35:33.350
SDG&amp;E continued to find
ways to improve in 2021.

01:35:33.350 --> 01:35:37.520
And while 2021 was
less impactful than 2020,

01:35:37.520 --> 01:35:41.110
and SDG&amp;E found ways
to improve in all areas,

01:35:41.110 --> 01:35:45.480
we are maintaining our relentless
focus on improving in 2022

01:35:45.480 --> 01:35:48.940
in order to create the best
possible customer experience

01:35:48.940 --> 01:35:51.820
while also managing the ever-increasing

01:35:51.820 --> 01:35:56.820
and evolving climate
change-induced wildfire risk

01:35:57.095 --> 01:35:58.090
that we all face.

01:35:58.090 --> 01:36:00.140
We have many new
enhancements that we're excited

01:36:00.140 --> 01:36:01.670
to talk about for 2022.

01:36:01.670 --> 01:36:04.116
We'll share those
with you today as well.

01:36:04.116 --> 01:36:07.460
But finally, on behalf of
Caroline Winn and everyone

01:36:08.488 --> 01:36:11.010
of my colleagues at SDG&amp;E
who passionately serve

01:36:11.010 --> 01:36:12.710
our customers and communities,

01:36:12.710 --> 01:36:15.800
I want to share with you that
the safety of our employees

01:36:17.010 --> 01:36:19.590
and of our public remained
as or value at SDG&amp;E,

01:36:19.590 --> 01:36:21.640
and that will never change.

01:36:21.640 --> 01:36:25.960
And when SDG&amp;E activates
a Public Safety Power Shutoff,

01:36:25.960 --> 01:36:27.163
I can personally assure you

01:36:27.163 --> 01:36:30.340
that it is indeed as a last resort.

01:36:30.340 --> 01:36:32.540
It's a last resort measure
to protect the safety

01:36:32.540 --> 01:36:35.220
of the community, and our focus remains,

01:36:35.220 --> 01:36:37.820
and will remain to make de-energizations

01:36:37.820 --> 01:36:41.490
associated with public
safety power shutoffs smaller,

01:36:41.490 --> 01:36:44.140
shorter and less likely.

01:36:44.140 --> 01:36:45.422
Thank you.

01:36:45.422 --> 01:36:47.839
And I'm just gonna move
straight into our presentation

01:36:47.839 --> 01:36:48.672
with Brian D'Agostino,

01:36:50.290 --> 01:36:51.140
and he's gonna present on forecasting.

01:36:51.140 --> 01:36:52.578
<v ->Yeah.</v>

01:36:52.578 --> 01:36:53.411
Well, thank you very much, Kevin,

01:36:53.411 --> 01:36:54.580
and good afternoon, everybody.

01:36:54.580 --> 01:36:57.010
I really appreciate the
opportunity to be here today

01:36:57.010 --> 01:37:01.110
to reflect back on our last
PSPS season and some

01:37:01.110 --> 01:37:05.060
of the steps that were taken
to actually perform better

01:37:05.060 --> 01:37:07.300
than we had the year before.

01:37:07.300 --> 01:37:09.470
So if we get into the
next slide, please,

01:37:09.470 --> 01:37:13.430
we can start talking about
kind of the overall story we had

01:37:13.430 --> 01:37:16.057
with the previous PSPS season,

01:37:16.057 --> 01:37:17.500
and it really started in
September and October.

01:37:17.500 --> 01:37:19.160
As we heard from SCE,

01:37:19.160 --> 01:37:21.580
we had a big influx
of monsoonal moisture

01:37:21.580 --> 01:37:24.560
in the Southern California
early in the season.

01:37:24.560 --> 01:37:27.530
Now, this introduced some
moisture that really prevented us

01:37:27.530 --> 01:37:29.170
from getting to that point that we had

01:37:29.170 --> 01:37:33.710
those real critiCal Fire
weather conditions in October.

01:37:33.710 --> 01:37:37.420
So we never really escalated
to that point where the winds

01:37:37.420 --> 01:37:39.620
and the dryness got us to the point

01:37:39.620 --> 01:37:43.650
that we reached that last
resort effort of de-energizing.

01:37:43.650 --> 01:37:46.510
So we were feeling pretty
good getting through October.

01:37:46.510 --> 01:37:50.220
And then November, for
only the sixth time in the history

01:37:50.220 --> 01:37:52.960
of weather observations
here in San Diego,

01:37:52.960 --> 01:37:54.770
we didn't get a drop of rain.

01:37:54.770 --> 01:37:57.190
So that really dried us
out and set the stage

01:37:57.190 --> 01:37:58.380
for the Thanksgiving Event,

01:37:58.380 --> 01:38:01.720
which we've already
heard quite a bit about.

01:38:01.720 --> 01:38:03.200
So here in San Diego,

01:38:03.200 --> 01:38:06.060
it was pretty evident
about a week in advance

01:38:06.060 --> 01:38:07.952
that we were going to be seeing

01:38:07.952 --> 01:38:12.290
a moderate-to-strong Santana
wind event on Thanksgiving,

01:38:12.290 --> 01:38:15.300
but as we moved into the
weekend the week before,

01:38:15.300 --> 01:38:18.230
we were still very closely
watching Monday and Tuesday

01:38:18.230 --> 01:38:20.410
for potentially some rainfall,

01:38:20.410 --> 01:38:23.890
and we were hoping that that
rainfall was gonna be enough

01:38:23.890 --> 01:38:26.770
that we weren't gonna
escalate to these extreme levels

01:38:26.770 --> 01:38:29.780
on Thanksgiving, but it
became very apparent

01:38:29.780 --> 01:38:31.363
the Sunday before Thanksgiving

01:38:31.363 --> 01:38:34.080
that that rain was not
going to materialize,

01:38:34.080 --> 01:38:35.280
and not only that,

01:38:35.280 --> 01:38:38.080
it was going to be a
very challenging event

01:38:38.080 --> 01:38:40.750
in terms of forecasting the winds.

01:38:40.750 --> 01:38:44.350
So we did end up kinda getting together

01:38:44.350 --> 01:38:47.840
that Monday morning right
about three days before the event,

01:38:47.840 --> 01:38:49.630
and that was when the decision was made

01:38:49.630 --> 01:38:52.840
to initiate Public Safety
Power Shutoff Protocols.

01:38:52.840 --> 01:38:56.170
The National Weather
Service did follow up by issuing

01:38:56.170 --> 01:39:00.663
a red flag warning for
the event, and overall,

01:39:00.663 --> 01:39:04.324
we were aggressive
with notifying customers.

01:39:04.324 --> 01:39:05.157
And part of the reason

01:39:05.157 --> 01:39:07.310
is, as we've heard from
Southern California Edison,

01:39:07.310 --> 01:39:09.710
this was gonna be a very
challenging wind event.

01:39:10.550 --> 01:39:12.640
We knew that it wasn't
going to impact a lot

01:39:12.640 --> 01:39:16.010
of the traditional areas
because of how mountain waves

01:39:16.010 --> 01:39:18.070
can form here in our complex terrain.

01:39:18.070 --> 01:39:21.993
So we did notify almost
55,000 customers.

01:39:23.468 --> 01:39:24.840
Out of those customers,

01:39:24.840 --> 01:39:28.700
just less than 6,000
ended up experiencing

01:39:28.700 --> 01:39:30.640
a Public Safety Power Shutoff.

01:39:30.640 --> 01:39:33.580
The longest duration
Public Safety Power Shutoff

01:39:33.580 --> 01:39:38.580
was just over 42 hours,
shortest was just under six,

01:39:38.722 --> 01:39:41.513
giving us an average
of just over 25 hours.

01:39:42.500 --> 01:39:44.930
One thing that we're
proud of with this event

01:39:44.930 --> 01:39:49.330
is we really leveraged
our technology and our FPI,

01:39:49.330 --> 01:39:50.760
and we feel that we avoided

01:39:50.760 --> 01:39:54.800
Public Safety Power Shutoff
to almost 23,000 customers.

01:39:54.800 --> 01:39:56.217
And what I mean by that

01:39:56.217 --> 01:39:59.980
is these customers reached thresholds

01:39:59.980 --> 01:40:03.100
where they were up around
the 99th percentile wind speed

01:40:03.100 --> 01:40:06.630
for that neighborhood, but
what we did is we really enabled

01:40:06.630 --> 01:40:08.560
30-second read observations.

01:40:08.560 --> 01:40:12.370
We really got in close to
inspecting what was happening

01:40:12.370 --> 01:40:15.150
in those neighborhoods,
and through close inspection,

01:40:15.150 --> 01:40:18.120
a lot of those, we ultimately
made the determination

01:40:18.120 --> 01:40:22.980
that it was not a last
resort type of situation,

01:40:22.980 --> 01:40:25.950
and we ended up maintaining
and keeping the system on,

01:40:25.950 --> 01:40:28.230
not only through closely
monitoring weather conditions

01:40:28.230 --> 01:40:31.600
in that area, but by having
field crews on the ground,

01:40:31.600 --> 01:40:34.310
observing those circuits
saying, no, we we'll be okay,

01:40:34.310 --> 01:40:36.330
let's see if it gets any worse.

01:40:36.330 --> 01:40:39.760
So because of that,
we did end saving PSPS

01:40:39.760 --> 01:40:41.210
to quite a few customers.

01:40:41.210 --> 01:40:44.210
We did open three
community resource centers

01:40:44.210 --> 01:40:46.430
to support those almost 6,000 customers.

01:40:46.430 --> 01:40:49.320
And then when we look at
how the event played out,

01:40:49.320 --> 01:40:51.860
we did have winds just
a mile per hour short

01:40:51.860 --> 01:40:55.030
of hurricane force here in
San Diego with a peak gust

01:40:55.030 --> 01:41:00.030
of 73, but then over six stations
exceeded 60 miles an hour,

01:41:01.590 --> 01:41:05.480
over 26 stations
exceeded 50 miles per hour.

01:41:05.480 --> 01:41:08.480
And then to the same
point we heard from SCE,

01:41:08.480 --> 01:41:10.630
we had 15 stations that met

01:41:10.630 --> 01:41:15.140
or exceeded all-time
records here in San Diego.

01:41:15.140 --> 01:41:17.470
And again, this is part of the
reason we were so aggressive

01:41:17.470 --> 01:41:20.440
with the notifications was
because we had mountain waves

01:41:20.440 --> 01:41:25.440
that were surfacing in
unusual areas during this event.

01:41:25.560 --> 01:41:28.320
So before I move on to the next slide,

01:41:28.320 --> 01:41:30.230
I just wanna pause and
see if there's any questions

01:41:30.230 --> 01:41:34.940
on that at all.

01:41:34.940 --> 01:41:35.810
All right.

01:41:35.810 --> 01:41:38.830
Moving forward, one thing
that was very important for us

01:41:38.830 --> 01:41:40.290
is that we looked at this year,

01:41:40.290 --> 01:41:43.920
and as you've heard
emphasized on the last call,

01:41:43.920 --> 01:41:48.090
is the weather that we see
in any given PSPS season

01:41:50.160 --> 01:41:52.060
will ultimately determine the impact.

01:41:52.060 --> 01:41:55.621
So we really over the
last year tried to strive

01:41:55.621 --> 01:41:58.880
to develop a way to
normalize the season,

01:41:58.880 --> 01:42:02.560
and normalize how we use
Public Safety Power Shutoff.

01:42:02.560 --> 01:42:03.850
So to explain that here,

01:42:03.850 --> 01:42:05.980
I wanna start with the equation

01:42:05.980 --> 01:42:08.120
up at the top of the slide.

01:42:08.120 --> 01:42:10.957
And it says, "Our Public
Safety Power Shutoff score

01:42:10.957 --> 01:42:13.360
"is made up of three different factors."

01:42:13.360 --> 01:42:14.678
Right?

01:42:14.678 --> 01:42:15.511
One is a determination

01:42:15.511 --> 01:42:19.610
of how strong the Santa
Ana wind actually is.

01:42:19.610 --> 01:42:23.199
So the way that we gauge
that in our meteorology group,

01:42:23.199 --> 01:42:25.281
and the way that we're
sharing with you now is we take

01:42:25.281 --> 01:42:27.850
the top 20 windiest weather
stations that we have,

01:42:27.850 --> 01:42:29.350
and we average that,

01:42:29.350 --> 01:42:33.130
and that gives us a score
for how strong and how windy

01:42:33.130 --> 01:42:34.823
an event actually is.

01:42:35.705 --> 01:42:39.660
Then next factor in this equation
is really how we determine

01:42:39.660 --> 01:42:42.020
how widespread an event is.

01:42:42.020 --> 01:42:44.470
And that is how many
of the weather stations

01:42:44.470 --> 01:42:45.360
that we operate?

01:42:45.360 --> 01:42:47.303
For us it's 221.

01:42:48.320 --> 01:42:52.500
How many of those exceeded
the 95th percentile in terms

01:42:52.500 --> 01:42:54.900
of historical Santa Ana wind speeds?

01:42:54.900 --> 01:42:57.380
So that tells us how
widespread the event is

01:42:57.380 --> 01:42:59.350
across our service territory.

01:42:59.350 --> 01:43:03.650
And then the last factor is
where we take our FPI component,

01:43:03.650 --> 01:43:05.623
which is our fire potential component,

01:43:06.623 --> 01:43:09.010
and it tells us how risky the event is.

01:43:09.010 --> 01:43:13.300
Now, when we run every PSPS
event through this equation,

01:43:13.300 --> 01:43:17.140
we get a score, and
then based off that's score,

01:43:17.140 --> 01:43:20.390
we can compare it to how
many customers were impacted,

01:43:20.390 --> 01:43:21.940
so then we can really measure,

01:43:21.940 --> 01:43:25.430
are we improving year in and year out?

01:43:25.430 --> 01:43:29.060
And that's how we are
measuring our improvement.

01:43:29.060 --> 01:43:31.860
So I wanna start with
the table on the left.

01:43:31.860 --> 01:43:35.150
And it was a very active
year, as we all know,

01:43:35.150 --> 01:43:39.099
the PSPS season of 2020.

01:43:39.099 --> 01:43:43.020
We know it even went into
early, early 2021 for many of us.

01:43:43.020 --> 01:43:46.650
And those are all the events
where PSPSs were activated.

01:43:46.650 --> 01:43:49.640
And you can see the column
on the left is an indication

01:43:49.640 --> 01:43:51.640
of how strong the event was.

01:43:51.640 --> 01:43:54.900
The second column is how
widespread the event was.

01:43:54.900 --> 01:43:57.330
And then there's the FPI.

01:43:57.330 --> 01:44:00.400
I wanna draw your attention
down to December 23rd

01:44:01.351 --> 01:44:04.470
and 24th, because that
event was actually very similar

01:44:04.470 --> 01:44:06.640
to the Thanksgiving
Event that we had last year,

01:44:06.640 --> 01:44:09.730
not only because it
fell on a major holiday,

01:44:09.730 --> 01:44:12.450
but if you look at the how windy it was

01:44:12.450 --> 01:44:16.820
from the top 20 wind
gusts, it was identical at 57.

01:44:16.820 --> 01:44:20.550
If you look at how widespread
the event was in terms

01:44:20.550 --> 01:44:22.660
of the number of our
stations and the percentage

01:44:22.660 --> 01:44:26.040
of our stations that exceeded
the 95th in both cases,

01:44:26.040 --> 01:44:28.650
right around 80%, and in both cases,

01:44:28.650 --> 01:44:30.590
the fire potential was on that high end

01:44:30.590 --> 01:44:34.820
of elevated, just shy of
those really extreme levels.

01:44:34.820 --> 01:44:39.480
So you'll notice the overall
PSPS score was very comparable,

01:44:39.480 --> 01:44:42.840
but we actually ended up
having less customers impacted

01:44:44.210 --> 01:44:47.110
in 2021 under a very similar scenario.

01:44:47.110 --> 01:44:50.510
So that's one of the
ways that we're measuring

01:44:50.510 --> 01:44:52.100
our performance and we're showing

01:44:52.100 --> 01:44:55.440
that we are coming in better
in a very similar situation

01:44:55.440 --> 01:44:56.750
than we have before.

01:44:56.750 --> 01:44:58.830
So I graphed this in the bottom right.

01:44:58.830 --> 01:45:00.910
And you'll look at that red line.

01:45:00.910 --> 01:45:05.910
And that red line is our
performance in the 2020 season.

01:45:06.430 --> 01:45:10.040
And it shows our PSPS
score versus the number

01:45:10.040 --> 01:45:11.950
of customers impacted.

01:45:11.950 --> 01:45:15.120
So when we started
looking at the 2021 season,

01:45:15.120 --> 01:45:18.160
we needed to come in
below that red line, right?

01:45:18.160 --> 01:45:19.240
And that shows us, hey,

01:45:19.240 --> 01:45:22.150
we have performed better in 2021

01:45:22.150 --> 01:45:23.750
than we did the year before.

01:45:23.750 --> 01:45:26.520
And we'll continue to hold
ourselves kind of accountable

01:45:26.520 --> 01:45:30.090
using this so that we
can compare every event

01:45:30.090 --> 01:45:34.163
to really show that
improvement as we move forward.

01:45:35.230 --> 01:45:38.530
The last slide that I wanted
to share with you was give you

01:45:38.530 --> 01:45:41.870
an update on our
forecasting enhancements

01:45:41.870 --> 01:45:45.320
and our meteorological advancements.

01:45:45.320 --> 01:45:49.680
And we still maintain our
culture of continuously improving

01:45:49.680 --> 01:45:52.960
every bit of our situational
awareness platform,

01:45:52.960 --> 01:45:55.020
from expanding our weather network,

01:45:55.020 --> 01:45:58.380
to increasing our capability
of the mountaintop network,

01:45:58.380 --> 01:45:59.950
updating the FPI,

01:45:59.950 --> 01:46:02.640
enhancing the Santa
Ana wildfire threat index,

01:46:02.640 --> 01:46:05.620
there was not a tool that
we had that went untouched

01:46:05.620 --> 01:46:08.100
or unenhanced last year,

01:46:08.100 --> 01:46:10.578
but there was a main theme last year,

01:46:10.578 --> 01:46:11.880
and that was really around the data.

01:46:11.880 --> 01:46:13.820
So the first thing was we have 10 years

01:46:13.820 --> 01:46:15.600
of historical data now,

01:46:15.600 --> 01:46:17.610
and how do we leverage that and use it?

01:46:17.610 --> 01:46:20.090
Two of the biggest impact
events we had last year

01:46:20.090 --> 01:46:22.670
was the full-scale implementation

01:46:22.670 --> 01:46:25.500
of the AI Forecasting System.

01:46:25.500 --> 01:46:26.930
We've heard that that's something

01:46:26.930 --> 01:46:29.973
that performed very
well for us last year,

01:46:30.940 --> 01:46:33.801
and even in a challenging
event like Thanksgiving,

01:46:33.801 --> 01:46:38.560
it did help us anticipate
the event coming the size,

01:46:38.560 --> 01:46:41.630
the scale and some of
the challenges with that.

01:46:41.630 --> 01:46:44.040
We've also used the data and implemented

01:46:44.040 --> 01:46:48.200
full wildfire detection
from all the mountain tops

01:46:48.200 --> 01:46:51.000
in San Diego, and we've also found that

01:46:51.000 --> 01:46:53.960
to be very effective,
but not only enhancing

01:46:53.960 --> 01:46:56.170
and using the data, but sharing the data

01:46:57.140 --> 01:47:00.550
has been a huge initiative in 2021.

01:47:00.550 --> 01:47:03.140
Working with the San Diego
Super Computing Center,

01:47:03.140 --> 01:47:07.700
we did develop a data-sharing
platform where all the data

01:47:07.700 --> 01:47:09.050
that we generate everyday,

01:47:09.050 --> 01:47:12.620
almost 200 gigs, is
available to any researcher

01:47:12.620 --> 01:47:14.640
in California, Australia,

01:47:14.640 --> 01:47:17.100
anywhere who wants to work on this data.

01:47:17.100 --> 01:47:20.210
And then even the image
you see on the right is part

01:47:20.210 --> 01:47:23.300
of a new mapping system
that's tied to all of that.

01:47:23.300 --> 01:47:26.093
So we know the National Weather Service

01:47:26.093 --> 01:47:27.160
in San Diego is using it.

01:47:27.160 --> 01:47:29.410
Even the numbers
that you see on that map

01:47:29.410 --> 01:47:33.190
are our-AI based forecast,
for all of the circuits.

01:47:33.190 --> 01:47:34.973
So it's all made available.

01:47:38.224 --> 01:47:39.880
Even fire agencies now are
using this for fuel information,

01:47:39.880 --> 01:47:42.870
and we're just continuing
to share and promote

01:47:42.870 --> 01:47:45.390
the distribution of a
lot of this information

01:47:45.390 --> 01:47:50.390
really is an innovation
enabler moving forward.

01:47:50.620 --> 01:47:52.680
And on the topic of moving forward,

01:47:52.680 --> 01:47:56.250
we will continue to build and
expand all of our products.

01:47:56.250 --> 01:47:59.730
The Weather Network, we're
adding air quality sensors.

01:47:59.730 --> 01:48:02.210
We are going to be
updating and replacing

01:48:02.210 --> 01:48:06.770
our Supercomputing Platform in 2022.

01:48:06.770 --> 01:48:10.090
So we will integrate lots of
lessons learned from SCE,

01:48:10.090 --> 01:48:14.360
so thank you for
helping kind of drive a lot

01:48:14.360 --> 01:48:16.160
of that initially.

01:48:16.160 --> 01:48:19.350
And then also our
AI-based Forecasting System

01:48:19.350 --> 01:48:23.060
will continue to learn
and retrain based off all

01:48:23.060 --> 01:48:26.950
of the challenges and
lessons learned in 2022.

01:48:26.950 --> 01:48:30.411
So for any questions,
I will conclude there,

01:48:30.411 --> 01:48:35.030
and I will hand it
onto our next speaker.

01:48:35.030 --> 01:48:38.150
Oh, I do see, I see a hand.

01:48:38.150 --> 01:48:39.050
Yes, Commissioner.

01:48:40.920 --> 01:48:43.270
<v ->Brian, I just wanna
confirm something with you.</v>

01:48:43.270 --> 01:48:46.960
If you go back one slide (clears throat)

01:48:46.960 --> 01:48:53.640
the metric you're using
for success is based a lot

01:48:53.640 --> 01:48:57.940
on system-wide average,
system-wide averaging,

01:48:57.940 --> 01:49:01.417
gust-averaging stations
above the 95th percentile

01:49:01.417 --> 01:49:03.090
and so forth.

01:49:03.090 --> 01:49:07.210
And I wanna confirm that one

01:49:07.210 --> 01:49:09.700
of, as I understand this from briefings

01:49:09.700 --> 01:49:11.870
you've given us in the
past, one of the things

01:49:11.870 --> 01:49:15.760
you really focus on and
have focused on over the years

01:49:15.760 --> 01:49:19.710
is having much as
granular data as possible

01:49:19.710 --> 01:49:22.013
based on individual,
individual wind speeds

01:49:22.013 --> 01:49:26.343
at very small geographic intervals.

01:49:27.470 --> 01:49:31.686
And maybe that's the
reason why last Thanksgiving,

01:49:31.686 --> 01:49:32.584
you were able

01:49:32.584 --> 01:49:37.570
to avoid doing, de-energizing
20-plus thousand customers

01:49:37.570 --> 01:49:38.970
who are otherwise in scope.

01:49:38.970 --> 01:49:41.160
So I just want you to explain that

01:49:41.160 --> 01:49:42.892
or talk about, is that in fact true

01:49:42.892 --> 01:49:44.840
that your continued focus

01:49:44.840 --> 01:49:48.320
is to be as micro-granular as possible

01:49:48.320 --> 01:49:52.534
in each your decision to
de-energize, even though here,

01:49:52.534 --> 01:49:56.810
you're talking about a
system-wide impact average?

01:49:56.810 --> 01:49:57.690
<v ->Yeah.</v>

01:49:57.690 --> 01:50:00.710
When we end up scoring the intensity

01:50:00.710 --> 01:50:02.950
of an overall weather event,

01:50:02.950 --> 01:50:07.470
we do it across our whole
service territory, right?

01:50:07.470 --> 01:50:09.950
We could bring it down
more granular and say,

01:50:09.950 --> 01:50:12.730
how intense was this
storm for this neighborhood

01:50:12.730 --> 01:50:14.000
and that neighborhood?

01:50:14.000 --> 01:50:16.692
But right now, for the
purpose of normalizing

01:50:16.692 --> 01:50:20.144
kind of the overall
strength of the event

01:50:20.144 --> 01:50:21.920
and the overall impact
on our service territory,

01:50:21.920 --> 01:50:25.200
that's why we take this approach.

01:50:25.200 --> 01:50:28.110
But the other question,
we continue to focus

01:50:28.110 --> 01:50:30.340
on that granularity.

01:50:30.340 --> 01:50:33.960
And yeah, the short answer
is the granularity is a big part

01:50:33.960 --> 01:50:38.920
of what enabled us to keep
the Thanksgiving Event last year

01:50:38.920 --> 01:50:42.740
so targeted to a
particular neighborhood.

01:50:42.740 --> 01:50:47.210
And then the historical data,
which we had as well, right?

01:50:47.210 --> 01:50:50.500
Because just like we saw up at SCE,

01:50:50.500 --> 01:50:55.150
we did have these wind
surface in a very unusual place

01:50:55.150 --> 01:50:56.670
in San Diego County.

01:50:56.670 --> 01:50:58.896
And that's part of why we thought

01:50:58.896 --> 01:50:59.729
even with 10 years of data,

01:50:59.729 --> 01:51:02.320
we had 15 weather stations that reported

01:51:02.320 --> 01:51:06.690
the windiest event that they'd ever had.

01:51:06.690 --> 01:51:08.091
Right?

01:51:08.091 --> 01:51:10.500
Just because it was
very unique type of event.

01:51:10.500 --> 01:51:13.880
But the granularity
really enabled us to target

01:51:13.880 --> 01:51:17.760
just that small area that
was seeing those winds,

01:51:17.760 --> 01:51:20.020
and it didn't end up
becoming a widespread event.

01:51:20.020 --> 01:51:23.763
We very much targeted
where those wins did surface.

01:51:26.220 --> 01:51:27.370
<v ->Thank you.</v>

01:51:27.370 --> 01:51:28.203
<v ->Yup.</v>

01:51:32.155 --> 01:51:33.947
<v ->I have a question.</v>

01:51:33.947 --> 01:51:35.979
(Genevieve clears throat)

01:51:35.979 --> 01:51:37.385
Oh, let's see.

01:51:37.385 --> 01:51:40.570
Your 2022 planning (clears throat)

01:51:40.570 --> 01:51:42.891
replaced, let's see,

01:51:42.891 --> 01:51:46.768
replaced Super Computing
Platform enabling (clears throat)

01:51:46.768 --> 01:51:49.353
next generation, where
processing analytics.

01:51:50.477 --> 01:51:54.390
Now, you did say you've
got 10 years of weather data.

01:51:55.376 --> 01:51:57.310
I know you've been able, has had

01:51:59.401 --> 01:52:02.633
a pretty extensive
weather station network,

01:52:03.920 --> 01:52:06.500
and what have you, we heard

01:52:06.500 --> 01:52:09.610
from, Edison about pulling in

01:52:09.610 --> 01:52:14.190
a European weather modeling tool,

01:52:14.190 --> 01:52:17.813
and is that something that
you all are doing as well?

01:52:19.370 --> 01:52:22.263
<v ->Yes, in a slightly
different way.</v>

01:52:23.350 --> 01:52:28.140
There is Scripps
Institution of Oceanography

01:52:28.140 --> 01:52:30.653
here in San Diego,
and they actually have

01:52:30.653 --> 01:52:33.620
a Center of Western
Weather Water Extremes

01:52:34.590 --> 01:52:37.920
that accesses this
European weather model.

01:52:37.920 --> 01:52:39.920
And we have partnered with Scripps

01:52:39.920 --> 01:52:41.450
that they're actually taking a lot

01:52:41.450 --> 01:52:43.650
of their atmospheric river work,

01:52:43.650 --> 01:52:45.610
and we're going to extend it.

01:52:45.610 --> 01:52:47.630
It normally starts in December,

01:52:47.630 --> 01:52:51.150
and we're working with them
now to back up all of that work

01:52:51.150 --> 01:52:52.690
to start in October.

01:52:52.690 --> 01:52:55.640
And one of the benefits
there is that having that,

01:52:55.640 --> 01:52:58.600
that will be for the whole
Western United States.

01:52:58.600 --> 01:53:01.920
It'll be a 200-member European ensemble,

01:53:01.920 --> 01:53:05.250
which means they're gonna use
the supercomputers San Diego

01:53:05.250 --> 01:53:08.750
to run 200 versions
of the European model

01:53:08.750 --> 01:53:10.850
and then make it publicly available

01:53:10.850 --> 01:53:12.840
up and down the West Coast.

01:53:12.840 --> 01:53:15.998
So it will be available,
not only here in San Diego,

01:53:15.998 --> 01:53:19.110
but it'll be available
to the entire state

01:53:19.110 --> 01:53:21.850
and even Pacific Northwest Utilities

01:53:21.850 --> 01:53:23.040
that are dealing with this now.

01:53:23.040 --> 01:53:27.270
So yeah, we certainly see
the you of the European model

01:53:27.270 --> 01:53:28.750
and look to, to integrate it

01:53:28.750 --> 01:53:31.223
and expand some of that as well.

01:53:33.690 --> 01:53:35.236
<v ->Okay.</v>

01:53:35.236 --> 01:53:36.986
All right, thank you.

01:53:42.200 --> 01:53:43.723
<v ->All right.</v>

01:53:43.723 --> 01:53:44.556
Not seeing any other questions,

01:53:44.556 --> 01:53:49.230
I will, now happy to
introduce Zoraya Griffin,

01:53:49.230 --> 01:53:51.430
our Senior Communications Manager,

01:53:51.430 --> 01:53:54.663
to talk to you more about notifications.

01:53:55.890 --> 01:53:56.723
<v ->Thank you, Brian.</v>

01:53:56.723 --> 01:53:58.710
And thank you, everybody,
for the opportunity to share

01:53:58.710 --> 01:54:01.900
with you, not only some
of the lessons learned,

01:54:01.900 --> 01:54:04.340
but also some of the
planning that we're gonna be,

01:54:04.340 --> 01:54:07.100
that we have in place for
our PR, our notifications

01:54:07.100 --> 01:54:10.470
as well as our public
education and outreach for 2022.

01:54:10.470 --> 01:54:14.110
I first of all wanna just set
some context in the sense

01:54:14.110 --> 01:54:19.110
that following the very impactful
2020 events that we had,

01:54:19.960 --> 01:54:24.960
we decided that we were
gonna start 2021 by really going

01:54:25.050 --> 01:54:27.863
to our customers and our stakeholders,

01:54:28.710 --> 01:54:31.743
and, 'cause I have the next
slide, please, by the way,

01:54:32.912 --> 01:54:35.520
and really start learning from them them

01:54:35.520 --> 01:54:38.350
what worked in 2020,

01:54:38.350 --> 01:54:41.340
and what we could
frankly do better in 2021.

01:54:41.340 --> 01:54:42.810
And how did we do that?

01:54:42.810 --> 01:54:47.230
So all of us SCE,
PG&amp;E and us, we all did

01:54:47.230 --> 01:54:49.370
very extensive post-event surveys,

01:54:49.370 --> 01:54:51.860
but we went a little
bit further than that,

01:54:51.860 --> 01:54:56.160
and what we did was we,
the first 90 days of 2021,

01:54:56.160 --> 01:54:58.990
we hosted online focus groups,

01:54:58.990 --> 01:55:01.300
online chats with our customers,

01:55:01.300 --> 01:55:04.520
especially the ones that were
affected the previous year.

01:55:04.520 --> 01:55:08.350
We continued to do monthly
customer opinion surveys

01:55:08.350 --> 01:55:11.280
with some of our customer
that were affected during the year

01:55:11.280 --> 01:55:15.100
where we really vetted and
tested some of the changes

01:55:15.100 --> 01:55:16.060
that we were gonna be doing,

01:55:16.060 --> 01:55:17.640
particularly some of the language

01:55:17.640 --> 01:55:20.760
that we were gonna be
changing in our notifications,

01:55:20.760 --> 01:55:23.580
just to make sure that we will work that

01:55:23.580 --> 01:55:27.182
with our customers and what
they really wanted and needed

01:55:27.182 --> 01:55:29.880
from us during a PSPS event.

01:55:29.880 --> 01:55:31.750
So with that,

01:55:31.750 --> 01:55:34.320
I think that really
was a driver for some

01:55:34.320 --> 01:55:36.890
of the high customer satisfaction rates

01:55:36.890 --> 01:55:39.120
that I'm gonna be talking to you about

01:55:39.120 --> 01:55:40.810
regarding our notification.

01:55:40.810 --> 01:55:45.810
So in addition to the 70%
of our surveyed respondents

01:55:46.900 --> 01:55:50.570
were overall satisfied with
our notification process,

01:55:50.570 --> 01:55:53.040
primarily because they really truly

01:55:53.040 --> 01:55:54.510
did help shape it for 2021.

01:55:54.510 --> 01:55:55.653
But additionally,

01:55:56.560 --> 01:56:01.560
over 80% recalled
receiving multiple notifications

01:56:02.240 --> 01:56:07.240
from us and felt that the
content was accurate, relevant,

01:56:08.330 --> 01:56:10.560
meaningful and provided information

01:56:10.560 --> 01:56:12.183
that that was useful to them.

01:56:13.320 --> 01:56:18.060
Additionally, we have over
70% customer satisfaction rating

01:56:18.060 --> 01:56:20.270
in our in-language communications,

01:56:20.270 --> 01:56:24.290
something that we are especially
proud of because last year

01:56:24.290 --> 01:56:27.620
we really focused on using
language that was relevant

01:56:27.620 --> 01:56:30.510
in our 20, excuse me,
22 prevalent languages.

01:56:30.510 --> 01:56:35.070
We also expanded that to
American Sign Language as well.

01:56:35.070 --> 01:56:37.260
Every notification that went out

01:56:37.260 --> 01:56:40.493
included American Sign
Language video associated with it,

01:56:41.810 --> 01:56:45.600
which led to 100% set
customer satisfaction rate

01:56:45.600 --> 01:56:50.200
with our AFN Community
that that were notified.

01:56:50.200 --> 01:56:54.883
So we also launched our PSPS App.

01:56:56.680 --> 01:56:59.970
And as you see here, we've
had over 38,000 downloads,

01:56:59.970 --> 01:57:04.160
but last year, we did a targeted
public education campaign

01:57:04.160 --> 01:57:09.160
bringing much more awareness
to the PSPS App, and going

01:57:09.170 --> 01:57:13.360
into of 2021 wildfire season,

01:57:13.360 --> 01:57:18.360
we have well over 15,000
additional download apps.

01:57:18.520 --> 01:57:21.640
So one thing that we are
especially proud of however,

01:57:21.640 --> 01:57:23.030
and this goes back to the question

01:57:23.030 --> 01:57:24.600
that was asked of the Edison,

01:57:24.600 --> 01:57:27.120
and we heard this loud and
clear from our customers,

01:57:27.120 --> 01:57:31.910
especially our customers
that are not particularly fond

01:57:31.910 --> 01:57:34.410
of using the technology,

01:57:34.410 --> 01:57:37.760
and that is that we started
using in-community Marques

01:57:39.090 --> 01:57:42.210
at churches, at some of our casinos,

01:57:42.210 --> 01:57:46.310
that, some locations that
were strategically placed

01:57:46.310 --> 01:57:48.170
in our affected HFTD.

01:57:48.170 --> 01:57:53.170
We also used over 31
portable electronic road signs,

01:57:54.080 --> 01:57:57.550
again, strategically placed
in areas that we went out

01:57:57.550 --> 01:58:01.690
and we tested and measured
what the high traffic volume

01:58:01.690 --> 01:58:03.730
during fire season.

01:58:03.730 --> 01:58:08.730
And then we also sent
out in-community flyers

01:58:09.170 --> 01:58:12.670
to our communities that were
posted in areas that we knew

01:58:12.670 --> 01:58:13.960
were high traffic areas,

01:58:13.960 --> 01:58:16.163
that we used to also
provide information.

01:58:17.070 --> 01:58:19.720
Additionally, this year we launched

01:58:19.720 --> 01:58:22.770
our Public Safety Partner Portal,

01:58:22.770 --> 01:58:25.599
which I'm not gonna
go into a lot of detail

01:58:25.599 --> 01:58:26.950
because my colleague,
Mona, is gonna be talking more

01:58:26.950 --> 01:58:30.150
about that, but basically
it's the one-stop shop

01:58:30.150 --> 01:58:31.810
of information of everything

01:58:31.810 --> 01:58:34.590
that our Public Safety partners need,

01:58:34.590 --> 01:58:39.590
and there was an 87% customer
satisfaction rating in the use

01:58:39.770 --> 01:58:42.330
of that Public Safety Portal.

01:58:42.330 --> 01:58:46.040
And in addition to the
things that I've talked about,

01:58:46.040 --> 01:58:47.100
we also leveraged

01:58:47.100 --> 01:58:51.900
about 200 or so
community-based organizations,

01:58:51.900 --> 01:58:53.900
and what's important about this is these

01:58:55.021 --> 01:58:57.250
are the most trusted organizations,

01:58:57.250 --> 01:59:00.630
especially by our
vulnerable populations,

01:59:00.630 --> 01:59:04.510
our community-based
organizations that they go to,

01:59:04.510 --> 01:59:08.120
probably more so than
coming to us for information,

01:59:08.120 --> 01:59:11.420
and they not only amplify our messages,

01:59:11.420 --> 01:59:13.550
but the organization like 211,

01:59:13.550 --> 01:59:16.580
they actually mirror everything
that we have on our website,

01:59:16.580 --> 01:59:18.680
all the information, they mirror,

01:59:18.680 --> 01:59:22.970
and their call center also
serves to a large degree

01:59:22.970 --> 01:59:24.630
to augment our call center.

01:59:24.630 --> 01:59:28.000
So that is one of the
key ways that we went out

01:59:28.000 --> 01:59:31.270
and continued to reach
a lot of these customers

01:59:31.270 --> 01:59:33.770
that probably would
not have contacted us.

01:59:33.770 --> 01:59:35.231
Right?

01:59:35.231 --> 01:59:37.013
But they felt comfortable
in contacting 211

01:59:37.959 --> 01:59:38.943
to get accurate information.

01:59:40.030 --> 01:59:42.965
As far as lessons learned,

01:59:42.965 --> 01:59:47.965
we augmented the capabilities
of our notification system

01:59:50.040 --> 01:59:51.890
so that now we can issue

01:59:51.890 --> 01:59:56.890
approximately 100,000
communications in under an hour.

01:59:56.990 --> 01:59:59.680
That was a lesson
learned from previous years,

01:59:59.680 --> 02:00:02.880
and so we strengthened
our notification system,

02:00:02.880 --> 02:00:06.950
and we are continuing
to look at the framework

02:00:06.950 --> 02:00:10.440
and improving the hardware
of that notification system

02:00:10.440 --> 02:00:13.820
so that we can continuously
improve that system.

02:00:13.820 --> 02:00:17.060
We did have a pretty
significant lesson learned

02:00:17.060 --> 02:00:20.350
with our notifications,
and that is that some

02:00:20.350 --> 02:00:23.633
of our carriers were blocking our calls,

02:00:25.242 --> 02:00:26.383
our notification calls as spam.

02:00:27.289 --> 02:00:30.660
So we are meeting
with our telco carriers

02:00:30.660 --> 02:00:33.890
to get that coding issue fixed
on their end and anticipate

02:00:33.890 --> 02:00:38.080
that we will not be having that
same issue this coming year.

02:00:38.080 --> 02:00:39.910
And then there were some customers

02:00:39.910 --> 02:00:44.910
that we did not have
accurate information,

02:00:45.064 --> 02:00:47.690
or, we just didn't simply
didn't have information

02:00:47.690 --> 02:00:51.040
in our notification system
or as part of their account.

02:00:51.040 --> 02:00:53.780
So we have issued them letters.

02:00:53.780 --> 02:00:56.593
We're pressing them to
please update their information.

02:00:58.380 --> 02:01:01.050
And we continue to work

02:01:01.050 --> 02:01:04.930
with our, this strong
partnerships that we have

02:01:04.930 --> 02:01:08.710
with the media and our TV and radio,

02:01:08.710 --> 02:01:12.830
they are fantastic at amplifying
our notification messages

02:01:13.920 --> 02:01:16.710
during our PSPS events as well,

02:01:16.710 --> 02:01:21.433
as do our trusted CBO partners as well.

02:01:23.130 --> 02:01:23.963
Next slide, please.

02:01:23.963 --> 02:01:25.260
Unless there's any other questions,

02:01:25.260 --> 02:01:30.000
I can certainly move on
to our public education and.

02:01:30.000 --> 02:01:31.650
<v ->Ms. Griffin, I have a question.</v>

02:01:32.993 --> 02:01:33.907
<v ->Sure.</v>

02:01:33.907 --> 02:01:34.740
<v ->Go ahead.</v>

02:01:34.740 --> 02:01:35.870
<v ->Oh, thank you.</v>

02:01:35.870 --> 02:01:39.453
So on the 70% respondent
satisfied notification,

02:01:40.344 --> 02:01:42.670
can you walk us through the
numbers of just how many people

02:01:42.670 --> 02:01:46.853
got the survey, and then
what the response rate was?

02:01:48.430 --> 02:01:50.160
And to me, honestly,

02:01:50.160 --> 02:01:53.400
70% actually seems really
low in terms of satisfaction.

02:01:53.400 --> 02:01:55.760
So I was curious what
actions you guys are taking

02:01:57.109 --> 02:01:58.963
to improve that satisfaction rate.

02:02:00.030 --> 02:02:01.460
<v ->So, yes.</v>

02:02:01.460 --> 02:02:05.220
So we reached out and
issued our survey to everybody

02:02:05.220 --> 02:02:08.300
that, to all of our
customers that were affected

02:02:08.300 --> 02:02:10.580
by the PSPS event in Thanksgiving,

02:02:10.580 --> 02:02:14.210
and we got about a 10% response rate,

02:02:14.210 --> 02:02:18.796
which is actually a little bit
higher than we have gotten

02:02:18.796 --> 02:02:19.696
in previous years.

02:02:19.696 --> 02:02:21.597
Previous years, we've
been averaging anywhere

02:02:21.597 --> 02:02:23.860
from six to eight, a six
to 8% response rate.

02:02:23.860 --> 02:02:27.412
So, and believe it or not,

02:02:27.412 --> 02:02:31.300
while that 70% customer
satisfaction rate may appear

02:02:31.300 --> 02:02:34.630
to be low, it's actually,,
in the statistical world,

02:02:34.630 --> 02:02:38.250
I learn, a pretty high
customer satisfaction rate,

02:02:38.250 --> 02:02:41.288
and especially from our previous years

02:02:41.288 --> 02:02:42.810
when we were hovering under 50%,

02:02:42.810 --> 02:02:45.020
and sometimes even lower than that.

02:02:45.020 --> 02:02:48.750
So a 20% increase for
us was pretty significant

02:02:48.750 --> 02:02:50.293
from one season to the next.

02:02:54.288 --> 02:02:57.448
<v ->With regard to your calls
being marked as spam</v>

02:02:57.448 --> 02:02:58.640
by telecom carriers,

02:02:58.640 --> 02:03:00.750
is that something that
other utilities encountered

02:03:00.750 --> 02:03:04.280
in your discussions
about PSPS performance

02:03:04.280 --> 02:03:08.030
with the other IUs, and can you provide

02:03:08.882 --> 02:03:10.541
a little bit more color on the status

02:03:10.541 --> 02:03:12.610
of those discussions with telecoms?

02:03:12.610 --> 02:03:14.004
<v ->Yes.</v>

02:03:14.004 --> 02:03:16.480
So we have in our joint IU discussions,

02:03:16.480 --> 02:03:18.540
the other IOUs have said that yes,

02:03:18.540 --> 02:03:22.196
that there have been instances
where they too are having

02:03:22.196 --> 02:03:24.030
to work with their telcos for this.

02:03:24.030 --> 02:03:29.000
And I will invite somebody from one

02:03:29.000 --> 02:03:31.650
of our, my colleagues
from, that's working directly

02:03:31.650 --> 02:03:35.192
with our telcos, they may
be on the line, to provide

02:03:35.192 --> 02:03:37.830
a status update on those communications.

02:03:37.830 --> 02:03:40.917
I believe that they're
gonna be taking place

02:03:40.917 --> 02:03:43.590
with, they were gonna be taking place

02:03:43.590 --> 02:03:45.460
within the first quarter of this year.

02:03:45.460 --> 02:03:47.080
So they may not, they may be scheduled

02:03:47.080 --> 02:03:48.683
for later this quarter.

02:03:51.745 --> 02:03:52.895
<v ->Zoraya, this is Mona.</v>

02:03:54.284 --> 02:03:56.960
I spoke with our business
services prior to getting

02:03:56.960 --> 02:04:00.387
on this call, 'cause that was
one of the lessons learned.

02:04:00.387 --> 02:04:01.730
We have received
confirmation from at AT&amp;T

02:04:01.730 --> 02:04:05.270
that they have changed
the flag on our 800 number

02:04:05.270 --> 02:04:07.779
that is associated with
our outbound dialer.

02:04:07.779 --> 02:04:11.950
So it will no longer be
flagged as spam with AT&amp;T.

02:04:11.950 --> 02:04:14.728
We have made the request
of all of the other carriers,

02:04:14.728 --> 02:04:16.480
but haven't yet received the
confirmation from the others,

02:04:16.480 --> 02:04:17.760
so that they're continuing conversation

02:04:17.760 --> 02:04:19.860
that our account
executive will be having.

02:04:20.900 --> 02:04:21.800
<v ->Thank you, Mona.</v>

02:04:23.280 --> 02:04:24.113
<v ->Thank you.</v>

02:04:26.923 --> 02:04:28.829
<v ->Question follow-up
(clears throat)</v>

02:04:28.829 --> 02:04:31.400
and actually I had the same reaction

02:04:31.400 --> 02:04:34.043
that Director Thomas
Jenkins had about the 70%.

02:04:34.932 --> 02:04:37.166
Now, improving from
below 50% of the 70%,

02:04:37.166 --> 02:04:40.520
it is really excellent,

02:04:40.520 --> 02:04:45.520
but do you have a goal
for the next go around

02:04:46.690 --> 02:04:49.710
to raise that in terms of
residents being satisfied

02:04:49.710 --> 02:04:53.303
or to get a higher than
10% response rate?

02:04:55.014 --> 02:04:57.380
You look at what would it take

02:04:57.380 --> 02:05:01.233
to get a higher satisfaction response?

02:05:02.590 --> 02:05:06.010
And I know from screen, it
takes resources and money

02:05:06.010 --> 02:05:09.060
to do that, but are you looking

02:05:09.060 --> 02:05:12.810
into (clears throat)
how to increase that?

02:05:12.810 --> 02:05:15.500
<v ->Yes, we absolutely are,</v>

02:05:15.500 --> 02:05:19.630
and in fact, those focus group

02:05:19.630 --> 02:05:22.420
and chat circles that we had last year,

02:05:22.420 --> 02:05:25.510
we're going to increase those
and be much more deliberate

02:05:25.510 --> 02:05:28.440
in working in partnership
with our customers to try

02:05:28.440 --> 02:05:31.290
to identify specific areas

02:05:31.290 --> 02:05:33.570
where we can improve that notification,

02:05:33.570 --> 02:05:35.233
our overall notification process.

02:05:36.760 --> 02:05:40.620
So where we really do
leverage our customers

02:05:40.620 --> 02:05:44.080
to help us inform our approach,

02:05:44.080 --> 02:05:46.199
on not only our notifications,

02:05:46.199 --> 02:05:47.983
but also our public
education and outreach.

02:05:49.580 --> 02:05:52.390
<v ->And, and Ms. Griffin,
I can definitely hear</v>

02:05:52.390 --> 02:05:57.390
your commitment, your
feeling of responsibility,

02:05:58.720 --> 02:06:02.565
the customers of the,
of really doing right

02:06:02.565 --> 02:06:03.850
by your customers.

02:06:03.850 --> 02:06:07.240
I'm just curious, are
you also at all involved

02:06:07.240 --> 02:06:11.130
in customer engagement
in signing up for care

02:06:11.130 --> 02:06:14.343
and, income and medical rate?

02:06:15.440 --> 02:06:20.440
<v ->So I am preferably from a
public education perspective,</v>

02:06:20.830 --> 02:06:22.640
but I do not wanna steal any

02:06:22.640 --> 02:06:27.480
of Danielle's Kyd's great
discussions she's gonna have,

02:06:27.480 --> 02:06:28.600
because she's gonna inform you

02:06:28.600 --> 02:06:30.550
about the work in that area.

02:06:30.550 --> 02:06:34.280
So I will refer to Danielle
who will follow me shortly

02:06:35.440 --> 02:06:38.153
to share some of the great
work that her team is doing.

02:06:39.060 --> 02:06:39.893
<v ->Thank you.</v>

02:06:43.710 --> 02:06:46.500
<v ->And if there are no other
questions we can move on</v>

02:06:46.500 --> 02:06:50.373
to the public education and
outreach efforts that we did.

02:06:52.140 --> 02:06:55.990
So again, as we did
with our notifications,

02:06:55.990 --> 02:07:00.410
we really do consider our
public education and outreach

02:07:00.410 --> 02:07:03.480
a partnership with our customers,

02:07:03.480 --> 02:07:06.460
especially our customers
that are most affected

02:07:06.460 --> 02:07:08.600
in our high-fire threat districts.

02:07:08.600 --> 02:07:11.380
We continuously vet ideas that we have.

02:07:11.380 --> 02:07:15.510
We solicit ideas from them continuously.

02:07:15.510 --> 02:07:17.820
We test those ideas on a monthly basis,

02:07:17.820 --> 02:07:21.300
and that really does
allow us to be nimble

02:07:21.300 --> 02:07:26.300
in our approach as we
decide to roll our campaigns up.

02:07:26.430 --> 02:07:29.100
But this year, this year we had

02:07:30.958 --> 02:07:35.220
over five wildfire safety
webinars with over 300 attendees,

02:07:35.220 --> 02:07:36.840
and those were supported

02:07:36.840 --> 02:07:39.750
not only by our internal
subject matter experts,

02:07:39.750 --> 02:07:44.520
but we also had agency
partnerships, such as Cal Fire,

02:07:44.520 --> 02:07:48.150
that joined us to also
participate in those.

02:07:48.150 --> 02:07:53.150
We expanded our wildfire safety fairs.

02:07:53.810 --> 02:07:56.420
They were drive-through
prayers because of the pandemic,

02:07:56.420 --> 02:08:00.713
so we did five that were in
the areas of highest fire risk.

02:08:01.577 --> 02:08:05.560
And we also had our first
Joint Wildfire Safety Fair

02:08:05.560 --> 02:08:07.600
with our tribal partners.

02:08:07.600 --> 02:08:08.960
So we do work

02:08:08.960 --> 02:08:13.640
with about 18 different
federally-recognized tribes

02:08:13.640 --> 02:08:14.940
here in San Diego.

02:08:14.940 --> 02:08:19.410
So for us to be able to
have our first joint-hosted fair

02:08:19.410 --> 02:08:22.760
was a big accomplishment for us.

02:08:22.760 --> 02:08:25.740
We, typically in 2021,

02:08:25.740 --> 02:08:29.560
we had about 11 separate
public education campaigns

02:08:29.560 --> 02:08:32.370
that we were running
many times simultaneously

02:08:32.370 --> 02:08:35.551
throughout our entire service territory.

02:08:35.551 --> 02:08:37.860
So that's one thing that we did in 2021

02:08:37.860 --> 02:08:40.280
that was a lesson learned where we used

02:08:40.280 --> 02:08:44.240
to only primarily focus in the
HFTD, but now we are focusing

02:08:44.240 --> 02:08:49.240
across our entire service
territories, and our campaign now,

02:08:50.762 --> 02:08:51.595
rather than starting in the summer

02:08:51.595 --> 02:08:53.570
right before wildfire season

02:08:53.570 --> 02:08:56.030
is now truly a year-round campaign.

02:08:56.030 --> 02:08:58.080
So we are getting
ready to launch that now,

02:08:58.080 --> 02:09:00.690
and that will run through
the end of the year.

02:09:00.690 --> 02:09:02.600
So with that, we've achieved

02:09:02.600 --> 02:09:06.090
over 300 million marketing impressions

02:09:06.090 --> 02:09:10.320
or touchpoints or engagement
across our service territory.

02:09:10.320 --> 02:09:15.000
And we leveraged over
20 diverse platforms

02:09:15.000 --> 02:09:18.130
to help us achieve our public education.

02:09:18.130 --> 02:09:22.480
As you'll see here, our
favorability rate was 88%,

02:09:22.480 --> 02:09:27.335
which in the statistical world
is a very high percentage.

02:09:27.335 --> 02:09:32.183
And that was about a 25%
increase from previous years.

02:09:33.640 --> 02:09:37.370
We added the
Spanish-speaking statistic here.

02:09:37.370 --> 02:09:40.220
We had an 84% overall favorability.

02:09:40.220 --> 02:09:43.090
And the reason for that is
because Spanish speakers

02:09:44.054 --> 02:09:45.720
is one of our most significant
prevalent languages

02:09:45.720 --> 02:09:48.470
with over a third of our population

02:09:48.470 --> 02:09:51.480
in the service territory
being Spanish speakers.

02:09:51.480 --> 02:09:53.250
This year in 2021,

02:09:53.250 --> 02:09:58.250
we also launched a customized
public education campaign

02:09:58.450 --> 02:10:01.560
for our customers with
Access and Functional Needs.

02:10:01.560 --> 02:10:04.050
And again, Danielle
will speak a little bit more

02:10:04.050 --> 02:10:06.730
as far as what was
accomplished through that effort.

02:10:06.730 --> 02:10:10.340
So what did we learn going into 2022?

02:10:10.340 --> 02:10:13.210
Well, we learned that we
need to continue to build

02:10:13.210 --> 02:10:14.770
on our wildfire safety fairs

02:10:15.616 --> 02:10:19.550
because we had more than
2,500 community participants

02:10:19.550 --> 02:10:20.660
in those fairs,

02:10:20.660 --> 02:10:24.980
and so we are planning
to do those again this year,

02:10:24.980 --> 02:10:28.540
and depending on what
the pandemic situation is,

02:10:28.540 --> 02:10:31.210
we're looking at potentially integrating

02:10:31.210 --> 02:10:34.230
in-person town hall this year as well

02:10:34.230 --> 02:10:36.593
in our areas of highest fire risk.

02:10:37.450 --> 02:10:41.220
This year, in addition to
our customized campaign

02:10:41.220 --> 02:10:43.470
for our access and
functional needs customers,

02:10:43.470 --> 02:10:48.470
we are working with tribal
councils and several focus groups

02:10:50.030 --> 02:10:55.030
within our tribes to real
help us develop a customized

02:10:56.000 --> 02:10:59.664
and culturally appropriate
public education campaign

02:10:59.664 --> 02:11:02.170
that's gonna be meaningful
and relevant to our tribes,

02:11:02.170 --> 02:11:03.620
because what we've learned

02:11:03.620 --> 02:11:08.320
is that our public
education campaign is not,

02:11:08.320 --> 02:11:10.000
that we do for the general public,

02:11:10.000 --> 02:11:12.130
there's a lot of room for opportunity

02:11:12.130 --> 02:11:14.430
to make that a little bit
more culturally sensitive

02:11:14.430 --> 02:11:16.163
for those customers.

02:11:17.595 --> 02:11:20.350
We're also going to expand

02:11:20.350 --> 02:11:22.740
our multi-channel engagement strategy.

02:11:22.740 --> 02:11:24.480
Primarily one of the things

02:11:24.480 --> 02:11:26.940
that we're looking into
exploring is building

02:11:26.940 --> 02:11:31.300
a strong public education and
communications partnership

02:11:31.300 --> 02:11:35.400
with our schools that are in our HFTD,

02:11:35.400 --> 02:11:38.720
and really leveraging that partnership.

02:11:38.720 --> 02:11:40.070
And also we're looking

02:11:40.070 --> 02:11:42.380
at other community-based organizations

02:11:42.380 --> 02:11:44.290
that we can partner with,

02:11:44.290 --> 02:11:47.280
and then looking to
see, and also exploring

02:11:47.280 --> 02:11:51.750
what other in-community
signage avenues there are for us

02:11:51.750 --> 02:11:54.040
to really be able to further strengthen

02:11:54.040 --> 02:11:57.010
our communications,
with some of our customers

02:11:57.010 --> 02:12:00.590
that frankly just are not technology,

02:12:00.590 --> 02:12:04.103
do not appreciate technology,
or use it or rely on it.

02:12:05.500 --> 02:12:09.110
So, and then we're gonna
continue throughout the year,

02:12:09.110 --> 02:12:12.660
these listening sessions
and working groups,

02:12:12.660 --> 02:12:15.080
not only with our customers,
but with our local government,

02:12:15.080 --> 02:12:17.150
our tribes, public safety partners

02:12:18.212 --> 02:12:20.970
and critical facilities
and infrastructure

02:12:21.977 --> 02:12:22.810
of account holders as well.

02:12:22.810 --> 02:12:23.730
And they're gonna be

02:12:23.730 --> 02:12:26.940
like a customer-listen
type of engagement.

02:12:26.940 --> 02:12:30.030
We're really going to
continue try to be as nimble

02:12:30.030 --> 02:12:33.410
as we can be so that we can have

02:12:33.410 --> 02:12:36.460
a meaningful public education

02:12:36.460 --> 02:12:38.060
and outreach campaign this year.

02:12:39.150 --> 02:12:44.030
So are there any other
questions that I can help answer?

02:12:44.030 --> 02:12:46.750
<v ->Yeah, I have one question
on the wildfire safety fairs.</v>

02:12:46.750 --> 02:12:49.172
You said you had six drive-through.

02:12:49.172 --> 02:12:51.050
Can you just talk a little
bit about where those were

02:12:51.050 --> 02:12:53.930
and the coverage
regarding the relevant areas

02:12:53.930 --> 02:12:57.080
that have the most PSPS?

02:12:58.610 --> 02:13:00.107
<v ->Yeah.</v>

02:13:00.107 --> 02:13:02.760
So they were all in our
high-fire threat areas.

02:13:06.980 --> 02:13:09.170
So Brian, I saw you, you pop in,

02:13:09.170 --> 02:13:11.760
if you wanna elaborate
a little bit more on that.

02:13:12.700 --> 02:13:13.533
<v ->Yeah.</v>

02:13:13.533 --> 02:13:16.300
We started off with those six
main communities where we did

02:13:16.300 --> 02:13:19.234
the town halls after 2007.

02:13:19.234 --> 02:13:23.210
So if you go down to North County,

02:13:23.210 --> 02:13:26.790
we did Tribal Nation there,
but then also Valley Center,

02:13:26.790 --> 02:13:30.763
which is our biggest
population up in North County.

02:13:31.632 --> 02:13:33.680
And then as you start
heading south, we did Ramona,

02:13:33.680 --> 02:13:35.630
which is in the foothills.

02:13:35.630 --> 02:13:37.792
Then if you start going up the hill,

02:13:37.792 --> 02:13:41.632
we did Julian up there,
then down in Alpine,

02:13:41.632 --> 02:13:45.530
which is getting down
into kind of further south,

02:13:45.530 --> 02:13:46.700
but then all the way down

02:13:46.700 --> 02:13:49.588
towards the Mexican border in Potrero.

02:13:49.588 --> 02:13:52.960
And then we actually went out
east towards Mountain Empire.

02:13:52.960 --> 02:13:57.770
So we really tried to cover
kind of foothills and mountains

02:13:57.770 --> 02:13:59.910
all the way up from North to south

02:13:59.910 --> 02:14:01.593
across the service territory.

02:14:02.870 --> 02:14:04.215
<v ->Great.</v>

02:14:04.215 --> 02:14:06.370
So are there any
areas, that I'm thinking

02:14:06.370 --> 02:14:08.860
about transportation distance,

02:14:08.860 --> 02:14:11.480
folks that might have
a struggle with getting

02:14:11.480 --> 02:14:14.470
to those locations, are
there any additional pockets

02:14:14.470 --> 02:14:17.593
that you feel like you guys
need to cover this coming year?

02:14:18.610 --> 02:14:22.500
<v ->This year, I feel like we
did try to be very thoughtful</v>

02:14:22.500 --> 02:14:25.860
with that by even putting
them right on the eight

02:14:25.860 --> 02:14:30.460
to get them very, very
close and easily accessible

02:14:30.460 --> 02:14:32.920
across the whole service territory.

02:14:32.920 --> 02:14:35.290
But I feel like we have good coverage,

02:14:35.290 --> 02:14:38.687
but we will continue to
keep that kind of very close,

02:14:38.687 --> 02:14:40.200
and we'll be thoughtful about that,

02:14:40.200 --> 02:14:44.270
especially as we continue to
expand onto the tribal nations,

02:14:44.270 --> 02:14:47.060
as we expand, we're almost
looking at it's catching on

02:14:48.118 --> 02:14:50.090
and there's so much interest
in this that we're looking

02:14:50.090 --> 02:14:53.760
at almost micro-fairs and
smaller community levels,

02:14:53.760 --> 02:14:57.190
and we're really gonna expand
this concept and continue

02:14:57.190 --> 02:14:58.360
to build on it this year,

02:14:58.360 --> 02:15:00.840
really being more aggressive of getting

02:15:00.840 --> 02:15:02.840
into the communities themselves.

02:15:02.840 --> 02:15:05.530
So, but yeah, we will keep that.

02:15:05.530 --> 02:15:06.363
Thank you.

02:15:08.598 --> 02:15:09.598
<v ->Thank you.</v>

02:15:12.430 --> 02:15:13.593
<v ->If there any no
other questions,</v>

02:15:13.593 --> 02:15:16.870
then I would like to invite
my colleague, Danielle Kyd,

02:15:16.870 --> 02:15:19.910
who is our Access and Functional
Needs Strategy Manager,

02:15:19.910 --> 02:15:23.390
to share some of the great
work that her team is doing

02:15:23.390 --> 02:15:26.563
around Medical Baseline,
tribal and our AFN customers.

02:15:28.660 --> 02:15:29.660
<v ->Thank you, Zoraya,
and thank you, everyone.</v>

02:15:29.660 --> 02:15:31.530
I'm very excited to be here today

02:15:31.530 --> 02:15:35.350
to talk about this wonderful
subject and building on a lot

02:15:35.350 --> 02:15:38.910
of the summaries that
Zoraya started to talk about

02:15:38.910 --> 02:15:41.250
with our public education campaigns.

02:15:41.250 --> 02:15:44.610
Could we go to the first slide, please?

02:15:44.610 --> 02:15:46.104
Thank you.

02:15:46.104 --> 02:15:47.690
I'll briefly go through
kind of our broader support

02:15:47.690 --> 02:15:49.820
of individuals with Access
and Functional Needs,

02:15:49.820 --> 02:15:52.153
our Medical Baseline, our tribal,

02:15:52.153 --> 02:15:54.310
and then the second slide
will be honed in on the specifics

02:15:54.310 --> 02:15:55.933
around the Thanksgiving Event.

02:15:56.800 --> 02:16:00.250
So I want to briefly start
by noting that this area

02:16:00.250 --> 02:16:03.160
is really heavily shaped
by our partnerships

02:16:03.160 --> 02:16:05.770
through our statewide
and our regional councils,

02:16:05.770 --> 02:16:07.380
and in particular, we have a group

02:16:07.380 --> 02:16:10.540
of very engaged AFN
executive stakeholders,

02:16:10.540 --> 02:16:14.030
such as the State Council
for Developmental Disabilities

02:16:14.030 --> 02:16:15.240
and several other members,

02:16:15.240 --> 02:16:18.490
and what's so critical about
that is they're really involved

02:16:18.490 --> 02:16:21.990
in the planning and the
evaluation of solutions

02:16:21.990 --> 02:16:24.723
for individuals with Access
and Functional Needs

02:16:24.723 --> 02:16:25.910
throughout the entire process.

02:16:25.910 --> 02:16:29.220
So that's a channel
and a really key resource

02:16:29.220 --> 02:16:32.655
that we leveraged heavily in 2021,

02:16:32.655 --> 02:16:33.991
and that we're gonna continue

02:16:33.991 --> 02:16:35.641
to leverage very heavily in 2022.

02:16:36.953 --> 02:16:38.170
I'm gonna briefly
touch on a couple points

02:16:38.170 --> 02:16:41.080
for Medical Baseline, but I
do want to note that our efforts

02:16:41.080 --> 02:16:44.090
are really more broadly
focused around all individuals

02:16:44.090 --> 02:16:46.700
with access and functional
needs and not limited

02:16:46.700 --> 02:16:49.510
to Medical Baselines specifically.

02:16:49.510 --> 02:16:52.170
However, as far as some
efforts with that program

02:16:53.008 --> 02:16:55.708
in particular, I think Zoraya
briefly touched on this,

02:16:57.872 --> 02:16:59.030
but a key focus was
getting out there prior

02:17:00.286 --> 02:17:01.587
to the wildfire season and making sure

02:17:01.587 --> 02:17:02.740
that we had updated contact information

02:17:02.740 --> 02:17:04.500
for our customers that are enrolled

02:17:04.500 --> 02:17:06.560
on the Medical Baseline Program.

02:17:06.560 --> 02:17:08.824
We took that a step further though,

02:17:08.824 --> 02:17:10.070
and we really went out
to a much broader group

02:17:10.070 --> 02:17:12.810
of individuals with Access and
Functional Needs to make sure

02:17:12.810 --> 02:17:14.970
that we had updated account information,

02:17:14.970 --> 02:17:17.780
as well as inviting
them to self-identify

02:17:17.780 --> 02:17:19.640
as having an Access and Functional Needs

02:17:19.640 --> 02:17:22.893
so that we can use that
for targeting and solutions.

02:17:24.110 --> 02:17:26.410
Additionally, we did work, again,

02:17:26.410 --> 02:17:28.848
through our statewide council and a lot

02:17:28.848 --> 02:17:30.860
of these partners to
promote at statewide level

02:17:30.860 --> 02:17:33.400
the availability of the
Medical Baseline Program.

02:17:33.400 --> 02:17:34.950
And I'll just call out one example

02:17:34.950 --> 02:17:36.520
we have listed on the slide,

02:17:36.520 --> 02:17:40.057
which is a joint effort
we did with the, sorry,

02:17:42.599 --> 02:17:45.820
the IHS Act and a regional
center where we developed a flyer

02:17:45.820 --> 02:17:48.660
promoting Medical
Baseline in 11 languages,

02:17:48.660 --> 02:17:51.280
and we were able to
leverage distribution channels

02:17:51.280 --> 02:17:54.310
through those partners to
get that out to a broader reach

02:17:54.310 --> 02:17:55.870
than we would normally have necessarily

02:17:55.870 --> 02:17:57.163
as the three.

02:17:59.553 --> 02:18:00.921
And I also just wanna mention

02:18:00.921 --> 02:18:03.150
that we didn't continue our
Enhanced PSPS door knock

02:18:03.150 --> 02:18:06.260
for individuals enrolled on
the Medical Baseline Program.

02:18:06.260 --> 02:18:08.700
And what that means is that when we go

02:18:08.700 --> 02:18:11.170
through our notification process,

02:18:11.170 --> 02:18:14.980
if we're unable to confirm
receipts by individuals enrolled

02:18:14.980 --> 02:18:16.414
in that program,

02:18:16.414 --> 02:18:18.900
we will actually go ahead
and send a truck to their home

02:18:18.900 --> 02:18:21.503
to check on them and make
sure they're aware of the event.

02:18:23.107 --> 02:18:25.540
With that, I wanna move
into the broader focus

02:18:25.540 --> 02:18:28.140
on individuals with Access
and Functional Needs.

02:18:28.140 --> 02:18:30.570
So really the Cornerstone
of our support program

02:18:30.570 --> 02:18:33.217
has been partnering with 211 San Diego

02:18:33.217 --> 02:18:34.810
and 211 Orange County

02:18:34.810 --> 02:18:39.150
who serve as a centralized
resource hub for us around PSPS.

02:18:39.150 --> 02:18:42.100
So they bring together
about 1,000 different CBOs

02:18:42.100 --> 02:18:44.540
across San Diego and Orange County

02:18:44.540 --> 02:18:47.610
in our service territory to
connect customers as Verizon,

02:18:47.610 --> 02:18:50.660
that maybe wouldn't
call us, but we'll call 211,

02:18:50.660 --> 02:18:52.640
connect them with available resources.

02:18:52.640 --> 02:18:55.620
But what we made
some significant strides in

02:18:55.620 --> 02:18:59.850
in 2021 was really enhancing
the services available.

02:18:59.850 --> 02:19:01.750
So we put in place direct partnerships

02:19:01.750 --> 02:19:05.326
around accessible
transportation through FACT.

02:19:05.326 --> 02:19:09.780
We put in no-cost hotel
states with the Salvation Army.

02:19:09.780 --> 02:19:12.690
We really enhanced the
available food support,

02:19:12.690 --> 02:19:14.340
both from a warm food perspective

02:19:17.577 --> 02:19:18.410
and from like a food bank
distribution perspective

02:19:20.012 --> 02:19:20.845
to support individuals during a PSPS.

02:19:20.845 --> 02:19:22.770
We also launched, and
Jon will talk about this more

02:19:22.770 --> 02:19:23.930
in the next section, but we launched

02:19:23.930 --> 02:19:27.330
an Emergency Generator
Backup Battery Program.

02:19:27.330 --> 02:19:31.110
So what that means is if we
are in the middle of a PSPS,

02:19:31.110 --> 02:19:33.888
we have customers who are calling 211

02:19:33.888 --> 02:19:36.290
or SDG&amp;E needing
assistance, and the hotel,

02:19:36.290 --> 02:19:39.310
transportation, food, resiliency items,

02:19:39.310 --> 02:19:40.870
if the combination of those services

02:19:40.870 --> 02:19:43.980
are still not sufficient to
meeting an individual's needs,

02:19:43.980 --> 02:19:47.490
we actually have the ability
to dispatch a generator,

02:19:47.490 --> 02:19:48.960
usually within one to four hours,

02:19:48.960 --> 02:19:50.700
typically a little bit
closer to one hour,

02:19:50.700 --> 02:19:53.750
depending on how many
customers are in need.

02:19:53.750 --> 02:19:57.940
But we use that broader suite
of solutions to help customers

02:19:57.940 --> 02:19:58.990
during a PSPS.

02:20:00.130 --> 02:20:03.150
I also wanna talk about
our CBO partnerships,

02:20:03.150 --> 02:20:05.520
and Zoraya started to touch on this,

02:20:05.520 --> 02:20:07.787
but I can't overemphasize
how critical that is.

02:20:07.787 --> 02:20:09.440
And we do have a network

02:20:09.440 --> 02:20:13.020
of 200 CBO partners that
we work with all year round

02:20:13.020 --> 02:20:16.480
on preparedness and
enduring PSPS events.

02:20:16.480 --> 02:20:21.160
In 2021, one of the areas of
enhancements that we undertook

02:20:21.160 --> 02:20:24.730
was we identified 40
specific CBO partners

02:20:24.730 --> 02:20:27.933
that served individuals in
the high-fire threat districts,

02:20:28.839 --> 02:20:31.770
and we provided them with
additional training and resources

02:20:31.770 --> 02:20:34.880
to really go out and help us
prepare those areas in advance

02:20:34.880 --> 02:20:38.000
of the season, but also
to amplify our notifications

02:20:38.000 --> 02:20:41.460
and services during a PSPS,
to build on the awareness

02:20:42.517 --> 02:20:43.593
of those available services.

02:20:44.920 --> 02:20:47.400
Let's see, one critical
aspect I wanna highlight

02:20:47.400 --> 02:20:49.923
is we do have it dedicated
tribal liaison who meet

02:20:49.923 --> 02:20:52.630
with their tribal leaders
year round to understand

02:20:52.630 --> 02:20:56.110
their needs and incorporate
that feedback into our program.

02:20:56.110 --> 02:20:58.352
A couple examples of that,

02:20:58.352 --> 02:21:00.770
we do have partnerships
with the Indian Health Council

02:21:00.770 --> 02:21:03.110
and Southern Indian Health Council,

02:21:03.110 --> 02:21:05.200
which represent all the
different tribal communities

02:21:05.200 --> 02:21:06.770
throughout our service territory.

02:21:06.770 --> 02:21:08.880
And why that's really
important is it gives us

02:21:08.880 --> 02:21:11.363
that direct link in providing services.

02:21:15.373 --> 02:21:16.210
So for example, prior to the season,

02:21:16.210 --> 02:21:18.090
with those two partners
to identify needs,

02:21:18.090 --> 02:21:20.170
and the two that we really heard

02:21:21.151 --> 02:21:23.000
were resiliency items and generators.

02:21:23.000 --> 02:21:24.240
So in advance of the season,

02:21:24.240 --> 02:21:26.473
we did go out and we distributed

02:21:26.473 --> 02:21:28.790
all the requested resiliency
items for those communities.

02:21:28.790 --> 02:21:29.860
But the generators, I think,

02:21:29.860 --> 02:21:32.090
was a really eye-opening moment for us,

02:21:32.090 --> 02:21:34.890
where we realized we
needed to streamline

02:21:34.890 --> 02:21:38.100
the delivery process
specific to tribal communities.

02:21:38.100 --> 02:21:39.400
So we partnered with, again,

02:21:39.400 --> 02:21:40.900
the Indian Health Council

02:21:40.900 --> 02:21:43.890
and our Generator Delivery Organization

02:21:43.890 --> 02:21:46.770
to allow the Indian
Health Council to direct

02:21:46.770 --> 02:21:49.560
where those generators
should go and kind of streamline

02:21:49.560 --> 02:21:52.380
that enrollment process to make it easy.

02:21:52.380 --> 02:21:54.710
So again, we will continue
to work very closely

02:21:54.710 --> 02:21:57.790
with our partners in the tribal
community going forward.

02:21:57.790 --> 02:21:59.625
I also just wanted to build,

02:21:59.625 --> 02:22:01.820
we did have the
opportunity to also in addition

02:22:01.820 --> 02:22:04.520
to our wildfire safety fairs host

02:22:04.520 --> 02:22:08.940
a joint event with the La
Jolla Band of Luiseno Indians

02:22:08.940 --> 02:22:11.165
back in July, which we were able to go

02:22:11.165 --> 02:22:14.570
to their community center and to engage

02:22:14.570 --> 02:22:16.880
with their community, to
provide resiliency items,

02:22:16.880 --> 02:22:20.700
backpacks, education, and
we're very much looking forward

02:22:21.750 --> 02:22:23.460
to continuing those types of
efforts, as Brian mentioned,

02:22:23.460 --> 02:22:27.320
really going into a broader space.

02:22:27.320 --> 02:22:28.400
I do wanna briefly talk

02:22:28.400 --> 02:22:30.970
about our Emergency Operating Center.

02:22:30.970 --> 02:22:33.130
In 2020, we created a dedicated

02:22:33.130 --> 02:22:35.070
Access and Functional News Unit,

02:22:35.070 --> 02:22:37.960
where our entire purpose
is really to be there

02:22:37.960 --> 02:22:40.800
to address any customer
concerns that come in

02:22:40.800 --> 02:22:43.120
during a PSPS event.

02:22:43.120 --> 02:22:46.470
In 2021, we moved
that to report directly

02:22:46.470 --> 02:22:48.250
to our Incident Commander,

02:22:48.250 --> 02:22:50.220
and we also doubled
the bench strength of that.

02:22:50.220 --> 02:22:52.740
So wanting to make sure that we're there

02:22:52.740 --> 02:22:54.883
during PSPS to support.

02:22:55.740 --> 02:22:59.370
We also added a couple
other support channels in place.

02:22:59.370 --> 02:23:01.510
One of them is an email address.

02:23:01.510 --> 02:23:03.440
So we do have an ASN email address.

02:23:03.440 --> 02:23:06.120
We do try to get the
word as much as possible,

02:23:06.120 --> 02:23:08.330
where we're able to
directly receive inquiries

02:23:08.330 --> 02:23:11.400
and help address any kind
of concerns that come in.

02:23:11.400 --> 02:23:14.120
So we've seen questions
about generators,

02:23:14.120 --> 02:23:17.180
around medical baseline
enrollment, around planned outages,

02:23:17.180 --> 02:23:19.940
and we've been able to kind
of directly work with customers

02:23:19.940 --> 02:23:21.650
to resolve those.

02:23:21.650 --> 02:23:23.550
The other one, though, I
wanna mention is we have

02:23:23.550 --> 02:23:25.313
a new AFN landing page.

02:23:26.274 --> 02:23:28.440
And what that means
is we wanted to take all

02:23:28.440 --> 02:23:30.740
of the different solutions
that are available

02:23:30.740 --> 02:23:32.830
to an individual with access
and functionally and put them

02:23:32.830 --> 02:23:36.850
in one place on our website
to make it easier to find.

02:23:36.850 --> 02:23:39.493
So that has been a useful tool as well.

02:23:41.430 --> 02:23:44.830
Let see, I'll finish a
couple more points.

02:23:44.830 --> 02:23:48.350
I do wanna talk a little
bit around targeting

02:23:48.350 --> 02:23:50.000
of outreaching solutions.

02:23:50.000 --> 02:23:53.100
The course, a key element of
our plan has been to make sure

02:23:53.100 --> 02:23:55.240
that individuals are
aware of what services

02:23:55.240 --> 02:23:57.340
are available to them.

02:23:57.340 --> 02:24:00.100
Zoraya did a fantastic
job of really doing

02:24:00.100 --> 02:24:03.250
a dedicated campaign around
211 and driving individuals

02:24:03.250 --> 02:24:05.830
to call 211 for assistance.

02:24:05.830 --> 02:24:08.840
But another component
that's been, a key focus of ours

02:24:08.840 --> 02:24:11.930
since last year has been
around AFN identification,

02:24:11.930 --> 02:24:15.330
and really proactively
going out there and trying

02:24:15.330 --> 02:24:17.870
to reach out to customers, first off,

02:24:17.870 --> 02:24:20.513
allow them to self-identify,
if they're interested,

02:24:21.664 --> 02:24:22.650
but then we can send

02:24:22.650 --> 02:24:27.170
specific targeted preparedness
materials, communications,

02:24:27.170 --> 02:24:31.403
and also solutions like
generators out to those customers.

02:24:32.590 --> 02:24:33.850
Let's see.

02:24:33.850 --> 02:24:37.350
And then I'll just finish on
community resource centers.

02:24:37.350 --> 02:24:40.500
So community resource
centers were a key focus, again,

02:24:40.500 --> 02:24:41.830
this year will continue to be,

02:24:41.830 --> 02:24:45.100
but really around ensuring
that they're comfortable

02:24:45.100 --> 02:24:47.660
for individuals with Access
and Functional Needs.

02:24:47.660 --> 02:24:50.681
So some of the enhancements
we put in there this year,

02:24:50.681 --> 02:24:52.460
and a lot of these stem
from feedback we received

02:24:52.460 --> 02:24:55.160
from the Statewide Council
and our other stakeholders,

02:24:56.041 --> 02:24:59.290
were around privacy screens,
around enhanced signage,

02:24:59.290 --> 02:25:00.733
dedicated parking,

02:25:01.835 --> 02:25:04.410
and then onsite American
Sign Language translation,

02:25:04.410 --> 02:25:05.750
which is done through a tablet.

02:25:05.750 --> 02:25:08.900
So if there's an individual
who needs assistance,

02:25:08.900 --> 02:25:11.966
any of our representatives
that are working

02:25:11.966 --> 02:25:13.303
at that Community Resource Center

02:25:13.303 --> 02:25:15.749
have the ability to pull
up their tablets and do

02:25:15.749 --> 02:25:17.120
a direct translation.

02:25:17.120 --> 02:25:18.787
So on the next slide,

02:25:18.787 --> 02:25:21.230
I'm gonna cover more on the
Thanksgiving Event specifically,

02:25:21.230 --> 02:25:24.360
but why don't I pause there
in case there's any questions

02:25:24.360 --> 02:25:25.773
or comments on this slide?

02:25:30.140 --> 02:25:31.678
Yes, please go ahead.

02:25:31.678 --> 02:25:32.983
<v ->I have a question, Danielle.</v>

02:25:35.300 --> 02:25:37.960
We talked to Southern
California Edison a lot

02:25:37.960 --> 02:25:39.570
about their Battery Program,

02:25:39.570 --> 02:25:41.330
and I heard your description

02:25:41.330 --> 02:25:44.220
of what sounds like
it's Generator Program.

02:25:44.220 --> 02:25:46.730
Is that, are you
using that term to refer

02:25:48.027 --> 02:25:50.840
to batteries as well, or
are these gas generators

02:25:50.840 --> 02:25:55.640
or so, and also, I guess my
question, the second part,

02:25:55.640 --> 02:25:58.990
which is a lot of what
you seem to emphasize

02:25:58.990 --> 02:26:03.293
was delivering
generators during an event.

02:26:03.293 --> 02:26:04.380
And so wanted to know a little bit more

02:26:04.380 --> 02:26:09.380
about as backup power
supply options that could be put

02:26:09.583 --> 02:26:11.683
into place prior to an event.

02:26:13.100 --> 02:26:15.010
<v ->Thank you, President Reynolds.</v>

02:26:15.010 --> 02:26:16.970
Most of that, again, I don't wanna feel

02:26:16.970 --> 02:26:18.363
my colleague Thunder,

02:26:19.406 --> 02:26:20.940
but Jon Kochik on the next
section is gonna go into those

02:26:20.940 --> 02:26:23.420
in detail, but thank
you for the question,

02:26:23.420 --> 02:26:26.280
particular around
generators versus batteries.

02:26:26.280 --> 02:26:29.870
I am specifically referring
to rechargeable batteries

02:26:29.870 --> 02:26:33.083
that we send out for our
individuals' Medical Baseline

02:26:33.083 --> 02:26:34.200
and Access and Functional Needs,

02:26:34.200 --> 02:26:37.506
but Jon is gonna spend
some time going through kind

02:26:37.506 --> 02:26:38.350
of all the programs available

02:26:39.243 --> 02:26:40.130
and going through more
specific numbers and goals

02:26:40.130 --> 02:26:41.130
in the next section.

02:26:42.560 --> 02:26:44.018
<v ->Okay, got it.</v>

02:26:44.018 --> 02:26:45.670
So that term means
backup energy generation,

02:26:45.670 --> 02:26:48.788
not gas generators, and
it's meant to include batteries.

02:26:48.788 --> 02:26:50.674
Okay.
<v ->Yes, thank you.</v>

02:26:50.674 --> 02:26:52.474
Some of them are not gas generators.

02:26:57.320 --> 02:26:58.821
Okay.

02:26:58.821 --> 02:26:59.654
Can we go ahead to the next slide,

02:26:59.654 --> 02:27:00.640
and I'll talk a little bit more

02:27:00.640 --> 02:27:02.090
about our Thanksgiving Event?

02:27:06.150 --> 02:27:07.523
Thank you very much.

02:27:09.030 --> 02:27:13.870
So we're all well aware that
SDG&amp;E's only event last year

02:27:13.870 --> 02:27:18.060
did unfortunately occur on
PSPS, I'm sorry, on Thanksgiving,

02:27:18.060 --> 02:27:19.240
and we worked very closely

02:27:19.240 --> 02:27:21.650
with our local AFN resource partners,

02:27:21.650 --> 02:27:24.760
including 211, FACT, Salvation Army,

02:27:24.760 --> 02:27:27.874
the San Diego Food
Bank, our tribal communities

02:27:27.874 --> 02:27:29.080
and many others to revise the course

02:27:29.080 --> 02:27:31.930
during that PSPS activation.

02:27:31.930 --> 02:27:35.005
Again, we did have no cost hotel stays,

02:27:35.005 --> 02:27:36.130
accessible transportation
and other forms

02:27:36.130 --> 02:27:37.870
of support available.

02:27:37.870 --> 02:27:42.870
In total, 211 received about
35 calls related to that PSPS,

02:27:44.038 --> 02:27:47.010
of which five of those
were requests for services.

02:27:47.010 --> 02:27:49.780
Of those, one customer requested

02:27:49.780 --> 02:27:51.080
round-trip transportation,

02:27:51.938 --> 02:27:54.480
and four hotel nights were provided.

02:27:54.480 --> 02:27:58.750
We did have emergency
backup batteries on hand,

02:27:58.750 --> 02:28:00.400
but we did not receive any requests

02:28:00.400 --> 02:28:02.503
for those during that PSPS.

02:28:03.440 --> 02:28:06.310
One opportunity that
was key is we did leverage

02:28:06.310 --> 02:28:08.240
San Diego County Partner Relay Network

02:28:08.240 --> 02:28:10.250
as well as our energy solutions partners

02:28:10.250 --> 02:28:14.880
that we've been talking a lot
about to provide daily updates

02:28:14.880 --> 02:28:16.200
for support and coordination

02:28:16.200 --> 02:28:18.708
and to help amplify our messaging,

02:28:18.708 --> 02:28:21.950
and we were able to reach
about 725 AFN partners

02:28:21.950 --> 02:28:24.530
through that about the PSPS.

02:28:24.530 --> 02:28:27.737
This does also include frequent updates

02:28:27.737 --> 02:28:29.969
to our supporting
partners like 211, FACT

02:28:29.969 --> 02:28:30.919
and Salvation Army,

02:28:32.402 --> 02:28:34.769
as well as our network of
paratransit agencies and a lot

02:28:34.769 --> 02:28:36.850
of other key partners,
including those 40

02:28:36.850 --> 02:28:38.397
I mentioned that specifically support

02:28:38.397 --> 02:28:40.293
the high-fire threat district.

02:28:41.710 --> 02:28:44.280
We did have three community
resource centers open

02:28:44.280 --> 02:28:46.830
in a drive-through format for that PSPS

02:28:47.935 --> 02:28:49.460
offering resiliency items,

02:28:49.460 --> 02:28:52.110
again, the same solutions,
no cost with health stays,

02:28:53.210 --> 02:28:55.440
backup batteries, et cetera.

02:28:55.440 --> 02:28:58.120
And I did wanna share
with this team though,

02:28:58.120 --> 02:29:00.740
our biggest challenge that
we face on the AFN side

02:29:00.740 --> 02:29:03.490
during this event, and
that was around warm food.

02:29:03.490 --> 02:29:07.140
So we had planned to be able
to provide warm food as needed

02:29:07.140 --> 02:29:10.750
during a PSPS, and we
had contracted with a couple

02:29:10.750 --> 02:29:12.990
of different catering companies
in advance to be prepared

02:29:12.990 --> 02:29:14.580
to do that.

02:29:14.580 --> 02:29:17.070
However, it turns out
it is very difficult to get

02:29:17.070 --> 02:29:20.450
a large amount of meals
delivered on Thanksgiving

02:29:20.450 --> 02:29:22.080
out to a lot of these communities.

02:29:22.080 --> 02:29:24.193
So we, luckily we were able to,

02:29:25.787 --> 02:29:26.670
we were able to make a lot of calls

02:29:26.670 --> 02:29:28.989
and get about 600 meals delivered

02:29:28.989 --> 02:29:31.010
to our community resource centers

02:29:31.010 --> 02:29:36.010
and also to one impacted
community, that needed them.

02:29:36.050 --> 02:29:38.806
So we were able to get
those on both the Thursday

02:29:38.806 --> 02:29:39.639
and the Friday.

02:29:39.639 --> 02:29:40.660
What we actually found

02:29:40.660 --> 02:29:43.480
was that we didn't need
nearly that many meals.

02:29:43.480 --> 02:29:46.550
We only saw, I think about 20 consumed

02:29:46.550 --> 02:29:48.480
at each of the, season
in that neighborhood.

02:29:48.480 --> 02:29:50.910
So we had a lot of extra food on hand,

02:29:50.910 --> 02:29:52.570
and luckily we were able to donate that

02:29:52.570 --> 02:29:56.540
to a food event with the
Filipino Veterans Association Hall

02:29:56.540 --> 02:29:59.310
the next day was a
senior food distribution.

02:29:59.310 --> 02:30:02.450
But I think two key lessons
that we learned from that, one,

02:30:02.450 --> 02:30:05.930
we need have a much deeper
bench strength on food support,

02:30:05.930 --> 02:30:08.490
just in case the worst
case scenario does happen

02:30:08.490 --> 02:30:11.510
and we have a PSPS on Thanksgiving,

02:30:11.510 --> 02:30:12.760
so we'll be prepared for that.

02:30:12.760 --> 02:30:14.370
And then the other key lesson

02:30:14.370 --> 02:30:17.420
was really around sustainable strategy

02:30:17.420 --> 02:30:18.770
for food waste, right?

02:30:18.770 --> 02:30:21.100
Again, we were fortunate
to be able to connect

02:30:21.100 --> 02:30:23.740
with some partners and put
all of that food to good use,

02:30:23.740 --> 02:30:25.910
but that's something that
we are going to streamline

02:30:25.910 --> 02:30:28.090
for the future as well.

02:30:28.090 --> 02:30:30.847
So that is the end of my presentation.

02:30:30.847 --> 02:30:32.070
Why don't I pause there for questions,

02:30:32.070 --> 02:30:34.210
and then I can turn that
over, if there are none,

02:30:34.210 --> 02:30:36.633
to Jon to talk about our
Backup Battery Program.

02:30:40.330 --> 02:30:41.290
Okay.

02:30:41.290 --> 02:30:43.277
I'd like to introduce Jon Kochik.

02:30:45.780 --> 02:30:47.215
<v ->Thanks, Danielle.</v>

02:30:47.215 --> 02:30:48.048
Hi, everyone.

02:30:48.048 --> 02:30:49.880
Thanks for giving a chance
to dive a little bit deeper

02:30:49.880 --> 02:30:52.680
into our Backup Battery
Generator Program.

02:30:52.680 --> 02:30:54.780
So you can flip to
the next slide, please.

02:30:57.380 --> 02:31:02.319
So I'll walk through each
of these three programs

02:31:02.319 --> 02:31:05.114
so that you get a better sense of these.

02:31:05.114 --> 02:31:06.240
And I'll with the one on the left,

02:31:06.240 --> 02:31:07.810
the Generator Grant Program,

02:31:07.810 --> 02:31:11.430
and for context, this
one is pretty consistent

02:31:11.430 --> 02:31:16.430
with Edison's Critical Care
Backup Battery Program.

02:31:16.460 --> 02:31:20.240
It provides those backup
battery, portable batteries

02:31:20.240 --> 02:31:22.720
to our most vulnerable customers,

02:31:22.720 --> 02:31:25.180
meaning those that
are on Medical Baseline

02:31:25.180 --> 02:31:27.590
and have access and
functional needs and live

02:31:27.590 --> 02:31:30.300
within the high-fire threat district.

02:31:30.300 --> 02:31:33.140
The battery unit is provided
at no charge to ensure

02:31:33.140 --> 02:31:36.943
we help these customers. When
they experience PSPS events.

02:31:37.902 --> 02:31:38.797
(Jon clears throat)

02:31:38.797 --> 02:31:39.630
Looking at 2021,

02:31:39.630 --> 02:31:44.203
we delivered 2,310
batteries to this audience,

02:31:45.070 --> 02:31:47.640
exceeding our target of 2,000.

02:31:47.640 --> 02:31:50.580
Program went live in 2019, and to date,

02:31:50.580 --> 02:31:53.923
we've delivered almost 3,800
batteries to this audience.

02:31:55.070 --> 02:31:58.180
The number that we've
delivered has increased each year,

02:31:58.180 --> 02:32:00.820
and the program
continues to be highly valued

02:32:00.820 --> 02:32:03.820
by our customers, as you can
see, the customer responses

02:32:03.820 --> 02:32:06.263
on customer satisfaction
and preparedness.

02:32:07.520 --> 02:32:10.562
We also, and Danielle touched on this,

02:32:10.562 --> 02:32:11.395
partnered more closely this year

02:32:11.395 --> 02:32:13.480
with our Tribal Relations Liaisons

02:32:13.480 --> 02:32:15.010
and Indian Health Councils

02:32:15.010 --> 02:32:17.440
to make sure that they had
information and can spread

02:32:17.440 --> 02:32:19.180
the word on these programs to make sure

02:32:19.180 --> 02:32:21.509
that those vulnerable customers

02:32:21.509 --> 02:32:24.100
in the tribal communities
could participate.

02:32:24.100 --> 02:32:29.100
For 2022, we are increasing
our target from 2,000

02:32:29.430 --> 02:32:31.250
to 3,000 battery deliveries

02:32:31.250 --> 02:32:33.050
to reach another significant portion

02:32:34.004 --> 02:32:35.610
of these vulnerable customers.

02:32:35.610 --> 02:32:39.320
We look closely at the customer
data to proactively identify

02:32:39.320 --> 02:32:42.400
these customer who meet the
criteria program and reach out

02:32:42.400 --> 02:32:44.470
to them to schedule the delivery.

02:32:44.470 --> 02:32:46.730
So we do, we schedule them

02:32:46.730 --> 02:32:50.570
and deliver these proactively,
in addition to what Danielle

02:32:50.570 --> 02:32:53.770
was talking about, so we
kind of hit it from both sides.

02:32:53.770 --> 02:32:56.000
We make sure they have
them when they're ready,

02:32:56.000 --> 02:32:59.330
but then if there are some
that don't, when they need it,

02:32:59.330 --> 02:33:00.936
we're able to deliver on demand,

02:33:00.936 --> 02:33:05.433
fully charged within the
one to four hours at the most.

02:33:08.351 --> 02:33:11.720
So our goal is to reach
all of those customers

02:33:13.270 --> 02:33:15.170
in the high-fire threat
district that enroll

02:33:15.170 --> 02:33:19.280
to Medical Baseline and qualify as AFN

02:33:19.280 --> 02:33:22.940
while we still do prioritize
those who experience

02:33:22.940 --> 02:33:25.103
the most PSPS events.

02:33:26.010 --> 02:33:29.070
But I wanted to kind of
summarize this progress and plan.

02:33:29.070 --> 02:33:32.270
I know that, I'm sure
Rechtschaffen had questions

02:33:32.270 --> 02:33:35.810
on that before in terms
of what is the total number.

02:33:35.810 --> 02:33:38.851
And so our total number
is about 11,000, and so far,

02:33:38.851 --> 02:33:42.091
we've delivered about
3,800, and then as we plan,

02:33:42.091 --> 02:33:47.091
so this is about third, and
then if we add another 3,000

02:33:48.100 --> 02:33:51.260
on top of that, we'll
get pretty close to 60%

02:33:51.260 --> 02:33:55.977
of that total 11,000 or so of customers.

02:33:57.690 --> 02:34:00.150
And then in terms of
continuous improvement,

02:34:00.150 --> 02:34:02.571
we have a bullet there continuing

02:34:02.571 --> 02:34:04.820
to evaluate proposals
for program support

02:34:04.820 --> 02:34:07.980
that we're in our, beginning
our fourth year really

02:34:07.980 --> 02:34:10.990
of delivering this program,
and so it seems prudent

02:34:12.607 --> 02:34:15.220
to just be looking at proposals
that focus on making sure

02:34:15.220 --> 02:34:17.020
we're looking closely at costs well,

02:34:17.020 --> 02:34:19.823
continuing to ensure
high quality service.

02:34:23.560 --> 02:34:27.860
So, going to the next one, the
Generator Assistance Program,

02:34:27.860 --> 02:34:29.680
this is where we offer a rebate program

02:34:29.680 --> 02:34:33.200
for portable fuel generator
and backup battery

02:34:33.200 --> 02:34:36.630
or portable power stations
for qualifying customers

02:34:36.630 --> 02:34:39.080
in the high-fire threat district.

02:34:39.080 --> 02:34:42.970
It's a $300 rebate for those customers,

02:34:42.970 --> 02:34:45.000
plus if they are a care customer,

02:34:45.000 --> 02:34:49.063
they get an additional $150
to offset the cost of those.

02:34:50.113 --> 02:34:54.880
In 2021, we provided 735 rebates,

02:34:54.880 --> 02:34:56.540
which was a little less than our target,

02:34:56.540 --> 02:34:58.240
which was based on 2020,

02:35:00.170 --> 02:35:02.783
were fewer activations last year,

02:35:02.783 --> 02:35:06.073
we're thinking that probably
drove less participation in it.

02:35:08.040 --> 02:35:10.780
To date, the program has
provided over 2,000 rebates

02:35:10.780 --> 02:35:13.150
in the last two years,
with a solid level

02:35:13.150 --> 02:35:16.390
of customer satisfaction
with the program.

02:35:16.390 --> 02:35:18.510
The program will continue into 2022,

02:35:18.510 --> 02:35:23.180
and we're gonna target
1,250 customers again,

02:35:23.180 --> 02:35:26.210
and are updating our
rebate process to seek

02:35:26.210 --> 02:35:30.210
to allow purchases at a
wider selection of retailers,

02:35:30.210 --> 02:35:33.776
and identify more models
that qualify for rebate

02:35:33.776 --> 02:35:35.970
while still meeting safety requirements

02:35:35.970 --> 02:35:39.650
to make sure that
inventory is isn't an issue,

02:35:39.650 --> 02:35:42.120
and that customers have flexibility

02:35:42.120 --> 02:35:46.563
in the generators and backup
power options that they choose.

02:35:48.130 --> 02:35:49.820
Going to the right hand,

02:35:49.820 --> 02:35:51.750
when the Fixed Backup Power Program,

02:35:51.750 --> 02:35:54.610
this is the one that provides
a permanent generator

02:35:54.610 --> 02:35:57.350
to those customers who have
experienced a high number

02:35:57.350 --> 02:35:59.980
of PSPS events and are not really able

02:35:59.980 --> 02:36:03.340
to be feasibly reached
by grid hardening events.

02:36:03.340 --> 02:36:05.830
In 2021, the program continued to serve

02:36:05.830 --> 02:36:08.470
a growing number of customers,

02:36:08.470 --> 02:36:13.110
with over 465 formerly
agreeing to install a generator,

02:36:13.110 --> 02:36:16.980
and over 350 operational
by the end of the year.

02:36:16.980 --> 02:36:19.220
The program also began installing

02:36:19.220 --> 02:36:23.290
solar plus storage
backup power solutions

02:36:23.290 --> 02:36:25.160
for two mobile home parks,

02:36:25.160 --> 02:36:27.970
providing a cleaner option
for resiliency for customers,

02:36:27.970 --> 02:36:29.680
and the team will continue evaluating

02:36:29.680 --> 02:36:33.820
non-fossil fuel options into 2022.

02:36:33.820 --> 02:36:38.263
Total target for this coming
year is larger than it's been.

02:36:39.329 --> 02:36:40.960
We keep trying to expand
and increasing each year.

02:36:40.960 --> 02:36:43.233
So it'll be 470 generators,

02:36:44.320 --> 02:36:47.373
and installations are
already happening in 2022.

02:36:48.450 --> 02:36:51.350
And in addition to the plans
to help residential customers

02:36:51.350 --> 02:36:52.250
with this program,

02:36:53.558 --> 02:36:55.295
the team is identifying
additional mobile home parks,

02:36:55.295 --> 02:36:57.080
schools, community resource centers

02:36:57.080 --> 02:37:00.503
and other critical
facilities, for this program.

02:37:02.550 --> 02:37:03.550
So I'll pause there.

02:37:06.260 --> 02:37:09.660
<v ->Jon, thank you for
anticipating my question</v>

02:37:09.660 --> 02:37:11.183
about the denominator.

02:37:12.630 --> 02:37:14.033
<v ->You bet.</v>

02:37:14.033 --> 02:37:15.540
<v ->The portable batteries,</v>

02:37:15.540 --> 02:37:19.550
they are sized to power

02:37:19.550 --> 02:37:21.840
some medical devices
and other appliances

02:37:21.840 --> 02:37:25.505
that they're not power
walls or things like that,

02:37:25.505 --> 02:37:26.338
I assume, right?

02:37:26.338 --> 02:37:27.300
<v ->That's right.</v>

02:37:27.300 --> 02:37:28.776
That's right.

02:37:28.776 --> 02:37:31.083
3,000 watt hours of storage.

02:37:31.980 --> 02:37:32.920
That's right.

02:37:32.920 --> 02:37:35.378
It's not a permanent power wall.

02:37:35.378 --> 02:37:37.263
It's mobile portable, it's on wheels.

02:37:39.540 --> 02:37:40.373
Yeah.

02:37:42.270 --> 02:37:43.717
<v ->Okay.</v>

02:37:43.717 --> 02:37:44.910
But (clears throat) it's portable,

02:37:44.910 --> 02:37:47.899
but once a customer gets it,

02:37:47.899 --> 02:37:49.149
it stays with a customer.

02:37:50.160 --> 02:37:54.130
It's not a shared backup
the way that some

02:37:54.130 --> 02:37:55.400
that you were refer to

02:37:55.400 --> 02:37:57.730
which are dispatched
based on someone's need

02:37:57.730 --> 02:38:00.580
at a particular
community resource center

02:38:00.580 --> 02:38:02.200
or something like that?

02:38:02.200 --> 02:38:03.140
<v ->Correct.</v>

02:38:03.140 --> 02:38:04.710
That's right.

02:38:04.710 --> 02:38:07.640
It stays with the customer,
and really it's intended

02:38:07.640 --> 02:38:09.390
to be inside.

02:38:09.390 --> 02:38:12.050
So that's why it's meant to be portable

02:38:12.050 --> 02:38:15.330
so people can move it if
they need the refrigerator

02:38:15.330 --> 02:38:18.763
to be charged or their medical device.

02:38:20.470 --> 02:38:22.780
And so it's sized to
be able to do those,

02:38:22.780 --> 02:38:26.033
but yet still be able
to be moved around.

02:38:26.950 --> 02:38:28.335
<v ->Got it.</v>

02:38:28.335 --> 02:38:29.168
Thank you.

02:38:29.168 --> 02:38:30.001
<v ->You bet.</v>

02:38:32.830 --> 02:38:34.580
<v ->And could you
talk a little bit more</v>

02:38:34.580 --> 02:38:37.770
about the fixed backup option?

02:38:37.770 --> 02:38:40.054
I wanted to make sure I understood

02:38:40.054 --> 02:38:43.130
the, what is the, is there
subsidy provided there,

02:38:43.130 --> 02:38:46.293
or is this just kind of matching
these with customers?

02:38:47.310 --> 02:38:49.590
So what is the assistance
that you're providing,

02:38:49.590 --> 02:38:51.640
and then who would
be eligible for those?

02:38:53.730 --> 02:38:57.840
<v ->So those that are eligible,</v>

02:38:57.840 --> 02:39:02.740
and we use our risk
spend efficiency model

02:39:02.740 --> 02:39:04.180
to figure this out,

02:39:04.180 --> 02:39:07.160
we look closely at those customers

02:39:07.160 --> 02:39:12.160
that have traditionally seen a
high number of PSPS events,

02:39:14.100 --> 02:39:17.140
and in looking at our
grid-hardening events

02:39:17.140 --> 02:39:19.940
on circuits or, devices

02:39:19.940 --> 02:39:23.980
that are not likely to
be able to be reached

02:39:23.980 --> 02:39:27.670
by hardening efforts in a near future.

02:39:27.670 --> 02:39:31.910
And so the idea is they are provided

02:39:31.910 --> 02:39:36.910
a large diesel generator
that is installed at their home

02:39:38.640 --> 02:39:40.520
for the residential customers,

02:39:40.520 --> 02:39:44.750
and it provides them a
full backup power resiliency

02:39:46.097 --> 02:39:50.313
during PSPS events.

02:39:54.770 --> 02:39:58.260
And then as well, looking
at some mobile home parks

02:39:58.260 --> 02:40:02.950
in the high-fire threat district
and some schools as well

02:40:02.950 --> 02:40:07.041
so that those, more community centers

02:40:07.041 --> 02:40:09.223
have resilient backup power.

02:40:11.300 --> 02:40:12.217
<v ->Okay, thank you.</v>

02:40:13.478 --> 02:40:14.311
<v ->You bet.</v>

02:40:15.281 --> 02:40:16.114
<v ->Could you speak a little bit</v>

02:40:16.114 --> 02:40:18.800
to the size of the
mobile home park solar

02:40:18.800 --> 02:40:20.960
and storage systems
that you've installed?

02:40:22.970 --> 02:40:24.743
<v ->That is a good question.</v>

02:40:25.710 --> 02:40:30.400
And I might want to see

02:40:30.400 --> 02:40:34.040
if Brian D'Agostino
was still on the line

02:40:34.040 --> 02:40:38.823
and have a little bit
more information, on-

02:40:40.630 --> 02:40:41.528
<v ->Yeah.</v>

02:40:41.528 --> 02:40:42.443
<v ->Yeah.</v>

02:40:42.443 --> 02:40:43.921
Thanks, Brian.

02:40:43.921 --> 02:40:44.835
<v ->Yeah, absolutely.</v>

02:40:44.835 --> 02:40:45.850
And you know what we went
with is when it comes down

02:40:45.850 --> 02:40:48.860
to the exact size, I would
have to get back to you

02:40:48.860 --> 02:40:51.720
on the exact specs,
but in, with Generac,

02:40:51.720 --> 02:40:54.850
you see here that we
had these generators.

02:40:54.850 --> 02:40:56.130
And really what we focused on

02:40:56.130 --> 02:40:57.900
is not only with the mobile home parks,

02:40:57.900 --> 02:40:59.560
but also with Ramona Elementary,

02:40:59.560 --> 02:41:01.340
Potrero Elementary,

02:41:01.340 --> 02:41:03.690
several of our community
resource centers,

02:41:03.690 --> 02:41:05.860
some very critical water pumps.

02:41:05.860 --> 02:41:08.580
We're finding we're
using Generac battery wall,

02:41:08.580 --> 02:41:10.020
in the particular case of one

02:41:10.020 --> 02:41:13.070
of the highest impact mobile
home parks, which is on one

02:41:13.070 --> 02:41:15.920
of those free impacted circuits,

02:41:15.920 --> 02:41:19.120
it's, we're actually
looking at solar panels

02:41:19.120 --> 02:41:22.850
and two battery walls,
is what it actually took.

02:41:22.850 --> 02:41:24.340
And four years ago

02:41:24.340 --> 02:41:26.270
when we were originally assessing this,

02:41:26.270 --> 02:41:30.460
there was a much bigger
cost differentiator between a lot

02:41:30.460 --> 02:41:32.510
of the generators that
you see in the picture there

02:41:32.510 --> 02:41:36.610
in the battery walls, but
becoming much more cost-effective,

02:41:36.610 --> 02:41:39.540
and it's becoming, it's starting

02:41:39.540 --> 02:41:41.870
to, we're looking at
integration of more and more

02:41:41.870 --> 02:41:45.430
of the battery walls into
this program moving forward

02:41:45.430 --> 02:41:47.063
for numerous reasons,

02:41:48.000 --> 02:41:51.010
but we'll have to get back
to you on the exact size

02:41:51.010 --> 02:41:52.373
of that generator.

02:41:54.290 --> 02:41:55.650
<v ->Appreciated, thank you.</v>

02:41:55.650 --> 02:41:56.483
<v ->Yes.</v>

02:42:03.302 --> 02:42:04.195
<v ->Okay.</v>

02:42:04.195 --> 02:42:05.106
Thanks so much.

02:42:05.106 --> 02:42:06.300
If there aren't any other
questions, I can hand it over

02:42:06.300 --> 02:42:07.173
to Mona Freels.

02:42:11.950 --> 02:42:13.830
<v ->Great, thank you very much.</v>

02:42:13.830 --> 02:42:16.180
And thanks for the
opportunity to present a little bit

02:42:16.180 --> 02:42:18.271
about our lessons learned.

02:42:18.271 --> 02:42:20.540
And some of our team
members integrated some

02:42:20.540 --> 02:42:21.950
of the lessons learned for the season

02:42:21.950 --> 02:42:23.610
throughout the presentation.

02:42:23.610 --> 02:42:25.870
I wanted to share just a
few additional operational

02:42:25.870 --> 02:42:27.600
or logistical lessons learned,

02:42:27.600 --> 02:42:29.650
and maybe expand a
little bit on some of the ones

02:42:29.650 --> 02:42:31.220
that they mentioned.

02:42:31.220 --> 02:42:32.920
Can we get the next slide, please?

02:42:33.920 --> 02:42:35.130
Thank you.

02:42:35.130 --> 02:42:36.430
So one of the things that we looked at

02:42:36.430 --> 02:42:38.480
was really the increased number

02:42:38.480 --> 02:42:42.050
of our new Emergency
Operations Center responders.

02:42:42.050 --> 02:42:45.560
So we have an average of
about a 40% annual attrition rate

02:42:45.560 --> 02:42:47.200
with EOC responders,

02:42:47.200 --> 02:42:50.300
and that is responders
are mobile in terms

02:42:50.300 --> 02:42:52.970
of they may take another
position within the company,

02:42:52.970 --> 02:42:57.460
but no longer provides them
that EOC response opportunity,

02:42:57.460 --> 02:42:59.790
or they may leave the
company, they may retire.

02:42:59.790 --> 02:43:03.870
So for a number of reasons,
we average about 40%.

02:43:03.870 --> 02:43:06.640
And so with the continuous
improvement that we have

02:43:06.640 --> 02:43:08.400
in our Virtual EOC Environment,

02:43:08.400 --> 02:43:11.510
which is currently our
primary EOC response tool

02:43:11.510 --> 02:43:14.400
due to COVID, that training

02:43:14.400 --> 02:43:18.660
is a continuous, ongoing
process that we're looking at,

02:43:18.660 --> 02:43:20.450
and we really have had to diversify

02:43:20.450 --> 02:43:22.140
both the training methodologies

02:43:22.140 --> 02:43:25.490
as well as our delivery
modalities in this virtual world

02:43:25.490 --> 02:43:26.870
that we've been living in.

02:43:26.870 --> 02:43:29.660
So one of the things
that we've done is in 2021,

02:43:29.660 --> 02:43:32.290
we invested in actually developing

02:43:32.290 --> 02:43:34.010
a Training and Exercise Division

02:43:34.010 --> 02:43:35.453
within Emergency Management,

02:43:36.440 --> 02:43:39.350
and we've hired training specialists.

02:43:39.350 --> 02:43:43.350
So FEMA Master Training
and Exercise Practitioners,

02:43:43.350 --> 02:43:48.170
as well as curriculum
instructional practitioners,

02:43:48.170 --> 02:43:52.440
and really what we're hoping
is that by making this a focus

02:43:52.440 --> 02:43:54.020
on training and exercise,

02:43:54.020 --> 02:43:56.300
we can enhance both the development

02:43:56.300 --> 02:44:03.260
of, and the focus on our
training, our exercising,

02:44:03.260 --> 02:44:05.853
as well as the tracking of all of that.

02:44:06.740 --> 02:44:09.840
And so as we lean
towards the credentialing

02:44:09.840 --> 02:44:13.210
for, for some of our EOC responder,

02:44:13.210 --> 02:44:18.210
ensuring that we have that
really formalized as a process.

02:44:18.360 --> 02:44:21.880
Additionally, our Public Safety
Partner Notification System,

02:44:21.880 --> 02:44:25.462
we recognized in the Thanksgiving Event,

02:44:25.462 --> 02:44:27.540
we had a safe-coding issue.

02:44:27.540 --> 02:44:29.410
So we recognized that, or we identified

02:44:29.410 --> 02:44:31.340
that there were eight individuals

02:44:31.340 --> 02:44:34.310
who did not receive
their initial notification.

02:44:34.310 --> 02:44:36.330
And that's not to say
that the organizations

02:44:36.330 --> 02:44:37.650
were not notified,

02:44:37.650 --> 02:44:39.800
it was eight individuals
within organizations.

02:44:39.800 --> 02:44:43.410
So for example, the City of Poway,

02:44:43.410 --> 02:44:45.510
the senior and elected
officials were notified,

02:44:45.510 --> 02:44:47.100
the Fire Chief was notified.

02:44:47.100 --> 02:44:49.260
The one individual,
the Emergency Manager

02:44:49.260 --> 02:44:51.213
did not get their initial notification.

02:44:52.100 --> 02:44:54.420
Because we have great
relationships with our partners,

02:44:54.420 --> 02:44:57.680
she immediately was able
to bring that to our attention.

02:44:57.680 --> 02:45:00.420
We went through with our IT
Department, looked at the flags,

02:45:00.420 --> 02:45:03.403
found eight individuals
that were incorrectly coded,

02:45:04.683 --> 02:45:07.270
and then corrected that
issue and then resent

02:45:07.270 --> 02:45:09.970
those initial communications
to those eight individuals.

02:45:09.970 --> 02:45:12.837
But again, the organizations themselves,

02:45:12.837 --> 02:45:14.710
other individuals were notified.

02:45:14.710 --> 02:45:17.010
We have since looked
at all of our flagging

02:45:17.010 --> 02:45:19.710
within our Public
Safety Partner Database,

02:45:19.710 --> 02:45:21.530
found that the reason for that coding

02:45:21.530 --> 02:45:23.170
was there was a duplicate flag,

02:45:23.170 --> 02:45:26.030
so we deleted the duplicate flags

02:45:26.030 --> 02:45:27.593
for any of our partners.

02:45:28.830 --> 02:45:31.200
So that issue has been remedied.

02:45:31.200 --> 02:45:34.990
The next one was
looking at our caterers.

02:45:34.990 --> 02:45:39.320
And I think Danielle had
mentioned earlier with our AFN

02:45:39.320 --> 02:45:41.000
that on Thanksgiving,
it was very difficult

02:45:41.000 --> 02:45:45.308
for our primary caterer get,
to provide those resources

02:45:45.308 --> 02:45:46.260
that we needed.

02:45:46.260 --> 02:45:48.550
Luckily, our Logistics Department

02:45:48.550 --> 02:45:50.000
and our Supply Diversity teams

02:45:50.000 --> 02:45:51.770
were able to leverage
their relationships

02:45:51.770 --> 02:45:53.530
to fulfill those gaps.

02:45:53.530 --> 02:45:55.090
So ultimately, there was no impact

02:45:55.090 --> 02:45:57.260
to our AFN support programs to ensure

02:45:57.260 --> 02:46:00.700
that they received the
meals that they needed.

02:46:00.700 --> 02:46:02.600
And then lastly, had mentioned,

02:46:02.600 --> 02:46:05.113
the customer notifications
received spam calls.

02:46:06.470 --> 02:46:10.820
And so, often we find the
telco partners don't even know

02:46:10.820 --> 02:46:13.480
that our number has been
flagged in spam in their system.

02:46:13.480 --> 02:46:16.890
So in working with them, we
have, as I mentioned earlier,

02:46:16.890 --> 02:46:19.550
received confirmation from
AT&amp;T that the phone number

02:46:19.550 --> 02:46:22.320
that we use in our auto
dial has been removed

02:46:22.320 --> 02:46:24.205
from their spam filter.

02:46:24.205 --> 02:46:25.420
And we anticipate the same will be true

02:46:25.420 --> 02:46:27.090
for the other carriers as we continue

02:46:27.090 --> 02:46:28.240
to follow up with them.

02:46:29.340 --> 02:46:31.120
Additionally, I wanted
to expand a little bit

02:46:31.120 --> 02:46:34.690
on, Zoraya had mentioned
our Public Safety Partner Portal.

02:46:34.690 --> 02:46:38.540
And so I wanted to talk about
some additional enhancements.

02:46:38.540 --> 02:46:41.490
So we have currently
over 900 registered users

02:46:41.490 --> 02:46:42.323
to our portal.

02:46:43.250 --> 02:46:45.580
Some enhancements that
we've already put into place

02:46:45.580 --> 02:46:50.500
since Thanksgiving
is our a portal lists all

02:46:50.500 --> 02:46:52.660
of the communities
that are either potentially

02:46:52.660 --> 02:46:54.360
or currently impacted.

02:46:54.360 --> 02:46:56.280
For each one of those communities now,

02:46:56.280 --> 02:47:00.090
we do have a color kind
of a slide bar next to it

02:47:00.090 --> 02:47:03.400
that has a color indicator
and a percentage in terms

02:47:03.400 --> 02:47:07.010
of what percentage of
that community is impacted

02:47:07.010 --> 02:47:09.040
or potentially impacted,

02:47:09.040 --> 02:47:11.780
and then can click on that
community and it drops down

02:47:11.780 --> 02:47:14.820
and it'll bring you all of
the sectionalizing devices

02:47:14.820 --> 02:47:18.180
that are within that community
and their current status.

02:47:18.180 --> 02:47:20.730
So that's a feature that we
heard from our focus group

02:47:20.730 --> 02:47:22.880
of partners that would
be helpful for them.

02:47:23.822 --> 02:47:24.980
So that enhancement
has already been created

02:47:24.980 --> 02:47:26.500
and is in place.

02:47:26.500 --> 02:47:30.050
Future enhancements
for our portal in 2022.

02:47:30.050 --> 02:47:32.920
Next week, we will be
reengaging the original focus group

02:47:32.920 --> 02:47:36.690
that we put together
for the portal to figure out

02:47:36.690 --> 02:47:40.420
what additional functionality
they think would be usable.

02:47:40.420 --> 02:47:42.780
The one thing that we
have heard from our partners

02:47:42.780 --> 02:47:44.697
is that they want the portal to have

02:47:44.697 --> 02:47:47.640
the better functionality
out in the field.

02:47:47.640 --> 02:47:50.600
So with that, in addition
to the web-based portal,

02:47:50.600 --> 02:47:53.760
we are adding a
mobile-based, a mobile app,

02:47:53.760 --> 02:47:55.520
and that mobile app
will give us the ability

02:47:55.520 --> 02:47:57.010
to do push notifications.

02:47:57.010 --> 02:47:59.380
So one of the things that
we heard from our partners

02:47:59.380 --> 02:48:03.990
was that during off hours,
whether it's weekends

02:48:03.990 --> 02:48:05.610
or after hours, that they
don't always have access

02:48:05.610 --> 02:48:08.560
to their work email on
their mobile devices.

02:48:08.560 --> 02:48:11.750
And so sometimes the
notifications that we you're sending,

02:48:11.750 --> 02:48:14.108
they're not receiving until the next day

02:48:14.108 --> 02:48:15.010
when they're in the office.

02:48:15.010 --> 02:48:19.050
So with having a push
notification on a mobile app,

02:48:19.050 --> 02:48:20.270
they will always have that ability

02:48:20.270 --> 02:48:23.630
to get those notifications
realtime when we send them.

02:48:23.630 --> 02:48:25.820
So that is currently in process now

02:48:25.820 --> 02:48:27.713
and will be in place later this year.

02:48:29.140 --> 02:48:30.790
With that, are there any questions

02:48:30.790 --> 02:48:32.410
regarding either of the lessons learned

02:48:32.410 --> 02:48:34.210
or our Public Safety Partner Portal?

02:48:40.513 --> 02:48:41.346
Okay.

02:48:41.346 --> 02:48:42.450
Seeing no questions,

02:48:42.450 --> 02:48:43.630
I'm gonna turn it over to
Jonathan Woldemariam,

02:48:43.630 --> 02:48:46.180
the Director of our Wildfire
Mitigation Department.

02:48:50.770 --> 02:48:51.603
<v ->Thank you, Mona.</v>

02:48:51.603 --> 02:48:52.730
Good afternoon.

02:48:52.730 --> 02:48:53.563
It's good to be here,

02:48:53.563 --> 02:48:55.990
and we'll start with
the next slide, please,

02:48:55.990 --> 02:48:58.163
and talk about our Microgrid Program.

02:48:59.040 --> 02:49:04.040
We have had the chance
to use our micro grids course

02:49:04.360 --> 02:49:06.960
in 2020, where we have four sites,

02:49:06.960 --> 02:49:11.960
mostly desert communities
in our Eastern County areas.

02:49:13.290 --> 02:49:18.290
We deployed the microgrids
in 2020 in Shelter Valley

02:49:18.430 --> 02:49:20.580
and in Butterfield Ranch,

02:49:20.580 --> 02:49:23.180
which are remote desert communities

02:49:23.180 --> 02:49:24.540
using conventional generators,

02:49:24.540 --> 02:49:28.620
and we have the same
opportunity to use those microgrids

02:49:28.620 --> 02:49:32.450
in 2021 during the
Thanksgiving PSPS Event,

02:49:32.450 --> 02:49:36.000
that affected around 400
customers that we were able

02:49:36.000 --> 02:49:40.910
to reduce the impacts of
PSPS in those two areas.

02:49:40.910 --> 02:49:44.900
We also have used the microgrids

02:49:44.900 --> 02:49:47.150
in the Ramona Air Attack Base,

02:49:47.150 --> 02:49:51.410
which is a critical airport
and has been used

02:49:51.410 --> 02:49:55.570
by Cal Fire every year
for the air attack missions

02:49:55.570 --> 02:49:57.110
when fires occur.

02:49:57.110 --> 02:50:01.460
And so we have used
that as our microgrid also.

02:50:01.460 --> 02:50:05.080
And then Cameron Corners is
a Eastern part of our community

02:50:05.080 --> 02:50:09.180
where we have used
the microgrid to power up

02:50:09.180 --> 02:50:13.030
some critical infrastructure,
like a Cal Fire Station,

02:50:13.030 --> 02:50:16.000
like the medical station,

02:50:16.000 --> 02:50:19.230
that medical hospital that's there,

02:50:19.230 --> 02:50:21.530
and as well as some convenience stores

02:50:21.530 --> 02:50:23.610
and the Border Patrol Station.

02:50:23.610 --> 02:50:27.460
And so all these critical
facilities are powered up

02:50:27.460 --> 02:50:29.690
by a microgrid during PSPS events.

02:50:29.690 --> 02:50:32.860
Now, all of these have been deployed

02:50:32.860 --> 02:50:34.610
using conventional generators,

02:50:34.610 --> 02:50:38.830
but our focus in 2021 was
to try and start to transition

02:50:38.830 --> 02:50:40.910
over to renewable solutions.

02:50:40.910 --> 02:50:43.540
And so, especially with
the Ramona Air Attack Base,

02:50:43.540 --> 02:50:46.600
we were busy installing energy storage,

02:50:46.600 --> 02:50:49.030
going away from a
conventional generator,

02:50:49.030 --> 02:50:53.580
and we have completed
that in January of this year

02:50:53.580 --> 02:50:57.650
with that being Commissioned
at the end of January.

02:50:57.650 --> 02:51:00.000
For the Cameron Corners,
it will be completed,

02:51:00.000 --> 02:51:03.059
the transition from the
conventional generator

02:51:03.059 --> 02:51:06.090
and putting in solar and energy storage,

02:51:06.090 --> 02:51:07.910
that transition will be
completed by the end

02:51:07.910 --> 02:51:12.360
of this quarter, this 2022
quarter by end of March.

02:51:12.360 --> 02:51:15.050
That top left picture
is actually a picture

02:51:15.050 --> 02:51:18.350
of Cameron Corners with the
solar panels that you see there.

02:51:18.350 --> 02:51:22.320
And as you continue down the
solar panels towards the North

02:51:22.320 --> 02:51:25.457
of that picture is where
the batteries will go.

02:51:25.457 --> 02:51:27.070
And it's a different battery

02:51:27.070 --> 02:51:29.060
from the normal lithium batteries.

02:51:29.060 --> 02:51:30.950
It's a iron flow battery.

02:51:30.950 --> 02:51:35.340
And this particular battery
that we're using is the first

02:51:35.340 --> 02:51:38.420
of its kind that's been
commercially deployed.

02:51:38.420 --> 02:51:41.600
We do have experience with
flow batteries that we have used

02:51:41.600 --> 02:51:44.890
in our service territory with
a vanadium redox battery

02:51:44.890 --> 02:51:46.630
outside of the HFTD.

02:51:46.630 --> 02:51:50.170
So this was a next generation,
if you will, of technology

02:51:50.170 --> 02:51:51.662
that we're using

02:51:51.662 --> 02:51:54.160
to help our customers
mitigate against PSPS.

02:51:54.160 --> 02:51:57.740
In 2022, we plan on
finishing our deployment

02:51:57.740 --> 02:52:01.620
of and the Commissioning
of our renewable solutions,

02:52:01.620 --> 02:52:05.510
and also continuing that
effort in Butterfield Ranch

02:52:05.510 --> 02:52:07.560
and Shelter Valley, those two sites,

02:52:07.560 --> 02:52:09.250
desert sites that I talked about

02:52:09.250 --> 02:52:11.570
that have about 400
customers that can benefit

02:52:11.570 --> 02:52:14.440
from the microgrid, and
they have been using

02:52:14.440 --> 02:52:17.520
our conventional generator,
now we're going to transition

02:52:17.520 --> 02:52:19.850
over to solar and energy storage.

02:52:19.850 --> 02:52:23.650
And so we are exploring
other solutions as well.

02:52:23.650 --> 02:52:26.450
That bottom left Corner
here on the picture,

02:52:26.450 --> 02:52:30.550
what you see there is a
mobile energy storage device

02:52:30.550 --> 02:52:33.992
that we used in 2021 during
the Thanksgiving PSPS.

02:52:33.992 --> 02:52:36.260
And one of the areas we're using it

02:52:36.260 --> 02:52:40.010
is at Feed America Station
to keep the food there

02:52:40.010 --> 02:52:42.170
for emergency purposes refrigerated,

02:52:42.170 --> 02:52:44.700
as well as in one of our
community resource centers

02:52:44.700 --> 02:52:49.160
where we do deployed this
portable energy storage unit.

02:52:49.160 --> 02:52:51.330
And so we're leveraging technology

02:52:51.330 --> 02:52:53.210
and continue to do that.

02:52:53.210 --> 02:52:54.530
And we are planning

02:52:54.530 --> 02:52:56.670
on using these mobile
energy storage units

02:52:57.690 --> 02:52:59.870
also for EV charging
out in the HFTD areas

02:52:59.870 --> 02:53:03.320
where customers are, so
customers are able to charge

02:53:03.320 --> 02:53:05.953
their batteries on their vehicles.

02:53:08.149 --> 02:53:10.930
So with that, I'll pause and
see if there's any questions.

02:53:12.457 --> 02:53:14.510
<v ->Hi, Jon, this is Caroline.</v>

02:53:14.510 --> 02:53:16.320
Quick question on the
Cameron Corner is I know

02:53:16.320 --> 02:53:20.051
that the battery, I think
for our last conversation,

02:53:20.051 --> 02:53:22.710
it was a supply chain issue
and back-ordered, correct?

02:53:22.710 --> 02:53:25.040
'Cause some of the global slide issues

02:53:25.040 --> 02:53:28.222
is do you have a
target date now for that?

02:53:28.222 --> 02:53:29.160
'Cause I know it says for 2022 planning,

02:53:29.160 --> 02:53:31.480
but do you have some timeframe?

02:53:31.480 --> 02:53:33.730
<v ->Yeah, it's actually
been fully delivered.</v>

02:53:33.730 --> 02:53:36.160
So yes, you're right,
Caroline, there was a delay,

02:53:36.160 --> 02:53:39.350
and that's why we were
unable to complete that in 2021,

02:53:39.350 --> 02:53:41.350
but now it's been fully
delivered in January

02:53:41.350 --> 02:53:44.730
and we've been busy
setting it up and installing it,

02:53:44.730 --> 02:53:48.763
and so we will see that
Commissioned here mid-March.

02:53:50.530 --> 02:53:51.363
<v ->Great.</v>

02:53:52.908 --> 02:53:55.220
<v ->I got a question on
the mobile EV charging</v>

02:53:55.220 --> 02:53:56.970
at your community resource centers,

02:53:58.061 --> 02:53:58.958
and I suppose also

02:53:58.958 --> 02:54:00.783
with your mobile battery
energy storage units.

02:54:02.070 --> 02:54:05.583
I'm curious, what sort of
prompted that kind of service?

02:54:07.256 --> 02:54:08.510
Are you hearing from a lot of
customers who are concerned

02:54:08.510 --> 02:54:13.510
about TV charging in PSPS
events or other outages?

02:54:13.730 --> 02:54:15.240
And then kind of as a, I apologize

02:54:15.240 --> 02:54:20.240
for the compound question,
but how do you balance investing

02:54:20.540 --> 02:54:23.760
in that kind of service for customers

02:54:23.760 --> 02:54:25.980
versus additional batteries

02:54:25.980 --> 02:54:28.310
for Medical Baseline customers or others

02:54:28.310 --> 02:54:29.913
who may need medical equipment?

02:54:32.530 --> 02:54:33.920
<v ->Yeah.</v>

02:54:33.920 --> 02:54:36.530
So we are trying to
balance the different needs

02:54:36.530 --> 02:54:38.235
of customers, right?

02:54:38.235 --> 02:54:39.530
And that's a very good question

02:54:39.530 --> 02:54:43.303
with the the mobile energy storage unit.

02:54:43.303 --> 02:54:45.403
Why do we go with that technology?

02:54:45.403 --> 02:54:46.270
Why do we select that service?

02:54:46.270 --> 02:54:48.760
Part of it was what was
brought up in discussions

02:54:48.760 --> 02:54:53.083
during the PSPS, from the
Commission, from CPUC.

02:54:53.083 --> 02:54:58.080
The other part of it was just
hearing from customers, right?

02:54:58.080 --> 02:55:00.160
That aren't able to use their vehicles

02:55:00.160 --> 02:55:02.040
during these PSPS events.

02:55:02.040 --> 02:55:05.810
So we're trying to
balance the deployment

02:55:05.810 --> 02:55:09.950
of more battery solutions,
portable battery solutions

02:55:09.950 --> 02:55:11.590
to customers of Medical Baseline.

02:55:11.590 --> 02:55:13.170
And we definitely
will continue with that,

02:55:13.170 --> 02:55:18.170
and we have quite a
fixed program for that,

02:55:18.380 --> 02:55:21.337
but we were also trying
to at the same time kind

02:55:21.337 --> 02:55:23.500
of balance it out with,
okay, are other needs

02:55:23.500 --> 02:55:26.873
that customers have and,
and trying to match that as well.

02:55:32.520 --> 02:55:34.100
<v ->Jonathan, while
we're on this topic,</v>

02:55:34.100 --> 02:55:35.970
if I could please
follow up on a question

02:55:35.970 --> 02:55:39.340
that was asked earlier
regarding the size

02:55:39.340 --> 02:55:43.460
of the battery walls at the
Heavenly Oaks Mobile Home Park,

02:55:43.460 --> 02:55:44.810
we did get that information.

02:55:44.810 --> 02:55:49.440
It is two 17.1 kilowatt
hour battery walls.

02:55:49.440 --> 02:55:53.320
So it looks like 34.2
kilowatt hours altogether.

02:55:53.320 --> 02:55:55.630
And then there are 36 rooftop panels

02:55:55.630 --> 02:55:57.800
that are feeding those battery walls.

02:55:57.800 --> 02:55:59.630
And there's about 100 sites.

02:55:59.630 --> 02:56:03.880
So it's about 100 folks
that now have kind

02:56:03.880 --> 02:56:07.860
of a devoted, fully
energy-resilient clubhouse there

02:56:07.860 --> 02:56:09.323
at that mobile home park.

02:56:11.619 --> 02:56:12.519
<v ->Great.</v>

02:56:12.519 --> 02:56:13.352
Thanks for your speedy follow-up.

02:56:17.330 --> 02:56:18.310
<v ->Okay.</v>

02:56:18.310 --> 02:56:19.886
Thank you for the questions.

02:56:19.886 --> 02:56:20.719
Well, if there are no more,

02:56:20.719 --> 02:56:22.850
we'll go forward to our next slide,

02:56:22.850 --> 02:56:27.850
and we'll talk about our
progress in the mitigations

02:56:28.480 --> 02:56:31.740
in terms of the grid-hardening
programs that we have

02:56:31.740 --> 02:56:35.723
as well as the inspections
and some of the things

02:56:35.723 --> 02:56:38.153
around situation awareness,

02:56:38.153 --> 02:56:40.575
so some general progress report here.

02:56:40.575 --> 02:56:42.570
I wanna start on the
top left and just orient you

02:56:42.570 --> 02:56:45.410
with this slide, that the first box

02:56:45.410 --> 02:56:48.610
you see there on the
left is the 2022 target.

02:56:48.610 --> 02:56:52.680
So 65 miles for undergrounding,
for example, for 2022.

02:56:52.680 --> 02:56:57.150
In the middle is our 2021
progress, almost 26 miles

02:56:57.150 --> 02:56:59.860
of the 25 targeted for 2021.

02:56:59.860 --> 02:57:04.670
And then the 56 miles is what
we installed over two years

02:57:04.670 --> 02:57:09.670
with the WP cycles, so 2020
plus 2021 gives us the 56 miles.

02:57:10.460 --> 02:57:12.840
And that's how the whole slide tracks

02:57:12.840 --> 02:57:15.240
throughout the different initiatives.

02:57:15.240 --> 02:57:16.970
For example, the covered conductor,

02:57:16.970 --> 02:57:20.950
we're targeting 60 miles
this year and 21 miles

02:57:20.950 --> 02:57:25.810
that were completed last year,
and then 22.5 miles overall,

02:57:25.810 --> 02:57:28.390
the two that we completed.

02:57:28.390 --> 02:57:31.790
And when we are
looking at these programs,

02:57:31.790 --> 02:57:35.270
we are really also not just
considering the wildfire risk,

02:57:35.270 --> 02:57:38.720
but also addressing areas
that have the high frequency

02:57:38.720 --> 02:57:42.640
of PSPS so that we are trying to balance

02:57:42.640 --> 02:57:43.890
the two risks, right?

02:57:43.890 --> 02:57:46.480
The wildfire and the PSPS risk.

02:57:46.480 --> 02:57:48.610
And I'm gonna talk a
little bit about that as we go

02:57:48.610 --> 02:57:51.300
into the following
slides, but not just yet

02:57:51.300 --> 02:57:53.960
because we'll both talk about some

02:57:53.960 --> 02:57:58.680
of these additional targets and
how we do the risk modeling.

02:57:58.680 --> 02:58:01.840
We, I wanted to just
move over to the next,

02:58:01.840 --> 02:58:03.930
to the right of this slide here,

02:58:03.930 --> 02:58:06.130
where we have the situational awareness.

02:58:06.130 --> 02:58:09.010
We continue to improve,
as Brian talked about,

02:58:09.010 --> 02:58:12.900
our insulation, not just of
additional weather stations,

02:58:12.900 --> 02:58:15.000
but also enhancing
those weather stations

02:58:15.000 --> 02:58:18.560
with various capabilities, right?

02:58:18.560 --> 02:58:21.890
The 30-second reads, as
well as the field moisture reads

02:58:21.890 --> 02:58:25.730
and having that additional
technology with that.

02:58:25.730 --> 02:58:27.750
With the aerial fire suppression,

02:58:27.750 --> 02:58:31.510
we just wanted to share
how much has been dropped

02:58:31.510 --> 02:58:35.080
right during the
efforts for fighting fires.

02:58:35.080 --> 02:58:37.900
So the total of 1.6
million over two years,

02:58:37.900 --> 02:58:42.690
and then the 793,000 gallons
of water dropped in 2021.

02:58:42.690 --> 02:58:47.690
So our aerial fleet is really
going to work and helping out

02:58:48.330 --> 02:58:50.150
in the community here.

02:58:50.150 --> 02:58:51.880
I'll talk about the inspections now.

02:58:51.880 --> 02:58:54.917
The three that I'm gonna talk about

02:58:54.917 --> 02:58:55.830
are the enhanced vegetation management,

02:58:55.830 --> 02:58:57.210
the distribution inspections

02:58:57.210 --> 02:58:59.140
and the transmission inspections.

02:58:59.140 --> 02:59:04.140
The enhanced vegetation
management is going above and beyond

02:59:04.280 --> 02:59:08.160
our regular inspections
and vegetation management.

02:59:08.160 --> 02:59:09.670
So for our regular inspections,

02:59:09.670 --> 02:59:14.460
we have over 460,000 trees
that we manage every year.

02:59:14.460 --> 02:59:17.370
We inspect them, and
then we are trimming

02:59:18.906 --> 02:59:20.950
up to 12 feet, 10 to 12
feet for our clearance

02:59:20.950 --> 02:59:22.250
away from the power lines.

02:59:23.140 --> 02:59:28.140
So we are meeting 100% of
our compliance and doing that

02:59:29.502 --> 02:59:30.370
on an annual basis.

02:59:30.370 --> 02:59:33.400
In addition, in the HFTD,
we go in and inspect

02:59:33.400 --> 02:59:35.553
an additional time.

02:59:35.553 --> 02:59:39.390
So twice a year in the
HFTD, over 250,000 trees,

02:59:39.390 --> 02:59:41.070
and every one of those meet

02:59:41.070 --> 02:59:43.110
the compliance requirements, right?

02:59:43.110 --> 02:59:45.610
We're trimming those back 10 to 12 feet.

02:59:45.610 --> 02:59:46.950
Now, what we did though

02:59:46.950 --> 02:59:49.330
with the enhanced vegetation
management a couple years ago

02:59:49.330 --> 02:59:54.330
is started looking at five
targeted species and looking,

02:59:54.920 --> 02:59:57.170
doing a more enhanced clearance.

02:59:57.170 --> 03:00:01.120
So going up to 25 feet
of additional clearance.

03:00:01.120 --> 03:00:06.120
So we started with the
target of 83,000 trees,

03:00:06.621 --> 03:00:08.970
and that's based on
the targeted species,

03:00:08.970 --> 03:00:13.650
and we thought we could
do 17,000 of these each year

03:00:13.650 --> 03:00:16.220
based on just the population,
based on understanding

03:00:16.220 --> 03:00:19.750
of how many trees would need
that 25-foot clearance, right?

03:00:19.750 --> 03:00:22.530
That additional clearance up to 25 feet.

03:00:22.530 --> 03:00:27.530
But what we found as we
learned from experience by 2020

03:00:27.570 --> 03:00:31.380
and 2021 is that we really
weren't getting 17,000 trees

03:00:31.380 --> 03:00:32.440
that needed that.

03:00:32.440 --> 03:00:36.270
We were only found 12,500
trees in 2021 that needed

03:00:36.270 --> 03:00:39.230
to be trimmed up to that level.

03:00:39.230 --> 03:00:41.040
So that's why you see

03:00:41.040 --> 03:00:44.260
that we didn't take it all
the way up to our target,

03:00:44.260 --> 03:00:46.580
but we did meet the
full compliance there

03:00:46.580 --> 03:00:49.283
that we wanted to in
terms of what was targeted.

03:00:50.370 --> 03:00:52.530
And then in our distribution inspection,

03:00:52.530 --> 03:00:57.530
similarly in 2021, we
had 168,000 inspections

03:00:58.210 --> 03:01:03.210
of the 169, and we fully met
our compliance inspections.

03:01:03.240 --> 03:01:06.060
So what we're doing here is
taking all of our inspections,

03:01:06.060 --> 03:01:08.720
that drone inspections, the
infrared inspections, right?

03:01:08.720 --> 03:01:11.780
The additional patrols
and aerial helicopter patrols

03:01:11.780 --> 03:01:12.760
that we do.

03:01:12.760 --> 03:01:14.360
And so taking all of that combined

03:01:14.360 --> 03:01:16.219
is what we're showing here.

03:01:16.219 --> 03:01:18.490
And we ran into a
problem on the inspection

03:01:18.490 --> 03:01:21.660
on distribution, where property
owners weren't as willing

03:01:21.660 --> 03:01:24.370
to give us access in certain areas.

03:01:24.370 --> 03:01:27.450
So we, that's why you
see we didn't quite reach

03:01:28.544 --> 03:01:29.440
the 169,000 that we targeted,

03:01:29.440 --> 03:01:32.730
but in terms of overall
compliance of inspections,

03:01:32.730 --> 03:01:36.460
we've met that 100%.

03:01:36.460 --> 03:01:38.050
Same with the transmission.

03:01:38.050 --> 03:01:41.800
We've really met our
compliance inspections.

03:01:41.800 --> 03:01:45.147
The reason why you see a
difference between the 17,000

03:01:45.147 --> 03:01:47.970
and the 19,000 is really
the newer inspections

03:01:47.970 --> 03:01:49.490
that we started with the program.

03:01:49.490 --> 03:01:53.250
So just zeroing on the
what's that right total

03:01:53.250 --> 03:01:55.150
for infrared inspections that we can do

03:01:55.150 --> 03:01:59.270
as well as the drone
assessments and our aerial patrol?

03:01:59.270 --> 03:02:02.020
So that's why there's
a little bit of a lag there,

03:02:02.020 --> 03:02:04.803
but we've met all the
compliance inspections.

03:02:06.530 --> 03:02:07.940
I'll pause there for questions,

03:02:07.940 --> 03:02:11.990
and before we transition
over to the next slide,

03:02:11.990 --> 03:02:12.953
which is the risk modeling.

03:02:16.160 --> 03:02:17.810
Okay, we'll go to risk
modeling now and talk

03:02:17.810 --> 03:02:21.680
about how we have advanced the program

03:02:21.680 --> 03:02:26.350
around how we view risk,
and really in 2020 and 2021,

03:02:26.350 --> 03:02:28.470
we worked really hard to advance

03:02:28.470 --> 03:02:31.020
our risk-modeling
capabilities by not just looking

03:02:31.020 --> 03:02:33.790
at wildfire risk, but
looking at PSPS risk.

03:02:33.790 --> 03:02:36.860
And that was for, on
the left, the grid planning

03:02:36.860 --> 03:02:40.380
or the how we select our
grid-hardening solutions.

03:02:40.380 --> 03:02:43.200
Power conductive versus
undergrounding versus generators.

03:02:43.200 --> 03:02:46.150
And so we look at a
variety of things, right?

03:02:46.150 --> 03:02:48.400
When we think about wildfire risk,

03:02:48.400 --> 03:02:50.730
it's the likelihood and consequence.

03:02:50.730 --> 03:02:53.860
So a lot of the inputs that
go in there around weather

03:02:53.860 --> 03:02:57.559
and around the assets
and what vegetation

03:02:57.559 --> 03:03:01.060
we might come across on the
various segments of circuits,

03:03:01.060 --> 03:03:03.940
but we do the same
on a PSPS side, right?

03:03:03.940 --> 03:03:07.210
We have the types of
customers and how much,

03:03:07.210 --> 03:03:10.310
how frequently they can
be impacted from PSPS,

03:03:10.310 --> 03:03:11.740
and put that in the model.

03:03:11.740 --> 03:03:13.500
So when we're looking at mitigations,

03:03:13.500 --> 03:03:15.740
we're weighing the wildfire risk score

03:03:16.633 --> 03:03:18.280
as well as the PSPS risk score,

03:03:18.280 --> 03:03:19.740
so that we're looking at both

03:03:19.740 --> 03:03:21.980
when we're implementing mitigations.

03:03:21.980 --> 03:03:26.140
And in 2021, we really
stepped up our risk modeling

03:03:26.140 --> 03:03:28.500
so that we automated more.

03:03:28.500 --> 03:03:31.160
We also made it more
granular where we identified

03:03:31.160 --> 03:03:33.630
a circuit risk index
that we actually put

03:03:33.630 --> 03:03:38.410
in our PSPS dashboard
for that additional knowledge

03:03:38.410 --> 03:03:40.430
and having that situational awareness

03:03:41.429 --> 03:03:42.780
of what our circuit
segments were risk is.

03:03:42.780 --> 03:03:44.370
Right?

03:03:44.370 --> 03:03:47.259
And that includes the type
of a assets that we have

03:03:47.259 --> 03:03:48.800
in that particular segment,
like the conductor size,

03:03:48.800 --> 03:03:53.070
as well as the the
vegetation amount, right?

03:03:53.070 --> 03:03:54.180
So how many trees,

03:03:54.180 --> 03:03:57.228
how many, what's the
tree strike potential?

03:03:57.228 --> 03:03:58.061
And so on.

03:03:58.061 --> 03:04:00.240
And so now we're
moving towards even more,

03:04:00.240 --> 03:04:01.853
we started a little bit in 2021,

03:04:03.017 --> 03:04:04.130
but migrating to the Cloud and enhancing

03:04:04.130 --> 03:04:06.520
our modeling capabilities.

03:04:06.520 --> 03:04:07.820
On the right there though,

03:04:08.800 --> 03:04:10.680
I do wanna highlight the
fact that we also used WNGS,

03:04:10.680 --> 03:04:14.724
which is our Wildfire Next
Generation System, right?

03:04:14.724 --> 03:04:15.623
The same risk model,

03:04:15.623 --> 03:04:17.630
but we created the operational
model that we are going

03:04:17.630 --> 03:04:22.080
to use in more of a planning
and a decision-making criteria

03:04:22.080 --> 03:04:26.450
for PSPS so that we're gonna
be able to use that same type

03:04:26.450 --> 03:04:29.450
of knowledge or that same
type of data that we're leveraging

03:04:29.450 --> 03:04:33.050
for planning for operations
in that we're going to be able

03:04:33.050 --> 03:04:37.220
to look at wildfire risk and
PSPS risk and use that as one

03:04:37.220 --> 03:04:41.180
of the inputs for our officers in charge

03:04:41.180 --> 03:04:42.900
that are in the LSE making decisions

03:04:42.900 --> 03:04:45.600
on whether we should
shut off power or not.

03:04:45.600 --> 03:04:48.610
This is gonna be an
additional tool to everything else

03:04:48.610 --> 03:04:50.037
that we use.

03:04:50.037 --> 03:04:51.219
Right?

03:04:51.219 --> 03:04:53.140
The we use the field input,
we use the wind speeds, right?

03:04:53.140 --> 03:04:54.974
We use the weather data,

03:04:54.974 --> 03:04:57.260
but we also are going to
use the risk modeling here

03:04:57.260 --> 03:05:01.170
to understand what is that
impact that we're gonna have

03:05:01.170 --> 03:05:03.280
when we're making that
decision of wildfire risk

03:05:03.280 --> 03:05:06.003
versus PSPS risk for PSPS events?

03:05:07.130 --> 03:05:11.033
So I'll pause there for any
questions before we move on.

03:05:13.833 --> 03:05:14.950
<v ->Can I ask you a question?</v>

03:05:14.950 --> 03:05:17.773
Is the tree strike?

03:05:19.340 --> 03:05:22.767
I can't quite read
the, is the tree strike.

03:05:26.570 --> 03:05:27.570
<v ->Potential, mm-hmm?</v>

03:05:29.956 --> 03:05:31.820
<v ->Is tree strike potential,
sorry, I can't see,</v>

03:05:31.820 --> 03:05:35.897
is that comparable to
the PG&amp;E overstrike pool

03:05:37.500 --> 03:05:41.193
or the overstrike input
that PG&amp;E is now using,

03:05:42.082 --> 03:05:44.433
and they talked about a couple days ago?

03:05:45.830 --> 03:05:47.453
<v ->Yes, it is comparable to that.</v>

03:05:48.955 --> 03:05:51.039
<v ->And did, is that
something you had?</v>

03:05:51.039 --> 03:05:54.132
'Cause they're implementing
it just the past year or two.

03:05:54.132 --> 03:05:57.900
Is that something SDG&amp;E
had done historically,

03:05:57.900 --> 03:06:01.690
or are you, is that a
new input for you in terms

03:06:01.690 --> 03:06:03.003
of assessing risk?

03:06:04.600 --> 03:06:07.140
<v ->We, yeah, we've
used it in the field.</v>

03:06:07.140 --> 03:06:08.596
Right?

03:06:08.596 --> 03:06:09.980
We do, as part of our vegetation
management inspections

03:06:09.980 --> 03:06:11.820
in the field, we've always looked

03:06:11.820 --> 03:06:13.520
at the tree strike potential,

03:06:13.520 --> 03:06:16.970
and we looked at as part
of our inspections, right?

03:06:16.970 --> 03:06:20.060
Beyond just how close is
the tree to the power line,

03:06:20.060 --> 03:06:21.780
but even if the tree is away,

03:06:21.780 --> 03:06:25.700
what's that potential for the
tree to fall or a tree branch

03:06:25.700 --> 03:06:27.350
to break off and strike the line?

03:06:28.235 --> 03:06:29.200
So we've always had that in the field,

03:06:29.200 --> 03:06:32.680
but now we're implementing
it into our models.

03:06:32.680 --> 03:06:34.760
And we started with
a vegetation risk index

03:06:34.760 --> 03:06:39.760
over two years ago, which
told us the historical impact,

03:06:39.960 --> 03:06:42.470
the outages historically from tree,

03:06:42.470 --> 03:06:47.470
but also the various
indications that we have

03:06:47.820 --> 03:06:50.200
at our database, the tree growth rate,

03:06:50.200 --> 03:06:54.280
the amount of
tree-trimming that we've done

03:06:54.280 --> 03:06:56.470
in the past, historically,
all of that was put

03:06:56.470 --> 03:06:58.040
into our vegetation risk index.

03:06:58.040 --> 03:07:01.700
Now we're including a tree
strike potential into our models,

03:07:01.700 --> 03:07:03.843
which is a little bit more enhanced.

03:07:06.010 --> 03:07:08.070
Hopefully I answered your question.

03:07:08.070 --> 03:07:08.993
<v ->Yeah, thank you.</v>

03:07:12.810 --> 03:07:14.178
<v ->Okay.</v>

03:07:14.178 --> 03:07:16.130
With that, we'll move
over to our next slide,

03:07:16.130 --> 03:07:20.030
and we're gonna talk
about the PSPS mitigations

03:07:20.030 --> 03:07:22.473
that we've been able to achieve here.

03:07:24.086 --> 03:07:26.070
We know that, I've talked

03:07:26.070 --> 03:07:29.520
about all the inspections,
all the grid enhancements

03:07:29.520 --> 03:07:33.050
that we did, but we also
specifically put an effort

03:07:33.050 --> 03:07:37.580
into the PSPS mitigations
and looking at how much,

03:07:37.580 --> 03:07:41.070
how many of the customers
could benefit from that?

03:07:41.070 --> 03:07:45.610
So in 2020, we, for example
in the PSPS sectionalizing,

03:07:45.610 --> 03:07:49.892
and these are switches,
we add into our grid system,

03:07:49.892 --> 03:07:53.420
into our circuits to reduce
the scope of the outages

03:07:53.420 --> 03:07:56.400
or the scope of the shutoff
that impacts customers,

03:07:56.400 --> 03:07:57.740
because by installing the switches,

03:07:57.740 --> 03:08:02.680
we can really segment
what customers are impacted.

03:08:02.680 --> 03:08:06.230
So in 2020, we installed 23 switches,

03:08:06.230 --> 03:08:09.040
and we were able to reduce impacts

03:08:09.040 --> 03:08:11.180
to over 12,000 customers.

03:08:11.180 --> 03:08:14.960
And then the way the
tables read is in 2021

03:08:14.960 --> 03:08:19.330
was an additional 9,700
as a result of 11 switches

03:08:19.330 --> 03:08:20.310
that we added.

03:08:20.310 --> 03:08:23.740
And then 10 more switches is
what we're gonna add in 2022

03:08:23.740 --> 03:08:25.700
to get over 4,600 customers

03:08:25.700 --> 03:08:29.070
in addition to what
we were able to benefit

03:08:29.070 --> 03:08:31.020
in 2021 and 2020.

03:08:31.020 --> 03:08:33.373
So that's how the chart goes,

03:08:34.358 --> 03:08:35.200
and with strategic undergrounding,

03:08:35.200 --> 03:08:36.680
that's what we're doing as well, right?

03:08:36.680 --> 03:08:39.630
Is the 15 miles helped us

03:08:39.630 --> 03:08:43.580
to achieve benefits to 276 customers,

03:08:43.580 --> 03:08:45.679
and then so on, right?

03:08:45.679 --> 03:08:48.438
65 miles, we're gonna
be able to help customers

03:08:48.438 --> 03:08:53.438
that mitigate against
for over 2,500 customers.

03:08:53.709 --> 03:08:56.710
So with microgrids, it's similar, right?

03:08:56.710 --> 03:08:58.733
We're going to be able to have the same.

03:08:59.686 --> 03:09:00.970
And there's an error in
our slide here, in 2020,

03:09:00.970 --> 03:09:05.010
we actually were able to
mitigate for 578 customers

03:09:05.010 --> 03:09:06.463
using six microgrids,

03:09:07.314 --> 03:09:10.130
and the reason why we chose zero in 2021

03:09:10.130 --> 03:09:12.470
is because we're really
working and focused

03:09:12.470 --> 03:09:15.410
on changing those microgrids,

03:09:15.410 --> 03:09:17.720
four of those, to
renewable solutions, right?

03:09:17.720 --> 03:09:21.117
So we're not adding any
new in 2021, but in 2022,

03:09:21.117 --> 03:09:23.567
we'll see some new additions.

03:09:23.567 --> 03:09:26.090
It's the same with the
generator programs.

03:09:26.090 --> 03:09:29.630
We talked about how we were
able to help mitigate customers

03:09:29.630 --> 03:09:32.430
by helping them ride
through these events.

03:09:32.430 --> 03:09:37.230
And so the totals are up on
top, over 39,500 customers

03:09:37.230 --> 03:09:39.010
that have benefited right?

03:09:39.010 --> 03:09:41.780
That we've been able to
save from PSPS impacts.

03:09:41.780 --> 03:09:43.540
And this is the plan, right?

03:09:43.540 --> 03:09:46.007
It depends on how the weather hits,

03:09:46.007 --> 03:09:47.310
it depends which circuits are shut off,

03:09:47.310 --> 03:09:49.280
and that's what will lead

03:09:49.280 --> 03:09:52.080
to which customers actually get benefit

03:09:52.080 --> 03:09:53.400
from these mitigations.

03:09:53.400 --> 03:09:56.480
So each weather pattern and
each weather event is different,

03:09:56.480 --> 03:10:00.573
but this is the planned
mitigation reduction.

03:10:03.520 --> 03:10:05.070
I'll pause there for questions.

03:10:07.710 --> 03:10:10.590
If not, I'll go to our next slide.

03:10:10.590 --> 03:10:12.310
That's our last one.

03:10:12.310 --> 03:10:14.600
I apologize for long here.

03:10:14.600 --> 03:10:17.720
On our just summary slide here,

03:10:17.720 --> 03:10:21.270
we are committed to
continuing the reduction

03:10:21.270 --> 03:10:23.720
of PSPS impacts to our customers.

03:10:23.720 --> 03:10:26.650
We're also going to be
very focused on wildfire risk,

03:10:26.650 --> 03:10:29.760
and this is gonna be done
through the various activities

03:10:29.760 --> 03:10:31.150
that we do, right?

03:10:31.150 --> 03:10:32.849
That we've highlighted already,

03:10:32.849 --> 03:10:34.170
the continued preparation, right?

03:10:34.170 --> 03:10:37.920
We're gonna focus on EOC
exercises, the public education,

03:10:37.920 --> 03:10:40.180
the partnerships that we
have in the community.

03:10:40.180 --> 03:10:42.530
We're gonna increase our
risk modeling because we feel

03:10:42.530 --> 03:10:46.250
that's a key to having a
structured approach for mitigation.

03:10:46.250 --> 03:10:49.810
So that risk modeling
is very, very effective.

03:10:49.810 --> 03:10:52.530
Then the continued grid
hardening will help us

03:10:52.530 --> 03:10:55.880
actually implement what
find through the risk-modeling,

03:10:55.880 --> 03:10:58.140
and then increasing
our customer support.

03:10:58.140 --> 03:10:59.689
Right?

03:10:59.689 --> 03:11:00.522
During these PSPS events,

03:11:00.522 --> 03:11:02.630
we know it's critical for our
customers to have power,

03:11:02.630 --> 03:11:04.980
and we're going to do
everything in our product

03:11:06.016 --> 03:11:06.918
to support them.

03:11:06.918 --> 03:11:08.330
And that there's some staff
there on the left that help

03:11:08.330 --> 03:11:11.560
just understand what we've
been able to achieve so far with.

03:11:11.560 --> 03:11:13.570
And one of the things
we're most proud of

03:11:13.570 --> 03:11:17.150
is that we are able
to reduce the fault rate

03:11:17.150 --> 03:11:21.530
on the transmission, 84%,
which means that we're also able

03:11:21.530 --> 03:11:24.817
to reduce the ignitions that way.

03:11:24.817 --> 03:11:28.160
And so I'll end there
by saying, thank you

03:11:28.160 --> 03:11:30.270
for the opportunity to speak today

03:11:30.270 --> 03:11:33.192
and share with you our PSPS mitigations

03:11:33.192 --> 03:11:35.260
and all our preparation and activities

03:11:35.260 --> 03:11:37.203
around public safety power shutoff.

03:11:41.010 --> 03:11:41.843
<v ->Thank you.</v>

03:11:41.843 --> 03:11:43.280
I wanted to open it up
to the panelists and see

03:11:43.280 --> 03:11:46.660
if they have any last
questions for SDG&amp;E.

03:11:51.360 --> 03:11:52.193
<v ->Question.</v>

03:11:53.490 --> 03:11:56.290
Thank you so much for the whole team

03:11:56.290 --> 03:11:59.927
for very thorough
presentation, both you and.

03:12:02.050 --> 03:12:05.860
For San Diego Gas Electric,
do you have any experience

03:12:05.860 --> 03:12:10.743
with the enhanced
power line safety settings?

03:12:12.491 --> 03:12:17.491
The, refers to, in terms of
equipment on power lines

03:12:18.330 --> 03:12:21.320
that allows and then to turn off

03:12:21.320 --> 03:12:23.830
and within one 10th of a
second of a tree branch,

03:12:23.830 --> 03:12:25.573
where object strikes the line,

03:12:26.720 --> 03:12:29.650
it was a mixed (clears
throat) experience

03:12:29.650 --> 03:12:32.100
for PG&amp;E last year,

03:12:32.100 --> 03:12:37.100
but are you using any
of that in San Diego?

03:12:38.360 --> 03:12:40.820
<v ->Yes, we are Commissioner.</v>

03:12:40.820 --> 03:12:45.160
We did start very early
with this technology

03:12:45.160 --> 03:12:48.010
of, we call sensitive profile setting.

03:12:48.010 --> 03:12:53.010
And what we do is we turn
off the sensors from re-closing

03:12:53.570 --> 03:12:55.960
or re-powering, and we've done that

03:12:57.146 --> 03:12:58.550
for some time now.

03:12:58.550 --> 03:13:03.550
So we, what that helps
us do is for any kind of fault,

03:13:07.220 --> 03:13:10.320
any kind of potential for ignition,

03:13:10.320 --> 03:13:12.420
that quick, the system quickly reacts,

03:13:12.420 --> 03:13:15.700
our sensors quickly
react and are able to keep

03:13:15.700 --> 03:13:18.520
from having additional damage, right?

03:13:18.520 --> 03:13:21.030
So it will shut off power right away.

03:13:21.030 --> 03:13:22.880
The other thing though that we leverage

03:13:22.880 --> 03:13:27.880
is the falling conductor
protection technology

03:13:29.330 --> 03:13:31.000
that we've talked about in the past.

03:13:31.000 --> 03:13:34.903
What that is is when
there's a break in our wire

03:13:34.903 --> 03:13:37.340
or any potential break in our wire,

03:13:37.340 --> 03:13:39.950
the power will shut off
before it hits the ground.

03:13:39.950 --> 03:13:43.502
So in less than 1.3 seconds, right?

03:13:43.502 --> 03:13:45.270
In less than a second,
it's going to shut off power

03:13:45.270 --> 03:13:47.817
before the line even hits the ground.

03:13:47.817 --> 03:13:49.010
So we have been
deploying that technology

03:13:49.010 --> 03:13:50.290
as we enhance our circuits.

03:13:50.290 --> 03:13:51.650
When we talk about grid-hardening,

03:13:51.650 --> 03:13:54.840
that's part of the sensors
and the technology

03:13:54.840 --> 03:13:56.448
that we installed.

03:13:56.448 --> 03:13:58.423
And then one more
technology I'll mention,

03:13:58.423 --> 03:14:03.170
and it's really going to
be a further enhancement

03:14:03.170 --> 03:14:05.664
that we're installing
and we've installed it

03:14:05.664 --> 03:14:08.550
on a few circuits so far,
and it's the early detection,

03:14:08.550 --> 03:14:10.767
early fault detection, EFD.

03:14:10.767 --> 03:14:14.820
And what that is is it's a
matter of looking at things

03:14:14.820 --> 03:14:16.230
even before they fail.

03:14:16.230 --> 03:14:19.280
Instead of waiting until
a wire breaks, right?

03:14:19.280 --> 03:14:21.230
Maybe you have freight wire,

03:14:21.230 --> 03:14:24.480
maybe you have a tree branch
that's momentarily touching

03:14:24.480 --> 03:14:29.480
a wire, so the technology
will allow for that detection

03:14:30.220 --> 03:14:32.200
and pointing to a problem

03:14:32.200 --> 03:14:35.689
so we can send people there and detect

03:14:35.689 --> 03:14:38.690
and figure out where the
location is electronically

03:14:39.566 --> 03:14:41.216
or remotely, but then address it.

03:14:45.546 --> 03:14:46.441
<v ->Okay.</v>

03:14:46.441 --> 03:14:47.274
Thank you.

03:14:50.730 --> 03:14:52.057
<v ->You're welcome.</v>

03:14:52.057 --> 03:14:55.760
Any other questions for SDG&amp;E?

03:15:00.300 --> 03:15:01.430
Okay.

03:15:01.430 --> 03:15:03.770
Let's move to public comment.

03:15:03.770 --> 03:15:07.460
Operator, do we have
any members of the public

03:15:08.697 --> 03:15:10.780
that would like to speak?

03:15:14.390 --> 03:15:15.792
<v Operator>Thank you.</v>

03:15:15.792 --> 03:15:16.707
And at this time,

03:15:16.707 --> 03:15:18.150
if you would like to
make a public comment,

03:15:18.150 --> 03:15:20.640
please unmute your
phone, press Star, One

03:15:22.155 --> 03:15:23.760
and clearly record your
full first and last name

03:15:23.760 --> 03:15:26.270
when prompted so I may introduce you.

03:15:26.270 --> 03:15:28.070
Again, that is Star,
One if you would like

03:15:28.070 --> 03:15:29.123
to make a comment.

03:15:34.970 --> 03:15:37.550
And it may take a few more
much for comments to come in.

03:15:37.550 --> 03:15:38.413
Please stand by.

03:16:03.470 --> 03:16:06.420
And I have no one in the public
comment queue at this time.

03:16:08.960 --> 03:16:10.472
<v ->Okay.</v>

03:16:10.472 --> 03:16:11.570
Hearing that there is
no one in the queue,

03:16:11.570 --> 03:16:15.120
let's move to the Commissioners
and Director Caroline,

03:16:15.120 --> 03:16:19.253
Thomas Jacobs, and Chief
Frank Bigelow for closing remarks.

03:16:24.680 --> 03:16:28.240
<v ->I'll just briefly thank
all of the presenters</v>

03:16:28.240 --> 03:16:30.820
that we had today, both
Southern California Edison,

03:16:30.820 --> 03:16:33.126
San Diego Gas and Electric.

03:16:33.126 --> 03:16:35.810
I appreciated the
reports that were made,

03:16:35.810 --> 03:16:39.170
not just for bringing
forward accomplishments,

03:16:39.170 --> 03:16:42.360
but also identifying
areas for improvement.

03:16:42.360 --> 03:16:44.100
I think that part of this presentation

03:16:44.100 --> 03:16:49.100
was critically important because
we need to see improvement

03:16:49.280 --> 03:16:51.150
from past mistakes.

03:16:51.150 --> 03:16:56.150
We still heard examples
of outages for multiple,

03:16:56.580 --> 03:17:00.183
multiple outages in one
season for the same customers.

03:17:01.240 --> 03:17:04.460
We heard about significant
missed or delayed notifications,

03:17:04.460 --> 03:17:09.460
and also really the need to
prioritize mitigation measures,

03:17:10.020 --> 03:17:11.817
not just for welfare mitigation,

03:17:11.817 --> 03:17:14.210
but also for reduction of PSPS.

03:17:14.210 --> 03:17:18.310
And so I appreciated the
work that both the utilities

03:17:18.310 --> 03:17:23.310
that spoke today are
doing on that, in those areas.

03:17:23.650 --> 03:17:25.260
The other thing that I wanted to note

03:17:25.260 --> 03:17:30.190
is that it was interesting to
me to hear all of the efforts

03:17:30.190 --> 03:17:32.090
to provide backup power,

03:17:32.090 --> 03:17:36.390
and I was pleased to the
movement towards cleaner sources

03:17:36.390 --> 03:17:37.533
of backup power.

03:17:38.370 --> 03:17:41.452
And I think that even the comments

03:17:41.452 --> 03:17:45.200
that you made today about
continued efforts in that area

03:17:45.200 --> 03:17:47.710
will be very helpful to
make sure that customers

03:17:47.710 --> 03:17:52.062
are protected in the event of outages,

03:17:52.062 --> 03:17:54.548
especially access and
functional need customers,

03:17:54.548 --> 03:17:55.881
critical care customers,

03:17:55.881 --> 03:17:58.441
all of our most vulnerable customers.

03:17:58.441 --> 03:18:00.360
And the other reflection
I wanted to make

03:18:00.360 --> 03:18:03.750
is that there was some
discussion on the fire season

03:18:03.750 --> 03:18:06.700
being year round, and just the dryness

03:18:06.700 --> 03:18:07.830
that we're seeing

03:18:07.830 --> 03:18:11.740
with potentially unprecedented
drought conditions,

03:18:11.740 --> 03:18:15.556
and just the uncertainty
that climate change is giving,

03:18:15.556 --> 03:18:20.053
is bringing to our state
with respect to fire risk.

03:18:20.890 --> 03:18:23.960
But I also appreciated the recognition

03:18:23.960 --> 03:18:27.090
that, and I hope this is something

03:18:27.090 --> 03:18:28.250
that you all are embracing,

03:18:28.250 --> 03:18:31.150
is that it's no longer a surprise to us

03:18:31.150 --> 03:18:33.380
that we are seeing unusual conditions,

03:18:33.380 --> 03:18:38.380
that we're seeing conditions
are unexpected, unprecedented,

03:18:39.980 --> 03:18:42.010
record heat waves, to record dryness,

03:18:42.010 --> 03:18:45.260
and really that the
models and the measures

03:18:45.260 --> 03:18:49.240
that are being used need
to adapt and be ready

03:18:49.240 --> 03:18:53.420
for the unexpected, and
really just the recognition

03:18:53.420 --> 03:18:56.540
that that's something that we
know is happening and we know

03:18:56.540 --> 03:18:57.933
will continue to happen.

03:18:59.270 --> 03:19:01.570
So with that, I just wanted to, again,

03:19:01.570 --> 03:19:02.913
thank the presenters.

03:19:03.860 --> 03:19:05.870
There was a lot of information here,

03:19:05.870 --> 03:19:08.830
but I think as you could
tell by the questions you got,

03:19:08.830 --> 03:19:12.500
we're all very interested in
the details and very interested

03:19:12.500 --> 03:19:14.193
in your continued progress.

03:19:15.070 --> 03:19:15.903
Thank you.

03:19:18.980 --> 03:19:21.963
<v ->I had just a couple closing
comments, if you don't mind.</v>

03:19:23.210 --> 03:19:25.350
One, also just wanted
to extend my thanks

03:19:25.350 --> 03:19:26.750
to everyone that presented.

03:19:26.750 --> 03:19:29.710
It's a lot of information,
a long afternoon.

03:19:29.710 --> 03:19:31.426
Really appreciate the work

03:19:31.426 --> 03:19:33.550
that everyone's doing around this.

03:19:33.550 --> 03:19:35.453
And to President Reynold's point,

03:19:36.480 --> 03:19:38.210
I think it's important to call out

03:19:38.210 --> 03:19:41.250
that while we may not have
had any public commenters

03:19:41.250 --> 03:19:43.714
on this, all of us on the phone,

03:19:43.714 --> 03:19:45.410
that this, the urgency
around this is continuing

03:19:45.410 --> 03:19:47.710
to escalate, not decrease,

03:19:47.710 --> 03:19:51.830
and so that the pace and
the effort and focus on it needs

03:19:51.830 --> 03:19:54.900
to keep increasing with
the threat that we've got

03:19:54.900 --> 03:19:57.950
given continued climate
change and impacts.

03:19:57.950 --> 03:20:01.110
So really appreciate the
work everyone's doing.

03:20:01.110 --> 03:20:04.158
I know we, literally, while
we're on the phone here,

03:20:04.158 --> 03:20:05.040
we just got PG&amp;Es, we got San Diego's

03:20:05.040 --> 03:20:08.740
and Edison's, last week
and the week before.

03:20:08.740 --> 03:20:11.560
So our team is already
digging into those,

03:20:11.560 --> 03:20:14.950
and look forward to
continuing to work with all of you

03:20:14.950 --> 03:20:18.050
to evaluate those and keep
doing this important work

03:20:18.050 --> 03:20:20.323
to get ahead of this risk.

03:20:21.320 --> 03:20:22.660
Thank you.

03:20:22.660 --> 03:20:25.202
<v Operator>And my apologies,
this is the Operator,</v>

03:20:25.202 --> 03:20:27.440
we did have one participant
queue up to make a comment.

03:20:27.440 --> 03:20:29.040
Would you like to hear that now?

03:20:32.296 --> 03:20:33.195
<v ->Yes, please.</v>

03:20:33.195 --> 03:20:34.089
That would be great.

03:20:34.089 --> 03:20:34.922
<v ->Yes, please.</v>

03:20:34.922 --> 03:20:36.064
<v Operator>Okay.</v>

03:20:36.064 --> 03:20:36.897
One moment.

03:20:36.897 --> 03:20:38.330
Melissa Kasnitz, you may go ahead.

03:20:39.780 --> 03:20:40.630
<v Melissa>Thank you.</v>

03:20:40.630 --> 03:20:41.880
This is Melissa Kasnitz

03:20:41.880 --> 03:20:44.300
from the Center for
Accessible Technology.

03:20:44.300 --> 03:20:46.560
I'll note that the phone
number wasn't posted

03:20:46.560 --> 03:20:48.100
on the computer screen,

03:20:48.100 --> 03:20:50.750
and so I had to go look
up the phone number

03:20:50.750 --> 03:20:52.350
because I was watching on my monitor,

03:20:52.350 --> 03:20:55.070
so there may be other people
who were delayed in trying

03:20:55.070 --> 03:20:57.740
to access the public comment line.

03:20:57.740 --> 03:21:01.160
I'd like to repeat a point
that I made the other day

03:21:01.160 --> 03:21:05.430
with regard to PG&amp;E and the
Small Utilities presentations,

03:21:05.430 --> 03:21:09.380
which is I very much appreciate
all of the wildfire analysis

03:21:09.380 --> 03:21:13.290
and work that's taking
place by the various utilities,

03:21:13.290 --> 03:21:17.110
but I strongly encourage
similar work and analysis

03:21:17.110 --> 03:21:21.120
to be done in investigating the
harms that people experience

03:21:21.120 --> 03:21:23.560
during power shutoffs.

03:21:23.560 --> 03:21:26.110
The mitigation efforts
that have been presented

03:21:26.110 --> 03:21:28.520
are definitely a market improvement

03:21:28.520 --> 03:21:31.570
since the Power Shutoff Program began,

03:21:31.570 --> 03:21:34.810
but it's unlikely to ever
expect that mitigation

03:21:34.810 --> 03:21:38.120
will reach all customers
in need and all customers

03:21:38.120 --> 03:21:41.640
who are experiencing risks
when the power goes out.

03:21:41.640 --> 03:21:42.650
And at this time,

03:21:42.650 --> 03:21:45.550
the analysis of that harm
is very superficial relative

03:21:45.550 --> 03:21:47.980
to the analysis of wildfire risk.

03:21:47.980 --> 03:21:50.840
I strongly encourage the
Commission and the utilities

03:21:50.840 --> 03:21:55.500
to pick up that element
of the work and really take

03:21:55.500 --> 03:21:58.670
into consideration
what happens to people,

03:21:58.670 --> 03:22:01.870
and especially vulnerable
people when the power goes off.

03:22:01.870 --> 03:22:02.703
Thank you.

03:22:09.190 --> 03:22:10.100
<v ->Thank you for your comment.</v>

03:22:10.100 --> 03:22:13.140
Operator, do we have any
other members of the public

03:22:13.140 --> 03:22:14.690
that would like to speak today?

03:22:15.790 --> 03:22:18.140
<v Operator>And no other
members at this time.</v>

03:22:20.815 --> 03:22:21.726
<v ->Okay.</v>

03:22:21.726 --> 03:22:22.559
With that being said,

03:22:22.559 --> 03:22:25.955
I'd like to get back to
closing remarks with the rest

03:22:25.955 --> 03:22:26.788
of the Commissioners.

03:22:32.060 --> 03:22:33.720
<v ->I'll go next.</v>

03:22:33.720 --> 03:22:37.370
Again, thank you
to all of the utilities,

03:22:37.370 --> 03:22:41.698
the teams that presented,
including the other day

03:22:41.698 --> 03:22:44.740
from Pacific Gas Electric,
Liberty and PacifiCorp.

03:22:46.143 --> 03:22:48.975
And I just wanted to
also add (clears throat)

03:22:48.975 --> 03:22:51.570
that the presentations are given

03:22:51.570 --> 03:22:53.480
to the Low Income Oversight Board

03:22:54.957 --> 03:22:59.930
on the impacts of PSPS
on low-income customers,

03:22:59.930 --> 03:23:03.468
and I very much
appreciate the effort made.

03:23:03.468 --> 03:23:06.263
The next meeting is on March 24th,

03:23:07.150 --> 03:23:09.700
and throughout (clears
throat) these past few years,

03:23:09.700 --> 03:23:14.700
it has been very helpful and
informative to the volunteers

03:23:15.410 --> 03:23:18.290
in the Low Income Oversight
Board to hear what the utilities

03:23:18.290 --> 03:23:21.713
are doing (clears throat)
for these communities.

03:23:22.840 --> 03:23:23.673
Thank you.

03:23:26.340 --> 03:23:27.173
<v ->Thank you.</v>

03:23:28.370 --> 03:23:30.300
<v ->I just wanted to
echo the comments</v>

03:23:30.300 --> 03:23:33.140
of my fellow Commissioners
and thank everyone

03:23:33.140 --> 03:23:34.560
for their presentations today.

03:23:34.560 --> 03:23:37.960
That was a lot of
information, and I look forward

03:23:37.960 --> 03:23:40.920
to seeing the progress and outcomes

03:23:40.920 --> 03:23:42.363
as we move through the year.

03:23:43.272 --> 03:23:44.355
So thank you.

03:23:45.613 --> 03:23:48.720
<v ->Can I also echo the, so
thanks to the presenters,</v>

03:23:49.760 --> 03:23:53.800
and the comments of
my fellow Commissioners.

03:23:53.800 --> 03:23:54.633
Thank you.

03:23:57.960 --> 03:23:59.840
<v ->Me three or me four,</v>

03:23:59.840 --> 03:24:04.123
I wanna thank all of you
for your presentations.

03:24:05.068 --> 03:24:08.060
And as President Reynolds said,

03:24:08.060 --> 03:24:11.813
your willingness to learn
and continue to improve.

03:24:12.950 --> 03:24:16.420
I do think we should
take very seriously to heart

03:24:16.420 --> 03:24:19.590
what Melissa Kasnitz said,

03:24:19.590 --> 03:24:23.400
which is it's harder
to analyze the impacts

03:24:23.400 --> 03:24:28.400
of PSPSs, quantify it, monetize it,

03:24:28.490 --> 03:24:31.600
whatever, but it's as important

03:24:31.600 --> 03:24:34.820
and it hasn't been
done nearly to the extent

03:24:36.029 --> 03:24:38.459
that we've analyzed the utilities,

03:24:38.459 --> 03:24:41.640
have analyzed other technical
aspects of this process.

03:24:41.640 --> 03:24:43.740
So I do urge you to think hard

03:24:43.740 --> 03:24:48.740
about how you can do
what she's suggesting.

03:24:49.350 --> 03:24:52.681
And it parallels to some degree

03:24:52.681 --> 03:24:55.990
the harder work that is necessary,

03:24:55.990 --> 03:24:58.683
but I'm gratified to see
that what the utilities

03:24:58.683 --> 03:25:01.687
are doing, which is how
to engage with community,

03:25:01.687 --> 03:25:04.238
how to improve communication,

03:25:04.238 --> 03:25:07.190
how to have more responsive
community resource centers,

03:25:07.190 --> 03:25:12.190
meet the needs of people
for support and backup or food,

03:25:12.720 --> 03:25:16.210
it, that don't lend
themselves to simple solutions

03:25:16.210 --> 03:25:20.710
by simply standing up a
resource center at a fair ground,

03:25:20.710 --> 03:25:24.220
but maybe dispatching a
portable battery to someone

03:25:24.220 --> 03:25:28.480
who's at a hotel or someone
with special dietary needs.

03:25:28.480 --> 03:25:31.940
And I did hear from both of
the utilities your commitment,

03:25:31.940 --> 03:25:34.610
and it's clear that you're looking hard

03:25:34.610 --> 03:25:39.610
at those more difficult, more,
I won't say more intractable,

03:25:40.010 --> 03:25:43.640
but less obvious, a somewhat
more difficult problem

03:25:43.640 --> 03:25:47.260
that don't lend themselves
to automated solutions

03:25:47.260 --> 03:25:51.903
or another supercomputer
crunching out the data.

03:25:52.850 --> 03:25:57.193
So in any case, it, maybe
we were lucky last year.

03:25:58.550 --> 03:25:59.563
I, you certainly,

03:26:01.037 --> 03:26:03.733
we certainly saw some
improvements in reductions.

03:26:05.243 --> 03:26:08.400
I hope it's, as much as a result

03:26:08.400 --> 03:26:10.240
of the targeted mitigation measures

03:26:10.240 --> 03:26:13.650
that you guys both outlined
as it was because of breaks

03:26:13.650 --> 03:26:17.384
in the weather, we'll knock wood,

03:26:17.384 --> 03:26:22.384
we'll see this this season,
but it's certainly encouraging

03:26:22.560 --> 03:26:24.939
to see your commitment
to continue to improve

03:26:24.939 --> 03:26:29.840
and refine this program.

03:26:29.840 --> 03:26:30.673
Thank you.

03:26:39.610 --> 03:26:40.443
<v Frank>Sorry.</v>

03:26:45.240 --> 03:26:46.970
This is Frank Bigelow with Cal Fire.

03:26:46.970 --> 03:26:49.240
I apologize, with all
the talk of technology,

03:26:49.240 --> 03:26:50.850
I had lost my internet connection,

03:26:50.850 --> 03:26:52.493
thus losing my video feed.

03:26:53.470 --> 03:26:55.650
First, I just wanted to
thank President Reynolds

03:26:55.650 --> 03:26:59.460
and the Commissioners for
allowing Cal Fire to participate

03:26:59.460 --> 03:27:01.223
in today's event.

03:27:02.440 --> 03:27:04.820
This is a very important topic,

03:27:04.820 --> 03:27:08.960
and we're already, just as
a reminder, in fire season.

03:27:08.960 --> 03:27:12.950
Across the state, we've seen
close to 4,700 acres burned,

03:27:12.950 --> 03:27:15.930
and we're only in February.

03:27:15.930 --> 03:27:18.180
So we've seen Santana
Ana wind conditions already

03:27:18.180 --> 03:27:20.100
in Southern California,

03:27:20.100 --> 03:27:25.053
and we are slowly seeing
the fuel start to dry out.

03:27:26.420 --> 03:27:29.650
And we just want to emphasize
and reemphasize the points

03:27:29.650 --> 03:27:34.420
that have been made today
that we feel PSPS is a measure

03:27:34.420 --> 03:27:38.270
of last resort and that
we really can't lose focus

03:27:38.270 --> 03:27:40.170
on the required vegetation management

03:27:40.170 --> 03:27:45.170
and grid-hardening tactics that
have been employed thus far.

03:27:45.450 --> 03:27:48.900
And we look to see continued
efforts from all the utilities.

03:27:48.900 --> 03:27:51.460
So again, from Cal Fire's perspective,

03:27:51.460 --> 03:27:53.853
thank you for allowing
us to participate today.

03:28:00.640 --> 03:28:02.770
<v ->Thank you, Chief Frank Bigelow.</v>

03:28:02.770 --> 03:28:04.923
Do we have any other closing remarks?

03:28:10.750 --> 03:28:12.950
Hearing none, I will
turn over to the Operator

03:28:12.950 --> 03:28:15.763
to check one more time if
we have any public speakers.

03:28:21.220 --> 03:28:23.220
<v Operator>And again, if you
would like to make a comment,</v>

03:28:23.220 --> 03:28:26.170
please press Star, One unmute your phone

03:28:26.170 --> 03:28:28.873
and record your full name when prompted.

03:28:43.690 --> 03:28:45.270
<v ->All right.</v>

03:28:45.270 --> 03:28:47.400
Hearing none, I would
like to close out today.

03:28:47.400 --> 03:28:48.690
Thank you, everyone, for joining us

03:28:48.690 --> 03:28:49.973
on this Friday afternoon.