WEBVTT

00:00:00.063 --> 00:00:02.646
(upbeat music)

00:00:12.580 --> 00:00:14.910
<v Joseph>Welcome to the
California Public Utilities</v>

00:00:14.910 --> 00:00:19.347
Commission on this day,
Monday, March 1st, 2021.

00:00:24.486 --> 00:00:26.320
<v Marybel>Okay, thank you.</v>

00:00:26.320 --> 00:00:28.350
Good afternoon, everyone.

00:00:28.350 --> 00:00:30.580
I'd like to thank my
fellow Commissioners

00:00:30.580 --> 00:00:32.840
for joining us today
for this public meeting

00:00:32.840 --> 00:00:36.970
with Southern California
Edison to report on their plan

00:00:36.970 --> 00:00:41.330
to improve their planning,
execution, and communications

00:00:41.330 --> 00:00:44.330
of their public safety
power shutoff events

00:00:44.330 --> 00:00:47.680
going into the 2021 fire season.

00:00:47.680 --> 00:00:50.440
Before we begin, I would like to cover

00:00:50.440 --> 00:00:51.930
some of the information

00:00:51.930 --> 00:00:55.360
on the public participation
in today's meeting.

00:00:55.360 --> 00:00:57.860
Participants can hear the live event

00:00:57.860 --> 00:01:01.250
and make comments at
the end of the public meeting.

00:01:01.250 --> 00:01:05.477
Dial into 800-857-1917

00:01:07.190 --> 00:01:10.073
and enter pass code 8147204 pound.

00:01:15.220 --> 00:01:17.780
Participants listening in by phone

00:01:17.780 --> 00:01:21.960
will be placed on mute
in a listen only mode

00:01:21.960 --> 00:01:26.323
until the public comment
portion of the meeting begins.

00:01:27.160 --> 00:01:30.369
Once the public comment
portion of the meeting begins,

00:01:30.369 --> 00:01:35.369
participants may dial star-one
when they wish to speak,

00:01:35.690 --> 00:01:38.143
to be placed in a queue by the operator.

00:01:39.209 --> 00:01:42.140
You will be called upon
to speak when we get

00:01:42.140 --> 00:01:45.300
to the public comment
period in today's agenda.

00:01:45.300 --> 00:01:47.460
If you encounter difficulty calling into

00:01:47.460 --> 00:01:50.080
the public telephone
line, please contact

00:01:50.920 --> 00:01:55.920
CPUC's Public Advisor at
public.advisor@cpuc.ca.gov

00:01:59.780 --> 00:02:04.520
or call toll free 866-849-8390.

00:02:10.870 --> 00:02:14.183
With that, turning to the
subject of today's meeting.

00:02:15.090 --> 00:02:16.520
When it comes to the decision

00:02:16.520 --> 00:02:18.890
to shutoff power to customers,

00:02:18.890 --> 00:02:22.630
utilities must execute PSPS events

00:02:22.630 --> 00:02:25.350
in a manner that places the wellbeing

00:02:25.350 --> 00:02:29.050
of the people and the
communities they serve first.

00:02:29.050 --> 00:02:32.300
Looking back at the
2020 wildfire season,

00:02:32.300 --> 00:02:37.300
Edison initiated 16 power shutoffs
between May and December.

00:02:37.300 --> 00:02:40.580
The majority of the events
were in November and December,

00:02:40.580 --> 00:02:42.593
including two major holidays.

00:02:43.470 --> 00:02:47.250
In January, I sent a letter to Edison,

00:02:47.250 --> 00:02:51.750
expressing my deep concerns
with Edison's PSPS execution,

00:02:51.750 --> 00:02:55.153
and we held a public meeting
to address the deficiencies.

00:02:56.030 --> 00:02:58.830
Among the various problems we observed

00:02:58.830 --> 00:03:01.063
with Edison's planning and execution

00:03:01.063 --> 00:03:05.010
were issues with the
level of transparency

00:03:05.010 --> 00:03:07.563
around the PSPS decision-making process,

00:03:08.740 --> 00:03:12.620
inadequate notification
to impacted customers,

00:03:12.620 --> 00:03:15.270
poor coordination and communication

00:03:15.270 --> 00:03:17.650
with state and local governments,

00:03:17.650 --> 00:03:20.350
shortcomings in
identifying and notifying

00:03:20.350 --> 00:03:25.350
Medical Baseline and Access
and Functional Needs customers,

00:03:26.000 --> 00:03:31.000
and inadequate PSPS post-event
reporting to the Commission.

00:03:31.750 --> 00:03:36.180
In addition, there were also
serious concerns with the pace

00:03:36.180 --> 00:03:40.020
at which Edison has been
deploying backup power

00:03:40.020 --> 00:03:44.113
to help vulnerable customers
endure PSPS events.

00:03:45.030 --> 00:03:49.070
In our January public meeting,
we had significant discussion

00:03:49.070 --> 00:03:51.750
with Edison leadership
on their shortcomings,

00:03:51.750 --> 00:03:55.340
and heard from
numerous elected officials

00:03:55.340 --> 00:03:58.310
and community members
about the severe impacts

00:03:58.310 --> 00:04:02.693
Edison's inadequate
execution had been on them.

00:04:03.630 --> 00:04:06.650
As part of the CPUC's ongoing actions

00:04:06.650 --> 00:04:09.810
to ensure Edison reduces the frequency,

00:04:09.810 --> 00:04:13.710
scope, and impact of
PSPS on their customers,

00:04:13.710 --> 00:04:18.010
we required Edison to
submit a corrective action plan

00:04:18.010 --> 00:04:21.610
to our staff and to
begin meeting with them

00:04:21.610 --> 00:04:25.730
on a bi-weekly basis to
have real-time accountability

00:04:25.730 --> 00:04:29.493
and feedback on their progress
on their corrective action.

00:04:30.580 --> 00:04:32.930
Today's public meeting
is meant to further

00:04:32.930 --> 00:04:35.920
inure accountability for Edison

00:04:35.920 --> 00:04:40.030
to both the Commission
and to its customers.

00:04:40.030 --> 00:04:41.810
Edison must demonstrate today,

00:04:41.810 --> 00:04:44.060
and throughout this Winter and Spring,

00:04:44.060 --> 00:04:48.100
that it is taking seriously
and taking appropriate action,

00:04:48.100 --> 00:04:52.600
to ensure the mistakes of
last Fall will not occur again

00:04:54.710 --> 00:04:57.240
and to ensure Edison is prioritizing

00:04:57.240 --> 00:04:59.243
the safety of their customers.

00:05:00.360 --> 00:05:03.660
Edison submitted their
PSPS corrective action plan

00:05:03.660 --> 00:05:06.810
to the CPUC on February 12th,

00:05:06.810 --> 00:05:10.100
and our safety leadership has begun

00:05:10.100 --> 00:05:12.503
oversight meetings with them.

00:05:13.660 --> 00:05:15.640
Today, we will hear from Edison

00:05:15.640 --> 00:05:18.500
the specifics of their
plan and how they intend

00:05:18.500 --> 00:05:21.423
to course correct over
the next few months.

00:05:22.360 --> 00:05:24.780
In terms of the order
of today's meeting,

00:05:24.780 --> 00:05:26.260
we will first hear from Edison

00:05:26.260 --> 00:05:28.180
on their corrective action plan

00:05:28.180 --> 00:05:30.480
and then Commissioners on the dais

00:05:31.500 --> 00:05:34.280
will have an opportunity
to ask questions,

00:05:34.280 --> 00:05:36.630
followed by public comments.

00:05:36.630 --> 00:05:39.550
With that, I would like to turn
to my fellow Commissioners

00:05:39.550 --> 00:05:41.530
to see if they have any opening remarks

00:05:41.530 --> 00:05:42.980
that they would like to make.

00:05:43.905 --> 00:05:45.255
Commissioner Rechtschaffen?

00:05:46.410 --> 00:05:47.710
<v ->No, thank you,
President Batjer.</v>

00:05:47.710 --> 00:05:49.440
No opening remarks.

00:05:49.440 --> 00:05:51.633
<v ->Okay, Commissioner Shiroma.</v>

00:05:53.870 --> 00:05:55.303
<v ->Yes, thank you.</v>

00:05:56.270 --> 00:06:01.018
I very much appreciate your
facilitating this discussion,

00:06:01.018 --> 00:06:04.603
President Batjer, it's
a very important one.

00:06:05.840 --> 00:06:08.590
We've witnessed massive destruction

00:06:08.590 --> 00:06:11.010
resulting from California wildfires.

00:06:11.010 --> 00:06:12.920
We've enacted massive efforts

00:06:12.920 --> 00:06:14.750
to prevent such further destruction,

00:06:14.750 --> 00:06:17.700
but there is so much
more work to be done.

00:06:17.700 --> 00:06:21.050
I appreciated that during
our January 26th meeting,

00:06:21.050 --> 00:06:24.790
that Southern California Edison
shared what they are doing,

00:06:24.790 --> 00:06:27.740
their ability to sectionalize outages

00:06:27.740 --> 00:06:30.850
towards reducing the
number of customers affected.

00:06:30.850 --> 00:06:34.390
That's useful, but there's
much more to be done.

00:06:34.390 --> 00:06:38.120
And especially the
communication from customers.

00:06:38.120 --> 00:06:40.600
It was very remarkable, as you outlined,

00:06:40.600 --> 00:06:45.070
the sheer number of
elected and customers

00:06:45.070 --> 00:06:49.270
who called in to share their experience.

00:06:49.270 --> 00:06:52.263
And it was very tough because

00:06:52.263 --> 00:06:55.210
some of those public
safety power shutoffs

00:06:55.210 --> 00:06:59.320
occurred right during
the holiday season.

00:06:59.320 --> 00:07:03.433
I do want to thank the Wildfire
Safety and Enforcement staff

00:07:03.433 --> 00:07:05.790
and their representatives
who are here today,

00:07:05.790 --> 00:07:09.010
from Southern California
Edison, and including Jessica Lim,

00:07:09.010 --> 00:07:13.270
who serves on our Low
Income Oversight Board.

00:07:13.270 --> 00:07:14.560
Looking forward to this session.

00:07:14.560 --> 00:07:15.823
Thank you, President Batjer.

00:07:15.823 --> 00:07:17.660
<v Marybel>Thank you,
Commissioner Shiroma,</v>

00:07:17.660 --> 00:07:19.380
Commissioner Houck,
would you like to make

00:07:19.380 --> 00:07:20.480
some opening comments?

00:07:22.660 --> 00:07:24.040
<v ->I also would like to thank you</v>

00:07:24.040 --> 00:07:27.430
for arranging for and
facilitating the meeting today.

00:07:27.430 --> 00:07:29.393
This is a very important issue.

00:07:30.385 --> 00:07:32.350
And as a new Commissioner,
I'm looking forward to hearing

00:07:32.350 --> 00:07:34.850
from Souther California
Edison and the staff,

00:07:34.850 --> 00:07:37.290
and thank them for being available today

00:07:37.290 --> 00:07:40.423
to present the issues, and
look forward to hearing more.

00:07:42.150 --> 00:07:43.550
<v Marybel>Okay, thank you.</v>

00:07:45.450 --> 00:07:48.210
I believe that Commissioner
Guzman Aceves

00:07:48.210 --> 00:07:52.423
is listening in today, so
she is participating by phone.

00:07:53.420 --> 00:07:54.560
<v ->Present Batjer, I am here.</v>

00:07:54.560 --> 00:07:56.983
I'm not sure why... &lt;v
Marybel&gt;Oh good!</v>

00:07:56.983 --> 00:07:58.796
I'm sorry, I couldn't see you, good.

00:07:58.796 --> 00:08:00.195
Commissioner Guzman Aceves.
<v ->It's okay,</v>

00:08:00.195 --> 00:08:01.600
I don't have any opening
remarks, thank you.

00:08:01.600 --> 00:08:03.700
I'm interested in hearing
from the company.

00:08:03.700 --> 00:08:06.180
<v Marybel>Okay,
thank you very much.</v>

00:08:06.180 --> 00:08:10.720
All right, with that, we
will turn to SoCal Edison

00:08:10.720 --> 00:08:14.430
to present on their
corrective action plan.

00:08:14.430 --> 00:08:15.263
Edison.

00:08:16.930 --> 00:08:17.770
<v ->Good afternoon.</v>

00:08:17.770 --> 00:08:20.020
And thank you, President Batjer,

00:08:20.020 --> 00:08:22.290
and Commissioners, for your time today,

00:08:22.290 --> 00:08:23.640
as we review the elements of the plan

00:08:23.640 --> 00:08:26.240
that we filed on February 12th.

00:08:26.240 --> 00:08:31.227
I would welcome, feel free
to post the slides at any time,

00:08:31.227 --> 00:08:34.403
although they're not necessary
for my opening remarks.

00:08:35.440 --> 00:08:36.940
So, my name is Erik Takayesu.

00:08:36.940 --> 00:08:40.800
And I am the current Vice
President of PSPS Readiness

00:08:40.800 --> 00:08:43.083
put in charge of our plan for 2021.

00:08:44.200 --> 00:08:46.510
I've been with Edison for 30 years.

00:08:46.510 --> 00:08:49.110
And I'm an Incident Commander for PSPS,

00:08:49.110 --> 00:08:51.883
and I've been involved in
some of our largest events.

00:08:52.723 --> 00:08:55.440
Your opening remarks
highlight the issues and concerns

00:08:55.440 --> 00:08:57.840
that are front and center in our plan.

00:08:57.840 --> 00:08:59.690
We look forward to continually engaging

00:08:59.690 --> 00:09:03.190
members of your staff
on a bi-weekly basis

00:09:03.190 --> 00:09:05.410
to ensure we successfully complete

00:09:05.410 --> 00:09:07.530
the elements we identified,

00:09:07.530 --> 00:09:09.200
with the end result of reducing

00:09:09.200 --> 00:09:12.180
the frequency and scope of PSPS,

00:09:12.180 --> 00:09:13.570
improving the execution,

00:09:13.570 --> 00:09:16.870
including our notifications
and communications,

00:09:16.870 --> 00:09:18.110
as well as our engagement

00:09:18.110 --> 00:09:20.770
with our partners and our stakeholders.

00:09:20.770 --> 00:09:23.260
And since the January 26th meeting,

00:09:23.260 --> 00:09:26.550
Edison has assembled
an organizational structure

00:09:26.550 --> 00:09:28.220
that pulls together this plan,

00:09:28.220 --> 00:09:31.620
leveraging subject matter
experts from across Edison

00:09:31.620 --> 00:09:34.250
that are now dedicated to this effort.

00:09:34.250 --> 00:09:36.350
A number of them are here with me today,

00:09:36.350 --> 00:09:39.700
so you can meet and directly
engage with the leaders

00:09:39.700 --> 00:09:42.850
who are working to significantly
improve key functions

00:09:42.850 --> 00:09:46.530
within our company involved
with PSPS, given this is one

00:09:46.530 --> 00:09:49.130
of the highest priorities
for our company this year.

00:09:49.999 --> 00:09:52.520
So, let me just start off
with brief introductions

00:09:52.520 --> 00:09:55.138
to the speakers we have on line today.

00:09:55.138 --> 00:09:58.880
Terry Ohanian is our Director
over our Southeast Division

00:09:58.880 --> 00:10:01.590
for Distribution,
Construction, Maintenance,

00:10:01.590 --> 00:10:05.010
working to execute all of
our grid hardening activities,

00:10:05.010 --> 00:10:07.623
and accelerating work on
our most impacted circuits.

00:10:08.620 --> 00:10:11.000
Jessica Lim is our Principal Manager

00:10:11.000 --> 00:10:12.870
over Customer Service Programs,

00:10:12.870 --> 00:10:17.000
where we have consolidated
all of the programs, services,

00:10:17.000 --> 00:10:20.393
customer notifications, and
communications for PSPS.

00:10:21.640 --> 00:10:24.940
Tom Brady is our Principal
Manager in Business Resiliency

00:10:24.940 --> 00:10:28.340
over all of our external
engagements in the area of PSPS,

00:10:28.340 --> 00:10:31.280
with state and local
emergency management,

00:10:31.280 --> 00:10:34.100
ICS protocols and reporting.

00:10:34.100 --> 00:10:36.210
And Ranbir Sekhon is our Director

00:10:36.210 --> 00:10:39.350
of Business Transformation,
integral to integrating

00:10:39.350 --> 00:10:42.920
our IT systems and digital
automation enhancements

00:10:42.920 --> 00:10:45.530
across the entire program.

00:10:45.530 --> 00:10:47.550
Each one is dedicated full time

00:10:47.550 --> 00:10:49.890
for the completion of our action plan,

00:10:49.890 --> 00:10:51.940
and all have been involved with PSPS,

00:10:51.940 --> 00:10:54.073
either in events or
ongoing improvements.

00:10:56.180 --> 00:10:58.850
Now I'll spend the rest of our
time covering the action plan

00:10:58.850 --> 00:11:00.900
and I'll have a few opening
remarks and comments

00:11:00.900 --> 00:11:05.090
related to our 2020 fire
season and response.

00:11:05.090 --> 00:11:06.440
And then we'll have a few of our leads

00:11:06.440 --> 00:11:08.940
review the plan in more detail.

00:11:08.940 --> 00:11:11.130
So if you wouldn't mind
going to the presentation

00:11:11.130 --> 00:11:14.443
and specifically going to
slide three, I'd appreciate it.

00:11:17.830 --> 00:11:18.663
Thank you.

00:11:19.530 --> 00:11:21.560
So, as our CEO, Kevin Payne, described

00:11:21.560 --> 00:11:24.860
at the January 26th
meeting, 2020 was a year

00:11:24.860 --> 00:11:28.083
of unimaginable tragedy
for many Californians.

00:11:28.930 --> 00:11:31.120
In our high fire risk
areas we experienced

00:11:31.120 --> 00:11:33.800
record dry fuel levels
throughout the year,

00:11:33.800 --> 00:11:36.040
from heat spells and
lack of precipitation,

00:11:36.040 --> 00:11:38.750
and a series of more
significant Santa Ana wind events

00:11:38.750 --> 00:11:40.820
towards the end of the year

00:11:40.820 --> 00:11:45.820
We saw 70% more red flag
days in 2020 versus 2019.

00:11:45.900 --> 00:11:48.520
And 2/3 of our activations occurred

00:11:48.520 --> 00:11:50.880
from November through
the end of the year,

00:11:50.880 --> 00:11:52.530
noting the particular hardships

00:11:52.530 --> 00:11:55.363
experienced by our customers
over the holiday season.

00:11:56.340 --> 00:11:58.980
I, and the members of our
teams, have heard the concerns

00:11:58.980 --> 00:12:01.610
and frustrations of our
customers and communities

00:12:01.610 --> 00:12:04.253
who have been affected by PSPS events.

00:12:05.176 --> 00:12:08.300
And with the challenges
with the COVID 19 pandemic,

00:12:08.300 --> 00:12:11.130
that has affected all
of us, the seriousness

00:12:11.130 --> 00:12:13.733
of the situation couldn't
be more significant.

00:12:15.010 --> 00:12:16.560
And this underscores the importance

00:12:16.560 --> 00:12:18.000
of having a more resilient grid

00:12:18.000 --> 00:12:21.520
that will significantly reduce
the risk of utility equipment

00:12:21.520 --> 00:12:25.820
sparking catastrophic
wildfires and the need for PSPS.

00:12:25.820 --> 00:12:28.550
And while more circuits and
customers were de-energized

00:12:28.550 --> 00:12:30.730
as a result of those weather events,

00:12:30.730 --> 00:12:33.220
we did see positive improvement.

00:12:33.220 --> 00:12:35.670
Our main emphasis in 2020 was focused

00:12:35.670 --> 00:12:39.530
on the distribution system,
creating segmentation plans

00:12:39.530 --> 00:12:42.070
for every one of our 1100 circuits

00:12:42.070 --> 00:12:44.100
in our high fire risk areas.

00:12:44.100 --> 00:12:47.160
Most notably, when we
compare to distribution circuits

00:12:47.160 --> 00:12:51.307
de-energized in 2019, we
saw fewer of those same circuits

00:12:51.307 --> 00:12:53.970
and customers de-energized in 2020,

00:12:53.970 --> 00:12:58.253
and we removed around 25,000
customers in scope for PSPS.

00:12:59.200 --> 00:13:02.420
But, while this yielded some benefit,

00:13:02.420 --> 00:13:04.930
there is clearly more work to do.

00:13:04.930 --> 00:13:07.570
Net overall, we saw more
circuits and customers

00:13:07.570 --> 00:13:11.610
coming in scope, with
230,000 customers impacted

00:13:11.610 --> 00:13:15.302
when we count the number
of repeated de-energizations.

00:13:15.302 --> 00:13:17.770
We use PSPS as a last resort

00:13:17.770 --> 00:13:20.910
to protect the lives and
property of the people we serve

00:13:20.910 --> 00:13:22.800
when weather and fire
conditions demand it.

00:13:22.800 --> 00:13:25.610
But we now need to
further direct our efforts

00:13:25.610 --> 00:13:29.050
to focus on the most
frequently impacted circuits.

00:13:29.050 --> 00:13:31.270
Now, based on our experience so far,

00:13:31.270 --> 00:13:33.050
the path towards
addressing these circuits

00:13:33.050 --> 00:13:37.930
have become clearer, with
our strategy addressing for 2021,

00:13:37.930 --> 00:13:39.420
circuits that have experienced

00:13:39.420 --> 00:13:42.830
four or more
de-energizations since 2019.

00:13:42.830 --> 00:13:44.590
And we believe the hardening of our grid

00:13:44.590 --> 00:13:47.110
will not only mitigate
the frequency of PSPS,

00:13:47.110 --> 00:13:49.640
but will serve to improve the overall

00:13:49.640 --> 00:13:52.173
reliability and
resiliency going forward.

00:13:53.090 --> 00:13:55.870
And while we continually
work to reduce PSPS,

00:13:55.870 --> 00:13:58.880
even beyond the circuits
highlighted in our plans,

00:13:58.880 --> 00:14:01.450
we also need to take
a further leadership role

00:14:01.450 --> 00:14:04.610
in helping our customers,
communities, and partners

00:14:04.610 --> 00:14:07.920
mitigate the impact of
PSPS when it does occur,

00:14:07.920 --> 00:14:11.440
providing clear and
transparent information status

00:14:11.440 --> 00:14:13.720
and further shaping
our programs to assist

00:14:13.720 --> 00:14:15.730
our most vulnerable customers,

00:14:15.730 --> 00:14:17.940
as addressed in the five main categories

00:14:17.940 --> 00:14:22.640
of actions in our plan, which
are to reduce the use of PSPS,

00:14:22.640 --> 00:14:24.970
execute our events effectively,

00:14:24.970 --> 00:14:27.370
mitigate the impacts of PSPS,

00:14:27.370 --> 00:14:30.150
keeping our partners
and customers informed,

00:14:30.150 --> 00:14:32.943
and enhancing and improving
our post-event reporting.

00:14:33.990 --> 00:14:36.861
We have quite a bit of
information to cover today.

00:14:36.861 --> 00:14:40.330
Unless there are any
questions at this point,

00:14:40.330 --> 00:14:44.420
I'll now hand over to Terry
Ohanian to review in more detail

00:14:44.420 --> 00:14:46.773
our plans to reduce the use of PSPS.

00:14:50.120 --> 00:14:51.792
<v Terry>Thank you, Erik.</v>

00:14:51.792 --> 00:14:52.625
Sorry.

00:14:55.115 --> 00:14:55.948
Begin?

00:14:55.948 --> 00:14:57.030
<v Marybel>Go ahead,
Terry, I'm sorry.</v>

00:14:57.030 --> 00:14:59.130
I was just thanking Erik.

00:14:59.130 --> 00:15:00.510
So go ahead, please.

00:15:00.510 --> 00:15:02.120
Sorry to interrupt.

00:15:02.120 --> 00:15:04.233
<v Terry>No worries,
all right, thanks.</v>

00:15:04.233 --> 00:15:05.550
Good afternoon, everyone.

00:15:05.550 --> 00:15:10.140
I'm Terry Ohanian, and like
Erik, I have served as an IC

00:15:10.140 --> 00:15:11.913
on a significant number of the events

00:15:11.913 --> 00:15:15.390
that just occurred in this past season.

00:15:15.390 --> 00:15:16.590
So, today I'll be covering

00:15:16.590 --> 00:15:18.217
our expedited grid hardening efforts.

00:15:18.217 --> 00:15:21.270
And as Erik mentioned, we
use PSPS as a last resort.

00:15:21.270 --> 00:15:23.240
And to that end, we have developed

00:15:23.240 --> 00:15:27.190
a concentrated effort to
reduce the use of PSPS.

00:15:27.190 --> 00:15:28.940
Our customers have
high expectations for us,

00:15:28.940 --> 00:15:31.679
two of which are, to keep them safe,

00:15:31.679 --> 00:15:33.230
and deliver reliable electricity.

00:15:33.230 --> 00:15:35.150
So we will focus particular attention

00:15:35.150 --> 00:15:37.270
on frequently impacted
circuits that experience

00:15:37.270 --> 00:15:42.270
four or more PSPS
de-energizations since 2019.

00:15:42.740 --> 00:15:44.597
And the goal is to reduce the scope

00:15:44.597 --> 00:15:47.380
and or the customers
impacted, the frequency,

00:15:47.380 --> 00:15:50.010
and also the duration of these events.

00:15:50.010 --> 00:15:52.680
We do understand 2020 was
a particularly challenging year.

00:15:52.680 --> 00:15:55.480
And we must learn from these past events

00:15:55.480 --> 00:15:58.340
to improve the customer experience.

00:15:58.340 --> 00:16:00.550
So, our work scope for
expedited grid hardening

00:16:00.550 --> 00:16:02.017
includes 72 circuits.

00:16:02.017 --> 00:16:04.999
And we identified these
circuits on February 19th

00:16:04.999 --> 00:16:07.650
as part of the action plan.

00:16:07.650 --> 00:16:11.240
And we intend to accomplish
this expedited effort

00:16:11.240 --> 00:16:12.980
through four primary methods.

00:16:12.980 --> 00:16:15.370
And although there are other
options for grid hardening,

00:16:15.370 --> 00:16:17.870
our intent here with this effort is

00:16:17.870 --> 00:16:19.400
to ensure that we can deliver benefits

00:16:19.400 --> 00:16:21.760
before the peak 2021 fire season.

00:16:21.760 --> 00:16:24.030
So ultimately, this
is a multi-year effort

00:16:24.030 --> 00:16:27.850
to more extensively harden
these and other circuits as well.

00:16:27.850 --> 00:16:29.730
But this effort is focused on delivering

00:16:29.730 --> 00:16:32.453
certain achievable
mitigations by October 1.

00:16:33.880 --> 00:16:36.360
The first one we list here is,

00:16:36.360 --> 00:16:38.360
the first grid hardening
method we list here,

00:16:38.360 --> 00:16:40.330
is covering our bare wire.

00:16:40.330 --> 00:16:42.110
I think you've all heard this before,

00:16:42.110 --> 00:16:44.670
covered conductor helps
prevent unintentional contact

00:16:44.670 --> 00:16:46.740
from becoming an
ignition, by allowing things

00:16:46.740 --> 00:16:49.680
like tree branches,
palm fronds, other debris,

00:16:49.680 --> 00:16:50.980
to float in and out of our lines

00:16:50.980 --> 00:16:53.340
without igniting or
interrupting the circuit.

00:16:53.340 --> 00:16:55.600
The wind-driven debris can ignite,

00:16:55.600 --> 00:16:56.640
cause our wire to come down,

00:16:56.640 --> 00:16:59.430
and create the
potential for an ignition.

00:16:59.430 --> 00:17:00.470
And by covering the wire,

00:17:00.470 --> 00:17:03.060
the potential for this
occurring is greatly diminished.

00:17:03.060 --> 00:17:05.220
The benefit to our customers is that

00:17:05.220 --> 00:17:09.140
covering an entire
circuit or a circuit segment

00:17:09.140 --> 00:17:11.770
enables Edison to raise
wind speed thresholds,

00:17:11.770 --> 00:17:15.470
thereby eliminating some
de-energization events entirely,

00:17:15.470 --> 00:17:18.290
because the winds may never
reach the higher thresholds,

00:17:18.290 --> 00:17:20.340
or if it does occur, the wind speeds

00:17:20.340 --> 00:17:22.260
will likely occur later in the event.

00:17:22.260 --> 00:17:24.080
So, if you can imagine,
when the winds are elevating,

00:17:24.080 --> 00:17:25.600
it will occur later in the event.

00:17:25.600 --> 00:17:28.100
And then they'll also go
below the threshold sooner,

00:17:28.100 --> 00:17:31.020
and therefore shortening the
events that actually do occur.

00:17:31.020 --> 00:17:33.810
So this will have, and
Erik mentioned this earlier,

00:17:33.810 --> 00:17:37.330
reliability benefits beyond
only reducing PSPS,

00:17:37.330 --> 00:17:39.510
as wind events can
occur throughout the year,

00:17:39.510 --> 00:17:41.403
not just during PSPS events.

00:17:42.259 --> 00:17:44.630
The second method we mention here is

00:17:44.630 --> 00:17:46.530
installing automated switching devices,

00:17:46.530 --> 00:17:48.500
or automating existing devices,

00:17:48.500 --> 00:17:50.950
so that we can more
narrowly isolate the areas

00:17:50.950 --> 00:17:52.690
that are experiencing
the elevated wind speeds.

00:17:52.690 --> 00:17:55.400
So this was a focus area for us in 2020.

00:17:55.400 --> 00:17:57.830
And now expanding on
this effort, we continue

00:17:57.830 --> 00:18:02.430
to look at circuit segments
rather than entire circuits.

00:18:02.430 --> 00:18:05.200
And the benefit of
sectionalizing devices

00:18:05.200 --> 00:18:08.250
is to reduce the scope of an event.

00:18:08.250 --> 00:18:10.000
And also, these devices have the ability

00:18:10.000 --> 00:18:12.500
to reduce the duration for
some customers as well.

00:18:13.405 --> 00:18:16.680
The third method, expedited
grid hardening method,

00:18:16.680 --> 00:18:18.800
that we mention here is to review

00:18:18.800 --> 00:18:21.500
whether certain circuits
or circuit segments,

00:18:21.500 --> 00:18:23.860
based on local or recent changes
in environmental conditions

00:18:23.860 --> 00:18:27.400
can be removed from
PSPS' scope entirely.

00:18:27.400 --> 00:18:30.470
The example we list
here is a recent burn scar.

00:18:30.470 --> 00:18:33.390
It may not have been previously
factored into our modeling.

00:18:33.390 --> 00:18:35.100
And so we want to make
sure that we incorporate that.

00:18:35.100 --> 00:18:37.900
And if the fuel conditions
are not conducive

00:18:37.900 --> 00:18:41.040
for an ignition to occur
or for a fire to spread,

00:18:41.040 --> 00:18:43.117
then we may be able to exempt

00:18:43.117 --> 00:18:44.770
that portion of the circuit from PSPS.

00:18:44.770 --> 00:18:48.020
So with greater segmentation
through continued installation

00:18:48.020 --> 00:18:49.580
of these automated switching devices,

00:18:49.580 --> 00:18:52.500
this becomes a greater
possibility, as we can isolate

00:18:52.500 --> 00:18:55.710
particular areas that
may not be a concern.

00:18:55.710 --> 00:18:57.980
The benefits to customers
could be a reduction in scope

00:18:57.980 --> 00:19:01.900
or a reduction in the
frequency of PSPS events.

00:19:01.900 --> 00:19:04.500
The fourth method is
adding new weather stations,

00:19:04.500 --> 00:19:06.810
thereby improving our
situational awareness

00:19:06.810 --> 00:19:08.590
of actual field conditions.

00:19:08.590 --> 00:19:10.535
By adding more weather stations,

00:19:10.535 --> 00:19:13.200
particularly in areas with
increased segmentation,

00:19:13.200 --> 00:19:15.530
we can attribute weather
conditions more specifically

00:19:15.530 --> 00:19:17.870
to certain segments of a circuit.

00:19:17.870 --> 00:19:21.350
And we're also looking to
deploy mobile weather stations.

00:19:21.350 --> 00:19:24.376
We obviously can't
install weather stations

00:19:24.376 --> 00:19:27.550
in very large numbers throughout

00:19:27.550 --> 00:19:29.670
all the different areas of a circuit,

00:19:29.670 --> 00:19:31.550
but mobile weather
stations give us the ability

00:19:31.550 --> 00:19:34.020
to respond quickly to
changing conditions.

00:19:34.020 --> 00:19:37.240
So, this will not only add to
the weather reading capacity

00:19:37.240 --> 00:19:38.930
that we have, but
also provide the ability

00:19:38.930 --> 00:19:40.720
to get more accurate
live field conditions

00:19:40.720 --> 00:19:44.300
at a particular location
that we're worried about.

00:19:44.300 --> 00:19:46.240
The benefit here to customers is

00:19:46.240 --> 00:19:47.520
the potential reduction in scope,

00:19:47.520 --> 00:19:50.970
frequency, and duration
of certain PSPS events.

00:19:50.970 --> 00:19:53.770
So I want to add, also,
that although we have

00:19:53.770 --> 00:19:55.500
a concentrated effort to develop

00:19:55.500 --> 00:19:58.230
mitigation strategies
for the 72 circuits,

00:19:58.230 --> 00:20:00.860
this doesn't mean other
circuits are left behind.

00:20:00.860 --> 00:20:04.100
This expedited effort
represents probably about half

00:20:04.100 --> 00:20:06.140
of all the grid hardening
work we're doing in 2020.

00:20:06.140 --> 00:20:08.120
So I don't want to imply that we are

00:20:08.120 --> 00:20:10.430
ignoring other customers,
but I believe it's appropriate

00:20:10.430 --> 00:20:12.610
to focus these efforts on those

00:20:12.610 --> 00:20:14.900
that are experiencing
the most PSPS events,

00:20:14.900 --> 00:20:17.450
particularly over the
last couple of years.

00:20:17.450 --> 00:20:19.210
I'll close by just a quick update

00:20:19.210 --> 00:20:20.250
on our high level milestones,

00:20:20.250 --> 00:20:23.000
as we committed to in our
action plan on February 19th.

00:20:23.000 --> 00:20:25.010
We did identify a list of 72 circuits

00:20:25.010 --> 00:20:27.820
we are targeting for
expedited improvements.

00:20:27.820 --> 00:20:29.560
And from a geographical standpoint,

00:20:29.560 --> 00:20:31.370
these will be mostly in
communities that experience

00:20:31.370 --> 00:20:33.730
the strongest winds,
because that's where

00:20:33.730 --> 00:20:37.160
most PSPS de-energizations
have been occurring.

00:20:37.160 --> 00:20:38.550
And by June 1, we intend to implement

00:20:38.550 --> 00:20:40.940
our risk informed circuit exceptions.

00:20:40.940 --> 00:20:43.500
I'll note here, that although
this represents our effort

00:20:43.500 --> 00:20:46.480
to review presently
identified exception conditions,

00:20:46.480 --> 00:20:48.970
it's possible some of the
review work we're doing

00:20:48.970 --> 00:20:53.010
in our grid hardening, it may
also provide for exceptions.

00:20:53.010 --> 00:20:56.393
So the work here likely
will continue beyond June 1.

00:20:57.250 --> 00:20:59.150
And lastly, as I mentioned earlier,

00:20:59.150 --> 00:21:01.150
we're targeting to complete this work

00:21:01.150 --> 00:21:03.750
in time for peak 2021 wildfire season.

00:21:03.750 --> 00:21:06.340
So by October 1, we intend to complete

00:21:06.340 --> 00:21:08.050
the key expedited hardening work

00:21:08.050 --> 00:21:10.350
that we are targeting
as part of this effort.

00:21:10.350 --> 00:21:13.300
And I should note, there
are considerable obstacles.

00:21:13.300 --> 00:21:15.840
There's a lot of work to do
in a short amount of time.

00:21:15.840 --> 00:21:17.710
So quite a bit to overcome.

00:21:17.710 --> 00:21:20.070
But we have a team focused on this

00:21:20.070 --> 00:21:21.890
to ensure that we have
appropriate resources

00:21:21.890 --> 00:21:23.363
to help us complete the work.

00:21:24.680 --> 00:21:26.930
So with that, unless
there are questions,

00:21:26.930 --> 00:21:28.440
I'll hand it over to Tom Brady

00:21:28.440 --> 00:21:29.850
who will review in more detail

00:21:29.850 --> 00:21:32.543
our plan to execute
PSPS more effectively.

00:21:34.344 --> 00:21:36.539
<v ->Okay, thank you, Terry.</v>
<v ->President Batjer?</v>

00:21:36.539 --> 00:21:37.372
<v Marybel>Yes?</v>

00:21:37.372 --> 00:21:39.730
<v Martha>Can I ask a
couple follow-ups on that?</v>

00:21:39.730 --> 00:21:42.073
<v Marybel>Commissioner
Guzman Aceves, please.</v>

00:21:43.222 --> 00:21:45.363
<v ->And maybe we can
go back one slide?</v>

00:21:51.230 --> 00:21:55.433
You mentioned that
you've identified 72 circuits.

00:21:55.433 --> 00:21:56.830
<v Terry>Correct.</v>

00:21:56.830 --> 00:21:59.140
<v Martha>Has that been increased</v>

00:21:59.140 --> 00:22:01.840
from an effort that you've
done over the Winter,

00:22:01.840 --> 00:22:03.453
or is that what you had?

00:22:04.511 --> 00:22:09.060
Can you explain, is this
something that you've augmented

00:22:09.060 --> 00:22:12.810
given what happened last Fall Winter?

00:22:12.810 --> 00:22:15.593
Or is this what you were planning?

00:22:17.400 --> 00:22:19.620
<v Terry>Yeah, I would say both.</v>

00:22:19.620 --> 00:22:24.620
It's a focused effort on those
that have been most impacted.

00:22:25.220 --> 00:22:30.220
There was already, in scope,
mitigations that were planned.

00:22:31.580 --> 00:22:33.630
But some of these are
gonna need to be accelerated.

00:22:33.630 --> 00:22:36.300
Some of them will need to be augmented.

00:22:36.300 --> 00:22:38.110
Because as we reviewed the circuits,

00:22:38.110 --> 00:22:41.700
we were really looking for
opportunities where we could

00:22:41.700 --> 00:22:44.480
really make a difference
in this short amount of time.

00:22:44.480 --> 00:22:46.910
So, it's really a little bit of both.

00:22:46.910 --> 00:22:50.840
There was already covered
conductor scope in-flight,

00:22:50.840 --> 00:22:52.620
but I'll use it as an example.

00:22:52.620 --> 00:22:56.100
We may have had a
completion date of October.

00:22:56.100 --> 00:22:58.990
And for us, that was too late.

00:22:58.990 --> 00:23:03.950
So, we were looking to advance
some of the completion dates

00:23:03.950 --> 00:23:06.100
for the scope that may
have already been in-flight.

00:23:06.100 --> 00:23:08.930
But in re-reviewing these
circuits, with really a focus on

00:23:08.930 --> 00:23:11.790
how do we improve the PSPS experience,

00:23:11.790 --> 00:23:13.640
we were able to identify, in some cases,

00:23:13.640 --> 00:23:15.610
new covered conductor scope

00:23:15.610 --> 00:23:18.760
or new isolating devices
that we can install.

00:23:24.371 --> 00:23:26.020
<v ->Okay I'm not sure
I quite understand.</v>

00:23:26.020 --> 00:23:28.563
So prior to February,

00:23:30.110 --> 00:23:34.890
well, even prior to this,
let's say last six months,

00:23:34.890 --> 00:23:37.360
that you have previously had identified?

00:23:37.360 --> 00:23:42.360
So it sounds like you had
these same 72 circuits identified

00:23:42.380 --> 00:23:46.770
and you're just enhancing
your review of them?

00:23:46.770 --> 00:23:48.650
Or are you actually enhancing

00:23:48.650 --> 00:23:50.900
the amount of circuits
that you're reviewing?

00:23:51.970 --> 00:23:55.300
<v ->Many of the 72
had work in-flight</v>

00:23:55.300 --> 00:23:57.905
that work was planned for 2021.

00:23:57.905 --> 00:24:02.905
But in some cases we identified
new scope that we could add

00:24:03.140 --> 00:24:08.140
to what we were doing that
would improve, reduce the scope,

00:24:08.157 --> 00:24:10.460
the frequency and the
duration of PSPS events.

00:24:10.460 --> 00:24:13.610
So we augmented it with new scope.

00:24:13.610 --> 00:24:16.600
But we also, because some of it we felt

00:24:16.600 --> 00:24:19.550
was gonna complete too late in the year

00:24:19.550 --> 00:24:21.400
to really provide as much benefit,

00:24:21.400 --> 00:24:24.833
we accelerated the completion
date for some of that work.

00:24:26.080 --> 00:24:29.503
<v ->And what is an example of
segments that goes beyond,</v>

00:24:31.797 --> 00:24:34.833
beyond doing the,
covering the conductor?

00:24:35.940 --> 00:24:39.163
<v ->So it would include
some of the things</v>

00:24:39.163 --> 00:24:43.140
that I mentioned
earlier, like a new switch,

00:24:43.140 --> 00:24:46.960
an automated switch, at
a location that we thought

00:24:46.960 --> 00:24:51.110
could isolate customers that we believed

00:24:51.110 --> 00:24:55.260
may not be as impacted by the winds.

00:24:55.260 --> 00:24:57.220
So, if there's a
particular segment that,

00:24:57.220 --> 00:24:59.220
where we have a weather station,

00:24:59.220 --> 00:25:00.053
that we're really concerned about,

00:25:00.053 --> 00:25:03.060
but there may be another
portion of that circuit

00:25:03.060 --> 00:25:05.610
that we don't believe is experiencing

00:25:05.610 --> 00:25:07.610
the same level of wind speeds,

00:25:07.610 --> 00:25:12.320
we could add a new
automated sectionalizing device,

00:25:12.320 --> 00:25:15.170
automated switch, to give us the ability

00:25:15.170 --> 00:25:19.503
to only de-energize the
portion that we're worried about.

00:25:22.110 --> 00:25:24.320
<v ->Okay, but, in the
way you described it is</v>

00:25:24.320 --> 00:25:26.610
you're currently
assessing the feasibility.

00:25:26.610 --> 00:25:29.480
So you don't have like
a master description

00:25:29.480 --> 00:25:31.570
of all the investments that are

00:25:31.570 --> 00:25:35.080
gonna take place on
these 72 circuits yet?

00:25:35.080 --> 00:25:37.110
<v ->Yes, I'm sorry.</v>

00:25:37.110 --> 00:25:38.920
Yeah, it's really circuit by circuit.

00:25:38.920 --> 00:25:42.820
So we've gone through a
series of what we call deep dives,

00:25:42.820 --> 00:25:46.200
going through each circuit,
understanding the scope

00:25:46.200 --> 00:25:49.540
that's already in place,
and what more we could do

00:25:49.540 --> 00:25:54.380
to further improve the PSPS experience

00:25:54.380 --> 00:25:58.440
for the 2021 wildfire season.

00:25:58.440 --> 00:26:00.950
So, it really was starting with

00:26:00.950 --> 00:26:04.580
what we already have in
place, and then getting a team

00:26:04.580 --> 00:26:07.910
of people together, engineers
and various other folks,

00:26:07.910 --> 00:26:10.083
and looking at what we could do.

00:26:11.640 --> 00:26:13.980
Could we cover an entire segment?

00:26:13.980 --> 00:26:15.610
How much is remaining there?

00:26:15.610 --> 00:26:18.040
Could we add a new
weather station over here,

00:26:18.040 --> 00:26:20.480
where we think the
wind speeds aren't as--

00:26:20.480 --> 00:26:21.460
<v ->Okay, yeah.</v>

00:26:21.460 --> 00:26:23.573
So when are you gonna be done with that?

00:26:25.010 --> 00:26:28.370
<v ->So, identification of the
72 circuits is complete.</v>

00:26:28.370 --> 00:26:31.580
We're currently going
through a benefits assessment.

00:26:31.580 --> 00:26:33.743
So, we want to make sure the mitigations

00:26:33.743 --> 00:26:36.010
that we've identified will yield

00:26:36.010 --> 00:26:37.570
the type of benefits
that we're hoping for.

00:26:37.570 --> 00:26:40.233
And if not, we plan
to iterate and go back.

00:26:41.130 --> 00:26:46.130
But, so, at this point we're
going through that process.

00:26:46.938 --> 00:26:51.360
And the goal is to finish
all this work by October 1.

00:26:53.470 --> 00:26:56.180
<v ->Okay. And then help me
understand this June threshold.</v>

00:26:56.180 --> 00:26:59.040
So June is when you decide that some

00:26:59.040 --> 00:27:02.490
of these distinct investments

00:27:02.490 --> 00:27:05.483
or particular circuits
don't need to be included?

00:27:06.820 --> 00:27:08.267
<v ->Yeah.</v>

00:27:08.267 --> 00:27:10.740
So, the June is the exception process.

00:27:10.740 --> 00:27:14.930
So we have another team
looking through the circuits

00:27:14.930 --> 00:27:18.480
and identifying areas of a circuit

00:27:18.480 --> 00:27:20.690
that may not be a concern.

00:27:20.690 --> 00:27:23.650
The obvious one is a recent burn scar.

00:27:23.650 --> 00:27:25.718
So the fuels just aren't there.

00:27:25.718 --> 00:27:29.480
And if we're able to
isolate that segment,

00:27:29.480 --> 00:27:33.080
we may be able to
avoid putting that segment

00:27:33.080 --> 00:27:37.480
under PSPS for this
upcoming fire season.

00:27:37.480 --> 00:27:40.630
Other areas we look at might be

00:27:40.630 --> 00:27:43.930
if we can install a switch
at a particular location,

00:27:43.930 --> 00:27:46.650
maybe there is a portion
of it that runs through

00:27:47.760 --> 00:27:49.580
a developed area, like a parking lot,

00:27:49.580 --> 00:27:53.370
or just an area that
doesn't appear to have fuels

00:27:53.370 --> 00:27:56.210
that would be conducive to a fire.

00:27:56.210 --> 00:27:59.370
So, they're identifying those.

00:27:59.370 --> 00:28:02.330
And what we'll do is
submit them for exception.

00:28:02.330 --> 00:28:04.650
We'll just confirm, we'll
send somebody out in the field

00:28:04.650 --> 00:28:06.830
and confirm what we're
seeing on the maps,

00:28:06.830 --> 00:28:09.740
that in fact it is not an area

00:28:09.740 --> 00:28:12.113
that we should be
overly concerned about.

00:28:12.113 --> 00:28:13.990
And in some of these
cases, we'll have to install

00:28:13.990 --> 00:28:16.260
some additional sectionalizing devices

00:28:16.260 --> 00:28:18.880
to be able to isolate it,
because the segment

00:28:18.880 --> 00:28:20.610
that we currently have might extend

00:28:20.610 --> 00:28:24.120
from this non-concerning area up into,

00:28:24.120 --> 00:28:26.470
let's just say a wildfire area.

00:28:26.470 --> 00:28:29.210
So we may have to do
some additional work there,

00:28:29.210 --> 00:28:34.210
but the intent is to exclude
it from PSPS considerations.

00:28:38.640 --> 00:28:42.323
And that'll be completed
June 1, with our initial effort.

00:28:43.400 --> 00:28:45.680
I don't want to imply
that our work is ever done.

00:28:45.680 --> 00:28:48.830
If new opportunities are
identified post-June 1,

00:28:48.830 --> 00:28:52.373
our intent is to continue
on with that work.

00:28:55.300 --> 00:28:57.200
<v ->Okay, thank you
for clarifying that.</v>

00:28:58.460 --> 00:28:59.748
<v ->You're welcome.</v>

00:28:59.748 --> 00:29:02.860
<v Marybel>Terry, before we
go to Tom, I have a question.</v>

00:29:02.860 --> 00:29:04.890
This may be premature
in your presentation.

00:29:04.890 --> 00:29:09.890
So, if it is, you can
wait and address it later.

00:29:10.160 --> 00:29:12.550
But, in real-time, when you get

00:29:12.550 --> 00:29:16.010
right down to calling a PSPS,

00:29:17.674 --> 00:29:20.400
can someone during the
course of the presentation

00:29:20.400 --> 00:29:22.540
please walk me through the steps

00:29:22.540 --> 00:29:26.373
that are considered
before you actually execute?

00:29:27.230 --> 00:29:31.670
What are those decision
points that, you as a team,

00:29:31.670 --> 00:29:35.008
you and the executive team,

00:29:35.008 --> 00:29:38.393
what is it that you absolutely consider?

00:29:38.393 --> 00:29:41.440
And what we're talking about here is,

00:29:41.440 --> 00:29:43.840
I understand shortening the duration,

00:29:43.840 --> 00:29:48.350
trying to harden the system

00:29:49.250 --> 00:29:52.320
so fewer PSPS has have to be called.

00:29:52.320 --> 00:29:57.000
But I really want to get
a good, solid picture of,

00:29:57.000 --> 00:30:00.900
to sort of define, when we all say

00:30:00.900 --> 00:30:05.900
a PSPS is at the last resort.

00:30:06.230 --> 00:30:08.470
So I want to know what are those three

00:30:08.470 --> 00:30:10.540
or four or five decision points

00:30:10.540 --> 00:30:14.070
that will determine
that, okay, we gotta do it.

00:30:14.070 --> 00:30:17.510
So again, it may be
premature in your presentation.

00:30:17.510 --> 00:30:19.063
But I want us to get to that.

00:30:23.235 --> 00:30:24.550
<v ->I have a suggestion.</v>

00:30:25.540 --> 00:30:28.970
Maybe we can try to
address your question now.

00:30:28.970 --> 00:30:33.630
But I think there'll probably
be other pieces of information

00:30:33.630 --> 00:30:36.790
that might also help
inform as we go through

00:30:36.790 --> 00:30:38.670
our engagement with external parties

00:30:38.670 --> 00:30:40.543
and some of the other considerations.

00:30:41.700 --> 00:30:44.730
So, why don't we go ahead and start.

00:30:44.730 --> 00:30:47.950
And I'll start it off, and
I'll look to the team here,

00:30:47.950 --> 00:30:50.140
to supplement the discussion.

00:30:50.140 --> 00:30:55.140
So, like all other PSPS
events, it begins with a forecast.

00:30:55.140 --> 00:30:58.090
And we have a circuit
by circuit forecast

00:30:58.090 --> 00:31:00.010
for every one of our
distribution circuits,

00:31:00.010 --> 00:31:04.100
as well as our sub transmission
and our transmission lines.

00:31:04.100 --> 00:31:08.850
And as part of that, we
look out three to five days.

00:31:08.850 --> 00:31:12.700
But we do look at this line by line,

00:31:12.700 --> 00:31:15.728
as far as what we, first of all,

00:31:15.728 --> 00:31:19.700
is this a credible event
that's coming in, and if so,

00:31:19.700 --> 00:31:22.420
we start to look at anywhere
from our transmission

00:31:22.420 --> 00:31:24.300
and everything that's
downstream of that,

00:31:24.300 --> 00:31:26.970
as well as all of
our distribution lines.

00:31:26.970 --> 00:31:28.780
If we think there's a transmission

00:31:28.780 --> 00:31:32.960
or a sub transmission event,
that's potentially in scope,

00:31:32.960 --> 00:31:35.240
one of the other things
that we do is we perform

00:31:35.240 --> 00:31:37.630
what's called a reliability study.

00:31:37.630 --> 00:31:41.250
And so there's a distinctive
difference here between

00:31:41.250 --> 00:31:43.500
power systems that are
on the distribution systems

00:31:43.500 --> 00:31:46.773
that are radial that
directly feed our customers

00:31:46.773 --> 00:31:49.330
versus a network system that we have

00:31:49.330 --> 00:31:51.980
on the sub transmission
and the transmission lines.

00:31:51.980 --> 00:31:54.420
And generally the wind speed thresholds

00:31:54.420 --> 00:31:55.980
for those are higher.

00:31:55.980 --> 00:31:58.203
So, there's a lot fewer
lines that we have in scope.

00:31:58.203 --> 00:32:01.510
But, what we try to
identify is whether or not,

00:32:01.510 --> 00:32:04.300
the lines in scope, are
there other alternatives

00:32:04.300 --> 00:32:08.840
that we could use instead
if we got into an issue

00:32:08.840 --> 00:32:11.870
whereby we could
continue to maintain service

00:32:11.870 --> 00:32:16.670
to our customers, and if
needed, de-energize portions

00:32:16.670 --> 00:32:19.310
of our sub trans or transmission lines.

00:32:19.310 --> 00:32:24.080
So we, I guess the best
case scenario here is,

00:32:24.080 --> 00:32:26.350
if we do have to de-energize,

00:32:26.350 --> 00:32:28.530
that we're able to de-energize sections

00:32:28.530 --> 00:32:30.380
of our sub trans and transmission system

00:32:30.380 --> 00:32:32.963
without interrupting
service to our customers.

00:32:34.040 --> 00:32:36.200
On the distribution side,

00:32:36.200 --> 00:32:40.240
we have grown and adapted and evolved

00:32:40.240 --> 00:32:45.240
towards a segment by
segment, real-time decision,

00:32:45.280 --> 00:32:47.730
as opposed to circuit by circuit.

00:32:47.730 --> 00:32:51.250
So, this raises some complexities

00:32:51.250 --> 00:32:53.575
that I do want to talk about.

00:32:53.575 --> 00:32:57.070
So, when we think
about a larger scale event,

00:32:57.070 --> 00:32:59.910
and I'm just gonna
say, typically we'll see

00:32:59.910 --> 00:33:03.743
somewhere northward of 150
to 200 circuits on a large event.

00:33:04.780 --> 00:33:08.720
What that means real-time is that we are

00:33:08.720 --> 00:33:13.550
monitoring 700 plus segments,

00:33:13.550 --> 00:33:16.450
because of the way we
sectionalize the system.

00:33:16.450 --> 00:33:19.120
But, in anticipation of the event,

00:33:19.120 --> 00:33:22.950
we do what's called
pre-patrols of our system.

00:33:22.950 --> 00:33:24.700
And what a pre-patrol is,

00:33:24.700 --> 00:33:29.420
is armed with information
that we know about

00:33:29.420 --> 00:33:33.230
in terms of prior maintenance
items or other areas

00:33:33.230 --> 00:33:38.230
of concern that our field
resources are aware of,

00:33:38.480 --> 00:33:40.670
they perform a cursory review before

00:33:40.670 --> 00:33:42.980
the weather event begins to identify

00:33:42.980 --> 00:33:46.350
if there's any issues on our system

00:33:46.350 --> 00:33:49.110
that needs to be remediated quickly.

00:33:49.110 --> 00:33:54.100
So, we call those pre-patrols,
and they are designed

00:33:54.100 --> 00:33:56.890
to be both conducted on the distribution

00:33:56.890 --> 00:33:59.540
as well as our sub trans
and our transmission system.

00:34:00.430 --> 00:34:03.886
So that's information that
is also taken into account.

00:34:03.886 --> 00:34:06.640
When we get into the
weather event itself,

00:34:06.640 --> 00:34:10.260
we look at what the size
of the event is going to be.

00:34:10.260 --> 00:34:12.460
If this is gonna be a small event,

00:34:12.460 --> 00:34:13.890
where we have a handful of circuits,

00:34:13.890 --> 00:34:15.920
a medium or a large size event,

00:34:15.920 --> 00:34:18.760
'cause that determines
the resources we need,

00:34:18.760 --> 00:34:21.772
the coverage we need in our
incident management team.

00:34:21.772 --> 00:34:24.870
It determines how much
in advance we need

00:34:24.870 --> 00:34:27.320
to stand up and get ready for an event.

00:34:27.320 --> 00:34:30.770
So, in small events, we
want our field resources

00:34:30.770 --> 00:34:32.430
and our teams to be stood up two hours

00:34:32.430 --> 00:34:34.330
before the period of concern when the.

00:34:39.070 --> 00:34:42.790
What we've seen in 2020 is
weather can come up very quickly,

00:34:42.790 --> 00:34:45.380
particularly in those larger events.

00:34:45.380 --> 00:34:47.357
So when we get into the actual event

00:34:47.357 --> 00:34:49.540
and the period of concern,
everybody's monitoring,

00:34:49.540 --> 00:34:52.160
we have live observers in the field.

00:34:52.160 --> 00:34:54.390
That's when we look at, well,

00:34:54.390 --> 00:34:56.566
and I'll take us a step back,

00:34:56.566 --> 00:34:59.460
prior to that beginning, we establish,

00:34:59.460 --> 00:35:02.340
if it is a larger event,
how might we prioritize

00:35:02.340 --> 00:35:05.330
de-energization segment by segment?

00:35:05.330 --> 00:35:08.060
'Cause one of the things
that we have to be able to do

00:35:08.060 --> 00:35:12.450
is not only exercise and
understand our thresholds,

00:35:12.450 --> 00:35:14.700
we have to manage the event responsibly.

00:35:14.700 --> 00:35:17.740
So, if we think that we're gonna face

00:35:17.740 --> 00:35:19.950
a large number of de-energizations

00:35:19.950 --> 00:35:22.730
subsequently happening
one after the other,

00:35:22.730 --> 00:35:25.820
because we were looking at
everything segment by segment,

00:35:25.820 --> 00:35:29.560
we look at how might we
prioritize that based on risk.

00:35:29.560 --> 00:35:32.690
So we establish some
alert levels for our threshold,

00:35:32.690 --> 00:35:36.500
that if we really started
to see events escalate,

00:35:36.500 --> 00:35:39.260
that we would take more
decisive actions sooner

00:35:39.260 --> 00:35:42.100
when we forecast our
threshold to be breached,

00:35:42.100 --> 00:35:44.040
but in larger numbers.

00:35:44.040 --> 00:35:46.480
So, when we get into the actual event,

00:35:46.480 --> 00:35:50.120
we look to our Business
Resiliency Department

00:35:50.120 --> 00:35:52.950
to see if there's any
issues that have come up.

00:35:52.950 --> 00:35:56.860
In our Public Safety Department,
we do the notifications.

00:35:56.860 --> 00:35:58.570
We identify if there's anything that

00:35:58.570 --> 00:36:01.420
we need to respond to
before the wind event begins.

00:36:01.420 --> 00:36:04.990
And what we've done most recently is,

00:36:04.990 --> 00:36:07.130
in the larger event in January,

00:36:07.130 --> 00:36:10.730
we reached out to all of the
hospitals and COVID centers

00:36:10.730 --> 00:36:15.460
that we knew were gonna be
potentially a significant issue.

00:36:15.460 --> 00:36:17.270
So, we wanted to understand if they had

00:36:17.270 --> 00:36:19.633
resiliency plans in
place, if there were things

00:36:19.633 --> 00:36:21.870
that we needed to do
differently in our system,

00:36:21.870 --> 00:36:26.480
in terms of de-energizations,
and do we need a stand-by

00:36:26.480 --> 00:36:30.020
to provide generation if we have to.

00:36:30.020 --> 00:36:32.660
So then when you get
into the event we look at

00:36:32.660 --> 00:36:35.520
both our FPI, as well
as our wind speeds,

00:36:35.520 --> 00:36:37.920
and input from our life observers.

00:36:37.920 --> 00:36:40.580
One of the things we noted in December,

00:36:40.580 --> 00:36:42.230
which is a bit challenging,

00:36:42.230 --> 00:36:46.680
is sometimes it's followed
by a precipitation event,

00:36:46.680 --> 00:36:49.330
or there's been some moisture

00:36:49.330 --> 00:36:52.070
coming in earlier expected to dry out.

00:36:52.070 --> 00:36:55.460
So we also track what's
called a weather rating

00:36:55.460 --> 00:36:58.940
on all of our circuits to
understand whether or not

00:36:58.940 --> 00:37:02.030
the FPI information we have,

00:37:02.030 --> 00:37:04.540
if there's any questions around it.

00:37:04.540 --> 00:37:07.160
So there have been times when moisture

00:37:07.160 --> 00:37:10.500
has settled in and we've backed off.

00:37:10.500 --> 00:37:12.590
But there's been other
times when the wind speeds

00:37:12.590 --> 00:37:14.780
have increased faster than expected

00:37:14.780 --> 00:37:17.480
and we have to take action sooner.

00:37:17.480 --> 00:37:21.030
So, we then, our
dashboards are looking at

00:37:21.030 --> 00:37:24.090
all of our weather stations
and all of our segments.

00:37:24.090 --> 00:37:27.350
And we're tracking each one and sort it

00:37:27.350 --> 00:37:30.380
by worst case situation,

00:37:30.380 --> 00:37:32.590
down to the ones we
don't have to worry about.

00:37:32.590 --> 00:37:35.882
Operations teams are in
constant communication

00:37:35.882 --> 00:37:38.830
with our partners, with our
business resiliency folks,

00:37:38.830 --> 00:37:40.490
and with the incident commander,

00:37:40.490 --> 00:37:42.650
so when a decision has to be made,

00:37:42.650 --> 00:37:45.870
we authorize imminent
notifications to be issued.

00:37:45.870 --> 00:37:48.600
And then, if all the
conditions then meet,

00:37:48.600 --> 00:37:51.170
that's when we take
action to de-energize.

00:37:51.170 --> 00:37:52.640
Now I was a little bit long winded,

00:37:52.640 --> 00:37:55.670
but I'm hoping to at least
hit most of the high points.

00:37:55.670 --> 00:37:59.223
And there's a lot of nuances
in and throughout the process.

00:38:00.230 --> 00:38:01.280
<v Marybel>One quick followup,</v>

00:38:01.280 --> 00:38:03.693
and then we will turn to Tom.

00:38:04.690 --> 00:38:09.530
The wind speed, speeds,
that you are gauge,

00:38:09.530 --> 00:38:11.970
that help in your decision-making,

00:38:11.970 --> 00:38:14.823
is that 35 miles an hour, sustained?

00:38:16.030 --> 00:38:21.030
<v ->So we use three
different levels for threshold.</v>

00:38:22.950 --> 00:38:25.510
Most of them are based either on

00:38:25.510 --> 00:38:28.810
the 99th percentile of
historical wind speeds.

00:38:28.810 --> 00:38:31.080
And sometimes they're using

00:38:31.080 --> 00:38:33.330
the National Weather
Service Wind Advisory level

00:38:33.330 --> 00:38:36.623
of 31 miles an hour sustained
with 46 mile an hour gusts.

00:38:38.270 --> 00:38:40.270
They're also gonna be ones that

00:38:40.270 --> 00:38:42.380
historically are slightly above that,

00:38:42.380 --> 00:38:44.220
but we'll use the
National Weather Service

00:38:44.220 --> 00:38:47.800
where we have
designated the highest risk,

00:38:47.800 --> 00:38:51.002
either by tier or by
consequence modeling.

00:38:51.002 --> 00:38:54.170
And then the third set that I referenced

00:38:54.170 --> 00:38:57.013
was ones that we have identified

00:38:57.013 --> 00:39:00.780
have particular outage increases

00:39:00.780 --> 00:39:03.723
or rates of outages for
particular wind speeds.

00:39:04.640 --> 00:39:06.370
But for the most part, they're either

00:39:06.370 --> 00:39:08.060
based on the 99th percentile

00:39:08.060 --> 00:39:10.360
or the National Weather
Service Wind Advisory.

00:39:13.300 --> 00:39:15.020
<v Marybel>Okay, thank you.</v>

00:39:15.020 --> 00:39:17.490
We can move on now, I think.

00:39:17.490 --> 00:39:18.740
<v Tom>All right, sound check.</v>

00:39:18.740 --> 00:39:20.440
This is Tom, can you hear me okay?

00:39:23.200 --> 00:39:24.870
<v Marybel>Yes, we can.</v>

00:39:24.870 --> 00:39:26.230
<v Tom>Thank you for that.</v>

00:39:26.230 --> 00:39:29.500
So, good afternoon, President
Batjer and Commissioners.

00:39:29.500 --> 00:39:31.100
I'm going to open on this slide

00:39:31.100 --> 00:39:33.080
by describing our ongoing efforts

00:39:33.080 --> 00:39:35.480
to work towards addressing the variance

00:39:35.480 --> 00:39:38.860
between notification
and de-energizations

00:39:38.860 --> 00:39:40.840
through improving the precision

00:39:40.840 --> 00:39:44.540
and the granularity of
our forecasting capabilities.

00:39:44.540 --> 00:39:47.440
I will also provide an update
on our continued efforts

00:39:47.440 --> 00:39:50.747
to improve the transparency
and the effectiveness

00:39:50.747 --> 00:39:53.000
of our communication and engagement

00:39:53.000 --> 00:39:55.160
with our emergency management partners

00:39:55.160 --> 00:39:58.193
prior to, during, and after events.

00:39:59.740 --> 00:40:01.990
SCE de-energizes circuits based on

00:40:01.990 --> 00:40:04.760
actual observed conditions in the field

00:40:04.760 --> 00:40:06.550
and not on forecasts.

00:40:06.550 --> 00:40:08.190
To help reduce the variance between

00:40:08.190 --> 00:40:11.010
notification and de-energizations,

00:40:11.010 --> 00:40:13.600
it is critical for our
forecasts to align

00:40:13.600 --> 00:40:17.380
as closely as possible with
actual conditions in the field

00:40:17.380 --> 00:40:19.559
during the period of concern

00:40:19.559 --> 00:40:22.770
SCE currently has two supercomputers

00:40:22.770 --> 00:40:26.520
that run a twice daily, high
resolution weather forecast

00:40:26.520 --> 00:40:29.060
for each of our PSPS circuits.

00:40:29.060 --> 00:40:32.620
These forecasts are
further refined in events

00:40:32.620 --> 00:40:34.580
by our expert fire scientists

00:40:34.580 --> 00:40:36.600
and teams of experienced meteorologists

00:40:36.600 --> 00:40:39.620
to identify the circuits
that are forecast

00:40:39.620 --> 00:40:43.619
to reach levels that create
an imminent fire hazard risk.

00:40:43.619 --> 00:40:46.440
We have initiated the
procurement process

00:40:46.440 --> 00:40:49.140
to bring on board two
additional supercomputers

00:40:49.140 --> 00:40:51.200
which will allow us to
double the resolution

00:40:51.200 --> 00:40:53.010
of our weather model by going from

00:40:53.010 --> 00:40:55.780
two kilometers to one kilometer.

00:40:55.780 --> 00:40:59.390
This will allow our meteorologists
and fire science team

00:40:59.390 --> 00:41:01.880
to predict weather
conditions more accurately

00:41:01.880 --> 00:41:04.820
throughout the complex
and dynamic topographies

00:41:04.820 --> 00:41:07.483
and microclimates
where our circuits exist.

00:41:08.490 --> 00:41:10.780
Additional supercomputing resources

00:41:10.780 --> 00:41:13.047
will also allow us to
provide our meteorologists

00:41:13.047 --> 00:41:15.940
with access to more forecast output,

00:41:15.940 --> 00:41:18.470
or a broader range of possible outcomes

00:41:18.470 --> 00:41:20.180
to base their predictions off,

00:41:20.180 --> 00:41:22.623
also known as ensemble forecasting.

00:41:23.470 --> 00:41:25.410
We are developing
machine learning models

00:41:25.410 --> 00:41:27.920
for 50 weather station locations,

00:41:27.920 --> 00:41:30.290
starting with highly impacted circuits

00:41:30.290 --> 00:41:32.740
and where forecasts have
been the least accurate.

00:41:33.720 --> 00:41:36.600
Beginning later in the
Summer and into next year

00:41:36.600 --> 00:41:37.960
we will begin developing models

00:41:37.960 --> 00:41:39.660
for all of our weather stations,

00:41:39.660 --> 00:41:42.020
representing some of
our longer term efforts

00:41:42.020 --> 00:41:45.610
to train and to retrain
our models over time

00:41:45.610 --> 00:41:47.940
as each station accumulates more data

00:41:47.940 --> 00:41:50.053
to produce a more accurate result.

00:41:51.480 --> 00:41:54.580
Switching gears and moving
down to the middle of the slide,

00:41:54.580 --> 00:41:56.330
let me start by reiterating,

00:41:56.330 --> 00:41:59.655
that nothing is more
important to us at SCE

00:41:59.655 --> 00:42:02.250
than the safety and the
wellbeing of our customers

00:42:02.250 --> 00:42:04.370
during de-energization events.

00:42:04.370 --> 00:42:07.540
We are continuing to build on
the longstanding relationships

00:42:07.540 --> 00:42:09.940
we have established with our county

00:42:09.940 --> 00:42:12.340
and state emergency management partners

00:42:12.340 --> 00:42:15.540
to mutually plan for
and help mitigate against

00:42:15.540 --> 00:42:18.293
public safety risks during PSPS events.

00:42:19.280 --> 00:42:22.000
We have scheduled
meetings with all of the county

00:42:22.000 --> 00:42:25.220
emergency management
officials in high fire risk areas,

00:42:25.220 --> 00:42:28.750
and those meetings will
occur prior to March 31st.

00:42:28.750 --> 00:42:33.220
We will use the discussions
to solicit feedback,

00:42:33.220 --> 00:42:35.020
listen to understand,

00:42:35.020 --> 00:42:37.870
and identify ways that we can
communicate more effectively

00:42:37.870 --> 00:42:41.140
prior to, during, and after events.

00:42:41.140 --> 00:42:44.290
We will use these learnings
to update our procedures

00:42:44.290 --> 00:42:46.170
for more effectively communicating

00:42:46.170 --> 00:42:48.920
with our emergency
management agency partners

00:42:48.920 --> 00:42:50.570
during these events.

00:42:50.570 --> 00:42:52.510
We are also meeting
monthly with our partners

00:42:52.510 --> 00:42:56.040
at the California State
Warning Center at Cal OES

00:42:56.040 --> 00:42:58.120
to align our in-event communication

00:42:58.120 --> 00:43:00.510
and information sharing protocols.

00:43:00.510 --> 00:43:02.300
We are committed to
providing our partners

00:43:02.300 --> 00:43:04.320
with the right information,

00:43:04.320 --> 00:43:07.240
at the right time, and in the right way.

00:43:07.240 --> 00:43:08.690
Now I'm gonna pause for questions

00:43:08.690 --> 00:43:10.600
before turning it over to Jessica

00:43:10.600 --> 00:43:12.050
to discuss some of our other updates

00:43:12.050 --> 00:43:15.253
in the area of effective PSPS execution.

00:43:17.630 --> 00:43:18.840
<v Marybel>Tom, did you say you all</v>

00:43:18.840 --> 00:43:23.103
are meeting with OES once a month?

00:43:25.330 --> 00:43:26.900
<v Tom>So we've scheduled meetings</v>

00:43:26.900 --> 00:43:29.770
with all of the county
emergency management officials

00:43:29.770 --> 00:43:31.890
to occur prior to March 31st.

00:43:31.890 --> 00:43:34.920
So sort of a pre-wildfire
season opportunity

00:43:34.920 --> 00:43:37.130
to connect and think and listen

00:43:37.130 --> 00:43:39.130
and make improvements to our protocols.

00:43:39.130 --> 00:43:40.920
And then we are meeting with Cal OES,

00:43:40.920 --> 00:43:43.770
the Warning Center folks monthly,

00:43:43.770 --> 00:43:46.070
from now and through
the start of fire season.

00:43:53.270 --> 00:43:54.540
<v Marybel>I don't see
any other questions.</v>

00:43:54.540 --> 00:43:56.740
So, I guess you can go ahead.

00:43:56.740 --> 00:43:58.820
<v Tom>All right, over to Jessica.</v>

00:43:58.820 --> 00:44:00.080
<v ->All right thank you, Tom.</v>

00:44:00.080 --> 00:44:02.220
Good afternoon, Commissioners.

00:44:02.220 --> 00:44:04.210
Thank you for the opportunity to share

00:44:04.210 --> 00:44:07.360
how we are prioritizing
our customers' experience

00:44:07.360 --> 00:44:10.080
during PSPS events, which also includes

00:44:10.080 --> 00:44:13.830
informing our customers
at every critical step.

00:44:13.830 --> 00:44:16.750
When PSPS events occur
in the same timeframe

00:44:16.750 --> 00:44:20.880
as other outages, such as
a storm or a rotating outage,

00:44:20.880 --> 00:44:24.370
this can be confusing to our
customers to have to decipher

00:44:24.370 --> 00:44:27.440
between these outages
for status updates.

00:44:27.440 --> 00:44:30.451
So, I wanted to share
that by June of this year

00:44:30.451 --> 00:44:34.080
on sce.com, customers, those
that are our account holders

00:44:34.080 --> 00:44:36.170
and those that are not account holders,

00:44:36.170 --> 00:44:38.070
they're gonna find it easier to navigate

00:44:38.070 --> 00:44:42.360
from our homepage to look up
the status of their PSPS event.

00:44:42.360 --> 00:44:44.730
And they're not going to
have to determine up front

00:44:44.730 --> 00:44:47.610
which type of outage
they are looking up.

00:44:47.610 --> 00:44:50.800
So customers can also
continue to go directly

00:44:50.800 --> 00:44:55.573
to sce.com/psps to get
their PSPS specific updates.

00:44:56.630 --> 00:45:00.000
We also understand that we
can improve on notifications.

00:45:00.000 --> 00:45:01.410
We heard a lot about this

00:45:01.410 --> 00:45:04.060
from our customers as a pain point,

00:45:04.060 --> 00:45:05.990
and we need to minimize the variance

00:45:05.990 --> 00:45:09.606
between notifications
and de-energizations,

00:45:09.606 --> 00:45:13.090
misnotifications and
the sources of confusion

00:45:13.090 --> 00:45:17.173
and redundant messages
that lead to notification fatigue.

00:45:18.130 --> 00:45:21.460
So, to improve the
notifications experience,

00:45:21.460 --> 00:45:24.590
we have initiated an
end to end analysis,

00:45:24.590 --> 00:45:25.830
which will be informed

00:45:25.830 --> 00:45:28.560
by our customers and our stakeholders.

00:45:28.560 --> 00:45:30.330
We are looking at improvements

00:45:30.330 --> 00:45:33.290
to our internal processes and tools,

00:45:33.290 --> 00:45:35.210
especially during the day of an event

00:45:35.210 --> 00:45:36.830
when we may have several circuits

00:45:36.830 --> 00:45:40.800
hits threshold simultaneously
in large-scale events.

00:45:40.800 --> 00:45:44.600
We're committed to improve
the precision of timeliness

00:45:44.600 --> 00:45:47.240
and the content of our notifications.

00:45:47.240 --> 00:45:50.080
A few of our near-term
deliverables include

00:45:50.080 --> 00:45:53.170
completing an examination of the causes

00:45:53.170 --> 00:45:57.370
of any 2020 notification
issued by the end of March,

00:45:57.370 --> 00:45:59.200
which will inform the design

00:45:59.200 --> 00:46:03.990
of our future internal practices
and digital tools by May.

00:46:03.990 --> 00:46:05.870
We will also complete a review

00:46:05.870 --> 00:46:08.800
of the entire notification experience

00:46:08.800 --> 00:46:10.880
from the customer's point of view.

00:46:10.880 --> 00:46:14.560
And identify future state
improvements by May,

00:46:14.560 --> 00:46:19.160
such as messaging and the
reduction of notifications fatigue

00:46:19.160 --> 00:46:23.140
by reviewing the frequency
of notifications sent out.

00:46:23.140 --> 00:46:26.950
Lastly, we will focus
on migrating customers

00:46:26.950 --> 00:46:30.800
to premise level alerts
to improve notification

00:46:30.800 --> 00:46:32.933
and information clarity by June.

00:46:34.360 --> 00:46:37.170
So, unless there are any questions,

00:46:37.170 --> 00:46:39.053
I can move on to the next slide.

00:46:40.810 --> 00:46:42.170
<v Marybel>As a follow-up,</v>

00:46:42.170 --> 00:46:44.410
oh, and then I'll turn to
Commissioner Shiroma.

00:46:44.410 --> 00:46:45.990
Would you just repeat what you said

00:46:45.990 --> 00:46:49.348
in terms of premise discussion?

00:46:49.348 --> 00:46:51.825
I mean premise decision?
<v ->Sure, yeah.</v>

00:46:51.825 --> 00:46:53.670
<v Marybel>As to where
the customers are?</v>

00:46:53.670 --> 00:46:55.730
Could you elaborate on that a bit?

00:46:55.730 --> 00:46:58.640
<v ->Yeah, I can elaborate on that.</v>

00:46:58.640 --> 00:47:02.540
Basically right now, customers
that are not account holders

00:47:02.540 --> 00:47:04.740
or even if they are account holders,

00:47:04.740 --> 00:47:06.550
we give them the choice
that they can signup

00:47:06.550 --> 00:47:08.580
for what we call zip code alerts.

00:47:08.580 --> 00:47:11.610
And zip code alerts
are easy to sign up for,

00:47:11.610 --> 00:47:16.081
and customers can get an
alert via the phone text or email.

00:47:16.081 --> 00:47:18.918
But what creates confusion is that

00:47:18.918 --> 00:47:21.060
a customer may get a zip code alert,

00:47:21.060 --> 00:47:24.860
which is based on all circuits
versus a premise level alert,

00:47:24.860 --> 00:47:27.450
which is based on just your address.

00:47:27.450 --> 00:47:30.750
And so premise level
alerts are more specific.

00:47:30.750 --> 00:47:34.240
So we believe that zip
code alerts, while convenient,

00:47:34.240 --> 00:47:37.520
are creating some
confusion for our customers.

00:47:37.520 --> 00:47:39.521
So we'd like to migrate those

00:47:39.521 --> 00:47:43.700
who are enrolled in zip code
alerts to premise level alerts.

00:47:43.700 --> 00:47:46.390
<v Marybel>We had many
comments in our January meeting,</v>

00:47:46.390 --> 00:47:50.570
if you listened in, about
how confusing it was

00:47:50.570 --> 00:47:54.623
to have zip code
alerts, so I hope this is a,

00:47:55.690 --> 00:47:58.813
definitely an improvement
for your customers.

00:48:00.070 --> 00:48:03.010
Again, this question
may be a little premature,

00:48:03.010 --> 00:48:06.310
but you've talked about
who you're meeting with,

00:48:06.310 --> 00:48:08.430
and the different
things that you're doing

00:48:08.430 --> 00:48:10.950
to make improvements
by the end of March,

00:48:10.950 --> 00:48:13.050
and then by the end of May.

00:48:13.050 --> 00:48:18.050
Are you planning any customer
town hall type style meetings

00:48:19.220 --> 00:48:24.005
or customer touches so
that you are hearing directly

00:48:24.005 --> 00:48:27.549
from your customers, not
just from emergency managers

00:48:27.549 --> 00:48:30.520
managers and county folks and the state,

00:48:30.520 --> 00:48:32.520
all of which are very important,

00:48:32.520 --> 00:48:34.390
but I'm concerned about how much

00:48:34.390 --> 00:48:36.590
you are actually getting input

00:48:36.590 --> 00:48:39.423
from those that have been
most impacted by the PSPS?

00:48:40.970 --> 00:48:43.250
<v ->Yeah, thank you.
And great question.</v>

00:48:43.250 --> 00:48:46.300
So, as I mentioned, we are
informing our recommendations

00:48:46.300 --> 00:48:48.630
with actual customer feedback.

00:48:48.630 --> 00:48:50.820
At the end of November, we initiated

00:48:50.820 --> 00:48:54.927
a new PSPS survey,
and that survey is called

00:48:54.927 --> 00:48:57.080
"Our Voice of the Customer Program",

00:48:57.080 --> 00:49:01.180
where customers have been
impacted by PSPS events,

00:49:01.180 --> 00:49:03.080
they are invited to take a survey

00:49:03.080 --> 00:49:06.360
and we can get their immediate feedback.

00:49:06.360 --> 00:49:10.460
We're also gonna plan to do
research on whatever messages

00:49:10.460 --> 00:49:13.870
we come up with to improve
the notification experience

00:49:13.870 --> 00:49:16.500
and have our customers directly inform

00:49:16.500 --> 00:49:18.390
the recommendations that we're making.

00:49:18.390 --> 00:49:20.940
So we have several
different touch points

00:49:20.940 --> 00:49:24.343
and opportunities for
customers to inform our plans.

00:49:26.070 --> 00:49:28.700
<v ->Yeah, Jessica, one
thing I'd add is that,</v>

00:49:28.700 --> 00:49:30.820
I think on slide nine,
we do have a listing

00:49:30.820 --> 00:49:32.720
of town hall style meetings

00:49:34.300 --> 00:49:35.950
with our most impacted communities.

00:49:35.950 --> 00:49:39.216
We're gonna host three
virtual community meetings

00:49:39.216 --> 00:49:42.880
far some of our most impacted
communities this month.

00:49:46.710 --> 00:49:49.200
And then the following
of those will be done

00:49:49.200 --> 00:49:51.470
by the end of the second quarter.

00:49:51.470 --> 00:49:52.710
<v Marybel>Okay, that'll
be very important.</v>

00:49:52.710 --> 00:49:55.567
Last thing, and then I'll turn
to Commissioner Shiroma.

00:49:55.567 --> 00:50:00.567
Just as FYI, we had over an
hour, maybe it was two hours,

00:50:00.730 --> 00:50:05.160
of comments in the January
meeting from your customers.

00:50:05.160 --> 00:50:06.470
And I'm just gonna say,

00:50:06.470 --> 00:50:08.830
not one mentioned this customer survey,

00:50:08.830 --> 00:50:11.780
that they had filled it out
or had been notified of it

00:50:11.780 --> 00:50:16.041
or were aware of it, just FYI.

00:50:16.041 --> 00:50:17.791
Commissioner Shiroma.

00:50:18.913 --> 00:50:20.620
<v ->Thank you, President Batjer.</v>

00:50:20.620 --> 00:50:25.620
Yeah, at that January
26th public session,

00:50:26.633 --> 00:50:28.480
we heard from a lot of people.

00:50:28.480 --> 00:50:32.480
And we heard from
electeds, from, I think,

00:50:32.480 --> 00:50:33.890
just about every single
city council member

00:50:33.890 --> 00:50:36.410
of Acton Town spoke.

00:50:36.410 --> 00:50:40.300
We also heard from
electeds from Simi Valley, Ojai,

00:50:40.300 --> 00:50:44.920
Stanton, Orange County,
Malibu, and so forth.

00:50:44.920 --> 00:50:47.580
From Senator Hueso and Senator Stern,

00:50:47.580 --> 00:50:50.300
various assembly members, and so forth.

00:50:50.300 --> 00:50:51.973
So, my question is,

00:50:54.330 --> 00:50:56.570
you're describing a
pretty massive effort,

00:50:56.570 --> 00:51:01.570
but in that effort, and your 72 circuits

00:51:01.820 --> 00:51:05.840
that you've made as a higher priority,

00:51:05.840 --> 00:51:10.840
are you going back and communicating

00:51:11.370 --> 00:51:15.230
with these electeds who are
representing their communities,

00:51:15.230 --> 00:51:18.610
juxtaposed against
what your priorities are

00:51:18.610 --> 00:51:21.673
with these circuits, and
what does it mean for them.

00:51:22.655 --> 00:51:25.720
In other words, are you
getting granular on this

00:51:25.720 --> 00:51:29.370
in going back to the people
who bothered to phone in

00:51:29.370 --> 00:51:31.983
and talk to us on the 26th?

00:51:33.859 --> 00:51:35.660
And not only these jurisdictions,

00:51:35.660 --> 00:51:37.460
but really all over as far as

00:51:38.680 --> 00:51:41.028
what's you're prioritizing for this work

00:51:41.028 --> 00:51:43.293
and what does it
mean, actually, for them?

00:51:45.220 --> 00:51:46.570
Whoever wants to answer,

00:51:46.570 --> 00:51:48.470
whether it's Jessica or somebody else.

00:51:51.600 --> 00:51:53.499
<v ->Yeah, I'll chime in here.</v>

00:51:53.499 --> 00:51:55.380
So we are meeting with a
number of elected officials,

00:51:55.380 --> 00:51:58.253
and notifications is one
of the things that we cover.

00:51:59.739 --> 00:52:01.730
One of the things that we've heard

00:52:01.730 --> 00:52:05.340
and some of the input
is around confusion,

00:52:05.340 --> 00:52:07.980
because potentially
at the end of the year

00:52:07.980 --> 00:52:10.330
we have so many back-to-back events

00:52:10.330 --> 00:52:13.915
that I think in one case,
one of the county supervisors

00:52:13.915 --> 00:52:15.730
sort of reported that
there was sort of like

00:52:15.730 --> 00:52:19.810
36 notifications that they
had received for a single event.

00:52:19.810 --> 00:52:24.570
So that kind of speaks to,
one, we are getting feedback,

00:52:24.570 --> 00:52:28.120
but the second thing
is there may be a way

00:52:28.120 --> 00:52:32.435
that we have to communicate
with our local government

00:52:32.435 --> 00:52:37.020
and our public safety partners
in a way that also simplifies

00:52:38.410 --> 00:52:40.870
what is happening during the event.

00:52:40.870 --> 00:52:43.500
And then our customers also have to have

00:52:43.500 --> 00:52:47.420
a level of simplification
and lack of redundancy

00:52:47.420 --> 00:52:50.500
and clarity in the
messaging to them as well.

00:52:50.500 --> 00:52:53.720
So, I think feedback we'll take

00:52:53.720 --> 00:52:56.970
and we'll continue to ask
more and more information

00:52:56.970 --> 00:53:00.070
about what we could do
to improve our response.

00:53:00.070 --> 00:53:02.030
But the short answer
to your question is, yes,

00:53:02.030 --> 00:53:03.260
that is one of the pieces,

00:53:03.260 --> 00:53:05.690
in addition to the grid hardening work

00:53:05.690 --> 00:53:07.540
that's going on in each of the areas.

00:53:09.510 --> 00:53:10.820
<v ->Yeah, I think it's important.</v>

00:53:10.820 --> 00:53:12.930
Somebody on your team needs to go back

00:53:12.930 --> 00:53:15.540
and listen to the public comments

00:53:16.560 --> 00:53:21.560
and overlay that with
the engineering priorities

00:53:22.870 --> 00:53:25.150
and software priorities that you set out

00:53:26.030 --> 00:53:28.730
towards making sure that you've got,

00:53:28.730 --> 00:53:33.087
you've linked up the human
condition with the technical.

00:53:35.435 --> 00:53:37.163
Thank you, President Batjer.

00:53:37.163 --> 00:53:39.323
Thank you, Erik.

00:53:39.323 --> 00:53:41.380
<v Marybel>Thank you,
Commissioner Shiroma.</v>

00:53:41.380 --> 00:53:44.180
Okay, seeing no other questions,

00:53:44.180 --> 00:53:46.323
back to you, I think, Jessica.

00:53:47.240 --> 00:53:49.180
<v ->Okay, thank you.</v>

00:53:49.180 --> 00:53:52.495
So, I'm gonna go ahead
and move on to this slide here.

00:53:52.495 --> 00:53:55.360
As Erik shared in his opening remarks,

00:53:55.360 --> 00:53:58.560
SCE will help our customers' communities

00:53:58.560 --> 00:54:01.820
and partners mitigate
the impact of PSPS,

00:54:01.820 --> 00:54:03.550
providing programs and services,

00:54:03.550 --> 00:54:07.020
especially for our most
vulnerable customers.

00:54:07.020 --> 00:54:11.550
So we have expanded our Critical
Care Backup Battery program

00:54:11.550 --> 00:54:14.640
to all eligible Medical
Baseline customers

00:54:14.640 --> 00:54:17.080
that reside in a high fire risk area

00:54:17.080 --> 00:54:19.850
and are enrolled in CARE or FERA.

00:54:19.850 --> 00:54:23.330
So, this year we are not
facing the same contributors

00:54:23.330 --> 00:54:27.220
to a delayed start as we
did last year to this program.

00:54:27.220 --> 00:54:30.390
So, I just want to briefly
mention that in 2020,

00:54:30.390 --> 00:54:33.240
with impacts from
COVID-19, we experienced

00:54:33.240 --> 00:54:36.540
some inventory challenges
and we took a more conservative

00:54:36.540 --> 00:54:39.780
marketing approach to
reduce in-person contact.

00:54:39.780 --> 00:54:42.060
And this year, we have inventory.

00:54:42.060 --> 00:54:45.570
We are supported by a more
robust marketing program

00:54:45.570 --> 00:54:48.110
to match our expanded population.

00:54:48.110 --> 00:54:51.040
We've already initiated
marketing for this program,

00:54:51.040 --> 00:54:53.230
with a combination of direct mail,

00:54:53.230 --> 00:54:55.680
email, and outbound phone calls.

00:54:55.680 --> 00:54:58.440
So each eligible
customer will now receive

00:54:58.440 --> 00:55:01.500
multiple contact attempts,
and we'll also send

00:55:01.500 --> 00:55:03.760
second and third follow-up letters

00:55:03.760 --> 00:55:06.460
to followup those phone call attempts.

00:55:06.460 --> 00:55:08.720
And then we're also
going to be partnering

00:55:08.720 --> 00:55:10.680
with local and tribal government

00:55:10.680 --> 00:55:13.020
and community based organizations

00:55:13.020 --> 00:55:16.200
to reach and enroll as
many customers as we can.

00:55:16.200 --> 00:55:19.244
So for example, we have
been finalizing messaging

00:55:19.244 --> 00:55:22.500
that will go into a March
newsletter that will be sent

00:55:22.500 --> 00:55:26.803
to all of our 1,600 network
CBO agencies just as a start.

00:55:29.020 --> 00:55:32.000
And we're going to be
routinely tracking our progress

00:55:32.000 --> 00:55:34.700
and taking proactive mitigation measures

00:55:34.700 --> 00:55:37.210
to support customer participation.

00:55:37.210 --> 00:55:39.400
And we'll also measure
customer satisfaction

00:55:39.400 --> 00:55:41.713
with our programs on a monthly basis.

00:55:42.550 --> 00:55:45.850
So this month, we're also promoting

00:55:45.850 --> 00:55:48.820
all of our other backup
battery solutions, such as

00:55:48.820 --> 00:55:52.890
our online marketplace portable
batteries for our customers,

00:55:52.890 --> 00:55:56.290
and generators for those
that rely on electricity

00:55:56.290 --> 00:55:59.430
to pump water in their
home or businesses.

00:55:59.430 --> 00:56:00.460
And with the approval

00:56:00.460 --> 00:56:03.530
of our Self-Generation
Incentive program,

00:56:03.530 --> 00:56:06.310
marketing education,
and outreach advice letter,

00:56:06.310 --> 00:56:08.910
we're launching
marketing efforts in April

00:56:08.910 --> 00:56:11.500
to promote the Equity
Resiliency Incentive

00:56:11.500 --> 00:56:14.590
for residential and
non-residential customers,

00:56:14.590 --> 00:56:17.023
which also supports
our vulnerable customers.

00:56:18.230 --> 00:56:22.150
And then lastly, for
community resiliency,

00:56:22.150 --> 00:56:23.640
we're working with groups--
<v ->Jessica?</v>

00:56:23.640 --> 00:56:24.473
<v Jessica>Yes?</v>

00:56:24.473 --> 00:56:26.860
<v ->Jessica, this is a
Cliff Rechtschaffen.</v>

00:56:26.860 --> 00:56:29.853
Can I ask you some follow-up questions,

00:56:29.853 --> 00:56:32.150
if I may--
<v ->Absolutely.</v>

00:56:32.150 --> 00:56:33.563
<v ->On the backup program.</v>

00:56:34.520 --> 00:56:38.440
At the hearing in January,

00:56:38.440 --> 00:56:40.910
you said that you
have provided batteries

00:56:40.910 --> 00:56:43.650
for 830 critical care customers.

00:56:43.650 --> 00:56:48.650
And your goal was to
reach 3,000 to 4,000

00:56:48.830 --> 00:56:50.343
in high fire start areas.

00:56:51.520 --> 00:56:55.202
So where are you, I assume
that's not a different goal

00:56:55.202 --> 00:56:57.833
than what you just articulated.

00:56:59.040 --> 00:57:04.040
So you said you've expanded
from 2,500 to 12,000 customers.

00:57:05.940 --> 00:57:10.940
I'm not sure, I guess
we should just level set.

00:57:12.230 --> 00:57:13.970
What is your goal, what does it mean

00:57:13.970 --> 00:57:16.390
that you've expanded the program?

00:57:16.390 --> 00:57:18.590
You extended eligibility,
but do you still have

00:57:18.590 --> 00:57:23.010
a goal to reach 3,000 to
4,000 customers directly?

00:57:23.010 --> 00:57:26.080
And are you any farther along

00:57:26.080 --> 00:57:30.543
than providing batteries for
830 customers at this point?

00:57:31.417 --> 00:57:34.650
<v ->Yeah, so you're correct
that we are expanding</v>

00:57:34.650 --> 00:57:38.531
the eligibility from about
2,500 critical care customers

00:57:38.531 --> 00:57:42.360
to about 12,000 Medical
Baseline customers.

00:57:42.360 --> 00:57:46.110
So our goal is to be able to promote

00:57:46.110 --> 00:57:49.830
so that all eligible customers
are aware of this program

00:57:49.830 --> 00:57:52.960
with multiple contact
attempts by Edison.

00:57:52.960 --> 00:57:56.950
And we are forecasting
that we may get around

00:57:56.950 --> 00:58:00.300
3,000 to 4,000 batteries this year,

00:58:00.300 --> 00:58:02.130
based on what we have experienced

00:58:02.130 --> 00:58:04.980
and our conversations
with the other IOUs.

00:58:04.980 --> 00:58:06.270
But again, I just want to end with,

00:58:06.270 --> 00:58:09.610
our goal is really not to have
a certain number in mind,

00:58:09.610 --> 00:58:12.130
but it's to reach all of
our eligible customers

00:58:12.130 --> 00:58:15.280
for this program, because
we know how critical it is.

00:58:15.280 --> 00:58:17.770
And we are really working with

00:58:17.770 --> 00:58:21.750
community-based organizations
and promoting these programs

00:58:21.750 --> 00:58:23.760
with our local and tribal governments

00:58:23.760 --> 00:58:25.563
and our upcoming meetings as well.

00:58:28.050 --> 00:58:31.350
Oh, and I'm sorry, I forgot to
answer your other question.

00:58:31.350 --> 00:58:35.270
We are about over
1,000 batteries enrolled,

00:58:35.270 --> 00:58:39.090
and we are now ramping up the marketing

00:58:39.090 --> 00:58:40.880
for the eligible base.

00:58:40.880 --> 00:58:45.830
And so the, about,
over 1,000 so far,

00:58:45.830 --> 00:58:48.550
it's really just with the
critical care customers,

00:58:48.550 --> 00:58:52.023
because we just started
on the eligible population.

00:58:53.910 --> 00:58:55.740
<v ->If I'm understanding
you correctly,</v>

00:58:55.740 --> 00:58:57.723
you're expanding eligibility.

00:58:58.580 --> 00:59:00.950
You want to offer it to 12,000.

00:59:00.950 --> 00:59:04.340
You believe it's realistic that you'll,

00:59:04.340 --> 00:59:08.213
3,000 to 4,000 customers will
take advantage of the program?

00:59:09.170 --> 00:59:10.003
<v ->That's right.</v>

00:59:11.210 --> 00:59:14.800
<v ->Okay. Let me ask
you a little bit more.</v>

00:59:14.800 --> 00:59:18.140
By the way, are these
ratepayer funded programs

00:59:18.140 --> 00:59:20.093
or shareholder funded programs?

00:59:22.505 --> 00:59:24.393
<v ->They are ratepayer
funded programs.</v>

00:59:26.580 --> 00:59:31.520
<v ->And let me ask you what
do you offer the customers</v>

00:59:31.520 --> 00:59:35.200
if it's a SCE specific program?

00:59:35.200 --> 00:59:40.200
We're familiar with the SGIP
Equity Resilience program,

00:59:40.290 --> 00:59:44.270
since that's subject to
Commission directive, of course.

00:59:44.270 --> 00:59:48.787
And the goal there is for
Medical Baseline customers

00:59:48.787 --> 00:59:50.740
and customers in
disadvantaged communities

00:59:50.740 --> 00:59:53.210
to get a rebate that's
essentially equivalent

00:59:53.210 --> 00:59:56.000
to the cost of a backup battery

00:59:56.000 --> 00:59:58.670
so that it's fully subsidized.

00:59:58.670 --> 01:00:02.750
Is that the case for
the backup equipment,

01:00:02.750 --> 01:00:04.730
the batteries that you offer

01:00:04.730 --> 01:00:06.673
to your critical care customers?

01:00:08.240 --> 01:00:09.605
<v ->Yes, that's correct.</v>

01:00:09.605 --> 01:00:11.226
<v ->Fully subsidized product?</v>

01:00:11.226 --> 01:00:12.760
<v ->Fully subsidized, free battery,</v>

01:00:12.760 --> 01:00:14.180
with a three-year warranty,

01:00:14.180 --> 01:00:17.083
as well as a 200 watt solar panel.

01:00:19.049 --> 01:00:20.823
<v ->Okay. Thank you.</v>

01:00:21.665 --> 01:00:22.498
<v ->Mm hm.</v>

01:00:22.498 --> 01:00:24.870
<v Marybel>The corrective
action plan, Jessica,</v>

01:00:24.870 --> 01:00:27.470
says that you will be doing
the mailing and emailing

01:00:27.470 --> 01:00:29.390
about the battery backup programs,

01:00:29.390 --> 01:00:32.580
but battery vendors will
be doing the actual calling.

01:00:32.580 --> 01:00:34.930
So you all won't be
contacting the customers,

01:00:34.930 --> 01:00:37.500
it'll be a third party or a vendor?

01:00:37.500 --> 01:00:41.019
Is that gonna be terribly
confusing to your customers?

01:00:41.019 --> 01:00:42.280
<v ->Not necessarily.</v>

01:00:42.280 --> 01:00:44.690
We do mention in our
letter to our customers

01:00:44.690 --> 01:00:47.960
that a qualified contractor
will be calling the customer.

01:00:47.960 --> 01:00:49.830
We also provide the
number for the customer

01:00:49.830 --> 01:00:52.300
to call the contractor themselves.

01:00:52.300 --> 01:00:56.030
We have four contractors
that are our ESA contractors,

01:00:56.030 --> 01:00:58.270
Energy Savings Assistance program.

01:00:58.270 --> 01:01:00.080
So they're very familiar

01:01:00.080 --> 01:01:02.900
with vulnerable customer populations.

01:01:02.900 --> 01:01:04.940
One of our contractors is also

01:01:04.940 --> 01:01:07.053
a community-based organization as well.

01:01:09.020 --> 01:01:11.820
<v ->Jessica, I just want to confirm</v>

01:01:11.820 --> 01:01:13.923
what you told me just a moment before,

01:01:14.920 --> 01:01:19.920
because I haven't, it says
that on your marketplace,

01:01:20.270 --> 01:01:22.821
there's the list of available batteries

01:01:22.821 --> 01:01:27.821
varies in cost from $600 to $1,400,

01:01:29.060 --> 01:01:31.770
but both have a $500 rebate

01:01:32.860 --> 01:01:35.430
depending on the customer status.

01:01:35.430 --> 01:01:37.260
But, you're telling me that they're,

01:01:37.260 --> 01:01:40.750
in fact you're providing the full cost

01:01:40.750 --> 01:01:44.113
of the battery to the customers.

01:01:45.280 --> 01:01:46.437
<v ->Right.</v>

01:01:46.437 --> 01:01:50.190
Commissioner, we have
various different battery programs.

01:01:50.190 --> 01:01:53.020
So the ones you're referring
to on our marketplace,

01:01:53.020 --> 01:01:54.400
those are for a rebate.

01:01:54.400 --> 01:01:56.600
They're not for the fully subsidized.

01:01:56.600 --> 01:02:00.740
The batteries available for our
Critical Care Backup program

01:02:00.740 --> 01:02:04.040
is fully subsidized, and
the cost for those batteries

01:02:04.040 --> 01:02:07.253
range from $2,000.00 to $5,000.00.

01:02:08.910 --> 01:02:10.690
<v ->And then one final question,</v>

01:02:10.690 --> 01:02:14.570
I heard you say, unlike in the
Fall, there was not a problem

01:02:14.570 --> 01:02:17.190
with backup inventory in
terms of actually getting

01:02:17.190 --> 01:02:19.293
the batteries delivered to California.

01:02:21.720 --> 01:02:23.170
<v Jessica>That's for
the Critical Care</v>

01:02:23.170 --> 01:02:24.670
Battery Backup program.

01:02:24.670 --> 01:02:27.660
With the manufacturer
that we have partnered with,

01:02:27.660 --> 01:02:30.130
they now have a Utah
facility that will help

01:02:30.130 --> 01:02:33.130
facilitate distribution and inventory.

01:02:33.130 --> 01:02:36.410
The issues that we had were more towards

01:02:37.560 --> 01:02:39.673
the beginning to the
middle of last year.

01:02:40.830 --> 01:02:41.663
<v ->Thank you.</v>

01:02:47.100 --> 01:02:49.900
<v Marybel>Okay, Jessica, I
think you can go ahead.</v>

01:02:49.900 --> 01:02:50.733
<v ->Okay.</v>

01:02:50.733 --> 01:02:53.760
I just want to end on
one last point on this slide,

01:02:53.760 --> 01:02:56.650
which is that for community resiliency,

01:02:56.650 --> 01:02:58.960
we're working with community leaders

01:02:58.960 --> 01:03:02.350
in certain remote areas
to enable backup power

01:03:02.350 --> 01:03:05.000
as part of our Resiliency Zones pilot.

01:03:05.000 --> 01:03:08.000
So four sites are
currently under construction

01:03:08.000 --> 01:03:10.390
and we are working with
local and tribal governments

01:03:10.390 --> 01:03:13.090
to identify additional sites.

01:03:13.090 --> 01:03:14.940
And we will identify certain

01:03:14.940 --> 01:03:17.690
remote community resource centers

01:03:17.690 --> 01:03:21.890
to enable onsite backup
power so that they can continue

01:03:21.890 --> 01:03:23.900
to provide service to the community

01:03:23.900 --> 01:03:28.240
if that CRC site is
impacted by a PSPS event.

01:03:28.240 --> 01:03:31.310
And so today we're
working with three CRCs

01:03:31.310 --> 01:03:33.870
and enabling backup power.

01:03:33.870 --> 01:03:36.620
And we're identifying
additional sites by June.

01:03:36.620 --> 01:03:39.810
Som are there any last questions

01:03:39.810 --> 01:03:42.430
before we go onto the next slide?

01:03:42.430 --> 01:03:44.809
<v ->I have a question. Thanks.</v>

01:03:44.809 --> 01:03:49.103
So, in your corrective
action plan, you outline

01:03:49.103 --> 01:03:54.103
that you have 56 community
resource centers under contract

01:03:55.020 --> 01:03:59.800
and nine of the CCVs, the mobile vans.

01:03:59.800 --> 01:04:04.230
So how are the other
community resource centers,

01:04:04.230 --> 01:04:06.450
other than the ones you just outlined,

01:04:06.450 --> 01:04:08.130
that are gonna have
on-site backup power?

01:04:08.130 --> 01:04:12.320
How are the other centers
powered, or are they outside?

01:04:12.320 --> 01:04:15.703
Or you said they're
outside of the PSPS zone?

01:04:17.490 --> 01:04:19.585
<v ->Yes, good question.</v>

01:04:19.585 --> 01:04:22.480
So, we are utilizing the thought

01:04:22.480 --> 01:04:25.010
of enabling backup power for those sites

01:04:25.010 --> 01:04:28.170
that are in certain
remote areas thinking that

01:04:28.170 --> 01:04:31.670
they might be more prone
towards our PSPS events,

01:04:31.670 --> 01:04:34.480
versus some of our other
sites are more adjacent

01:04:34.480 --> 01:04:38.020
to PSPS events and
they're sited in such a way

01:04:38.020 --> 01:04:40.213
that we can utilize them during PSPS.

01:04:43.530 --> 01:04:44.363
<v ->Thank you.</v>

01:04:45.870 --> 01:04:46.703
<v ->Sure.</v>

01:04:48.417 --> 01:04:51.410
Okay, we can go on to this slide here.

01:04:52.660 --> 01:04:54.050
So, I want to just talk about

01:04:54.050 --> 01:04:58.430
that SCE understands
our partners and customers

01:04:58.430 --> 01:05:00.980
need to be informed about PSPS.

01:05:00.980 --> 01:05:03.280
And so our marketing campaign this year

01:05:03.280 --> 01:05:07.690
focuses on educating customers
and the public on PSPS,

01:05:07.690 --> 01:05:10.680
including the conditions
that trigger a PSPS,

01:05:10.680 --> 01:05:14.930
how to prepare, and how to
access information about events,

01:05:14.930 --> 01:05:17.480
including signing up for notifications,

01:05:17.480 --> 01:05:19.170
and all the available programs,

01:05:19.170 --> 01:05:21.790
rebates, and services that we offer.

01:05:21.790 --> 01:05:24.010
So, I wanted to mention that by April,

01:05:24.010 --> 01:05:27.910
we will have new ads
to refresh our marketing

01:05:27.910 --> 01:05:32.280
to improve customer awareness
of our available programs,

01:05:32.280 --> 01:05:35.490
and to provide clear and
concise language on mitigation,

01:05:35.490 --> 01:05:38.867
preparedness, and community investments.

01:05:38.867 --> 01:05:41.130
And our new ads will be informed

01:05:41.130 --> 01:05:43.093
by customer message testing.

01:05:44.790 --> 01:05:47.100
And then for our most
vulnerable customers,

01:05:47.100 --> 01:05:50.310
SCE will be expanding the verification

01:05:50.310 --> 01:05:52.390
of notifications deliveries

01:05:52.390 --> 01:05:55.750
during PSPS events to Medical Baseline

01:05:55.750 --> 01:05:59.800
and self-certified
vulnerable customers by July.

01:05:59.800 --> 01:06:01.860
And we'll expand marketing to promote

01:06:01.860 --> 01:06:04.893
the Medical Baseline
program starting this month.

01:06:05.900 --> 01:06:09.580
To better identify the
needs of AFN customers,

01:06:09.580 --> 01:06:13.910
we are partnering with members
of the AFN Statewide Council.

01:06:13.910 --> 01:06:16.560
And next month, SCE will initiate

01:06:16.560 --> 01:06:19.060
the development of a research study.

01:06:19.060 --> 01:06:23.190
And by July, we will have
a web page that will enable

01:06:23.190 --> 01:06:27.170
customers to self-certify
as vulnerable online,

01:06:27.170 --> 01:06:30.050
update contact information, and receive

01:06:30.050 --> 01:06:33.343
helpful information on
programs and services.

01:06:35.640 --> 01:06:38.490
And keeping our customers
informed about PSPS

01:06:38.490 --> 01:06:41.540
is a partnership with
public safety partners,

01:06:41.540 --> 01:06:44.670
stakeholders, local
and tribal governments.

01:06:44.670 --> 01:06:46.900
And by June, SCE will launch

01:06:46.900 --> 01:06:51.140
a public safety partner
portal to improve coordination

01:06:51.140 --> 01:06:54.720
in the planning and in-event response.

01:06:54.720 --> 01:06:57.840
Similar to PG&amp;E's
portal, SCE will provide

01:06:57.840 --> 01:07:02.360
user login access to information,
and for planning purposes,

01:07:02.360 --> 01:07:05.010
the portal will provide circuit maps,

01:07:05.010 --> 01:07:08.610
a summary of potentially
impacted customers,

01:07:08.610 --> 01:07:13.610
PSPS policies, procedures,
and sample notifications.

01:07:15.350 --> 01:07:18.510
And for event information,
SCE will provide

01:07:18.510 --> 01:07:21.350
event specific information and maps,

01:07:21.350 --> 01:07:24.839
PSPS outage and restoration areas,

01:07:24.839 --> 01:07:28.253
a list of affected customers,
and situation reports.

01:07:29.880 --> 01:07:32.190
And then lastly, SCE engages

01:07:32.190 --> 01:07:34.450
with local and tribal governments

01:07:34.450 --> 01:07:37.200
and public safety partners
throughout the year

01:07:37.200 --> 01:07:40.860
to share information and
to receive ongoing feedback

01:07:40.860 --> 01:07:44.000
on improvement and
collaboration opportunities.

01:07:44.000 --> 01:07:46.300
So we are having one
of our quarterly meetings

01:07:46.300 --> 01:07:49.320
with our PSPS working groups this week

01:07:49.320 --> 01:07:51.760
and the Advisory Board next week.

01:07:51.760 --> 01:07:54.640
And we'll be specifically
seeking additional feedback

01:07:54.640 --> 01:07:58.230
on the action plan that we
just filed with the Commission.

01:07:58.230 --> 01:08:00.720
And on our next steps
slide, Erik will provide

01:08:00.720 --> 01:08:03.463
more information on
other upcoming meetings.

01:08:04.350 --> 01:08:07.440
So, that's all I had, unless
there are any other questions,

01:08:07.440 --> 01:08:10.023
I was gonna turn it
over back to Tom Brady.

01:08:11.010 --> 01:08:13.020
<v Marybel>I have a quick
question on your followup</v>

01:08:13.020 --> 01:08:15.270
on your public safety partner portal,

01:08:15.270 --> 01:08:17.550
and you just referenced PG&amp;E.

01:08:17.550 --> 01:08:21.127
One of the issues, very
much improved by the way,

01:08:21.127 --> 01:08:25.280
that they had a portal
between 2019 and 2020.

01:08:25.280 --> 01:08:30.280
But one of the concerns that
folks had, that I'm recalling,

01:08:30.500 --> 01:08:32.990
was that the information on the portal

01:08:32.990 --> 01:08:37.200
needed to be kept up-to-date, timely,

01:08:37.200 --> 01:08:39.850
and as useful as possible.

01:08:39.850 --> 01:08:42.800
And that was a bit
of a struggle, I think.

01:08:42.800 --> 01:08:47.050
And the other thing we
all need to keep in mind,

01:08:47.050 --> 01:08:52.050
is oftentimes, in the areas
where you have a PS,

01:08:52.140 --> 01:08:57.140
you have people who,
because of the lack of electricity,

01:08:57.140 --> 01:09:02.140
they have no access to their computers,

01:09:02.300 --> 01:09:04.923
they have no access to telephones.

01:09:06.610 --> 01:09:11.610
So it's a real safety issue, of
course, and communication.

01:09:13.214 --> 01:09:15.670
And we have to keep that in mind.

01:09:15.670 --> 01:09:18.130
And I'm hoping that you're communicating

01:09:18.130 --> 01:09:20.720
very closely, along
the way, as you're doing

01:09:20.720 --> 01:09:24.430
all of these different
preparations for 2021 fire season,

01:09:24.430 --> 01:09:27.920
with the telecommunications companies

01:09:27.920 --> 01:09:30.363
that are in your service territory.

01:09:32.210 --> 01:09:33.560
<v Jessica>Yes, thank you.</v>

01:09:35.150 --> 01:09:37.010
We do meet on a monthly basis

01:09:37.010 --> 01:09:39.777
with our critical
infrastructure customers.

01:09:39.777 --> 01:09:41.560
And we are planning to meet, actually,

01:09:41.560 --> 01:09:44.433
with our telecom partners
by the end of this month.

01:09:52.477 --> 01:09:55.820
<v Martha>President Batjer,
can I ask a follow up to that?</v>

01:09:55.820 --> 01:09:57.870
<v Marybel>Of course, please.</v>

01:09:57.870 --> 01:10:00.320
<v ->Yeah, and I think we've heard</v>

01:10:00.320 --> 01:10:01.800
different things in the past.

01:10:01.800 --> 01:10:05.910
In some cases, the utilities
have expressed concern

01:10:05.910 --> 01:10:09.430
with not being able to identify
the right points of contact

01:10:09.430 --> 01:10:13.070
at the telecommunication
providers with them.

01:10:13.070 --> 01:10:14.973
And then we hear the inverse.

01:10:15.992 --> 01:10:18.336
And can you talk a little bit about

01:10:18.336 --> 01:10:21.430
what are the topics you're
gonna be talking about?

01:10:21.430 --> 01:10:22.650
And what's the work plan?

01:10:22.650 --> 01:10:26.380
Are you getting specific,
as an example, to talk about

01:10:26.380 --> 01:10:30.350
opportunities for
coordinated backup power,

01:10:30.350 --> 01:10:33.850
coordinated locations
on keeping towers lit,

01:10:33.850 --> 01:10:36.433
at a minimum, for wireless connectivity?

01:10:37.330 --> 01:10:40.550
There's already an overlap
with your infrastructure.

01:10:40.550 --> 01:10:44.410
Is there a more specific set of planning

01:10:44.410 --> 01:10:46.210
that you could be doing
with these providers

01:10:46.210 --> 01:10:50.083
so that customers
can at least retain their,

01:10:51.303 --> 01:10:54.213
as much communication
and connectivity as possible?

01:10:56.230 --> 01:10:59.080
<v ->Yes, I think that our
overall general approach</v>

01:10:59.080 --> 01:11:00.730
is that we want to first start off

01:11:00.730 --> 01:11:03.830
with listening to what
the pain points are.

01:11:03.830 --> 01:11:05.380
And we also want to integrate

01:11:05.380 --> 01:11:10.380
the new CPUC decision on
resiliency for telecom providers.

01:11:10.610 --> 01:11:14.910
We have a business customer division

01:11:14.910 --> 01:11:18.076
that meets with these critical customers

01:11:18.076 --> 01:11:20.170
and our Business Customer Division

01:11:20.170 --> 01:11:23.610
will be meeting to
discuss and help enable

01:11:23.610 --> 01:11:27.400
the resiliency plans for
each of these customers.

01:11:27.400 --> 01:11:30.850
And so, I imagine that as
the agenda gets developed

01:11:30.850 --> 01:11:33.010
for this first meeting
at the end of March,

01:11:33.010 --> 01:11:37.100
we'll be getting specific
as to how we can

01:11:37.100 --> 01:11:40.073
best support and partner
with our telecom customers.

01:11:43.240 --> 01:11:46.610
<v ->And just as an example,
you mention you're targeting</v>

01:11:48.140 --> 01:11:51.430
these 72 circuits where
you would be reviewing

01:11:51.430 --> 01:11:54.233
the possibility of how
to mitigate the PSPSes,

01:11:54.233 --> 01:11:57.250
that you have identified these circuits

01:11:57.250 --> 01:11:59.910
as likely PSPS areas.

01:11:59.910 --> 01:12:03.430
Do you have a plan with the
telecommunication providers

01:12:03.430 --> 01:12:04.780
for each of those circuits?

01:12:06.809 --> 01:12:08.330
<v ->I think I might
have to reach out</v>

01:12:08.330 --> 01:12:10.970
to some of the others on this panel

01:12:10.970 --> 01:12:13.063
to help out with that question.

01:12:13.063 --> 01:12:15.140
<v Tom>Hey, Jessica, it's Tom Brady.</v>

01:12:15.140 --> 01:12:17.930
I'll just add that in 2020, we did meet

01:12:17.930 --> 01:12:20.020
with the major telecom providers

01:12:20.020 --> 01:12:22.010
within our service territory,

01:12:22.010 --> 01:12:24.760
in coordination with our
Business Customer Division,

01:12:24.760 --> 01:12:27.470
and did provide those telecom companies

01:12:27.470 --> 01:12:30.360
with a list of their most
frequently impacted circuits

01:12:30.360 --> 01:12:32.630
to assist with resiliency planning,

01:12:32.630 --> 01:12:35.460
understanding that although
weather conditions can change,

01:12:35.460 --> 01:12:36.940
what's occurred in the past is often

01:12:36.940 --> 01:12:39.820
a good predictor of future PSPS impacts.

01:12:39.820 --> 01:12:43.721
So we'll look to do that again in 2021

01:12:43.721 --> 01:12:46.310
to help the telecom providers

01:12:46.310 --> 01:12:48.530
prioritize their resiliency efforts

01:12:48.530 --> 01:12:51.370
in the locations that are most at risk

01:12:51.370 --> 01:12:53.327
for potential de-energization.

01:12:59.018 --> 01:13:00.760
<v ->And do they meet with you,</v>

01:13:00.760 --> 01:13:03.040
along with the
emergency first responders

01:13:03.040 --> 01:13:05.404
that you are coordinating with?

01:13:05.404 --> 01:13:06.433
Are they at the table as well?

01:13:07.960 --> 01:13:10.050
<v Tom>So when we have the monthly,</v>

01:13:10.050 --> 01:13:11.630
or not the monthly, when
we have our meetings

01:13:11.630 --> 01:13:14.580
with the county emergency
management agencies

01:13:14.580 --> 01:13:16.660
that are gonna happen before March 31st,

01:13:16.660 --> 01:13:18.820
the telecom providers
aren't currently invited.

01:13:18.820 --> 01:13:20.600
But I will share that
the telecom providers

01:13:20.600 --> 01:13:24.160
are included in our working
groups and advisory boards.

01:13:24.160 --> 01:13:26.360
And so that's an opportunity to work

01:13:26.360 --> 01:13:29.320
through lessons learned
and solicit feedback

01:13:29.320 --> 01:13:32.160
and sort of an information sharing forum

01:13:32.160 --> 01:13:35.973
with multiple partners
in the same forum.

01:13:42.660 --> 01:13:44.200
<v Marybel>Commissioner Shiroma.</v>

01:13:44.200 --> 01:13:45.033
<v ->Thank you.</v>

01:13:45.033 --> 01:13:46.820
So Jessica, I think you mentioned

01:13:46.820 --> 01:13:50.470
that your advisory group
is meeting this week?

01:13:50.470 --> 01:13:55.251
And would you describe
who's on the advisory,

01:13:55.251 --> 01:13:59.223
which entities are represented
on that advisory group?

01:14:01.699 --> 01:14:04.123
<v ->Yes, give me one moment.</v>

01:14:09.906 --> 01:14:14.656
<v ->And maybe a little back up
on how you chose this group?</v>

01:14:19.270 --> 01:14:22.240
<v ->Okay, so we are starting with</v>

01:14:22.240 --> 01:14:25.120
the working groups,
Commissioner, this week.

01:14:25.120 --> 01:14:27.420
I know you're asking
about the advisory group,

01:14:27.420 --> 01:14:29.250
but maybe I'll just provide some context

01:14:29.250 --> 01:14:31.150
on the working groups first.

01:14:31.150 --> 01:14:33.650
These are regionalized working groups.

01:14:33.650 --> 01:14:37.890
And they are made
up of different regions

01:14:37.890 --> 01:14:39.350
in terms of our territory.

01:14:39.350 --> 01:14:42.410
So we have three meetings
coming up this week.

01:14:42.410 --> 01:14:46.590
And they are made
up of the different IOUs,

01:14:46.590 --> 01:14:49.210
communication and
water service providers,

01:14:49.210 --> 01:14:53.463
CPUC staff, community
choice aggregators,

01:14:54.470 --> 01:14:57.800
small multi-jurisdictional
electric utilities,

01:14:57.800 --> 01:15:00.330
tribal and local government entities,

01:15:00.330 --> 01:15:01.943
public safety partners,

01:15:02.800 --> 01:15:04.850
and representatives of those

01:15:04.850 --> 01:15:06.793
with Access and Functional Needs.

01:15:09.320 --> 01:15:14.280
And advisory board consists
of public safety partners,

01:15:14.280 --> 01:15:17.120
communications and
water service providers,

01:15:17.120 --> 01:15:19.640
local and tribal government officials,

01:15:19.640 --> 01:15:22.810
business groups,
non-profit organizations,

01:15:22.810 --> 01:15:27.553
representatives of AFN,
and academic organizations.

01:15:31.750 --> 01:15:36.750
<v ->Okay, and these are
compiled on a regional basis</v>

01:15:38.100 --> 01:15:43.100
so that there is a sense
for the localized needs?

01:15:45.230 --> 01:15:48.567
<v ->Correct, so there are
three regions, as I mentioned.</v>

01:15:48.567 --> 01:15:50.970
The first region is Los Angeles,

01:15:50.970 --> 01:15:53.540
Orange, Ventura, and
Santa Barbara County

01:15:53.540 --> 01:15:57.060
Region five is Kern,
Tulare, Fresno, Madera,

01:15:57.060 --> 01:16:01.220
and Tuolumne County,
sorry, I can't pronounce that.

01:16:01.220 --> 01:16:03.560
And then region six is San Bernardino,

01:16:03.560 --> 01:16:06.503
Riverside, Mano, and Inyo County.

01:16:11.590 --> 01:16:13.920
<v Genevieve>Okay.
All right, thank you.</v>

01:16:13.920 --> 01:16:14.753
<v ->Sure.</v>

01:16:18.021 --> 01:16:19.971
<v Marybel>I think we
can move on now.</v>

01:16:23.190 --> 01:16:26.709
<v Tom>Okay, so Tom
Brandy here again.</v>

01:16:26.709 --> 01:16:30.130
Wanting to spend a few
minutes on slide eight

01:16:30.130 --> 01:16:31.670
to discuss the
improvements we are making

01:16:31.670 --> 01:16:34.860
to our post-event reporting protocols

01:16:34.860 --> 01:16:36.150
to ensure that we're describing

01:16:36.150 --> 01:16:37.450
each of de-energization events

01:16:38.285 --> 01:16:41.690
in a clear, transparent,
and compliant manner.

01:16:41.690 --> 01:16:43.850
We did complete an initial gap analysis

01:16:43.850 --> 01:16:46.590
of our current post-event
reporting template

01:16:46.590 --> 01:16:48.560
by reviewing regulatory decisions

01:16:48.560 --> 01:16:51.590
and considering input
from our stakeholders,

01:16:51.590 --> 01:16:54.040
including intervenors,
public safety partners,

01:16:54.040 --> 01:16:55.780
as well as the Commission.

01:16:55.780 --> 01:16:59.120
This effort allowed us to
begin to identify further areas

01:16:59.120 --> 01:17:01.210
where we do need to
provide additional information

01:17:01.210 --> 01:17:03.910
in our post-event reports to better

01:17:03.910 --> 01:17:07.170
and more comprehensively
describe the factors we consider

01:17:07.170 --> 01:17:10.200
when deciding to
activate for a PSPS event,

01:17:10.200 --> 01:17:13.870
notify customers, and
de-energize circuits.

01:17:13.870 --> 01:17:16.570
Some initial examples of
the changes we're making

01:17:16.570 --> 01:17:18.760
based on these lessons learned include

01:17:18.760 --> 01:17:20.680
strengthening our data validation,

01:17:20.680 --> 01:17:23.700
our quality assurance
and quality control activities,

01:17:23.700 --> 01:17:26.050
separately and clearly describing

01:17:26.050 --> 01:17:29.720
multiple periods of
concern for complex events,

01:17:29.720 --> 01:17:32.730
comprehensively reporting complaints,

01:17:32.730 --> 01:17:34.730
and providing notification status

01:17:34.730 --> 01:17:37.080
of Medical Baseline customers.

01:17:37.080 --> 01:17:38.830
We did make initial changes

01:17:38.830 --> 01:17:41.580
to our February 4th post-event report

01:17:41.580 --> 01:17:44.020
to begin implementing
some of these learnings.

01:17:44.020 --> 01:17:45.410
And we do acknowledge that more work

01:17:45.410 --> 01:17:47.290
still needs to be done in this area

01:17:47.290 --> 01:17:50.000
prior to the 2021 fire season.

01:17:50.000 --> 01:17:54.080
We intend to use Phase 3 of the PSPS OIR

01:17:54.080 --> 01:17:56.890
to seek further clarity
on the expectations

01:17:56.890 --> 01:17:59.130
and preferred reporting framework

01:17:59.130 --> 01:18:02.120
for future post-event
reporting activities.

01:18:02.120 --> 01:18:03.700
This will include gleaning into

01:18:03.700 --> 01:18:05.640
our ongoing benchmarking efforts

01:18:05.640 --> 01:18:09.560
with our sister IOUs to
align on best practices.

01:18:09.560 --> 01:18:12.440
We will continue to work
closely with Commission staff

01:18:12.440 --> 01:18:15.090
to discuss the results
of our gap analysis

01:18:15.090 --> 01:18:17.620
and to solicit input on
planned enhancements

01:18:17.620 --> 01:18:20.880
to content, format, or other parameters,

01:18:20.880 --> 01:18:22.610
to make sure we are
coming into alignment

01:18:22.610 --> 01:18:25.670
on expectations and requirements.

01:18:25.670 --> 01:18:28.360
With that, I will close
and pause for questions,

01:18:28.360 --> 01:18:31.010
before handing it back to
Erik to discuss next steps.

01:18:33.760 --> 01:18:36.530
<v Marybel>You said
that you were reporting</v>

01:18:36.530 --> 01:18:39.184
in a list of things that you
said, I may have missed it.

01:18:39.184 --> 01:18:41.500
You said you're reporting complaints.

01:18:41.500 --> 01:18:43.550
To whom are you
reporting the complaints?

01:18:44.970 --> 01:18:47.240
<v Tom>I'm sorry, can you
please repeat the question?</v>

01:18:47.240 --> 01:18:48.870
<v Marybel>I thought
you said something</v>

01:18:48.870 --> 01:18:51.260
about reporting complaints,

01:18:51.260 --> 01:18:54.610
when you listed the
various things you're doing.

01:18:54.610 --> 01:18:57.128
And I want to know to whom
<v ->Yeah, so--</v>

01:18:57.128 --> 01:18:59.570
<v Marybel>No, go ahead, go ahead.</v>

01:18:59.570 --> 01:19:02.710
<v Tom>Yeah, so, one of
the areas that we believe</v>

01:19:02.710 --> 01:19:07.520
that we have a gap that we
need to have more information in

01:19:07.520 --> 01:19:11.850
is how we report a complaint
in the post-event report.

01:19:11.850 --> 01:19:15.090
So we have always reported complaints,

01:19:15.090 --> 01:19:18.670
but prior to our most recent
event, those complaints

01:19:18.670 --> 01:19:20.904
were generally formal complaints

01:19:20.904 --> 01:19:22.860
that were filed with the Commission.

01:19:22.860 --> 01:19:25.940
In our 2021 post-events
and starting with

01:19:25.940 --> 01:19:28.730
the post event report
that we recently submitted,

01:19:28.730 --> 01:19:31.670
we did begin including
additional complaints,

01:19:31.670 --> 01:19:32.900
such as the ones that are filed

01:19:32.900 --> 01:19:35.390
with our Consumer Affairs groups,

01:19:35.390 --> 01:19:36.640
as well as formal complaints

01:19:36.640 --> 01:19:38.500
that we receive through the Commission

01:19:38.500 --> 01:19:41.913
and through our liaison
officers during events.

01:19:46.320 --> 01:19:47.426
<v Marybel>Thank you.</v>

01:19:47.426 --> 01:19:49.343
<v Tom>You're welcome.</v>

01:19:57.360 --> 01:19:59.100
<v ->Okay, if there are
no further questions,</v>

01:19:59.100 --> 01:20:01.903
I think we can move to slide nine.

01:20:03.180 --> 01:20:07.690
This is the last slide for
the presentation today.

01:20:07.690 --> 01:20:11.316
A lot of what's listed
here we actually covered

01:20:11.316 --> 01:20:13.690
throughout the presentation,

01:20:13.690 --> 01:20:16.690
in discussing the upcoming working group

01:20:16.690 --> 01:20:18.816
and advisory board meetings,

01:20:18.816 --> 01:20:21.900
upcoming community engagement meetings

01:20:21.900 --> 01:20:25.520
to solicit feedback and
hear from our customers,

01:20:25.520 --> 01:20:29.993
and also additional meetings
with local elected leaders,

01:20:31.440 --> 01:20:35.370
local government tribes,
critical infrastructure customers,

01:20:35.370 --> 01:20:37.363
and our public safety partners.

01:20:39.649 --> 01:20:40.899
One thing I just want to,

01:20:41.810 --> 01:20:46.160
if there are any other
questions, but I just want to thank,

01:20:46.160 --> 01:20:48.230
you, President Batjer,
and the Commissioners,

01:20:48.230 --> 01:20:53.230
for your really great
questions about the feedback.

01:20:55.682 --> 01:20:58.910
We really appreciate
the engagement today.

01:20:58.910 --> 01:21:01.510
We believe that the action
plan that we've outlined

01:21:01.510 --> 01:21:04.187
is a significant step towards addressing

01:21:04.187 --> 01:21:06.880
the issues raised throughout 2020.

01:21:06.880 --> 01:21:09.360
And we do look forward to
the next part of the session

01:21:09.360 --> 01:21:10.460
of the public comment.

01:21:11.550 --> 01:21:13.080
<v Marybel>Thank you, Erik.</v>

01:21:13.080 --> 01:21:14.400
Just real quickly,

01:21:14.400 --> 01:21:16.956
and then I'll turn to my
fellow Commissioners.

01:21:16.956 --> 01:21:21.080
You just listed all of the
working groups on slide nine.

01:21:21.080 --> 01:21:24.480
One of the things I
needed to clarify earlier

01:21:24.480 --> 01:21:28.080
and perhaps did not is,
have you actually dedicated

01:21:29.684 --> 01:21:32.890
people within the company for a liaison

01:21:32.890 --> 01:21:36.760
specifically to the
county, people that have

01:21:36.760 --> 01:21:39.730
operational awareness and understanding

01:21:39.730 --> 01:21:43.910
so that they can very
quickly and efficiently address

01:21:43.910 --> 01:21:47.853
the county questions and
concerns in a real-time manner?

01:21:49.950 --> 01:21:52.690
<v ->Yeah, and Mr. Brady,
I think this might be</v>

01:21:52.690 --> 01:21:54.380
a good question for you, because I think

01:21:54.380 --> 01:21:58.100
you live in this space every day.

01:21:58.100 --> 01:21:59.520
<v Tom>Yeah, that's great, Erik.</v>

01:21:59.520 --> 01:22:01.210
Happy to answer the question.

01:22:01.210 --> 01:22:03.833
So, specific to government partners,

01:22:04.906 --> 01:22:06.550
let me get my video back on here,

01:22:06.550 --> 01:22:08.770
we do communicate directly with them

01:22:08.770 --> 01:22:11.910
through a liaison officer on
our Incident Management team.

01:22:11.910 --> 01:22:15.300
So that's a 24 by 7,
dedicated point of contact

01:22:15.300 --> 01:22:17.330
between local and state
government partners

01:22:17.330 --> 01:22:19.063
and our Incident Management team.

01:22:20.090 --> 01:22:22.870
Relatedly, on the
emergency management side,

01:22:22.870 --> 01:22:25.960
we do have a business
resiliency duty manager

01:22:25.960 --> 01:22:29.170
and PSPS lead coach,
who are a direct conduit

01:22:29.170 --> 01:22:31.458
into the emergency management agencies

01:22:31.458 --> 01:22:33.830
at both the county and state levels.

01:22:33.830 --> 01:22:36.840
And so there's a lot of ongoing
and frequent conversations

01:22:36.840 --> 01:22:39.660
between the business resiliency contacts

01:22:39.660 --> 01:22:42.400
and those emergency
management officials,

01:22:42.400 --> 01:22:45.310
both formally and then
also on an adhoc basis

01:22:45.310 --> 01:22:49.173
as issues or concerns
come up during each event.

01:22:52.100 --> 01:22:54.430
<v Marybel>Okay, I'm
sure we're going to have</v>

01:22:54.430 --> 01:22:57.810
followup questions in
our regular meetings

01:22:57.810 --> 01:23:02.430
to make sure that those
are really tight contacts.

01:23:02.430 --> 01:23:04.320
So, okay, thank you.

01:23:04.320 --> 01:23:07.270
And I think Commissioner
Rechtschaffen, you had a question.

01:23:08.500 --> 01:23:12.220
<v ->Thank you, I have a comment
first and then a question.</v>

01:23:12.220 --> 01:23:15.270
In terms of next steps, I
just want to let you know

01:23:15.270 --> 01:23:20.270
that our public outreach
team has observed

01:23:20.310 --> 01:23:25.120
that at some of your
PSPS public meetings

01:23:25.120 --> 01:23:26.550
you're not leaving enough time

01:23:26.550 --> 01:23:29.380
for public comments and questions.

01:23:29.380 --> 01:23:32.580
I think it's very, very
important that you try to do that.

01:23:32.580 --> 01:23:37.500
And we've heard this
criticism about the other utilities

01:23:37.500 --> 01:23:40.313
and it applies to us, I'm sure, as well,

01:23:40.313 --> 01:23:42.010
that there's too much information

01:23:42.010 --> 01:23:44.940
just thrown at ratepayers and customers,

01:23:44.940 --> 01:23:48.030
and not enough time for the
give and take in the feedback.

01:23:48.030 --> 01:23:50.160
So, this is something
that we've observed,

01:23:50.160 --> 01:23:53.860
so we ask you to try to
adopt your meetings in a way

01:23:53.860 --> 01:23:55.670
that you leave enough time

01:23:55.670 --> 01:23:56.953
for public comments and questions.

01:23:58.320 --> 01:24:00.243
So, that's the comment.

01:24:02.004 --> 01:24:06.300
And the question I have is
last year you had a program

01:24:06.300 --> 01:24:10.460
where you provided
some refunds to customers

01:24:10.460 --> 01:24:13.620
resulting from certain financial harm,

01:24:13.620 --> 01:24:16.542
food spoilage and things like that,

01:24:16.542 --> 01:24:18.830
if you didn't provide adequate notice,

01:24:18.830 --> 01:24:20.873
advance notice of a shutoff.

01:24:22.250 --> 01:24:26.083
Are you planning a similar
program for this year?

01:24:28.320 --> 01:24:29.670
<v ->I can take that question.</v>

01:24:30.928 --> 01:24:32.800
Yes, so, Commissioner, you're referring

01:24:32.800 --> 01:24:35.670
to our 2019 claims exemption process

01:24:35.670 --> 01:24:38.488
that we had instituted last year.

01:24:38.488 --> 01:24:43.488
We are currently looking at alternatives

01:24:43.580 --> 01:24:46.800
for our customers impacts to food loss

01:24:46.800 --> 01:24:51.800
and we will report back
if we have made progress

01:24:52.450 --> 01:24:54.650
in the exploration of alternatives.

01:24:54.650 --> 01:24:57.570
But for now we still have
our current claims process

01:24:57.570 --> 01:24:58.807
that is in effect.

01:25:00.660 --> 01:25:03.110
<v ->So that means you're
honoring the same process</v>

01:25:03.110 --> 01:25:04.363
that you used before?

01:25:05.890 --> 01:25:09.680
<v ->That means that the 2019
exemption is no longer in effect</v>

01:25:09.680 --> 01:25:13.733
and we are utilizing our
current claims process,

01:25:16.740 --> 01:25:21.043
which does not include that
exemption as it has expired.

01:25:22.333 --> 01:25:24.900
<v ->But, you're evaluating
whether or not</v>

01:25:24.900 --> 01:25:27.560
to include that going forward?

01:25:27.560 --> 01:25:31.250
<v ->We're evaluating something
that might be similar,</v>

01:25:31.250 --> 01:25:34.220
whether it makes sense
to include going forward,

01:25:34.220 --> 01:25:36.650
which also could include other ideas

01:25:36.650 --> 01:25:38.373
that are not related to claims.

01:25:39.930 --> 01:25:41.630
<v ->What would those
other ideas be?</v>

01:25:42.653 --> 01:25:46.440
<v ->So they would be more in
the vein of program solutions,</v>

01:25:46.440 --> 01:25:50.580
such as more donations to food banks

01:25:50.580 --> 01:25:55.580
or similar programs that
PG&amp;E is implementing.

01:25:55.610 --> 01:25:58.240
So we're starting with looking at

01:25:58.240 --> 01:26:00.220
what types of customers are impacted

01:26:00.220 --> 01:26:04.280
to see if we can come up with
those programmatic solutions.

01:26:04.280 --> 01:26:07.273
And we're just in the
beginning exploration stages.

01:26:08.610 --> 01:26:10.670
<v ->Do you have an estimate
of the number of claims</v>

01:26:10.670 --> 01:26:14.508
you got this last Fall,
this last fire season,

01:26:14.508 --> 01:26:18.350
with all the shutoffs, Fall and Winter?

01:26:18.350 --> 01:26:20.500
<v ->We do have all
the claims metrics</v>

01:26:20.500 --> 01:26:22.893
that we can followup with if necessary.

01:26:25.500 --> 01:26:26.370
<v ->Yes, thank you.</v>

01:26:26.370 --> 01:26:27.390
I'd be interested in that.

01:26:27.390 --> 01:26:30.300
And also I'd be
interested in hearing back

01:26:30.300 --> 01:26:32.330
when you determine
how you're gonna proceed

01:26:32.330 --> 01:26:33.943
on this issue going forward.

01:26:34.987 --> 01:26:35.853
<v ->Definitely.</v>

01:26:43.807 --> 01:26:44.920
<v Marybel>Any other questions?</v>

01:26:44.920 --> 01:26:46.110
Yes, Commissioner Shiroma.

01:26:46.110 --> 01:26:50.633
<v ->Just one last question
from me, for today.</v>

01:26:51.859 --> 01:26:56.859
I know you're planning
for the 2021 season,

01:26:57.100 --> 01:27:00.990
and ordinarily we would be talking about

01:27:02.490 --> 01:27:05.720
the Summer to Fall timeframe.

01:27:05.720 --> 01:27:10.627
But those PSPSes around the holidays

01:27:11.600 --> 01:27:16.600
and around the New Year were startling.

01:27:17.320 --> 01:27:22.320
So, in your outlook, for
the team's outlook for 2021,

01:27:24.507 --> 01:27:27.530
are you planning for the potential

01:27:27.530 --> 01:27:31.550
for the season to start far earlier?

01:27:31.550 --> 01:27:35.827
You've outlined activities
in March and April,

01:27:35.827 --> 01:27:38.023
going into June.

01:27:38.910 --> 01:27:42.400
Are you also prepared
that you may have to invoke

01:27:42.400 --> 01:27:46.980
PSPSes in the middle of
all of your outreach efforts,

01:27:46.980 --> 01:27:48.330
and are you ready for that?

01:27:51.230 --> 01:27:53.340
<v ->Yeah, thank you,
Commissioner Shiroma.</v>

01:27:53.340 --> 01:27:54.173
I'll take this.

01:27:54.173 --> 01:27:58.305
So we are concerned
about the weather this year.

01:27:58.305 --> 01:28:03.305
The lack of precipitation
seems to have carried over so far.

01:28:04.144 --> 01:28:07.530
Certainly it's still, time will tell,

01:28:07.530 --> 01:28:11.035
over the course of
the next month or two.

01:28:11.035 --> 01:28:15.230
I think at least according
to our meteorologist,

01:28:15.230 --> 01:28:18.370
the La Nina pattern is
expected to kind of loosen up

01:28:18.370 --> 01:28:22.370
and start to diminish
beginning in April.

01:28:22.370 --> 01:28:25.960
So, I think we are seeing potentially

01:28:25.960 --> 01:28:29.230
some upcoming precipitation,
but certainly right now,

01:28:29.230 --> 01:28:32.470
our outlook at this
time looks to be dryer.

01:28:32.470 --> 01:28:35.880
So, in terms of the
preparation, it is on our minds

01:28:35.880 --> 01:28:38.835
that the folks that
are working really hard

01:28:38.835 --> 01:28:40.270
and getting our plans ready,

01:28:40.270 --> 01:28:43.780
we're gonna have to, and
are planning to supplement,

01:28:43.780 --> 01:28:48.025
to be able to conduct
operational activities,

01:28:48.025 --> 01:28:52.130
while in the midst of
improving the situation

01:28:52.130 --> 01:28:56.170
for our customers, which
is the highest priority.

01:28:56.170 --> 01:28:59.950
And so we, operationally,
just need to supplement

01:28:59.950 --> 01:29:03.153
our resources with
that ability to continue.

01:29:08.013 --> 01:29:09.603
<v ->All right, thank you.</v>

01:29:13.600 --> 01:29:16.723
<v Marybel>Do we have any other
questions, Commissioners?</v>

01:29:20.761 --> 01:29:23.410
All right, I will fill in one question.

01:29:23.410 --> 01:29:25.760
I know you've given us
some good timeframes here,

01:29:25.760 --> 01:29:27.400
March, June.

01:29:27.400 --> 01:29:30.653
I hope, and we will continue
to ask these questions of you,

01:29:30.653 --> 01:29:33.630
because there's still
things that are underway,

01:29:33.630 --> 01:29:36.320
gonna be done, soon will be done,

01:29:36.320 --> 01:29:41.320
and it's extremely important,
as you all well know,

01:29:42.100 --> 01:29:47.100
that all of this be done
well before fire season,

01:29:47.430 --> 01:29:50.970
particularly your communications
with the communities,

01:29:50.970 --> 01:29:53.070
tribal governments,
the local governments.

01:29:54.180 --> 01:29:58.890
The battery backup is
so incredibly important.

01:29:58.890 --> 01:30:01.160
And we, almost every Commission meeting,

01:30:01.160 --> 01:30:04.290
we have public comment of concern,

01:30:04.290 --> 01:30:06.700
not only whether they
have battery backup,

01:30:06.700 --> 01:30:08.523
but the cost of battery backup.

01:30:09.870 --> 01:30:12.923
So very critical to stay
on track with all of that.

01:30:13.930 --> 01:30:16.230
And as I said, we will be making sure,

01:30:16.230 --> 01:30:19.630
in our every other week meetings,

01:30:19.630 --> 01:30:23.210
that we're tracking with you
on your accomplishments

01:30:23.210 --> 01:30:25.260
and that you're nailing
those timeframes.

01:30:26.326 --> 01:30:29.820
I think somebody said a lot
going on with very little time,

01:30:29.820 --> 01:30:32.143
and I'll just underscore
that, that's so true.

01:30:33.140 --> 01:30:35.450
All right, any other questions?

01:30:35.450 --> 01:30:40.450
Okay, seeing none, we will
now turn to public comment.

01:30:41.910 --> 01:30:45.190
Let me just say, if you wish
to make a public comment,

01:30:45.190 --> 01:30:49.597
dial into 800-857-1917

01:30:51.550 --> 01:30:54.390
and enter pass code 8147204 pound,

01:30:58.290 --> 01:31:02.200
and press star-one to
be placed into the queue

01:31:02.200 --> 01:31:05.520
and the operator will take
your name and information.

01:31:05.520 --> 01:31:08.310
If you have already dialed in

01:31:08.310 --> 01:31:10.340
to the public comment telephone line,

01:31:10.340 --> 01:31:15.340
please press star-one to get
into the public comment queue.

01:31:17.270 --> 01:31:20.990
We will allot two minutes of time

01:31:20.990 --> 01:31:23.930
for your comment, for you speak.

01:31:23.930 --> 01:31:25.360
You will hear a bell.

01:31:25.360 --> 01:31:28.370
You will hear a bell
sound when your time is up.

01:31:28.370 --> 01:31:31.370
And please, be mindful of
other speakers in the queue

01:31:31.370 --> 01:31:35.020
and keep to your allotted
time of two minutes.

01:31:35.020 --> 01:31:37.220
With that guidance in mind,

01:31:37.220 --> 01:31:41.720
I welcome today's callers in
the public comment period.

01:31:41.720 --> 01:31:43.390
I will now turn to the operator

01:31:43.390 --> 01:31:46.220
to open the public
comment telephone line.

01:31:46.220 --> 01:31:47.133
Operator.

01:31:48.240 --> 01:31:50.080
<v Joseph>Thank you.</v>

01:31:50.080 --> 01:31:52.860
The public comment line is now open.

01:31:52.860 --> 01:31:54.890
Our first speaker is

01:31:57.180 --> 01:31:59.583
Rachel Wong, your line is open.

01:32:01.860 --> 01:32:03.042
<v Rachel>Hi, there.</v>

01:32:03.042 --> 01:32:03.875
Can you hear me okay?

01:32:03.875 --> 01:32:06.467
<v Marybel>Yes, we
can hear you, Rachel.</v>

01:32:06.467 --> 01:32:08.017
<v Rachel>Hi, my
name's Rachael Wong.</v>

01:32:08.017 --> 01:32:10.220
I'm the Associate University Engineer

01:32:10.220 --> 01:32:13.210
at California State
University Chancellor's Office.

01:32:13.210 --> 01:32:16.740
I am listening in today on
behalf of some of our campuses,

01:32:16.740 --> 01:32:21.063
and I have a request
for kind of more robust

01:32:21.930 --> 01:32:25.950
and transparent reporting on the work

01:32:25.950 --> 01:32:29.030
that SCE has done to
date to kind of strengthen

01:32:29.030 --> 01:32:31.290
the resilience of our electric grid,

01:32:31.290 --> 01:32:33.500
as well as maybe
something along the lines

01:32:33.500 --> 01:32:36.810
of a prioritization
matrix and a timeline

01:32:36.810 --> 01:32:40.760
for when each project that
is coming along the pipe,

01:32:40.760 --> 01:32:42.600
for example the 72 circuits

01:32:42.600 --> 01:32:44.500
and anything else that's relevant,

01:32:44.500 --> 01:32:47.463
so that us, as customers, we are able,

01:32:47.463 --> 01:32:50.160
and our campuses are able to plan

01:32:50.160 --> 01:32:52.250
to improve our own infrastructure

01:32:52.250 --> 01:32:56.550
and improve our own
infrastructure resilience.

01:32:56.550 --> 01:32:59.770
And then my last
point is just that access

01:32:59.770 --> 01:33:02.860
to reliable infrastructure
is an equity issue.

01:33:02.860 --> 01:33:06.630
So, if we could develop
this reporting to maybe

01:33:06.630 --> 01:33:09.870
also include some socioeconomic
and demographic data,

01:33:09.870 --> 01:33:13.423
of the impacted communities,
that would be great.

01:33:17.530 --> 01:33:20.050
<v Marybel>Thank you
very much, Rachel.</v>

01:33:20.050 --> 01:33:21.893
Operator, the next caller please.

01:33:22.900 --> 01:33:24.090
<v Joseph>Yes, thank you.</v>

01:33:24.090 --> 01:33:27.290
Our next speaker is Reese Holland.

01:33:27.290 --> 01:33:28.313
Your line is open.

01:33:35.730 --> 01:33:37.130
<v Marybel>Please go ahead.</v>

01:33:39.480 --> 01:33:41.283
Reese Holland, please go ahead.

01:33:46.950 --> 01:33:49.373
<v Joseph>Mr. Holland, please
check your mute button.</v>

01:34:01.460 --> 01:34:02.810
<v Marybel>Okay, we
seem to be having</v>

01:34:02.810 --> 01:34:04.990
some difficulties
with Mr. Holland's line.

01:34:04.990 --> 01:34:07.370
Would you like to go
on to the next caller,

01:34:07.370 --> 01:34:12.370
and hopefully that line
will be able to be reopened.

01:34:13.900 --> 01:34:15.240
<v Joseph>Yes, ma'am.</v>

01:34:15.240 --> 01:34:18.670
Our next speaker is Nasisa Gobian.

01:34:19.570 --> 01:34:20.733
Your line is open.

01:34:22.490 --> 01:34:24.355
<v Nasisa>President Batjer
and Commissioners,</v>

01:34:24.355 --> 01:34:26.270
Nasisa Gobian, city of Santa Clarita.

01:34:26.270 --> 01:34:28.150
On behalf of the Santa
Clarita City Council,

01:34:28.150 --> 01:34:29.850
I want to express our appreciation

01:34:29.850 --> 01:34:32.670
for the Commission's
attention to this critical matter

01:34:32.670 --> 01:34:35.620
and the opportunity to
provide public comment.

01:34:35.620 --> 01:34:37.750
Surrounded by mountain
passes and canyons,

01:34:37.750 --> 01:34:39.640
the city historically experiences

01:34:39.640 --> 01:34:43.010
strong Santa Ana winds during
the Fall and Winter season,

01:34:43.010 --> 01:34:45.530
with gusts up to 70 miles per hour.

01:34:45.530 --> 01:34:48.100
And over the last three years,
our residents and businesses

01:34:48.100 --> 01:34:51.210
have experienced several
Edison PSPS events,

01:34:51.210 --> 01:34:54.890
significantly impacting
public wellbeing and safety.

01:34:54.890 --> 01:34:56.570
At times, these power shutoff events

01:34:56.570 --> 01:34:59.660
have impacted over 25,000
households and businesses

01:34:59.660 --> 01:35:03.120
at periods of over 24 consecutive hours,

01:35:03.120 --> 01:35:05.000
including major power loss events

01:35:05.000 --> 01:35:07.360
during the holidays
at the end of last year.

01:35:07.360 --> 01:35:10.770
We full-heartedly appreciate
the accessibility demonstrated

01:35:10.770 --> 01:35:13.134
by local representatives
of Edison, however,

01:35:13.134 --> 01:35:16.940
in an effort to ensure immediate
reliable electrical service

01:35:16.940 --> 01:35:19.460
we respectfully urge the
Commission to mandate

01:35:19.460 --> 01:35:22.940
Edison harden their infrastructure
in an expedited manner,

01:35:22.940 --> 01:35:25.470
with a defined and accelerated schedule

01:35:25.470 --> 01:35:29.760
to target and harden circuits
most impacted by PSPS events,

01:35:29.760 --> 01:35:31.900
and that serve the greatest
number of customers,

01:35:31.900 --> 01:35:35.030
and that circuits and
infrastructure in Santa Clarita

01:35:35.030 --> 01:35:37.870
be included in the
expedited hardening plans,

01:35:37.870 --> 01:35:41.150
and PSPS exception
efforts as appropriate.

01:35:41.150 --> 01:35:43.760
This concludes my comments.
and I appreciate the opportunity

01:35:43.760 --> 01:35:45.790
to share our comments on this matter.

01:35:45.790 --> 01:35:46.623
Thank you.

01:35:52.410 --> 01:35:53.460
<v Joseph>Thank you.</v>

01:35:55.670 --> 01:36:00.670
Our next question comes
from Reese Holland.

01:36:00.990 --> 01:36:02.023
Your line is open.

01:36:03.717 --> 01:36:05.510
<v Reese>Hello, I hope you
can hear me this time.</v>

01:36:05.510 --> 01:36:07.710
Unfortunately, I was
watching on the website

01:36:07.710 --> 01:36:09.300
and the latency between
that and the phone

01:36:09.300 --> 01:36:10.150
was a little bit off.

01:36:10.150 --> 01:36:14.820
So, I appreciate that we're
having this meeting here

01:36:14.820 --> 01:36:17.987
and CPUC, I appreciate it.

01:36:17.987 --> 01:36:20.150
SCE it's a good for you to show up.

01:36:20.150 --> 01:36:22.800
I, unfortunately, think
this needs to be redone,

01:36:22.800 --> 01:36:24.760
or at least the comment
section from the public

01:36:24.760 --> 01:36:27.070
needs to be done at a later time,

01:36:27.070 --> 01:36:30.354
with a longer comment period,

01:36:30.354 --> 01:36:32.580
so that way working class folks

01:36:32.580 --> 01:36:34.280
who should be probably working right now

01:36:34.280 --> 01:36:35.830
and probably can't really take time off

01:36:35.830 --> 01:36:39.200
to comment on this
can actually participate.

01:36:39.200 --> 01:36:40.390
I think that was part of the reason

01:36:40.390 --> 01:36:43.870
why we had so many
participants last time, perhaps,

01:36:43.870 --> 01:36:46.280
but even if it wasn't,
we definitely need

01:36:46.280 --> 01:36:48.560
to really open the door and allow

01:36:48.560 --> 01:36:50.340
a lot more communication on this.

01:36:50.340 --> 01:36:52.730
Quite honestly, all I'm hearing is still

01:36:52.730 --> 01:36:54.160
a whole lot of half solutions.

01:36:54.160 --> 01:36:56.710
I feel like the infrastructure issues

01:36:56.710 --> 01:36:59.180
are things that we've known
about since I was a kid.

01:36:59.180 --> 01:37:01.850
I've been in the area
for all of 36 years.

01:37:01.850 --> 01:37:04.480
And quite honestly, we're way behind.

01:37:04.480 --> 01:37:06.010
Things needed to have been entrenched.

01:37:06.010 --> 01:37:08.890
Things needed to have
been set up to be as resistant.

01:37:08.890 --> 01:37:09.950
We know that there's winds.

01:37:09.950 --> 01:37:10.980
We know that there's fires.

01:37:10.980 --> 01:37:12.760
That's always been the case here.

01:37:12.760 --> 01:37:14.390
The fact that we're doing half measures

01:37:14.390 --> 01:37:16.160
to try to protect and work around them,

01:37:16.160 --> 01:37:19.330
instead of using the most efficient

01:37:19.330 --> 01:37:20.780
and powerful technology we have

01:37:20.780 --> 01:37:25.186
to protect ourselves
from these events entirely.

01:37:25.186 --> 01:37:27.430
And part of the problem
I think is really just

01:37:27.430 --> 01:37:30.330
the amount of profit that
goes into and comes out

01:37:30.330 --> 01:37:33.130
of the company and how much
that really ought to be banned.

01:37:33.130 --> 01:37:36.100
All profit is basically
money that wasn't spent

01:37:36.100 --> 01:37:39.596
to fix the infrastructure and
take care of these issues.

01:37:39.596 --> 01:37:41.100
It's kind of a big problem.

01:37:41.100 --> 01:37:44.550
Instead that money, that profit,
ends up being used to lobby

01:37:44.550 --> 01:37:49.210
and try to fight to shield
themselves from liability.

01:37:49.210 --> 01:37:53.530
So I think banning profits
from SCE and PG&amp;E

01:37:53.530 --> 01:37:56.720
for the next 20 years
would probably a good start.

01:37:56.720 --> 01:37:58.780
Otherwise they can
just donate their assets

01:37:58.780 --> 01:38:00.650
and infrastructure of
the state of California.

01:38:00.650 --> 01:38:03.740
And we can just
basically municipalize it.

01:38:03.740 --> 01:38:04.680
I feel like that's really

01:38:04.680 --> 01:38:06.430
the sort of solutions that we need.

01:38:07.730 --> 01:38:11.320
There's a memo coming from
UCLA Public Policy Department

01:38:11.320 --> 01:38:14.363
that will be sent to
CPUC and SCE and PG&amp;E

01:38:15.850 --> 01:38:20.850
about the current use of
power and the state of things.

01:38:22.490 --> 01:38:24.810
I think that was my ring,
so I'll send that along.

01:38:24.810 --> 01:38:25.853
Thank you very much.

01:38:27.210 --> 01:38:28.740
<v Marybel>Thank you very much.</v>

01:38:28.740 --> 01:38:30.443
I'm glad you were able to get back in.

01:38:31.400 --> 01:38:33.530
Operator, the next caller, please.

01:38:33.530 --> 01:38:34.744
<v Joseph>Thank you.</v>

01:38:34.744 --> 01:38:37.240
Our next comment comes
from Jacqueline Ayer.

01:38:37.240 --> 01:38:38.263
Your line is open.

01:38:39.610 --> 01:38:41.640
<v Jacqueline>Hello. Thank
you, Commissioners.</v>

01:38:41.640 --> 01:38:42.597
My name is Jacquelyn Ayer,

01:38:42.597 --> 01:38:44.320
and I am the Utilities Committee Chair

01:38:44.320 --> 01:38:45.730
for the Acton Town Council.

01:38:45.730 --> 01:38:49.060
And I'm very grateful for this
opportunity to address you.

01:38:49.060 --> 01:38:50.830
There is a lot that the
Acton Town Council

01:38:50.830 --> 01:38:53.370
would like to say about
Edison's performance in 2020

01:38:53.370 --> 01:38:54.710
and its corrective action plan,

01:38:54.710 --> 01:38:56.910
but we'll focus on just a few things.

01:38:56.910 --> 01:38:58.700
First, Edison has reported that

01:38:58.700 --> 01:39:01.500
it was abnormal Fall
weather conditions in 2020

01:39:01.500 --> 01:39:04.280
that drove its successive
PSPS activities.

01:39:04.280 --> 01:39:06.410
But you need to know that
there was nothing abnormal

01:39:06.410 --> 01:39:08.960
about the Fall weather
conditions in 2020.

01:39:08.960 --> 01:39:10.876
In fact, for half of
the years since 1998

01:39:10.876 --> 01:39:14.660
rainfall in our area was at
or below the rainfall levels

01:39:14.660 --> 01:39:16.630
that occurred in the Fall of 2020.

01:39:16.630 --> 01:39:19.160
In other words, what
we experienced in 2020

01:39:19.160 --> 01:39:23.000
will be the norm for us
on average going forward.

01:39:23.000 --> 01:39:25.990
Second, Edison keeps
telling you that PSPS decisions

01:39:25.990 --> 01:39:29.020
are based on when windblown
debris poses an ignition risk,

01:39:29.020 --> 01:39:33.200
which is 31 miles sustained,
46 miles per hour gusts.

01:39:33.200 --> 01:39:35.590
However, these are not the
de-energization thresholds

01:39:35.590 --> 01:39:37.650
that Edison uses in Acton.

01:39:37.650 --> 01:39:40.670
In fact, on Thanksgiving
Day, Edison cut power in Acton

01:39:40.670 --> 01:39:44.080
based on the 25 mile an
hour de-energization threshold,

01:39:44.080 --> 01:39:45.617
which is one reason why our community

01:39:45.617 --> 01:39:47.870
was so terribly impacted that day.

01:39:47.870 --> 01:39:49.710
This fact is shown clearly in Edison's

01:39:49.710 --> 01:39:52.290
post-event report filed
on December 11th.

01:39:52.290 --> 01:39:53.650
They are not telling you the truth

01:39:53.650 --> 01:39:56.530
when they say they're using 31 and 46.

01:39:56.530 --> 01:39:58.970
Third, a discovery response
received from Edison

01:39:58.970 --> 01:40:02.042
just last week regarding
their January PSPS activities

01:40:02.042 --> 01:40:06.020
reports that 450 distribution
infrastructure elements

01:40:06.020 --> 01:40:08.330
have been designated as high P2,

01:40:08.330 --> 01:40:11.470
with a failure potential
within six months,

01:40:11.470 --> 01:40:13.830
particularly under windy conditions.

01:40:13.830 --> 01:40:17.120
Edison de-energizes
facilities based on circuit health,

01:40:17.120 --> 01:40:18.950
and in Acton, our
circuits are not healthy,

01:40:18.950 --> 01:40:21.650
and we have paid for it, because
Edison cuts power in Acton

01:40:21.650 --> 01:40:25.790
at wind speeds that are much
less than the 31, 46 thresholds

01:40:25.790 --> 01:40:26.980
that they're telling you.

01:40:26.980 --> 01:40:29.320
Fourth, in a discovery
response from Edison,

01:40:29.320 --> 01:40:31.540
we have learned that even
when our distribution lines

01:40:31.540 --> 01:40:33.260
are replaced with covered conductor,

01:40:33.260 --> 01:40:36.140
Edison is still going to apply
adjustments and multipliers

01:40:36.140 --> 01:40:37.510
that will result in lower wind speed

01:40:37.510 --> 01:40:40.850
PSPS thresholds in Acton
compared to other areas.

01:40:40.850 --> 01:40:42.540
These adjustments are based on factors

01:40:42.540 --> 01:40:44.390
that have nothing to do (bell chiming).

01:40:44.390 --> 01:40:45.500
Okay, thank you.

01:40:45.500 --> 01:40:47.090
I will submit this in writing I guess.

01:40:47.090 --> 01:40:48.180
There's a lot more to be said.

01:40:48.180 --> 01:40:49.013
Thank you.

01:40:50.348 --> 01:40:53.290
<v Marybel>Thank you, Ms. Ayer.</v>

01:40:53.290 --> 01:40:55.113
Operator, the next caller, please.

01:40:57.028 --> 01:41:01.020
<v Joseph>President Batjer,
there are no more speakers</v>

01:41:01.020 --> 01:41:03.323
on the public comment telephone line.

01:41:04.510 --> 01:41:05.360
<v Marybel>Okay.</v>

01:41:08.876 --> 01:41:13.876
With that, we will close
the public comment.

01:41:13.890 --> 01:41:16.990
And I want to thank
everyone who has joined

01:41:16.990 --> 01:41:21.360
in the meeting today, for calling in,

01:41:21.360 --> 01:41:23.220
and watching and observing.

01:41:23.220 --> 01:41:28.057
I want to thank Edison
for their participation

01:41:28.057 --> 01:41:29.470
and their information.

01:41:29.470 --> 01:41:33.610
And we look forward to
a great deal of followup.

01:41:33.610 --> 01:41:35.870
As I said, time is of the essence.

01:41:35.870 --> 01:41:39.070
We appreciate your time
and your effort very much.

01:41:39.070 --> 01:41:40.083
So thank you all.

01:41:42.380 --> 01:41:43.563
That ends the meeting.

01:41:44.416 --> 01:41:45.868
<v ->Thank you.</v>

01:41:45.868 --> 01:41:46.868
<v ->Thank you.</v>

01:41:48.160 --> 01:41:49.820
<v Joseph>That concludes
today's conference.</v>

01:41:49.820 --> 01:41:51.470
Thank you for your participation.