WEBVTT

00:00:00.000 --> 00:00:01.400 line:20%
<v Presenter>Evening event brought to you</v>

00:00:01.400 --> 00:00:03.180 line:20%
by adminmonitor.com

00:00:03.180 --> 00:00:04.710 line:20%
will begin momentarily.

00:00:04.710 --> 00:00:06.110 line:20%
Thank you for your patience.

00:00:08.360 --> 00:00:10.970
<v ->Hello everyone, and thank you for joining us today</v>

00:00:10.970 --> 00:00:13.930
from public meeting, a Public Briefing

00:00:13.930 --> 00:00:16.670
from Southern California Edison Company,

00:00:16.670 --> 00:00:19.140
to update us on its readiness

00:00:19.140 --> 00:00:21.820
for the Public Safety Power Shutoff Events

00:00:21.820 --> 00:00:23.730
this wildfire season.

00:00:23.730 --> 00:00:27.310
Today's briefing from SCE is the second

00:00:27.310 --> 00:00:30.040
in a series of three public briefings

00:00:30.040 --> 00:00:31.630
we are holding this week.

00:00:31.630 --> 00:00:34.910
Yesterday, San Diego Gas and Electric Company

00:00:34.910 --> 00:00:36.260
briefed us on their readiness

00:00:36.260 --> 00:00:39.210
and we will have Pacific Gas and Electric Company

00:00:39.210 --> 00:00:44.210
provide a briefing this Thursday, August 13th at 10:00a.m.

00:00:44.450 --> 00:00:48.340
Agendas and information on how to watch and listen

00:00:48.340 --> 00:00:50.710
to the remote briefing is available

00:00:50.710 --> 00:00:54.580 line:20%
on the CPUCs Public Safety Power Shutoff website

00:00:54.580 --> 00:00:59.580 line:20%
at www.cpuc.ca.gov/psps.

00:01:02.480 --> 00:01:05.070
I am honored to have joining me today

00:01:05.070 --> 00:01:07.130
on this virtual diocese

00:01:07.130 --> 00:01:09.500
representatives from the California Governor's office

00:01:09.500 --> 00:01:11.150
of Emergency Service.

00:01:11.150 --> 00:01:12.810
And that is Eric Lamoureux,

00:01:12.810 --> 00:01:15.690
and from the office of the California Department

00:01:15.690 --> 00:01:18.320
of Forestry and Fire Prevention,

00:01:18.320 --> 00:01:21.210
and that is Assistant Chief Daniel Berlant.

00:01:21.210 --> 00:01:23.550
As well as my fellow Commissioners,

00:01:23.550 --> 00:01:26.290
Commissioner Rechtschaffen and Commissioner Shiroma,

00:01:26.290 --> 00:01:27.750
welcome.

00:01:27.750 --> 00:01:30.730
In terms of the format for today's briefing,

00:01:30.730 --> 00:01:33.353
following opening remarks from the dioce,

00:01:33.353 --> 00:01:36.210
SCE Senior Vice President of transmission

00:01:36.210 --> 00:01:38.530
and distribution, Phil Harrington,

00:01:38.530 --> 00:01:42.590
will provide an overview of CSE's state of preparedness

00:01:42.590 --> 00:01:46.300
for PSPS events this wildfire season, we will listen.

00:01:46.300 --> 00:01:48.750
We will then move onto the discussion

00:01:48.750 --> 00:01:51.060
and Q&amp;A with Commissioners

00:01:51.060 --> 00:01:53.420
and panelists on the diocese

00:01:53.420 --> 00:01:55.470
followed by public comment.

00:01:55.470 --> 00:02:00.120
We are scheduled to conclude the briefing by around 3:30.

00:02:00.120 --> 00:02:02.810
For the public comment portion of the day,

00:02:02.810 --> 00:02:07.500
which is scheduled to be around 2:50, two, five, zero.

00:02:07.500 --> 00:02:08.820
You will wish to make,

00:02:08.820 --> 00:02:10.570
and if you wish to make a public comment,

00:02:10.570 --> 00:02:14.417
please dial into this number (800) 857-1917

00:02:18.960 --> 00:02:23.960
and enter passcode 989 9501 and press star one.

00:02:27.950 --> 00:02:29.300
You will be placed into a queue

00:02:29.300 --> 00:02:32.910
and the operator will take your name and organization.

00:02:32.910 --> 00:02:36.020
There may be a delay from the time you press star one

00:02:36.020 --> 00:02:39.900
to the time the operator asks you for your information,

00:02:39.900 --> 00:02:42.560
so please be patient and stay on the line.

00:02:42.560 --> 00:02:44.460
You will be called upon to speak,

00:02:44.460 --> 00:02:47.880
when we get to the public comment period in today's agenda,

00:02:47.880 --> 00:02:52.880
which again should be around 2:50, two, five, zero.

00:02:53.420 --> 00:02:58.420
And we will provide three minutes for each speaker

00:02:58.730 --> 00:03:00.820
and we'll keep my opening remarks brief

00:03:00.820 --> 00:03:02.850
so that the majority of our time today

00:03:02.850 --> 00:03:07.180
can be used to ensure the public and impacted communities

00:03:07.180 --> 00:03:10.440
are able to hear from SCE on their state

00:03:10.440 --> 00:03:14.190
of preparedness going into this year's wildfire season.

00:03:14.190 --> 00:03:17.000
In a sense, I am sure a number of people listening today

00:03:17.000 --> 00:03:21.880
were not able to join us yesterday for the SDG&amp;E briefing.

00:03:21.880 --> 00:03:24.630
I do want to address a few items

00:03:24.630 --> 00:03:26.690
that I also raised yesterday.

00:03:26.690 --> 00:03:28.840
With climate change driven weather events,

00:03:28.840 --> 00:03:32.450
our wildfire seasons are starting earlier and ending later,

00:03:32.450 --> 00:03:34.700
and they are persistently more severe.

00:03:34.700 --> 00:03:37.610
After a dry winter and warm spring this year,

00:03:37.610 --> 00:03:40.220
we're likely in store for a long

00:03:40.220 --> 00:03:42.280
and difficult wildfire season.

00:03:42.280 --> 00:03:43.470
These weather events,

00:03:43.470 --> 00:03:45.540
when combined with negligent maintenance

00:03:45.540 --> 00:03:50.540
of utilities electrical system can be a disaster.

00:03:50.730 --> 00:03:53.800
While the legislature and the CPUC policies

00:03:53.800 --> 00:03:57.000
are driving the utilities to significantly plan

00:03:57.000 --> 00:03:59.990
for and execute approaches to mitigate

00:03:59.990 --> 00:04:02.310
the risk of utility caused wildfires

00:04:02.310 --> 00:04:04.800
through better planning, grid hardening

00:04:04.800 --> 00:04:06.560
and vegetation management,

00:04:06.560 --> 00:04:10.370
one of the tools available to the utilities

00:04:10.370 --> 00:04:14.357
to mitigate wildfire risk is to turn off power to customers,

00:04:14.357 --> 00:04:17.400
to avoid the potential to start a fire.

00:04:17.400 --> 00:04:20.756 line:20%
While these shut offs are one tool available

00:04:20.756 --> 00:04:23.170 line:20%
to the utilities, protect public safety,

00:04:23.170 --> 00:04:26.003 line:20%
they are a measure of last resort,

00:04:26.939 --> 00:04:29.439 line:20%
and I cannot emphasize enough,

00:04:30.472 --> 00:04:33.770 line:20%
it is absolutely imperative that they shut off if

00:04:33.770 --> 00:04:38.760 line:20%
and when called, are executed safely and thoughtfully.

00:04:38.760 --> 00:04:41.560
The importance of doing this is particularly critical

00:04:41.560 --> 00:04:43.040
this wildfire season,

00:04:43.040 --> 00:04:47.530
as we are also dealing with the COVID-19 pandemic,

00:04:47.530 --> 00:04:51.690
which will complicate and exacerbate the PSPS planning

00:04:51.690 --> 00:04:53.870
and execution challenges.

00:04:53.870 --> 00:04:58.370
And we'll make the stakes of ensuring PSPS is truly used

00:04:58.370 --> 00:05:02.460
only as a measure of last resort, that much higher.

00:05:02.460 --> 00:05:05.490
The implications of being without power,

00:05:05.490 --> 00:05:09.220
the families who are working and learning from home,

00:05:09.220 --> 00:05:11.610
to the state's most vulnerable people,

00:05:11.610 --> 00:05:13.530
to the critical facility supporting

00:05:13.530 --> 00:05:16.140
our state's COVID response,

00:05:16.140 --> 00:05:20.090
the implications are not merely questions of inconvenience,

00:05:20.090 --> 00:05:24.060
they are questions of, can I pay my rent this month?

00:05:24.060 --> 00:05:26.100
Can I feed my family this month?

00:05:26.100 --> 00:05:27.980
Can I power my medical equipment?

00:05:27.980 --> 00:05:29.870
I need to live.

00:05:29.870 --> 00:05:31.720
The impacts on people's lives

00:05:31.720 --> 00:05:34.380
and the stakes can not be overstated.

00:05:34.380 --> 00:05:36.270
The utilities have the obligation

00:05:36.270 --> 00:05:38.690
to manage their grid's responsibility,

00:05:38.690 --> 00:05:41.740
and they have the obligation to keep the safety

00:05:41.740 --> 00:05:45.290
and wellbeing of their customers as their highest priority,

00:05:45.290 --> 00:05:48.210
which is what this Commission expects of them

00:05:48.210 --> 00:05:52.300
with each decision they make this wildfire season.

00:05:52.300 --> 00:05:56.040
So while we can drive the point that PSPS is absolutely

00:05:56.040 --> 00:05:57.700
a measure of last resort,

00:05:57.700 --> 00:05:59.690
and is not a sustainable approach

00:05:59.690 --> 00:06:01.740
to mitigating wildfire risk,

00:06:01.740 --> 00:06:03.735
we must also ensure that if

00:06:03.735 --> 00:06:07.470
and when they do decide to call a PSPS event,

00:06:07.470 --> 00:06:10.130
they're adequately prepared to execute

00:06:10.130 --> 00:06:12.480
and communicate the shut off in a way

00:06:12.480 --> 00:06:15.590
that significantly minimizes the scope

00:06:15.590 --> 00:06:17.720
and duration of the events.

00:06:17.720 --> 00:06:20.540
They must have planned and prepared so that people

00:06:20.540 --> 00:06:23.520
are without power for the shortest amount of time

00:06:23.520 --> 00:06:28.520
and are communicated with in a way

00:06:28.610 --> 00:06:31.780
that provides enough notice and enough detail

00:06:31.780 --> 00:06:34.800
for them to make the arrangements they need to make,

00:06:34.800 --> 00:06:36.770
to ensure that their families are safe

00:06:36.770 --> 00:06:38.520
and that they are prepared

00:06:38.520 --> 00:06:41.500
to weather the duration of the event.

00:06:41.500 --> 00:06:42.840
This is the minimum,

00:06:42.840 --> 00:06:45.930
and this is why we're holding these briefings this week.

00:06:45.930 --> 00:06:48.760
The haphazardly implemented PSPS events

00:06:48.760 --> 00:06:51.820
of last fall cannot be repeated.

00:06:51.820 --> 00:06:55.600
It has been one of my, and my fellow Commissioners,

00:06:55.600 --> 00:06:57.800
highest priorities coming out of those events

00:06:57.800 --> 00:07:01.380
to ensure the CPUC takes every possible step

00:07:01.380 --> 00:07:03.550
to drive the utilities to do better,

00:07:03.550 --> 00:07:06.960
to ensure that any power shutoff that is called this year

00:07:06.960 --> 00:07:09.240
is initiated and executed

00:07:09.240 --> 00:07:12.000
in a way that considers the best interests

00:07:12.000 --> 00:07:14.660
of all those impacted.

00:07:14.660 --> 00:07:18.300
CPUC staff and the staff at our sister agencies

00:07:18.300 --> 00:07:20.460
at Cal OES and CAL FIRE,

00:07:20.460 --> 00:07:21.720
they spent countless hours

00:07:21.720 --> 00:07:24.800
meeting with utilities and overseeing their efforts

00:07:24.800 --> 00:07:29.370
to reduce the use, scope and impact of the PSPS event.

00:07:29.370 --> 00:07:32.690
The utilities have made progress,

00:07:32.690 --> 00:07:36.830
but what this comes down to is planning

00:07:36.830 --> 00:07:38.920
and proper execution.

00:07:38.920 --> 00:07:42.230
This week's briefings are focused on PSPS readiness

00:07:42.230 --> 00:07:45.380
because we need to be sure that when the events are called,

00:07:45.380 --> 00:07:48.560
the utilities can bring all of the elements together

00:07:48.560 --> 00:07:51.380
in a way that reflects our highest priorities,

00:07:51.380 --> 00:07:55.090
the safety and wellbeing of Californians.

00:07:55.090 --> 00:07:57.203
We are in August, with a pandemic

00:07:57.203 --> 00:08:00.000
that is not going away anytime soon,

00:08:00.000 --> 00:08:03.400
SCE has already called a PSPS event,

00:08:03.400 --> 00:08:06.393
whether events are only going to become more severe,

00:08:08.132 --> 00:08:11.140
we are in precisely the moment to understand

00:08:11.140 --> 00:08:13.940
and hear from SCE today.

00:08:13.940 --> 00:08:15.810
Are you ready?

00:08:15.810 --> 00:08:18.520
With that, I will say that I'm very much looking forward

00:08:18.520 --> 00:08:20.400
to hearing from SCE today,

00:08:20.400 --> 00:08:22.740
I will now turn to my representatives

00:08:22.740 --> 00:08:25.060
from Cal OES and CAL FIRE,

00:08:25.060 --> 00:08:28.903
if you have any opening remarks to share, Eric Lamoureux.

00:08:30.660 --> 00:08:31.583
<v ->Thank you President Batjer,</v>

00:08:31.583 --> 00:08:33.280
it's a pleasure to be here today

00:08:33.280 --> 00:08:35.580
representing Director Mark Ghilarducci,

00:08:35.580 --> 00:08:37.560
who's unfortunately not able to join us

00:08:37.560 --> 00:08:41.170
as he's tackling many of the COVID challenges

00:08:41.170 --> 00:08:43.000
that we're helping to guide at the state level

00:08:43.000 --> 00:08:44.420
with the Governor's office.

00:08:44.420 --> 00:08:45.670
It's a pleasure to be here today,

00:08:45.670 --> 00:08:48.590
Cal OES have had opportunity to work with our partners

00:08:48.590 --> 00:08:52.740
at the PUC and CAL FIRE over the last several months

00:08:52.740 --> 00:08:56.010
to participate in both operations, claiming meetings

00:08:56.010 --> 00:08:58.840
as well as executive group meetings.

00:08:58.840 --> 00:09:01.510
Those opportunities to work with the IOUs,

00:09:01.510 --> 00:09:04.067
to understand the steps they're taking,

00:09:04.067 --> 00:09:06.713
to reduce the scope of events in 2020,

00:09:07.766 --> 00:09:10.880
and then the duration of those events.

00:09:10.880 --> 00:09:13.970 line:20%
At Cal OES, we've been working with the IOUs

00:09:13.970 --> 00:09:16.610 line:20%
to help them to standardize their systems

00:09:16.610 --> 00:09:18.270 line:20%
and procedures that are utilized,

00:09:18.270 --> 00:09:21.070
support and provide support with training,

00:09:21.070 --> 00:09:23.458
and generally we're cautiously optimistic

00:09:23.458 --> 00:09:28.380
that we can see events in 2020 that are smaller in scale

00:09:28.380 --> 00:09:29.680
and shorter in duration,

00:09:29.680 --> 00:09:31.170
that's our hope.

00:09:31.170 --> 00:09:34.180
That's what we're hearing from the utilities.

00:09:34.180 --> 00:09:37.402
And so we'll certainly withhold judgment

00:09:37.402 --> 00:09:40.540
and see how the events play out,

00:09:40.540 --> 00:09:42.940
but we are cautiously optimistic.

00:09:42.940 --> 00:09:47.150
However, and it's a pleasure today to hear from our partners

00:09:47.150 --> 00:09:50.058
in Southern California Edison, but we do have concerns.

00:09:50.058 --> 00:09:53.840
We have concerns operationally in 2019

00:09:53.840 --> 00:09:58.840
with what felt like a perpetual PSPS cycle

00:09:58.900 --> 00:10:02.210
that we saw ourselves in with Southern California Edison.

00:10:02.210 --> 00:10:04.580
And it feels to some degree

00:10:04.580 --> 00:10:07.240
that we are entering a similar cycle this year,

00:10:07.240 --> 00:10:08.940
where it appears that they we're using

00:10:08.940 --> 00:10:11.060
a Utility Safety Power Shutoff,

00:10:11.060 --> 00:10:14.710
as opposed to a Public Safety Power Shutoff tool,

00:10:14.710 --> 00:10:17.680
a tool that appears to be more focused

00:10:17.680 --> 00:10:20.650
on reducing the scope of liability,

00:10:20.650 --> 00:10:25.110
as opposed to exercising and utilizing the same data

00:10:25.110 --> 00:10:27.790
that we are using the Emergency Management

00:10:27.790 --> 00:10:31.230
and Fire Services to make sure that our events are aligned.

00:10:31.230 --> 00:10:33.630
The data just isn't thinking up

00:10:33.630 --> 00:10:37.000
with what we're seeing during events, there are wind events,

00:10:37.000 --> 00:10:41.207
but these events are not events that appear to be situations

00:10:42.610 --> 00:10:46.830
where we're gonna see a catastrophic wildfire potential.

00:10:46.830 --> 00:10:49.387
And so that is something that Director Ghilarducci

00:10:49.387 --> 00:10:50.953
and our team feels strongly about

00:10:50.953 --> 00:10:55.953
that we need to continue to work, to refine that effort,

00:10:56.010 --> 00:11:00.046
to ensure that the data that Edison is using is in sync

00:11:00.046 --> 00:11:05.046
with that data that is used by our fire and weather team

00:11:05.280 --> 00:11:06.393
on the state side.

00:11:07.330 --> 00:11:10.404
As I said, we're hopeful that we're gonna see events in 2020

00:11:10.404 --> 00:11:13.866
that do not cause the same longterm impact.

00:11:13.866 --> 00:11:14.699
At the end of the day,

00:11:14.699 --> 00:11:17.140
that's the responsibility of emergency managers

00:11:17.140 --> 00:11:18.930
at the state and local government level

00:11:18.930 --> 00:11:20.860
to deal with the consequences.

00:11:20.860 --> 00:11:24.000
And I know that our IOU partners has been helpful

00:11:24.000 --> 00:11:25.590
in addressing those consequences,

00:11:25.590 --> 00:11:28.580
but we need to get to the point where we are utilizing

00:11:28.580 --> 00:11:33.580
this tool to the most precise extent possible.

00:11:34.610 --> 00:11:36.970
So again, it's a pleasure to be here today,

00:11:36.970 --> 00:11:39.229
look forward to the presentation

00:11:39.229 --> 00:11:41.420
and thank you President Batjer.

00:11:41.420 --> 00:11:42.996
<v ->Thank you, Eric very much,</v>

00:11:42.996 --> 00:11:45.500
Assistant Chief Berlant.

00:11:45.500 --> 00:11:48.020
<v ->Yeah, well, good afternoon President Batjer,</v>

00:11:48.020 --> 00:11:49.097
Commissioners, Daniel Berlant,

00:11:49.097 --> 00:11:51.507
the Assistant Deputy Director with CAL FIRE

00:11:51.507 --> 00:11:54.180
and the chief of our Wildfire Planning Engineering Division

00:11:54.180 --> 00:11:57.150
sitting in today for Director Thom Porter.

00:11:57.150 --> 00:11:59.870
And obviously one of our main intends of our mission

00:11:59.870 --> 00:12:02.800
is to mitigate wildfires and to prevent them.

00:12:02.800 --> 00:12:06.210
And so we've been working very closely with the CPUC

00:12:06.210 --> 00:12:08.760
as well as the utilities in the development

00:12:08.760 --> 00:12:10.300
of the wildfire mitigation plans

00:12:10.300 --> 00:12:12.115
and this being a component of it,

00:12:12.115 --> 00:12:16.300
this is definitely a good focus for all of us to discuss.

00:12:16.300 --> 00:12:17.610
Obviously our efforts are aimed

00:12:17.610 --> 00:12:19.536
to reduce utility spark wildfires

00:12:19.536 --> 00:12:21.770
and to mitigate the destruction

00:12:21.770 --> 00:12:23.770
from these preventable fires.

00:12:23.770 --> 00:12:25.500
And just to kind of give you a little scope

00:12:25.500 --> 00:12:26.960
of where we are this year,

00:12:26.960 --> 00:12:30.540
already, we have responded to over 6,000 wildfires

00:12:30.540 --> 00:12:33.550
that have burned over 225,000 acres

00:12:33.550 --> 00:12:36.340
in just the first half of the year.

00:12:36.340 --> 00:12:38.010
And of course, it's the fall months

00:12:38.010 --> 00:12:40.440
where we typically experienced the largest

00:12:40.440 --> 00:12:43.490
and most damaging of those wildfires.

00:12:43.490 --> 00:12:45.470
Looking out into our forecast

00:12:45.470 --> 00:12:47.140
over the next couple of months,

00:12:47.140 --> 00:12:50.750
unfortunately it continues to show an above normal

00:12:50.750 --> 00:12:53.683
wildfire potential for much of Southern California

00:12:53.683 --> 00:12:55.130
throughout the basin.

00:12:55.130 --> 00:12:57.610
And so with a below normal rain fall,

00:12:57.610 --> 00:13:01.000
and then even the potential of above normal offshore winds

00:13:01.000 --> 00:13:02.530
come October and November,

00:13:02.530 --> 00:13:05.610
I think that these planning measures are critical.

00:13:05.610 --> 00:13:09.140
So we are appreciative of the opportunity to be here

00:13:09.140 --> 00:13:12.210
and as always continue to be a partner

00:13:12.210 --> 00:13:15.240
with not only our sister agencies,

00:13:15.240 --> 00:13:18.700
but also with the utilities as we work to mitigate

00:13:18.700 --> 00:13:21.880
and reduce if not eliminate

00:13:21.880 --> 00:13:23.340
the types of preventable wildfire.

00:13:23.340 --> 00:13:25.990
So thank you very much president for the opportunity.

00:13:33.840 --> 00:13:35.880
<v ->Okay, thank you, chairman.</v>

00:13:35.880 --> 00:13:37.409
Thank you everyone.

00:13:37.409 --> 00:13:40.140
And good afternoon Commissioners and our partners

00:13:40.140 --> 00:13:43.550
at Cal OES, CAL FIRE, public safety agencies.

00:13:43.550 --> 00:13:44.560
Again, I'm Phil Harrington,

00:13:44.560 --> 00:13:46.850
Senior Vice President of transmission and distribution

00:13:46.850 --> 00:13:48.860
for Southern California Edison.

00:13:48.860 --> 00:13:50.930
I'm joined here today by Marc Ulrich

00:13:50.930 --> 00:13:53.820
our vice president for Customer Service Operations,

00:13:53.820 --> 00:13:54.653
and Erik Takayesu our vice president

00:13:54.653 --> 00:13:57.970
of Transmission Substations operations.

00:13:57.970 --> 00:14:01.300
And he absolutely many of our PSPS planning initiatives,

00:14:01.300 --> 00:14:03.250
so he'll have some contributions today.

00:14:04.410 --> 00:14:07.070
First of all, thank you for holding this public briefing

00:14:07.070 --> 00:14:09.426
and allowing SCE the opportunity to share

00:14:09.426 --> 00:14:12.670
the major PSPS enhancements we've made

00:14:12.670 --> 00:14:15.840
based on the lessons learned from last year's PSPS events.

00:14:15.840 --> 00:14:17.450
Now we provided a presentation

00:14:17.450 --> 00:14:18.720
and I will occasionally reference

00:14:18.720 --> 00:14:21.130
as we move through our conversation today,

00:14:21.130 --> 00:14:23.867
of course, questions will be handled at the end,

00:14:23.867 --> 00:14:27.490
but they're welcome throughout the presentation as well.

00:14:27.490 --> 00:14:30.720
Our approach to our PSPS enhancements is driven primarily

00:14:30.720 --> 00:14:33.317
by two of our core values at SCE,

00:14:33.317 --> 00:14:35.810
and these are values we hold very dearly,

00:14:35.810 --> 00:14:37.886
safety and continuous improvement.

00:14:37.886 --> 00:14:41.100
Now, we've heard the remarks from CAL FIRE

00:14:41.100 --> 00:14:43.180
as we had anticipated this year.

00:14:43.180 --> 00:14:46.110
2020 has already been an active fire season.

00:14:46.110 --> 00:14:48.650
If we look at Apple fire and Riverside, Stagecoach,

00:14:48.650 --> 00:14:51.340
Incurrence, the Texas fire LA County,

00:14:51.340 --> 00:14:53.820
it's so burning in our service territory.

00:14:53.820 --> 00:14:58.130
So last month we saw the vegetation steadily dry out

00:14:58.130 --> 00:14:59.280
across the region,

00:14:59.280 --> 00:15:01.170
and by August 1st, the dead fuels

00:15:01.170 --> 00:15:04.190
throughout many interior areas were near record dry levels

00:15:04.190 --> 00:15:05.650
for this time of year.

00:15:05.650 --> 00:15:07.100
Now, in addition to moisture values,

00:15:07.100 --> 00:15:08.714
we did a living vegetation from the origin levels

00:15:08.714 --> 00:15:12.160
that favor larger and longer duration fires.

00:15:12.160 --> 00:15:13.800
And this was evidenced by the size

00:15:13.800 --> 00:15:15.690
and behavior of the Apple Fire,

00:15:15.690 --> 00:15:18.620
which started in the last day of July.

00:15:18.620 --> 00:15:21.580
So while the vegetation is not historically dry levels,

00:15:21.580 --> 00:15:24.440
it's much stronger than it was this time last year.

00:15:24.440 --> 00:15:26.560
So on with the dry vegetation,

00:15:26.560 --> 00:15:28.980
we're expecting above normal temperatures

00:15:28.980 --> 00:15:30.110
throughout the fall,

00:15:30.110 --> 00:15:33.525
and along with that more frequent Santa Ana Winds.

00:15:33.525 --> 00:15:37.990
So SCE has already conducted three PSPS events this year,

00:15:37.990 --> 00:15:39.710
and one of the three events involved

00:15:39.710 --> 00:15:41.207
de-energizing 17 customers,

00:15:41.207 --> 00:15:43.550
that will also point out that if you compare

00:15:43.550 --> 00:15:45.280
where we were last year,

00:15:45.280 --> 00:15:47.520
we had essentially been in the PSPS event

00:15:47.520 --> 00:15:49.573
from the 4th of July weekend

00:15:49.573 --> 00:15:52.250
to the early part of August continuously.

00:15:52.250 --> 00:15:54.076
And that's a reflection of some of the changes we made

00:15:54.076 --> 00:15:57.110
and we'll come to those in a little bit.

00:15:57.110 --> 00:15:59.900
This is a backdrop to the conversation we're having today.

00:15:59.900 --> 00:16:02.150
And while we anticipate an active fire season,

00:16:02.150 --> 00:16:04.867
the PSPS enhancements I'll cover in this presentation

00:16:04.867 --> 00:16:07.330
have made us much better equipped

00:16:07.330 --> 00:16:10.590
and prepared to support our customers through PSPS events.

00:16:10.590 --> 00:16:13.040
And before we go too much further,

00:16:13.040 --> 00:16:15.290
on behalf of Southern California Edison,

00:16:15.290 --> 00:16:16.730
I wanna thank the first responders

00:16:16.730 --> 00:16:19.700
who've been working around the clock, containing fires,

00:16:19.700 --> 00:16:21.980
as well as our dedicated employees at SCE,

00:16:21.980 --> 00:16:23.537
have also been responding to these fires,

00:16:23.537 --> 00:16:25.240
have been taking great care

00:16:25.240 --> 00:16:26.640
to ensure our customers

00:16:26.640 --> 00:16:29.420
have the assistance they need during these events.

00:16:29.420 --> 00:16:31.670
Now, could we move to the next slide, please?

00:16:34.860 --> 00:16:36.410
We'll go ahead and get started.

00:16:37.420 --> 00:16:40.970
We in SCE recognized the PSPS is a disruptive hardship,

00:16:40.970 --> 00:16:43.320
even more so the added complexity brought on

00:16:43.320 --> 00:16:45.538
by COVID-19 pandemic.

00:16:45.538 --> 00:16:47.867
And this pandemic has put an unprecedented strain

00:16:47.867 --> 00:16:50.750
on public resources and highlighted the importance

00:16:50.750 --> 00:16:52.630
of a robust electric infrastructure

00:16:52.630 --> 00:16:54.327
to the welfare of our state.

00:16:54.327 --> 00:16:56.770
We acknowledge and respect the desirable local governments

00:16:56.770 --> 00:16:58.750
and officials to protect our communities

00:16:58.750 --> 00:17:01.430
at this very, very difficult time.

00:17:01.430 --> 00:17:02.897
We really appreciate the need to address

00:17:02.897 --> 00:17:05.080
the COVID revenue act insurance.

00:17:05.080 --> 00:17:08.230
Our employees, our families live in, to go to school,

00:17:08.230 --> 00:17:09.620
and they're otherwise part of the fabric

00:17:09.620 --> 00:17:11.690
of the communities in which we serve.

00:17:11.690 --> 00:17:13.470
We've taken action to implement measures

00:17:13.470 --> 00:17:16.143
to reduce the infection of possible de-energization

00:17:16.143 --> 00:17:18.900
and a lot of the ongoing shelter in place.

00:17:18.900 --> 00:17:20.800
And when necessary,

00:17:20.800 --> 00:17:23.170
I wanna underscore and when necessary,

00:17:23.170 --> 00:17:24.230
to the safety and welfare of the public,

00:17:24.230 --> 00:17:26.420
which is our top priority,

00:17:26.420 --> 00:17:29.570
we will employ PSPS responsibly,

00:17:29.570 --> 00:17:32.490
and drawing on the collective expertise to the SCE team

00:17:32.490 --> 00:17:35.350
and our partners at Cal OES, CAL FIRE,

00:17:35.350 --> 00:17:37.858
the County and City Emergency Management

00:17:37.858 --> 00:17:40.490
to use upon which we rely for input.

00:17:40.490 --> 00:17:42.880
And the PSPS events that transpires last year

00:17:42.880 --> 00:17:45.560
reinforced the value of efforts are on the grid

00:17:45.560 --> 00:17:48.900
to the key pillar of SCE wildfire mitigation plan.

00:17:48.900 --> 00:17:51.570
Now was the great improvements we've made since last year,

00:17:51.570 --> 00:17:54.390
under the same weather conditions as 2019,

00:17:54.390 --> 00:17:56.690
we expect to see a 30% reduction

00:17:56.690 --> 00:18:00.661
in the number of customers affected by future PSPS events.

00:18:00.661 --> 00:18:04.230
And that equates to approximately 40,000 fewer customers.

00:18:04.230 --> 00:18:06.380
And of those 40,000 customers,

00:18:06.380 --> 00:18:08.620
about half of those customers will not be expected

00:18:08.620 --> 00:18:10.300
to experience a PSPS again,

00:18:10.300 --> 00:18:13.100
unless it's due to an extraordinarily rare circumstance.

00:18:13.960 --> 00:18:15.877
Now, in addition to these big improvements today,

00:18:15.877 --> 00:18:17.850
we are highlight the major enhancements

00:18:17.850 --> 00:18:20.360
to our PSPS protocols,

00:18:20.360 --> 00:18:23.330
which includes our customer and stakeholder engagement plans

00:18:23.330 --> 00:18:24.340
based on the significant lessons learned

00:18:24.340 --> 00:18:28.019
from the 2019 PSPS events.

00:18:28.019 --> 00:18:30.033
Can we advance to the next slide, please.

00:18:35.138 --> 00:18:38.830
So as you know, we have had many, many opportunities

00:18:38.830 --> 00:18:40.000
to discuss this.

00:18:40.000 --> 00:18:42.360
Last October, part of our service territory

00:18:42.360 --> 00:18:45.650
faced many days of elevated wildfire dry conditions,

00:18:45.650 --> 00:18:48.793
marked by severe winds, low humidity, and dry fuels.

00:18:49.910 --> 00:18:53.070
And during these periods, we exercised our PSPS protocols

00:18:53.070 --> 00:18:54.750
to protect the public from the risk

00:18:54.750 --> 00:18:57.640
that our electric equipment will start a fire.

00:18:57.640 --> 00:18:59.950
We shared this before, but as a reminder,

00:18:59.950 --> 00:19:02.800
for the 5 million customer accounts in our service area,

00:19:02.800 --> 00:19:05.920
approximately 100,000, around 2%,

00:19:05.920 --> 00:19:08.963
were impacted on our most severe PSPS event 2019.

00:19:09.810 --> 00:19:12.070
And 2% may seem like a small number,

00:19:12.070 --> 00:19:14.920
but this number represents more than just customer accounts.

00:19:14.920 --> 00:19:18.520
These are people, their households, their livelihoods,

00:19:18.520 --> 00:19:20.370
where they go to work, where they go to school,

00:19:20.370 --> 00:19:21.980
where they live.

00:19:21.980 --> 00:19:24.920
And that said, line patrols conducted after those shutoffs,

00:19:24.920 --> 00:19:27.290
so I'm more than 40 instances

00:19:27.290 --> 00:19:29.490
of damage or blowing in vegetation

00:19:29.490 --> 00:19:31.110
resulting from these severe conditions.

00:19:31.110 --> 00:19:35.190
And those examples could have sparked a catastrophic fire,

00:19:35.190 --> 00:19:36.023
but they didn't,

00:19:36.023 --> 00:19:38.660
'cause we powered down, preemptively patrolled the line

00:19:38.660 --> 00:19:41.423
to ensure they were safe for turning the power back on.

00:19:42.294 --> 00:19:44.610
Then most recently, after the PSPS event

00:19:44.610 --> 00:19:46.380
on August 2nd this year,

00:19:46.380 --> 00:19:48.610
our post controls found wind damage,

00:19:48.610 --> 00:19:51.580
actually a broken tap line at the insulator on a pole,

00:19:51.580 --> 00:19:53.430
in a tier two high fire risk area.

00:19:53.430 --> 00:19:56.520
And that line has been de-energized.

00:19:56.520 --> 00:19:57.353
So in other words,

00:19:57.353 --> 00:19:59.853
we potentially prevented amunition there.

00:19:59.853 --> 00:20:03.268
This year's events in the October and 2019 events,

00:20:03.268 --> 00:20:07.180
nowadays the presented de-energization is an important,

00:20:07.180 --> 00:20:10.923
necessary, is difficult tool to protect public safety.

00:20:12.270 --> 00:20:14.640
Now, of course, last year's events also revealed lessons

00:20:14.640 --> 00:20:17.840
that have helped us to refine and improve our process.

00:20:17.840 --> 00:20:19.810
The first lesson confirm we're on the right track

00:20:19.810 --> 00:20:22.550
when it comes to deployment and system hardening technology,

00:20:22.550 --> 00:20:25.233
which is cover conductor in sectionalizing devices.

00:20:26.120 --> 00:20:29.110
The second, we identified better opportunities

00:20:29.110 --> 00:20:32.720
to support our PSPS operations and decision making

00:20:32.720 --> 00:20:35.910
by improving our weather forecasting analytic capabilities

00:20:35.910 --> 00:20:39.570
and establishing a dedicated PSPS incident management team

00:20:39.570 --> 00:20:42.040
to support these events in the future.

00:20:42.040 --> 00:20:43.710
Now much more importantly,

00:20:43.710 --> 00:20:45.480
we learned more about what our customers need

00:20:45.480 --> 00:20:47.150
during PSPS events,

00:20:47.150 --> 00:20:50.760
related to communications, information and customer care,

00:20:50.760 --> 00:20:53.650
especially among our most vulnerable customers.

00:20:53.650 --> 00:20:54.483
And while we're committed

00:20:54.483 --> 00:20:56.720
to putting in place operational improvements,

00:20:56.720 --> 00:20:59.220
especially during the COVID-19 pandemic,

00:20:59.220 --> 00:21:02.070
we're just as focused on improving the customer experience

00:21:02.070 --> 00:21:03.853
throughout the PSPS event cycle.

00:21:05.570 --> 00:21:08.770
Lastly, we recognize the desire for more transparency

00:21:08.770 --> 00:21:10.580
around our decision making process

00:21:10.580 --> 00:21:12.330
in our post event reporting.

00:21:12.330 --> 00:21:15.010
Particularly around how we weigh the risk versus benefits

00:21:15.010 --> 00:21:16.123
of shutting off power.

00:21:17.510 --> 00:21:19.423
And we've mentioned, next slide, please.

00:21:21.670 --> 00:21:22.900
I'd like to spend just a moment

00:21:22.900 --> 00:21:25.163
on our PSPS decision making process.

00:21:28.160 --> 00:21:30.120
<v ->This is Commissioner Rechtschaffen,</v>

00:21:32.250 --> 00:21:33.083
Can I just,

00:21:33.083 --> 00:21:36.570
I'm very glad to hear you say about transparency,

00:21:36.570 --> 00:21:39.450
'cause I know that's been a concern of our staff,

00:21:39.450 --> 00:21:40.760
so I want to hear more about that,

00:21:40.760 --> 00:21:43.830
but if I could just go back to your discussion

00:21:43.830 --> 00:21:46.707
about the lessons learned from 2019

00:21:46.707 --> 00:21:49.318
and just go over a couple of things.

00:21:49.318 --> 00:21:51.250
As I try to do the Math,

00:21:51.250 --> 00:21:52.563
you said you expect the 30% reduction

00:21:52.563 --> 00:21:56.193
in the number of customers affected, 20,000 fewer customers.

00:21:57.290 --> 00:22:01.489
So if conditions were the same as there were in 2019,

00:22:01.489 --> 00:22:05.200
so does that mean roughly there are 80,000 customers

00:22:05.200 --> 00:22:10.070
who would be at risk now if there were events

00:22:10.070 --> 00:22:14.040
comparable to 2019, more or less.

00:22:15.090 --> 00:22:16.640
<v ->That is correct Commissioner.</v>

00:22:17.530 --> 00:22:19.447
I will say this however,

00:22:19.447 --> 00:22:21.820
that many of the improvements we've made

00:22:21.820 --> 00:22:23.520
and we'll come to these in a moment,

00:22:23.520 --> 00:22:26.710
having to do at least with our predictive capabilities.

00:22:26.710 --> 00:22:28.860
It's one of the reasons why we have stood up

00:22:28.860 --> 00:22:31.623
fewer PSPS events so far this year.

00:22:32.950 --> 00:22:36.290
What results, and I would say fewer notifications

00:22:36.290 --> 00:22:39.700
of an event that ultimately does not occur.

00:22:39.700 --> 00:22:41.500
That will also say there's a number of factors

00:22:41.500 --> 00:22:43.320
and we'll cover those in some detail

00:22:43.320 --> 00:22:44.830
that are very difficult to predict.

00:22:44.830 --> 00:22:47.650
So it doesn't mean 80,000 would necessarily have those,

00:22:47.650 --> 00:22:49.190
but what we've been able to do

00:22:49.190 --> 00:22:52.540
with some of the, I would say infrastructure changes

00:22:52.540 --> 00:22:56.270
to those circuits, isolating courses of them

00:22:56.270 --> 00:22:58.160
that are not in a high fire risk area,

00:22:58.160 --> 00:23:03.160
really take them out of play completely for a PSPS event.

00:23:03.700 --> 00:23:04.840
There's other things we've done

00:23:04.840 --> 00:23:08.370
that make that 80,000 less likely to have an event,

00:23:08.370 --> 00:23:12.909
some spans of the conductor had been covered.

00:23:12.909 --> 00:23:14.856
In addition to that,

00:23:14.856 --> 00:23:16.793
the additional maintenance we've done,

00:23:16.793 --> 00:23:19.860
I'll talk about this very briefly later,

00:23:19.860 --> 00:23:23.450
in terms of our inspections has given us a much better sense

00:23:23.450 --> 00:23:24.980
of the conditions of our circuits,

00:23:24.980 --> 00:23:28.740
which is an input to making it PSPS decision.

00:23:28.740 --> 00:23:31.310
So additional eyes on the circuits,

00:23:31.310 --> 00:23:33.190
additional weather devices that we've deployed

00:23:33.190 --> 00:23:36.440
to make our information, real time information better.

00:23:36.440 --> 00:23:39.470
In all reality, the remaining 80,000

00:23:39.470 --> 00:23:43.310
also generally less likely under the same events

00:23:43.310 --> 00:23:44.493
to have a PSPS.

00:23:45.640 --> 00:23:47.470
<v ->Okay, that answers the question.</v>

00:23:47.470 --> 00:23:50.390
Thank you, although we may have worse conditions

00:23:50.390 --> 00:23:51.223
than last year,

00:23:51.223 --> 00:23:54.580
so the 2019 comparison may not be totally apt

00:23:54.580 --> 00:23:57.430
because of the dryness and the potential Santa Ana event,

00:23:57.430 --> 00:24:00.070
but that's a very helpful explanation.

00:24:00.070 --> 00:24:02.340
And then the second question I have,

00:24:02.340 --> 00:24:05.570
and I don't know if you have an answer to this,

00:24:05.570 --> 00:24:07.350
but we're always interested in measures

00:24:07.350 --> 00:24:09.190
that have the most bang for the buck.

00:24:09.190 --> 00:24:10.313
You suspect a 30% reduction

00:24:10.313 --> 00:24:12.683
in the number of customers affected.

00:24:13.770 --> 00:24:17.190
Do you have analysis of what you attributed that to?

00:24:17.190 --> 00:24:20.290
How much from sectionalization, better weather forecasting,

00:24:20.290 --> 00:24:22.900
cover conductors, do you have even rough ideas of that

00:24:22.900 --> 00:24:24.543
or is that too hard to evaluate?

00:24:26.200 --> 00:24:29.260
<v ->We do, I don't have all that at my fingertips.</v>

00:24:29.260 --> 00:24:32.320
The bulk of it is due to the sectionalization

00:24:32.320 --> 00:24:34.440
and something we call switching playbooks,

00:24:34.440 --> 00:24:37.420
which are very effective, we'll come to that in a moment,

00:24:37.420 --> 00:24:39.790
but essentially one of the things you can do

00:24:39.790 --> 00:24:43.480
is reconsider your circuitry before events.

00:24:43.480 --> 00:24:46.470
Previously in events, we were essentially assessing

00:24:46.470 --> 00:24:48.630
the circuits in real time,

00:24:48.630 --> 00:24:50.490
and what we've done now is create

00:24:50.490 --> 00:24:51.630
exactly what is in the playbook.

00:24:51.630 --> 00:24:53.280
It says, these are the different configurations

00:24:53.280 --> 00:24:54.480
you can operate under,

00:24:54.480 --> 00:24:56.300
and that's been a large portion.

00:24:56.300 --> 00:24:57.970
And some of these, they overlap,

00:24:57.970 --> 00:25:01.640
so which came first, the sectionalization or the playbook,

00:25:01.640 --> 00:25:03.540
and there's some other things to tease it out.

00:25:03.540 --> 00:25:04.850
And it's something we can provide

00:25:04.850 --> 00:25:07.180
some additional insight into

00:25:07.180 --> 00:25:09.541
if you would find that helpful Commissioner.

00:25:09.541 --> 00:25:11.380
<v ->Thank you very much.</v>

00:25:11.380 --> 00:25:12.213
<v ->Yeah.</v>

00:25:13.730 --> 00:25:16.660
We're actually on slide four, so we're showing seven here,

00:25:16.660 --> 00:25:18.210
we can go back a couple please.

00:25:20.900 --> 00:25:22.233
I'll go ahead and get started in the conversation

00:25:22.233 --> 00:25:23.593
when we back up the slides.

00:25:25.160 --> 00:25:26.850
Again, we're talking right now

00:25:26.850 --> 00:25:28.520
about decision making process,

00:25:28.520 --> 00:25:33.520
and as I mentioned, de-energization is a complex process

00:25:34.252 --> 00:25:37.880
and it's one we do not take lightly.

00:25:37.880 --> 00:25:40.010
Many factors go into the decision,

00:25:40.010 --> 00:25:42.000
I'll highlight this in just a moment.

00:25:42.000 --> 00:25:45.880
Of course, weather is one of the biggest factors,

00:25:45.880 --> 00:25:48.660
red flag warnings from the National Weather Service,

00:25:48.660 --> 00:25:51.160
our ongoing assessments or our in house meteorologists

00:25:51.160 --> 00:25:52.440
and fire scientists

00:25:52.440 --> 00:25:54.450
who use very high resolution weather models

00:25:54.450 --> 00:25:56.800
and data from our weather stations

00:25:56.800 --> 00:25:59.060
and the publicly available data we have.

00:25:59.060 --> 00:26:01.480
Some of our forecasting is very granular

00:26:01.480 --> 00:26:06.320
as opposed to, I say broader focused forecasting.

00:26:06.320 --> 00:26:08.650
Sometimes that is accounting for the difference

00:26:08.650 --> 00:26:10.420
in views of whether there's a situation

00:26:10.420 --> 00:26:13.500
that suggest that PSPS should occur.

00:26:13.500 --> 00:26:15.600
We also look at our Fire Potential Index,

00:26:15.600 --> 00:26:18.430
and this is a tool that uses a weather forecast

00:26:18.430 --> 00:26:20.707
and fuel conditions to assess wildfire risks.

00:26:20.707 --> 00:26:22.460
And of course wind speeds.

00:26:22.460 --> 00:26:24.018
Particularly when they're expecting to receive

00:26:24.018 --> 00:26:27.100
the National Weather Service Wind Advisory Levels,

00:26:27.100 --> 00:26:29.720
these pretty much assess when

00:26:29.720 --> 00:26:32.140
you expect to see a lot of blowing vegetation

00:26:32.140 --> 00:26:34.090
or when they exceed the top 1%

00:26:34.090 --> 00:26:37.255
of a historical wind speed in a given area.

00:26:37.255 --> 00:26:38.830
In addition to these inputs,

00:26:38.830 --> 00:26:41.990
we're looking at inputs from underground observers

00:26:41.990 --> 00:26:43.810
and the high fire which we are able to send out

00:26:43.810 --> 00:26:45.517
to moderate conditions in real time.

00:26:45.517 --> 00:26:47.600
And we only do that when it's safe

00:26:47.600 --> 00:26:50.700
and during extreme fire weather conditions,

00:26:50.700 --> 00:26:53.700
and we're generally able to deploy those staff.

00:26:53.700 --> 00:26:56.140
Now, we've also established very strong partnerships

00:26:56.140 --> 00:26:56.973
with senior officials

00:26:56.973 --> 00:26:59.970
from the County State Emergency Management agencies,

00:26:59.970 --> 00:27:01.940
the local state and fire authorities,

00:27:01.940 --> 00:27:04.010
and other first responder agencies.

00:27:04.010 --> 00:27:06.130
Our fire management personnel work very closely

00:27:06.130 --> 00:27:09.010
with all fire agencies and SCE service territory

00:27:09.010 --> 00:27:11.690
to ensure shared situational awareness

00:27:11.690 --> 00:27:15.750
and greater collaboration during incidents.

00:27:15.750 --> 00:27:17.160
And in the event itself,

00:27:17.160 --> 00:27:19.490
we begin out restore public safety powerless

00:27:19.490 --> 00:27:22.197
around three days prior to the PSPS event.

00:27:22.197 --> 00:27:23.940
And we're looking at weather coming ends,

00:27:23.940 --> 00:27:27.060
sometimes over seven days in advance

00:27:27.060 --> 00:27:29.490
and on occasion we'll be reaching out to partners,

00:27:29.490 --> 00:27:31.920
but again, we want to balance notification

00:27:32.950 --> 00:27:33.810
when we see it coming

00:27:33.810 --> 00:27:38.550
versus making a notification when there's a good chance

00:27:38.550 --> 00:27:40.797
the condition alleviates, it doesn't show up.

00:27:40.797 --> 00:27:43.330
And we continue to communicate with these important partners

00:27:43.330 --> 00:27:44.540
throughout the event,

00:27:44.540 --> 00:27:46.370
including regularly scheduled calls

00:27:46.370 --> 00:27:48.957
with County operational areas.

00:27:48.957 --> 00:27:51.254
And the combination of local coordination,

00:27:51.254 --> 00:27:55.810
forecast data and pre patrols, live field observation

00:27:55.810 --> 00:27:57.440
allows us to reach out to customers

00:27:57.440 --> 00:27:59.880
who are at risk potential de-energization

00:27:59.880 --> 00:28:02.260
around 48 hours in advance.

00:28:02.260 --> 00:28:04.510
And because these situations are very dynamic

00:28:04.510 --> 00:28:06.160
and every incident is unique,

00:28:06.160 --> 00:28:09.360
we take each of these factors and other factors.

00:28:09.360 --> 00:28:13.010
It's well over over a dozen factors we look at

00:28:13.010 --> 00:28:15.390
and more depending on the particular situation

00:28:15.390 --> 00:28:17.010
and a consideration before we make a decision

00:28:17.010 --> 00:28:19.630
to de-energize a section.

00:28:19.630 --> 00:28:21.130
Can we move a slide by please.

00:28:24.520 --> 00:28:28.220
Now, PSPS de-energization again is only implemented

00:28:28.220 --> 00:28:29.990
when the forecast and conditions actually occur,

00:28:29.990 --> 00:28:32.470
and we see no other options available

00:28:32.470 --> 00:28:35.123
to mitigate the fire weather danger.

00:28:35.123 --> 00:28:38.470
And this year, to accelerate and concentrate our effort

00:28:38.470 --> 00:28:42.130
on enhancing our PSPS operations, proving our accuracy,

00:28:42.130 --> 00:28:44.390
the effectiveness of our program,

00:28:44.390 --> 00:28:47.190
minimizing the impact for our customers and communities,

00:28:47.190 --> 00:28:50.270
we established a PSPS readiness Incident Management Team

00:28:50.270 --> 00:28:54.180
or IMT, complete with incident commanders

00:28:54.180 --> 00:28:56.663
and full staff to support that effort.

00:28:56.663 --> 00:29:01.180
Now, this team included people from all across the company

00:29:01.180 --> 00:29:03.620
and customer service, in this resiliency,

00:29:03.620 --> 00:29:07.860
local public affairs, operations, transmission distribution,

00:29:07.860 --> 00:29:10.310
information technology, and frankly just

00:29:10.310 --> 00:29:12.460
about every other discipline across the company

00:29:12.460 --> 00:29:14.160
who could support our effort

00:29:14.160 --> 00:29:17.640
to focus on 2020 wildfire season preparedness.

00:29:17.640 --> 00:29:18.750
This includes implementing

00:29:18.750 --> 00:29:20.090
a number of operational enhancements

00:29:20.090 --> 00:29:21.840
as I mentioned some of them earlier,

00:29:21.840 --> 00:29:24.280
to reduce the scope and frequency of PSPS events

00:29:24.280 --> 00:29:27.344
and help minimize the impacts for our customers.

00:29:27.344 --> 00:29:29.650
Some of the teams would accomplishments include,

00:29:29.650 --> 00:29:31.490
this is just a broad one cut,

00:29:31.490 --> 00:29:33.840
created an integrated decision-making dashboard

00:29:33.840 --> 00:29:36.850
to support activations, reducing power BI,

00:29:36.850 --> 00:29:38.346
consolidating our tools.

00:29:38.346 --> 00:29:41.650
We installed over 350 weather stations,

00:29:41.650 --> 00:29:44.700
bring our total right now to over 900.

00:29:44.700 --> 00:29:46.010
We think we'll have around a thousand

00:29:46.010 --> 00:29:47.940
by the end of the year.

00:29:47.940 --> 00:29:49.130
Now we also developed,

00:29:49.130 --> 00:29:51.300
because we wanna make sure we're consistently applying

00:29:51.300 --> 00:29:53.140
these programs and consistently documenting

00:29:53.140 --> 00:29:53.973
what we're doing,

00:29:53.973 --> 00:29:57.557
an end event and a post event QA/QC program.

00:29:57.557 --> 00:29:59.500
And we also developed at virtual

00:29:59.500 --> 00:30:02.093
and in-person IMT activation protocol.

00:30:03.070 --> 00:30:04.840
We also identified and contracted

00:30:04.840 --> 00:30:07.530
with 40 Community Resource Centers, CRCs.

00:30:07.530 --> 00:30:09.700
And we automated our customer

00:30:09.700 --> 00:30:12.130
and public safety partner notification platforms,

00:30:12.130 --> 00:30:14.200
just enhanced our accuracy and speed

00:30:14.200 --> 00:30:15.710
that we could deliver notifications,

00:30:15.710 --> 00:30:17.242
this was a game changer.

00:30:17.242 --> 00:30:21.060
We also made significant upgrades to our sce.com

00:30:21.060 --> 00:30:23.350
and implemented enhanced public alert tools

00:30:23.350 --> 00:30:26.780
like zip code alerts, and also use of the Nextdoor App,

00:30:26.780 --> 00:30:27.930
which we're leveraging.

00:30:29.310 --> 00:30:32.930
May of 2020, we transitioned from the readiness IMT,

00:30:32.930 --> 00:30:35.520
recognizing we are now entering the summertime,

00:30:35.520 --> 00:30:38.554
to a dedicated PSPS IMT.

00:30:38.554 --> 00:30:41.030
And we're following the National Incident Command System

00:30:41.030 --> 00:30:43.810
to ensure a consistency across the organization

00:30:43.810 --> 00:30:45.580
when executing PSPS,

00:30:45.580 --> 00:30:48.110
which will ultimately reduce the impact to customers.

00:30:48.110 --> 00:30:49.550
What we want to make sure

00:30:49.550 --> 00:30:51.759
is that a single alert incident commander,

00:30:51.759 --> 00:30:54.430
basically similar and incident commander

00:30:54.430 --> 00:30:59.430
face with similar data, information and ground level truth,

00:31:00.010 --> 00:31:02.573
we'll make a similar decision around a PSPS event.

00:31:03.570 --> 00:31:06.730
Already we've conducted five PSPS exercises

00:31:06.730 --> 00:31:08.630
in which we simulated the PSPS event,

00:31:08.630 --> 00:31:11.624
and we use the Microsoft teams platform.

00:31:11.624 --> 00:31:13.750
And we tested the tools we have developed,

00:31:13.750 --> 00:31:16.610
the ones I mentioned that consolidated dashboards

00:31:16.610 --> 00:31:19.460
to enhance our situational awareness in PSPS operations

00:31:19.460 --> 00:31:21.057
during these events.

00:31:21.057 --> 00:31:23.950
Now two of the five events were open to external observers

00:31:23.950 --> 00:31:25.310
and more than a hundred external observers

00:31:25.310 --> 00:31:28.670
participated in the last exercise we had this July.

00:31:28.670 --> 00:31:30.680
And during the pandemic,

00:31:30.680 --> 00:31:32.840
we've actually had the live test this things,

00:31:32.840 --> 00:31:34.230
and we use our virtual platform

00:31:34.230 --> 00:31:37.810
to manage the three PSPS events that we've stood up.

00:31:37.810 --> 00:31:42.400
And we don't expect to be able to do this for large events,

00:31:42.400 --> 00:31:45.070
I think it's similar to a utility.

00:31:45.070 --> 00:31:46.890
So it's yesterday I expect to have,

00:31:48.099 --> 00:31:50.980
that's what we do completely remotely, hybrids,

00:31:50.980 --> 00:31:53.230
and then one with a much heavier touch

00:31:53.230 --> 00:31:54.987
in the emergency operation center.

00:31:54.987 --> 00:31:56.563
And that's all due to COVID.

00:31:58.010 --> 00:31:59.410
Another major enhancement,

00:31:59.410 --> 00:32:01.810
it is our circuit sectionalizing capabilities.

00:32:01.810 --> 00:32:03.760
This will continue to be a really important tool

00:32:03.760 --> 00:32:06.895
to reduce the scope and frequency of de-energizations.

00:32:06.895 --> 00:32:08.170
Now, for the past two years,

00:32:08.170 --> 00:32:10.970
we've accelerated the installation of switching devices.

00:32:12.560 --> 00:32:14.040
This has been kind of the hallmark

00:32:14.040 --> 00:32:16.283
of what Edison's System Designs,

00:32:17.420 --> 00:32:19.630
including like 1400 switches that we installed

00:32:19.630 --> 00:32:21.280
that also helps sectionalize,

00:32:21.280 --> 00:32:23.050
and these are remote controlled, not the fuses,

00:32:23.050 --> 00:32:25.680
but are remote controlled devices

00:32:25.680 --> 00:32:27.280
on circus to isolate segments.

00:32:27.280 --> 00:32:29.427
And we've used those to go to sets.

00:32:29.427 --> 00:32:34.230
And this last event where de-energized 17 customers,

00:32:34.230 --> 00:32:36.547
we initially notify 500 potential customers,

00:32:36.547 --> 00:32:38.247
but we're able, alternately sectionalize the circuit

00:32:38.247 --> 00:32:40.700
to get it down to 17.

00:32:40.700 --> 00:32:43.583
Can we advance to the next slide please, slide six.

00:32:46.450 --> 00:32:48.180
With those operational enhancements covered,

00:32:48.180 --> 00:32:50.130
I'd like to focus now on how we've improved

00:32:50.130 --> 00:32:51.710
our customer communication system

00:32:51.710 --> 00:32:54.225
to improve the information readily available

00:32:54.225 --> 00:32:56.290
and provide easier access.

00:32:56.290 --> 00:32:58.690
After the 2019 PSPS events,

00:32:58.690 --> 00:33:00.630
we reviewed our customer care plans

00:33:00.630 --> 00:33:02.490
by surveying actual customers

00:33:02.490 --> 00:33:04.277
who experienced PSPS instances.

00:33:04.277 --> 00:33:06.530
And we ask them what their pain points were.

00:33:06.530 --> 00:33:09.443
That certainly helped us to prioritize our improvements.

00:33:10.720 --> 00:33:13.850
First, expand our alerts for non-SCE account holders

00:33:13.850 --> 00:33:15.280
and non-SEC account customers,

00:33:15.280 --> 00:33:18.130
which is renters, tenants, family, and relatives,

00:33:18.130 --> 00:33:21.453
not registered to receive outage alerts based on zip codes.

00:33:21.453 --> 00:33:25.000
Regarding our website, sce.com,

00:33:25.000 --> 00:33:27.803
candidly, we had difficulty keeping that system up

00:33:27.803 --> 00:33:30.150
here in certain times due to all the traffic

00:33:30.150 --> 00:33:32.810
generated by customer interests in October.

00:33:32.810 --> 00:33:35.810
The sce.com performance has been significantly upgraded,

00:33:35.810 --> 00:33:37.320
provide increased site capacity

00:33:37.320 --> 00:33:40.410
and reliability for PSPS content.

00:33:40.410 --> 00:33:43.000
The site's now capable of revival serving

00:33:43.000 --> 00:33:46.530
greater than 5 million PSPS specific pages per hour.

00:33:46.530 --> 00:33:49.100
That's up from a capability of around 200,000 before,

00:33:49.100 --> 00:33:52.093
so we've seen a 25 fold increase in capacity there.

00:33:53.200 --> 00:33:55.710
We also heard from stakeholders that are circuit based maps

00:33:55.710 --> 00:33:57.620
with difficult to understand.

00:33:57.620 --> 00:33:59.390
The sce.com has been upgraded

00:33:59.390 --> 00:34:01.600
to provide customer friendly outage information,

00:34:01.600 --> 00:34:03.520
which includes interactive mapping,

00:34:03.520 --> 00:34:05.810
enabled street level zoom capabilities,

00:34:05.810 --> 00:34:07.700
the upended to index, which I think we all have,

00:34:07.700 --> 00:34:09.233
we have a samples of the maps

00:34:09.233 --> 00:34:10.870
that are available to the public.

00:34:10.870 --> 00:34:14.603
It also goes available to our agency partners.

00:34:15.810 --> 00:34:18.290
Using the interactive maps on our website,

00:34:18.290 --> 00:34:21.180
customers can zoom in to see speak level information,

00:34:21.180 --> 00:34:24.010
including areas under consideration for de-energization,

00:34:24.010 --> 00:34:27.786
including the periods of concern for a start and end time.

00:34:27.786 --> 00:34:29.460
We also highlight de-energized circuits

00:34:29.460 --> 00:34:31.920
with an estimated restoration date and time

00:34:31.920 --> 00:34:34.200
and the locations of community crude vehicles

00:34:34.200 --> 00:34:36.760
and community resource centers and the address date

00:34:36.760 --> 00:34:39.487
and hours that the facilities will be operational.

00:34:39.487 --> 00:34:41.110
That customers will also have access

00:34:41.110 --> 00:34:43.113
to dynamic near realtime information

00:34:43.113 --> 00:34:46.123
for the potential hand access PSPS event.

00:34:47.094 --> 00:34:48.820
Additionally, we're working

00:34:48.820 --> 00:34:51.330
with our 211 information service entities

00:34:51.330 --> 00:34:52.850 line:20%
across our service area

00:34:52.850 --> 00:34:54.460 line:20%
to better support effective customers

00:34:54.460 --> 00:34:57.653
who may dial in for assistance during a PSPS event.

00:34:58.730 --> 00:35:01.310
Now, in addition to improving customer communications,

00:35:01.310 --> 00:35:02.950
we also concentrate our efforts

00:35:02.950 --> 00:35:05.580
on expanding our customer programs and services,

00:35:05.580 --> 00:35:08.800
especially for our most vulnerable populations.

00:35:08.800 --> 00:35:12.000
Among the most vulnerable customers during de-energization

00:35:12.000 --> 00:35:13.760
are those reliant on medical devices

00:35:13.760 --> 00:35:15.217
for life sustaining purposes

00:35:15.217 --> 00:35:17.766
and who cannot afford certain critical items

00:35:17.766 --> 00:35:19.567
that support their resiliency.

00:35:19.567 --> 00:35:21.310
And we're offering a full subsidy

00:35:21.310 --> 00:35:23.683
for battery backups solutions to all.

00:35:25.170 --> 00:35:28.845
<v ->This is Genevieve, are you on the next slide,</v>

00:35:28.845 --> 00:35:33.140
which says providing valued programs and services?

00:35:33.140 --> 00:35:37.303
<v ->Oh, I think we need to prevent the conflict,</v>

00:35:38.429 --> 00:35:39.760
Can you go to the next slide please?

00:35:39.760 --> 00:35:41.943
<v Genevieve>Yeah, okay, thank you.</v>

00:35:43.850 --> 00:35:44.974
<v ->Okay, here we are,</v>

00:35:44.974 --> 00:35:46.641
thank you Genevieve.

00:35:51.880 --> 00:35:54.010
Again, sorry, the intent of the program is to provide

00:35:54.010 --> 00:35:57.150
a backup battery facility, 24 hours of resiliency,

00:35:57.150 --> 00:36:00.260
we began offering the subsidy in early July of 2020.

00:36:01.130 --> 00:36:02.900
Customers rely on Well Water Company

00:36:02.900 --> 00:36:07.220
to receive a rebate of up to $500 towards backup generation

00:36:07.220 --> 00:36:09.610
and customers that need a portable power battery

00:36:09.610 --> 00:36:11.770
can receive a $50 rebate.

00:36:11.770 --> 00:36:14.210
Now, in addition, we've taken a targeted approach

00:36:14.210 --> 00:36:16.410
to augment our services for customers

00:36:16.410 --> 00:36:18.770
who've been impacted by power shut off.

00:36:18.770 --> 00:36:21.090
For example, we're creating resiliency zones

00:36:21.090 --> 00:36:22.710
in which backup power will be provided

00:36:22.710 --> 00:36:25.953
to essential services in certain rural areas.

00:36:25.953 --> 00:36:28.600
It's like a gas station, maybe a convenience store

00:36:28.600 --> 00:36:31.170
or a school, the location that the community needs

00:36:31.170 --> 00:36:33.630
to support their resiliency.

00:36:33.630 --> 00:36:36.440
And we're also exploring the capability and feasibility

00:36:36.440 --> 00:36:39.020
that is still on temporary back up generation.

00:36:39.020 --> 00:36:42.030
An underground portions of selected de-energized circuits

00:36:42.030 --> 00:36:44.350
that've experienced PSPS events.

00:36:44.350 --> 00:36:46.110
These are bigger blocks.

00:36:46.110 --> 00:36:48.460
But we've also developed 1,100 circuits

00:36:48.460 --> 00:36:50.400
specific customer care plans,

00:36:50.400 --> 00:36:52.570
re circuiting our high fire risk area.

00:36:52.570 --> 00:36:54.920
These plans are going to provide an overview

00:36:54.920 --> 00:36:56.440
of the customer profiles on a circuit,

00:36:56.440 --> 00:36:58.880
including how many are identified as critical care

00:36:58.880 --> 00:37:00.750
or business essential services.

00:37:00.750 --> 00:37:03.150
We'll also be able to see which programs the customers

00:37:03.150 --> 00:37:05.240
are eligible for and which programs

00:37:05.240 --> 00:37:07.700
and services they participate in.

00:37:07.700 --> 00:37:09.460
We're also providing preparedness

00:37:09.460 --> 00:37:11.280
and resiliency planning support

00:37:11.280 --> 00:37:13.473
for critical infrastructure providers.

00:37:13.473 --> 00:37:16.557
Can we advance to the next slide please.

00:37:17.440 --> 00:37:20.910
<v ->So Phil, let me ask a few questions right here.</v>

00:37:20.910 --> 00:37:25.220
Yesterday, we heard from San Diego Gas and Electric,

00:37:25.220 --> 00:37:29.970
that medical rate customers

00:37:29.970 --> 00:37:32.290
who experienced the PSPS last year,

00:37:32.290 --> 00:37:37.290
they had a little over 1200 customers were earmarked

00:37:40.260 --> 00:37:44.810
to receive the lease on battery backup unit.

00:37:44.810 --> 00:37:49.810
And you have here that you're looking to deploy (mumbles)

00:37:53.020 --> 00:37:54.313
So you're looking to,

00:37:55.690 --> 00:37:57.160
do you have some similar metrics,

00:37:57.160 --> 00:37:59.841
I recall we all had oversight board meeting

00:37:59.841 --> 00:38:01.091
with your representative,

00:38:03.110 --> 00:38:06.233
gave us some metrics and I'm not recalling what they are.

00:38:07.083 --> 00:38:07.916
<v ->Okay.</v>

00:38:07.916 --> 00:38:10.166
(mumbling)

00:38:11.245 --> 00:38:12.560
Certainly, certainly Commissioner.

00:38:12.560 --> 00:38:14.467
Yeah, we are targeting again 2,500

00:38:14.467 --> 00:38:17.803
and these are income qualified critical care customers.

00:38:18.640 --> 00:38:22.080
And we focus on really the set that we expect

00:38:22.080 --> 00:38:25.283
we'll need these that are in both intersecting programs.

00:38:26.130 --> 00:38:30.250
I'd like to ask our vice president of customer service,

00:38:30.250 --> 00:38:32.830
operations support operations, Marc Ulrich

00:38:32.830 --> 00:38:34.450
to jump in with some more metrics.

00:38:34.450 --> 00:38:39.450
I believe you were at that workshop, Marc.

00:38:40.300 --> 00:38:42.450
<v Marc>Thanks Phil, can you hear me?</v>

00:38:42.450 --> 00:38:43.283
<v ->We hear you.</v>

00:38:44.560 --> 00:38:47.460
<v ->Thank you, Commissioner Shiroma.</v>

00:38:47.460 --> 00:38:50.500
We had listened to San Diego's yesterday.

00:38:50.500 --> 00:38:53.790
Similar to them, we intend to cover all customers

00:38:53.790 --> 00:38:56.270
that are in a high fire risk area

00:38:56.270 --> 00:38:57.467
that are eligible for this.

00:38:57.467 --> 00:38:59.780
And that means they have two criteria.

00:38:59.780 --> 00:39:01.720
One is they're a critical care customer,

00:39:01.720 --> 00:39:05.090
and the second is their income qualified or low income.

00:39:05.090 --> 00:39:06.690
The last time we pulled a report,

00:39:06.690 --> 00:39:10.060
it was slightly less than 2,500 customers.

00:39:10.060 --> 00:39:12.680
That population moves over time,

00:39:12.680 --> 00:39:15.963
but we intend to cover all customers in that category.

00:39:19.741 --> 00:39:23.800
<v ->Commissioner Rechtschaffen, just a follow up question.</v>

00:39:23.800 --> 00:39:25.550
Actually, a couple of them.

00:39:25.550 --> 00:39:28.310
Were you able in your exercises that you conducted,

00:39:28.310 --> 00:39:32.017
were you able to test to see if you are communicating

00:39:34.310 --> 00:39:38.100
with your medical baseline customers?

00:39:38.100 --> 00:39:39.800
Were they part of your tasks?

00:39:39.800 --> 00:39:41.743
And if so, how did that work

00:39:41.743 --> 00:39:43.950
and do you have some lessons learned?

00:39:43.950 --> 00:39:46.343
And then I want to ask another followup question.

00:39:47.307 --> 00:39:49.220
<v Marc>Phil, I can take that if you like.</v>

00:39:49.220 --> 00:39:51.510
This as Marc Ulrich again.

00:39:51.510 --> 00:39:54.220
Yes, for our medical baseline population,

00:39:54.220 --> 00:39:56.910
we separated into two populations.

00:39:56.910 --> 00:40:00.880
One is medical baseline where you have any medical equipment

00:40:00.880 --> 00:40:05.350
and that helps with rate by giving you more kilowatt hours

00:40:05.350 --> 00:40:06.660
at a lower rate.

00:40:06.660 --> 00:40:10.740
The second is which customers are critical care medical

00:40:10.740 --> 00:40:14.720
baseline customers, where they have living issues,

00:40:14.720 --> 00:40:18.160
if their equipment's without power for more than two hours.

00:40:18.160 --> 00:40:21.130
So in our notifications,

00:40:21.130 --> 00:40:24.510
we give out notifications to all the medical baseline

00:40:24.510 --> 00:40:28.150
customers in our circuits during an event

00:40:28.150 --> 00:40:29.550
and before the event.

00:40:29.550 --> 00:40:32.900
We also make sure that for their critical care portion

00:40:32.900 --> 00:40:36.473
of the population, that we have positive contact with them,

00:40:36.473 --> 00:40:38.690
what that means is that we can confirm

00:40:38.690 --> 00:40:40.780
that they have received a notification

00:40:40.780 --> 00:40:42.590
in the form that they prefer,

00:40:42.590 --> 00:40:43.830
whether it's a landline,

00:40:43.830 --> 00:40:46.220
they pushed a button that said, yes, one,

00:40:46.220 --> 00:40:49.393
hit one for you've received this and you understand.

00:40:50.420 --> 00:40:53.150
And that gives us confirmation on the landline,

00:40:53.150 --> 00:40:55.880
on the text, we have them reply back

00:40:55.880 --> 00:40:56.870
that they've received it,

00:40:56.870 --> 00:40:59.760
or they click on a button in the email,

00:40:59.760 --> 00:41:01.640
and that gives us positive confirmation

00:41:01.640 --> 00:41:03.370
that they've received that notice.

00:41:03.370 --> 00:41:05.510
If they do not receive that notice,

00:41:05.510 --> 00:41:09.070
then we do outbound calling with a human.

00:41:09.070 --> 00:41:11.110
And if we don't get contact with them,

00:41:11.110 --> 00:41:14.700
then we send a field service rep to knock on the door.

00:41:14.700 --> 00:41:16.210
<v ->Okay, thank you.</v>

00:41:16.210 --> 00:41:18.980
One follow up question.

00:41:18.980 --> 00:41:20.580
You may have heard it yesterday,

00:41:22.544 --> 00:41:23.630
and my fellow Commissioners and I have talked

00:41:23.630 --> 00:41:24.670
about this more than once.

00:41:24.670 --> 00:41:28.170
We're very concerned about the customers

00:41:28.170 --> 00:41:29.720
that are behind the master meter

00:41:29.720 --> 00:41:31.300
and how they get notification

00:41:31.300 --> 00:41:34.170
and how the timing of that notification.

00:41:34.170 --> 00:41:36.870
That would be people who are in mobile home parks,

00:41:36.870 --> 00:41:40.360
people who live in Section Eight housing apartments,

00:41:40.360 --> 00:41:43.197
for example, folks that you don't necessarily know

00:41:43.197 --> 00:41:45.530
are your customers, but indeed they are your customers.

00:41:45.530 --> 00:41:47.930
How are you identifying them?

00:41:47.930 --> 00:41:51.170
Including those who have medical needs.

00:41:51.170 --> 00:41:53.913
And how are you communicating with them?

00:41:55.080 --> 00:41:56.125
<v Marc>Excellent question.</v>

00:41:56.125 --> 00:41:59.940
This is a major concern for us also at Edison.

00:41:59.940 --> 00:42:03.750
So we have 500 master meter accounts

00:42:03.750 --> 00:42:06.870
that are mobile home parks, where there are sub tenants

00:42:06.870 --> 00:42:09.420
that are not direct customer accounts.

00:42:09.420 --> 00:42:13.610
Of those 500, we know that there are 1700 customers

00:42:13.610 --> 00:42:15.780
behind those master meters.

00:42:15.780 --> 00:42:20.370
And all the medical baseline and critical care customers

00:42:20.370 --> 00:42:25.280
behind the master meter are now getting direct messages,

00:42:25.280 --> 00:42:28.830
using the contact information from their applications.

00:42:28.830 --> 00:42:31.940
So that was a problem last year in 2019,

00:42:31.940 --> 00:42:34.550
it was a very big concern for us.

00:42:34.550 --> 00:42:35.640
We do send a letter

00:42:35.640 --> 00:42:38.530
and we work with all the master accounts each year.

00:42:38.530 --> 00:42:42.480
They're legally obligated to pass along our information

00:42:42.480 --> 00:42:44.956
about, we give them kits about

00:42:44.956 --> 00:42:48.290
and have them post publicly in their facilities

00:42:48.290 --> 00:42:50.550
information about PSPS,

00:42:50.550 --> 00:42:53.020
information about our medical baseline program,

00:42:53.020 --> 00:42:56.170
information about customer care, et cetera.

00:42:56.170 --> 00:42:58.250
So that was one change we made.

00:42:58.250 --> 00:43:01.380
The other was the now master meter

00:43:01.380 --> 00:43:06.380
can give to the subtenants, their account number and name,

00:43:06.530 --> 00:43:10.320
and they can call directly to set up direct communication,

00:43:10.320 --> 00:43:11.720
so they do not need to rely

00:43:11.720 --> 00:43:13.890
on the master meter account holder.

00:43:13.890 --> 00:43:16.700
And then finally we use total alerts,

00:43:16.700 --> 00:43:19.260
which allows anyone to sign up for alerts.

00:43:19.260 --> 00:43:20.093
<v ->Okay, good.</v>

00:43:20.093 --> 00:43:24.400
So does that 1700, that seems like a very low number

00:43:24.400 --> 00:43:28.011
to me, but I don't wanna quibble with your data,

00:43:28.011 --> 00:43:30.930
but I'm assuming you're continuing to work on that

00:43:30.930 --> 00:43:33.743
population in preparation.

00:43:34.920 --> 00:43:38.910
<v Marc>Yeah, that population is very important to us.</v>

00:43:38.910 --> 00:43:41.040
There's a larger set of population

00:43:41.040 --> 00:43:42.300
that are medical baseline,

00:43:42.300 --> 00:43:45.383
but the equipment that they have is not life threatening.

00:43:47.421 --> 00:43:50.230
And so they're also important to us,

00:43:50.230 --> 00:43:52.350
but not as important as the customers

00:43:52.350 --> 00:43:55.433
who have medical equipment, that's life based.

00:43:56.310 --> 00:43:59.140
<v ->So let me just get this straight with you,</v>

00:43:59.140 --> 00:44:00.800
get an understanding.

00:44:01.830 --> 00:44:06.460
You are supplying subsidized, backup battery,

00:44:06.460 --> 00:44:09.010
I mean, you you're basically providing subsidies.

00:44:09.010 --> 00:44:11.850
You're not actually providing any type of small batteries

00:44:11.850 --> 00:44:12.860
or any type of kits.

00:44:12.860 --> 00:44:15.953
We've gone from Edison yesterday that they actually are.

00:44:16.971 --> 00:44:21.480
<v Marc>Yeah, actually it was San Diego yesterday,</v>

00:44:21.480 --> 00:44:26.480
Edison's today, but we are actually doing exactly

00:44:27.280 --> 00:44:28.470
the same thing as San Diego,

00:44:28.470 --> 00:44:32.360
we were providing a physical battery and a solar panel

00:44:32.360 --> 00:44:35.620
to charge the battery, completely free to the customer,

00:44:35.620 --> 00:44:38.160
they do not have to pay and get reimbursed.

00:44:38.160 --> 00:44:39.680
This is not a rebate program,

00:44:39.680 --> 00:44:41.700
it's a battery backup program

00:44:41.700 --> 00:44:44.540
and it's designed to power their equipment

00:44:44.540 --> 00:44:46.410
for at least 24 hours.

00:44:46.410 --> 00:44:48.430
And one slight difference is

00:44:48.430 --> 00:44:50.250
ours comes with a three year warranty

00:44:50.250 --> 00:44:52.580
instead of a one year warranty.

00:44:52.580 --> 00:44:54.050
<v ->All right, good.</v>

00:44:54.050 --> 00:44:56.490
All right, thank you for clarifying.

00:44:56.490 --> 00:44:58.733
I think Mr. Rechstchaffen has a question.

00:44:59.740 --> 00:45:00.640
<v ->Right (mumbles).</v>

00:45:02.619 --> 00:45:06.220
Just to follow up on your response to the President Batjer

00:45:06.220 --> 00:45:09.917
and Commissioner Shiroma's,

00:45:09.917 --> 00:45:12.010
in the instances where you're providing

00:45:12.010 --> 00:45:14.490
the physical battery and the solar panel,

00:45:14.490 --> 00:45:17.170
what about someone who's renting?

00:45:17.170 --> 00:45:20.803
How are they getting, what's the solutions for them?

00:45:22.250 --> 00:45:24.410
<v Marc>The solution is still the same</v>

00:45:24.410 --> 00:45:27.900
because the battery backup and the solar panel

00:45:27.900 --> 00:45:31.080
do not have to connect into the home.

00:45:31.080 --> 00:45:33.520
It can connect directly to the medical equipment.

00:45:33.520 --> 00:45:37.720
That way we did not want a hamstring a renter

00:45:37.720 --> 00:45:40.570
from being able to adjust their electrical systems

00:45:40.570 --> 00:45:41.403
in their homes.

00:45:42.300 --> 00:45:47.170
<v ->Okay, and if I am not to parse this to find</v>

00:45:47.170 --> 00:45:51.760
but as I understand what Danielle Gas and Electric

00:45:51.760 --> 00:45:55.157
told us yesterday, it's a little bit different than yours

00:45:55.157 --> 00:45:59.690
because they said that they are providing daddy batteries,

00:45:59.690 --> 00:46:02.540
which sounds like it's comparable to what you're doing.

00:46:02.540 --> 00:46:05.330
Batteries says hookup directly to appliances

00:46:05.330 --> 00:46:08.340
or medical equipment rather than to an electric system

00:46:08.340 --> 00:46:11.647
of the house, but they said that at 1,250 medical baseline

00:46:11.647 --> 00:46:15.180
customers, that they were providing all of them

00:46:15.180 --> 00:46:16.620
with these portable batteries,

00:46:16.620 --> 00:46:20.480
whereas what I heard you say is you're providing this

00:46:20.480 --> 00:46:23.820
to 2,500 medical baseline customers

00:46:23.820 --> 00:46:25.330
who are one, income qualified,

00:46:25.330 --> 00:46:27.780
and two who are defined as critical care,

00:46:27.780 --> 00:46:29.593
would you, I heard you say,

00:46:31.028 --> 00:46:32.890
who can't be without power for more than two hours,

00:46:32.890 --> 00:46:35.130
because otherwise it would life threatening.

00:46:35.130 --> 00:46:40.130
So yours is a smaller universe and then there's,

00:46:42.220 --> 00:46:44.863
if I'm understanding what they said yesterday,

00:46:44.863 --> 00:46:48.160
what you said today, and if that's the case,

00:46:48.160 --> 00:46:50.700
do you have a figure of the total number

00:46:50.700 --> 00:46:53.100
of medical baseline customers

00:46:53.100 --> 00:46:57.550
who are within the PSPS period that you've identified,

00:46:57.550 --> 00:46:58.517
including the ones who would not be covered

00:46:58.517 --> 00:47:01.590
by your battery subsidy program?

00:47:01.590 --> 00:47:02.770
<v Marc>Yes.</v>

00:47:02.770 --> 00:47:04.910
You have Commissioner Rechtschaffen,

00:47:04.910 --> 00:47:06.726
you have our statistics correct,

00:47:06.726 --> 00:47:08.520
and our program correct.

00:47:08.520 --> 00:47:12.180
So here, the way you decided it is exactly correct.

00:47:12.180 --> 00:47:16.070
I don't recall whether San Diego's was also income qualified

00:47:16.070 --> 00:47:19.730
or not, I thought it was, but I may be wrong on that.

00:47:19.730 --> 00:47:23.670
But the total population of medical baseline customers

00:47:23.670 --> 00:47:27.040
that we have in the high fire risk areas

00:47:27.040 --> 00:47:31.320
is a much larger than just 2,500.

00:47:31.320 --> 00:47:34.780
We have roughly 20,000 medical baseline customers

00:47:34.780 --> 00:47:36.820
in high fire risk areas.

00:47:36.820 --> 00:47:38.110
But some of those,

00:47:38.110 --> 00:47:43.110
some of the equipment that the other medical baseline

00:47:44.367 --> 00:47:46.867
customers have are not life threatening equipment.

00:47:48.769 --> 00:47:53.263
And this is judged by a selection that the customer chooses,

00:47:53.263 --> 00:47:55.115
it's not Edison.

00:47:55.115 --> 00:47:58.698
<v ->Okay, have you for these 2,500 customers,</v>

00:47:59.710 --> 00:48:03.050
do they already have the equipment right now?

00:48:03.050 --> 00:48:04.910
Have you already deployed this?

00:48:04.910 --> 00:48:07.700
<v Marc>We have deployed, and we have roughly,</v>

00:48:07.700 --> 00:48:10.390
I believe about a hundred or so

00:48:10.390 --> 00:48:15.310
that are either installed today or going to be installed.

00:48:15.310 --> 00:48:18.620
Our supply chain was slightly delayed,

00:48:18.620 --> 00:48:20.509
partly because we wanted to negotiate

00:48:20.509 --> 00:48:23.870
longer warranty periods than just 12 months.

00:48:23.870 --> 00:48:27.840
And so we anticipate getting the shipment for about,

00:48:27.840 --> 00:48:30.790
we have about 250 to 500 batteries on hand

00:48:30.790 --> 00:48:32.370
that we're installing now.

00:48:32.370 --> 00:48:34.930
And about 2000 should come in September

00:48:34.930 --> 00:48:36.153
in about three weeks.

00:48:37.930 --> 00:48:39.077
<v ->Thank you.</v>

00:48:39.077 --> 00:48:42.493
<v ->President Batjer, I had one more question.</v>

00:48:43.911 --> 00:48:46.420
And this being similar to the questions I asked

00:48:46.420 --> 00:48:48.520
San Diego Gas and Electric.

00:48:48.520 --> 00:48:53.520
So when I see you provide up to $500 rebate

00:48:54.320 --> 00:48:56.300
for water pumping,

00:48:56.300 --> 00:49:01.300
and I just wanted to know in terms of energizing food banks

00:49:03.600 --> 00:49:06.460
and any kinds of additional efforts

00:49:06.460 --> 00:49:07.293
to ensure that folks have clean drinking water.

00:49:07.293 --> 00:49:12.167
Can you describe any additional efforts?

00:49:17.660 --> 00:49:19.480
<v ->President Batjer, I'll jump in</v>

00:49:19.480 --> 00:49:24.187
and Marc, you please recall the question

00:49:24.187 --> 00:49:25.893
on the food bags from STG,

00:49:27.310 --> 00:49:29.670
that is an area where we need to continue to do more work,

00:49:29.670 --> 00:49:31.840
one of the areas we spend a lot of time

00:49:32.680 --> 00:49:35.340
and up until this PSPS season is working

00:49:35.340 --> 00:49:39.260
with County agencies and our emergency partners.

00:49:39.260 --> 00:49:41.640
And in events, we also are working with them

00:49:41.640 --> 00:49:44.110
to look at what the critical loads are on a system.

00:49:44.110 --> 00:49:49.110
So we would certainly look to work with those entities,

00:49:49.220 --> 00:49:51.890
food banks, and other similar facilities

00:49:51.890 --> 00:49:54.480
in events and if backup power required,

00:49:54.480 --> 00:49:55.313
we've worked with them

00:49:55.313 --> 00:49:59.490
to define solutions as far as pre identifying

00:49:59.490 --> 00:50:01.510
those at this point in time, Marc,

00:50:01.510 --> 00:50:03.260
I think we have a little bit of work to do there,

00:50:03.260 --> 00:50:07.240
but why don't you jump in and share what we've done so far?

00:50:07.240 --> 00:50:08.439
<v Marc>Yeah, that's correct Phil,</v>

00:50:08.439 --> 00:50:11.130
this is an area we need to improve.

00:50:11.130 --> 00:50:13.300
We do see the concern you have,

00:50:13.300 --> 00:50:18.300
we have seen anecdotally some of our food banks

00:50:18.300 --> 00:50:22.060
have gone from two facilities to four facility

00:50:22.060 --> 00:50:23.500
to six facilities,

00:50:23.500 --> 00:50:28.110
and so they're growing and spreading since the pandemic.

00:50:28.110 --> 00:50:29.880
And some of the things we have done is

00:50:29.880 --> 00:50:33.250
we've looked at, are they on the right rate?

00:50:33.250 --> 00:50:34.650
Can they get a cheaper rate?

00:50:34.650 --> 00:50:37.150
Is there a way to make sure that

00:50:37.150 --> 00:50:40.680
they are all availing themselves

00:50:40.680 --> 00:50:42.840
of all the programs we have.

00:50:42.840 --> 00:50:45.500
But one thing we have not done is plotted out

00:50:45.500 --> 00:50:50.500
and treated them separately from other business customers

00:50:51.170 --> 00:50:53.060
and treated them like essential customers.

00:50:53.060 --> 00:50:55.580
So hearing your guys' questions yesterday,

00:50:55.580 --> 00:50:57.080
we've been thinking about it already,

00:50:57.080 --> 00:50:58.980
but now it's give us confirmation,

00:50:58.980 --> 00:51:01.913
it's an additional area we need to look into.

00:51:03.100 --> 00:51:06.291
<v ->Marc, since we are in this area of questioning,</v>

00:51:06.291 --> 00:51:10.530
I know you still have several slides to go through.

00:51:10.530 --> 00:51:15.220
However, one of the questions we asked San Diego yesterday,

00:51:15.220 --> 00:51:20.220
asking you again today is in terms of critical sites

00:51:20.746 --> 00:51:23.179
that we didn't have to consider last year,

00:51:23.179 --> 00:51:27.140
of course we have to now consider COVID-19 testing sites

00:51:27.140 --> 00:51:29.929
and testing sites are not all, as we all know,

00:51:29.929 --> 00:51:32.212
always medical facilities,

00:51:32.212 --> 00:51:33.600
which you probably already have

00:51:33.600 --> 00:51:35.653
on your critical facility web,

00:51:35.653 --> 00:51:36.790
they could be at fairgrounds

00:51:36.790 --> 00:51:39.950
and other places throughout your service territory.

00:51:39.950 --> 00:51:43.123
Are you considering backup power for them as well?

00:51:44.616 --> 00:51:46.270
<v ->We are chairman,</v>

00:51:46.270 --> 00:51:50.420
and I will say that this is a fluid area as you note,

00:51:50.420 --> 00:51:53.573
some of these facilities are popping up very quickly.

00:51:54.550 --> 00:51:57.400
We have worked quite a bit with county directors

00:51:57.400 --> 00:52:01.250
to identify as many of these locations as we possibly could.

00:52:01.250 --> 00:52:03.940
I had a time Marc's team

00:52:03.940 --> 00:52:07.600
and our local public affairs team has also been engaged

00:52:07.600 --> 00:52:10.400
in the field to identify as many of these facilities

00:52:10.400 --> 00:52:13.090
as we can and work with them

00:52:13.090 --> 00:52:14.323
to understand their resiliency needs,

00:52:14.323 --> 00:52:18.830
and in the event that there is a PSPS event,

00:52:18.830 --> 00:52:21.540
to help them with arranging backup generation.

00:52:21.540 --> 00:52:23.230
Now there's been some additional outreach

00:52:23.230 --> 00:52:26.893
with the hospital association that Marc's team has done.

00:52:26.893 --> 00:52:30.029
So I will say it's something we've been very conscious of,

00:52:30.029 --> 00:52:33.776
we worked with the Pomona Fairground recently,

00:52:33.776 --> 00:52:34.695
not too long ago at least,

00:52:34.695 --> 00:52:37.680
where they set up a COVID testing center.

00:52:37.680 --> 00:52:39.730
It's part of our program to reach out to

00:52:39.730 --> 00:52:40.790
as many of these as we can

00:52:40.790 --> 00:52:42.620
and get as much insight as we can.

00:52:42.620 --> 00:52:46.970
I do expect that will also be an end event action item

00:52:48.380 --> 00:52:50.370
that our teams will be dealing with

00:52:50.370 --> 00:52:52.460
when we set up a PSPS IMT,

00:52:52.460 --> 00:52:54.670
something our teams will be working with,

00:52:54.670 --> 00:52:57.610
the emergency managers in the jurisdictions

00:52:57.610 --> 00:53:00.310
that we are expecting a PSPS.

00:53:00.310 --> 00:53:01.430
But we have done quite a few things

00:53:01.430 --> 00:53:03.500
in the last several months.

00:53:03.500 --> 00:53:06.030
Marc, you gotten any gaps there?

00:53:06.030 --> 00:53:07.690
I may have missed something.

00:53:07.690 --> 00:53:11.570
<v Marc>Yeah, you didn't miss anything, Phil, good job.</v>

00:53:11.570 --> 00:53:13.660
The only other thing I would add is

00:53:13.660 --> 00:53:16.073
it's not just PSPS related,

00:53:16.073 --> 00:53:19.960
that we're concerned for the COVID popup testing sites

00:53:19.960 --> 00:53:21.450
and Pomona Fairgrounds

00:53:21.450 --> 00:53:23.850
and example that was a maintenance outage

00:53:23.850 --> 00:53:25.010
that was gonna be done.

00:53:25.010 --> 00:53:27.840
And that was a particular concern for us,

00:53:27.840 --> 00:53:30.160
so we rearrange the maintenance outage

00:53:30.160 --> 00:53:35.160
and helped provide and help them procure a generation

00:53:36.110 --> 00:53:38.580
so that the outside could continue on,

00:53:38.580 --> 00:53:41.330
but otherwise you got it all straight, so.

00:53:41.330 --> 00:53:44.360
<v ->Yeah, chairman we've been having the opportunity</v>

00:53:44.360 --> 00:53:47.370
to work much closely with our local governments,

00:53:47.370 --> 00:53:50.300
with a stay at home orders.

00:53:50.300 --> 00:53:53.410
And so we've been really up to our whole program,

00:53:53.410 --> 00:53:54.920
in terms of outage coordination,

00:53:54.920 --> 00:53:58.390
which has given us more insight into specific loads,

00:53:58.390 --> 00:54:01.150
loads that we might not have been as focused on,

00:54:01.150 --> 00:54:05.320
but for COVID-19, and so that I think has helped us.

00:54:05.320 --> 00:54:10.320
And it's as Marc knows really align with our PSPS efforts.

00:54:13.060 --> 00:54:15.030
<v Daniel>Phil, this is Daniel Berlant from CAL FIRE,</v>

00:54:15.030 --> 00:54:15.890
quick question for you,

00:54:15.890 --> 00:54:17.750
at how closely are you guys working

00:54:17.750 --> 00:54:19.500
with the telecommunication providers

00:54:19.500 --> 00:54:21.940
to ensure that they have the necessary data

00:54:21.940 --> 00:54:26.261
on where the PSPS circuits are gonna be shut off

00:54:26.261 --> 00:54:29.053
and just can you talk about that collaboration?

00:54:30.460 --> 00:54:35.010
<v ->I can, and we have conducted outreach both locally</v>

00:54:35.010 --> 00:54:37.090
and at the national level.

00:54:37.090 --> 00:54:41.110
We have spent time with the telecoms

00:54:41.110 --> 00:54:43.400
to help them understand some of our circuits

00:54:43.400 --> 00:54:44.660
and what our circus look like.

00:54:44.660 --> 00:54:49.210
We also have a program when we are in an event also

00:54:49.210 --> 00:54:52.980
to engage with the critical services, telecommunications

00:54:52.980 --> 00:54:55.040
and water agencies, as well,

00:54:55.040 --> 00:54:58.050
to explain to them what our circuit playbooks look like,

00:54:58.050 --> 00:54:59.904
what that could mean for the event,

00:54:59.904 --> 00:55:02.314
and what could ultimately be de-energized.

00:55:02.314 --> 00:55:07.030
So we have spent a good amount of time with telecoms,

00:55:07.030 --> 00:55:08.760
water agencies and others.

00:55:08.760 --> 00:55:11.020
I think more work continues to need to be done there,

00:55:11.020 --> 00:55:13.780
I don't wanna suggest we're anywhere near complete

00:55:13.780 --> 00:55:15.230
with that effort,

00:55:15.230 --> 00:55:16.990
but it is a place we've been spending time

00:55:16.990 --> 00:55:18.900
to make sure that they understand

00:55:18.900 --> 00:55:20.890
and we understand their needs

00:55:20.890 --> 00:55:23.030
and the resiliency implications.

00:55:23.030 --> 00:55:25.610
Recognizing that there are obligations there

00:55:25.610 --> 00:55:27.810
for their own resilience, but we wanna help them

00:55:27.810 --> 00:55:29.250
and want them to understand our system

00:55:29.250 --> 00:55:30.990
and what a PSPS looks like.

00:55:30.990 --> 00:55:32.364
And there may be cases frankly,

00:55:32.364 --> 00:55:36.284
where their backup generation may not work as intended,

00:55:36.284 --> 00:55:37.432
and we wanna understand that,

00:55:37.432 --> 00:55:40.424
and in an incident be prepared

00:55:40.424 --> 00:55:43.518
if we have the resources to support them

00:55:43.518 --> 00:55:46.935
if their back of generation doesn't work.

00:55:48.221 --> 00:55:50.580
<v ->As a follow on to that question, if I may,</v>

00:55:50.580 --> 00:55:55.580
one of the concerns that was voiced to us by AT&amp;T,

00:55:55.692 --> 00:55:58.793
in particular, but other Telcos,

00:56:01.190 --> 00:56:04.080
that they were not given adequate time,

00:56:04.080 --> 00:56:07.935
not adequately alerted by you all.

00:56:07.935 --> 00:56:10.500
And I'm sure, I hope during this past year,

00:56:10.500 --> 00:56:14.780
you all have worked out that communications with them.

00:56:14.780 --> 00:56:19.310
<v ->Yeah, chairman we have improved all of our communications,</v>

00:56:19.310 --> 00:56:21.290
including that one, the Telcos,

00:56:21.290 --> 00:56:23.433
and we intend to continue to do that.

00:56:24.840 --> 00:56:26.330
One thing that has arisen

00:56:26.330 --> 00:56:29.550
and it's something we continue to work on

00:56:29.550 --> 00:56:34.470
is the nature of some PSPS events come relatively rapidly,

00:56:34.470 --> 00:56:36.550
we have seen a couple of events

00:56:36.550 --> 00:56:38.940
that have appeared not with a three day roll off,

00:56:38.940 --> 00:56:41.700
but with a 24 hour or less roll up,

00:56:41.700 --> 00:56:45.000
it's just the nature of some events,

00:56:45.000 --> 00:56:47.820
but regardless, we will work diligently with them,

00:56:47.820 --> 00:56:50.730
and that I feel is in much better shape

00:56:50.730 --> 00:56:52.780
than it was before.

00:56:52.780 --> 00:56:55.250
Eric, I think you've been doing some work in that regard

00:56:55.250 --> 00:56:57.005
and Marc, is there anything you wanna add?

00:56:57.005 --> 00:56:59.124
Didn't you do think this is an important topic

00:56:59.124 --> 00:57:02.027
that we've addressed and we need to make sure that

00:57:02.027 --> 00:57:05.587
we're responsive here.

00:57:05.587 --> 00:57:07.940
<v Marc>Eric, I can jump in real quick</v>

00:57:07.940 --> 00:57:09.060
and then hand it to you?

00:57:09.060 --> 00:57:14.060
I know that for the last three years, 2018, 19 and 20,

00:57:14.820 --> 00:57:18.700
we've had three day workshops with our telecom partners,

00:57:18.700 --> 00:57:20.760
as Phil said, it's important

00:57:20.760 --> 00:57:22.630
that they own their own resiliency,

00:57:22.630 --> 00:57:25.750
but they really need us to be a partner in it.

00:57:25.750 --> 00:57:30.200
So we'll continue to have those three day workshops.

00:57:30.200 --> 00:57:33.857
We also each year confirm who is the right contacts,

00:57:33.857 --> 00:57:37.630
for 24 hour a day partners,

00:57:37.630 --> 00:57:40.390
we need to know who they want us to contact with.

00:57:40.390 --> 00:57:44.740
So our business customer division confirms that each year

00:57:44.740 --> 00:57:47.260
and we refresh that information.

00:57:47.260 --> 00:57:51.882
And then, we send these notifications in multiple forms

00:57:51.882 --> 00:57:53.310
to the contacts too.

00:57:53.310 --> 00:57:57.560
So if there's a contact problem, I think it was in the past,

00:57:57.560 --> 00:58:01.150
I'm hoping we won't see another one in the future

00:58:01.150 --> 00:58:04.823
because it's hard for them to be resilient without our help.

00:58:05.673 --> 00:58:09.020
<v ->I appreciate that very much, I agree with you.</v>

00:58:09.020 --> 00:58:10.333
I hope it's resolved.

00:58:12.380 --> 00:58:13.570
<v ->President Batjer, this is Eric,</v>

00:58:13.570 --> 00:58:15.563
if I could ask a couple of questions.

00:58:17.900 --> 00:58:20.190
First to go back to COVID,

00:58:20.190 --> 00:58:21.910
appreciate the work you guys are doing

00:58:21.910 --> 00:58:23.927
in terms of identifying facilities

00:58:23.927 --> 00:58:25.790
to President Batjer's point,

00:58:25.790 --> 00:58:28.340
not just our traditional healthcare facilities,

00:58:28.340 --> 00:58:29.950
but the other operations.

00:58:29.950 --> 00:58:31.730
I know several months ago,

00:58:31.730 --> 00:58:34.730
as we got started on that COVID emergency response,

00:58:34.730 --> 00:58:37.810
we provided a list at that time

00:58:37.810 --> 00:58:39.710
of a number of alternate care sites.

00:58:39.710 --> 00:58:43.330
These are sites that oftentimes are not located

00:58:43.330 --> 00:58:44.630
adjacent to a hospital,

00:58:44.630 --> 00:58:47.010
but we're setting them up in gymnasiums,

00:58:47.010 --> 00:58:50.080
at colleges and schools at other locations,

00:58:50.080 --> 00:58:53.665
we've provided that list previously to all three IOUs.

00:58:53.665 --> 00:58:57.650
I will take for action for us to update that list

00:58:57.650 --> 00:58:59.170
and provide it back out.

00:58:59.170 --> 00:59:01.720
But one of the things, especially on testing sites,

00:59:02.620 --> 00:59:07.270
there's an active RGIS site that's updated in real time,

00:59:07.270 --> 00:59:10.106
that shows every testing site in the state of California.

00:59:10.106 --> 00:59:13.863
That's on the Governorscovid.ca.gov website.

00:59:14.950 --> 00:59:18.137
So I would encourage your teams to access that,

00:59:18.137 --> 00:59:22.490
and you can begin mapping against your polygons

00:59:23.980 --> 00:59:25.360
where those sites occur.

00:59:25.360 --> 00:59:28.100
And if we need to have an offline conversation

00:59:28.100 --> 00:59:31.370
to provide some of those data layers, happy to do that.

00:59:31.370 --> 00:59:33.570
But Phil, I wanted to go back to

00:59:33.570 --> 00:59:35.860
you're talking about generation,

00:59:35.860 --> 00:59:40.150
relative to keeping key community centers up.

00:59:40.150 --> 00:59:42.750
And obviously as you know well,

00:59:42.750 --> 00:59:46.270
the ability for us to keep critical operations,

00:59:46.270 --> 00:59:49.856
grocery stores, gas stations, and key resources live

00:59:49.856 --> 00:59:54.233
and up, within an outage area.

00:59:55.110 --> 00:59:57.320
It wasn't clear to me from your comments,

00:59:57.320 --> 01:00:02.060
if you guys have since 2019 done that

01:00:02.060 --> 01:00:04.250
and can have that generation in place

01:00:04.250 --> 01:00:06.930
or that's something you are looking at doing

01:00:06.930 --> 01:00:11.520
that we won't be able to realize the benefits until 2021.

01:00:11.520 --> 01:00:15.203
<v ->Yeah, it's a good question, it's a little bit of both.</v>

01:00:17.060 --> 01:00:19.858
The big blocks that we mentioned,

01:00:19.858 --> 01:00:23.080
looking at getting whole communities up.

01:00:23.080 --> 01:00:25.917
At this point, we're still evaluating whether we can do,

01:00:25.917 --> 01:00:28.980
and it requires extremely large generation sources.

01:00:28.980 --> 01:00:30.520
And so we have environmental issues,

01:00:30.520 --> 01:00:31.730
we have to balance with that.

01:00:31.730 --> 01:00:34.050
So we're still looking at a mechanism

01:00:34.050 --> 01:00:35.980
to at least find some segments of those circuits

01:00:35.980 --> 01:00:39.210
that we can essentially reconfigure

01:00:39.210 --> 01:00:43.290
to allow us to test generation there.

01:00:43.290 --> 01:00:44.800
What we have done however,

01:00:44.800 --> 01:00:49.670
we procured around the 15 megawatts of backup generation

01:00:49.670 --> 01:00:51.884
that we can deploy in events

01:00:51.884 --> 01:00:55.451
to the extent that they are needed in different places

01:00:55.451 --> 01:00:58.950
and the resiliency centers that I did mention,

01:00:58.950 --> 01:01:01.873
we are in the process of configuring some facilities,

01:01:01.873 --> 01:01:04.820
so some will be done by 2020 I expect.

01:01:04.820 --> 01:01:07.970
I expect more of just to be available in 2020.

01:01:07.970 --> 01:01:12.700
I wanna give Erik Takayesu an opportunity to jump in here.

01:01:12.700 --> 01:01:14.370
Erik's been spending a lot of time

01:01:14.370 --> 01:01:17.373
with this aspect of our program, Erik.

01:01:18.260 --> 01:01:19.430
<v Erik>Thank you, Phil.</v>

01:01:19.430 --> 01:01:24.430
And thank you Deputy Director on MRO.

01:01:25.330 --> 01:01:26.910
Just a couple of things I wanna mention

01:01:26.910 --> 01:01:29.450
that Phil didn't cover, I think he covered it quite well.

01:01:29.450 --> 01:01:32.990
We have been developing a generator strategy,

01:01:32.990 --> 01:01:35.120
but one of the things that we have been working on,

01:01:35.120 --> 01:01:38.210
to what degree do we have clean,

01:01:38.210 --> 01:01:41.740
environmentally adequate units available?

01:01:41.740 --> 01:01:45.850
So the 15 are actually 17 megawatts that Phil referred to

01:01:45.850 --> 01:01:48.100
as well, we've been able to procure,

01:01:48.100 --> 01:01:52.240
we also have an additional 17 and a half megawatts

01:01:52.240 --> 01:01:56.550
on retainer that FR needs surpassed that,

01:01:56.550 --> 01:01:59.780
we wouldn't be able to respond accordingly.

01:01:59.780 --> 01:02:01.760
But one thing I would like to highlight,

01:02:01.760 --> 01:02:04.290
and I think it's an important issue,

01:02:04.290 --> 01:02:05.720
when we get it to an event,

01:02:05.720 --> 01:02:08.390
is the collaboration and the coordination

01:02:08.390 --> 01:02:10.890
because they may, at times,

01:02:10.890 --> 01:02:15.052
we don't know how many units may be required

01:02:15.052 --> 01:02:17.380
identifying and prioritizing those

01:02:17.380 --> 01:02:18.967
with the County Emergency Management,

01:02:18.967 --> 01:02:20.400
that'd be critical.

01:02:20.400 --> 01:02:24.070
So we're able to ensure that we are adjusting

01:02:24.070 --> 01:02:27.067
the most critical needs in the most expedient way.

01:02:29.920 --> 01:02:32.535
<v ->I hear you, I'm sorry.</v>

01:02:32.535 --> 01:02:34.430
<v ->Oh, sorry, excuse me.</v>

01:02:34.430 --> 01:02:37.260
If I may just follow up, question to Erik,

01:02:38.210 --> 01:02:40.360
could you repeat perhaps I didn't hear correctly,

01:02:40.360 --> 01:02:45.340
did you say 17 megawatts of clean energy for backup?

01:02:45.340 --> 01:02:47.210
<v Erik>Yeah, those are the cleanest units</v>

01:02:47.210 --> 01:02:49.520
that are available technically

01:02:49.520 --> 01:02:53.490
and they typically fall into the smaller units.

01:02:53.490 --> 01:02:56.870
So you won't see it as availability

01:02:56.870 --> 01:03:00.260
of those in the larger unit, like in the one megawatt range,

01:03:00.260 --> 01:03:03.227
these happens to be mostly in the 300KW, 500KW

01:03:05.434 --> 01:03:09.207
and that's also the same sizes of generation

01:03:10.090 --> 01:03:11.740
that we have on retainer as well.

01:03:12.660 --> 01:03:14.030
<v Marc>But Erik, let me,</v>

01:03:14.030 --> 01:03:17.030
this is Marc Ulrich, President Batjer, when he says clean,

01:03:17.030 --> 01:03:19.606
he means the best available control technology,

01:03:19.606 --> 01:03:23.930
he does not mean solar with batteries.

01:03:23.930 --> 01:03:26.100
<v ->I was just going to follow up with that comment,</v>

01:03:26.100 --> 01:03:27.833
so thanks for the clarification.

01:03:29.170 --> 01:03:31.310
I probably understood that he didn't mean solar

01:03:31.310 --> 01:03:34.320
with backup batteries, but I wasn't sure what he meant.

01:03:34.320 --> 01:03:35.720
So thank you, appreciate it.

01:03:37.100 --> 01:03:38.650
<v Marc>And then Director Lamoreaux,</v>

01:03:38.650 --> 01:03:40.910
this is Marc Ulrich again,

01:03:40.910 --> 01:03:42.700
the idea that you came up with,

01:03:42.700 --> 01:03:46.789
the resiliency zones is one we are absolutely pursuing.

01:03:46.789 --> 01:03:50.990
We are now in the stage where we have seven different pilots

01:03:50.990 --> 01:03:52.100
that we're looking at,

01:03:52.100 --> 01:03:53.500
where we're trying to figure out

01:03:53.500 --> 01:03:57.660
what's the best way to do, select the services,

01:03:57.660 --> 01:03:58.890
and as you said,

01:03:58.890 --> 01:04:03.090
this is in an area where there'll be de-energization,

01:04:03.090 --> 01:04:06.600
how can we energize a grocery store, a pharmacy,

01:04:06.600 --> 01:04:09.770
a gas station, certain services

01:04:09.770 --> 01:04:11.460
that our customers still need?

01:04:11.460 --> 01:04:14.030
And so we we'll continue to work that,

01:04:14.030 --> 01:04:17.000
I hope we do get some in 2020.

01:04:17.000 --> 01:04:20.830
I know we've been soliciting input,

01:04:20.830 --> 01:04:22.710
one of the things we're also doing

01:04:22.710 --> 01:04:25.230
is for local governments to help us select,

01:04:25.230 --> 01:04:26.230
as you can imagine,

01:04:26.230 --> 01:04:27.930
we don't wanna be in the middle of a lawsuit

01:04:27.930 --> 01:04:30.010
where one grocery store sued us

01:04:30.010 --> 01:04:32.242
because we picked a different grocery store,

01:04:32.242 --> 01:04:35.103
but we'll get through some of those minor hurdles.

01:04:36.660 --> 01:04:38.350
<v ->You know what, I appreciate that,</v>

01:04:38.350 --> 01:04:39.850
but I also appreciate that

01:04:39.850 --> 01:04:43.700
you've already executed the first PSPS of 2020.

01:04:43.700 --> 01:04:48.080
We're approaching 12 months from your largest event in 2019,

01:04:48.080 --> 01:04:51.480
and it sounds like there's a lot of good planning,

01:04:51.480 --> 01:04:54.313
but we're 10 months since,

01:04:55.620 --> 01:04:58.600
I hope that we can see some tangible results

01:04:58.600 --> 01:05:00.500
in the way of being able to create

01:05:00.500 --> 01:05:03.700
some resiliency services in 2020,

01:05:03.700 --> 01:05:05.913
so that we can reduce those consequences

01:05:05.913 --> 01:05:07.080
that we're dealing with,

01:05:07.080 --> 01:05:08.770
especially in your service territory,

01:05:08.770 --> 01:05:11.830
where someone's going to be out of power in Inyo County

01:05:11.830 --> 01:05:16.660
or Mono County, and have a significant way to travel

01:05:16.660 --> 01:05:19.600
in order to get out of that de-energized zone

01:05:19.600 --> 01:05:21.430
to a place where there's a grocery store

01:05:21.430 --> 01:05:23.380
with the power on and a gas station that's up.

01:05:23.380 --> 01:05:24.670
So, thank you.

01:05:24.670 --> 01:05:26.510
<v ->Thank you, Director Lamoureux.</v>

01:05:26.510 --> 01:05:29.930
We absolutely take the point, we are pushing this one hard.

01:05:29.930 --> 01:05:33.010
And in fact, the locations that you signed

01:05:33.010 --> 01:05:35.070
are largely the places where we are assigning

01:05:35.070 --> 01:05:38.500
these resiliency zones to be constructed,

01:05:38.500 --> 01:05:41.810
so we're with you, we're pushing this hard

01:05:41.810 --> 01:05:46.193
and I appreciate the extra motivation to get this moving.

01:05:47.910 --> 01:05:49.430
Thank you.

01:05:49.430 --> 01:05:51.100
<v ->So, Phil, this Marybel.</v>

01:05:51.100 --> 01:05:53.217
I think you have just a couple more,

01:05:53.217 --> 01:05:55.070
probably only one more slide.

01:05:55.070 --> 01:05:56.870
So why don't we let you get through that?

01:05:56.870 --> 01:05:59.032
I think we all have a few more questions

01:05:59.032 --> 01:06:03.850
and of course, then we'll turn to the public comment period.

01:06:03.850 --> 01:06:05.350
But why don't we let you finish the last,

01:06:05.350 --> 01:06:06.733
that last half of it,

01:06:07.700 --> 01:06:09.860
the one slide and then your final slide.

01:06:09.860 --> 01:06:11.760
And then I know you have the maps too.

01:06:14.571 --> 01:06:17.089
<v ->The maps are for everyone to join the president,</v>

01:06:17.089 --> 01:06:20.690
but yeah, the good news is we've largely covered a lot

01:06:20.690 --> 01:06:22.480
of things that we were going to talk about right now,

01:06:22.480 --> 01:06:23.410
which is great.

01:06:23.410 --> 01:06:27.420
I did wanna point out that we are working closely

01:06:27.420 --> 01:06:31.053
with our AFN communities, local and statewide agencies

01:06:31.053 --> 01:06:33.780
to amplify our offerings to the ASN,

01:06:34.977 --> 01:06:37.430
access and functional of these customers

01:06:37.430 --> 01:06:40.220
as PSPS events unfold,

01:06:40.220 --> 01:06:42.400
now, we work in collaboration

01:06:42.400 --> 01:06:45.630
with the other California Investor Owned utilities

01:06:45.630 --> 01:06:48.600
to help launch the AFN Statewide Advisory Council,

01:06:48.600 --> 01:06:52.520
I know everyone's familiar with that group,

01:06:52.520 --> 01:06:53.570
and it's again intended

01:06:53.570 --> 01:06:55.220
so that we can better understand needs,

01:06:55.220 --> 01:06:57.330
to the access and functional needs populations,

01:06:57.330 --> 01:06:58.680
and partner on creating solutions

01:06:58.680 --> 01:07:02.480
that we'll really better serve that community.

01:07:02.480 --> 01:07:03.420
One thing we've added,

01:07:03.420 --> 01:07:05.107
I don't know if this is unique or not,

01:07:05.107 --> 01:07:07.253
but we think it's absolutely important.

01:07:08.360 --> 01:07:11.110
We've added a dedicated AFN specialist

01:07:11.110 --> 01:07:13.790
to our PSPS Incident Management team

01:07:13.790 --> 01:07:15.090
who will manage those partnerships

01:07:15.090 --> 01:07:16.600
and customer needs during events.

01:07:16.600 --> 01:07:18.770
So when we stand up an IMT,

01:07:18.770 --> 01:07:22.310
we will have somebody whose focus is the AFN community

01:07:22.310 --> 01:07:24.910
to be there, advising the incident commander

01:07:24.910 --> 01:07:29.222
and the team on needs and what we can do to support them.

01:07:29.222 --> 01:07:32.300
Now, we've also increased our partnerships

01:07:32.300 --> 01:07:34.150
with the Independent Living Centers, ILCs

01:07:34.150 --> 01:07:38.423
across our service area, focused on outreach and awareness.

01:07:39.330 --> 01:07:40.840
And through these partnerships,

01:07:40.840 --> 01:07:43.280
we're deliberately focused on increasing medical baseline

01:07:43.280 --> 01:07:44.943
awareness and enrollments.

01:07:46.330 --> 01:07:48.880
By the way, I would say with the additional outreach

01:07:48.880 --> 01:07:53.880
that we did also associated with our recent outage work,

01:07:54.580 --> 01:07:57.063
I think the Commission is aware of that.

01:07:57.063 --> 01:07:58.730
We just saw controls and engagement,

01:07:58.730 --> 01:08:00.340
we have with local communities,

01:08:00.340 --> 01:08:04.650
which required us to engage with more of a heavy touch

01:08:04.650 --> 01:08:05.640
with our customers.

01:08:05.640 --> 01:08:08.566
We also use that opportunity to explore with customers

01:08:08.566 --> 01:08:11.920
if they needed to be registered in one of those forums.

01:08:11.920 --> 01:08:15.430
So we use that as an opportunity to help us out.

01:08:15.430 --> 01:08:17.883
I'm looking through here,

01:08:19.380 --> 01:08:20.750
one thing we haven't touched on,

01:08:20.750 --> 01:08:25.750
I'll hit it very quickly is our PSPS COVID-19 preparations,

01:08:26.930 --> 01:08:27.763
we hit on some of them,

01:08:27.763 --> 01:08:32.060
but we've adjusted our plans to provide in-person services

01:08:32.060 --> 01:08:34.803
where we can with the proper precautions,

01:08:34.803 --> 01:08:36.783
expanding our whole community resource centers,

01:08:36.783 --> 01:08:41.783
And that was one way, more centers, less crowding there,

01:08:41.830 --> 01:08:44.800
and adjusting the protocols for social distancing

01:08:44.800 --> 01:08:47.170
for customers and our employees

01:08:47.170 --> 01:08:49.510
and supporters when they there are there.

01:08:49.510 --> 01:08:51.610
We've also enhanced our virtual services,

01:08:51.610 --> 01:08:55.210
webpage has provided info and more directions customers

01:08:55.210 --> 01:08:57.086
to key resources.

01:08:57.086 --> 01:08:59.360
We've moved forward, a lot of coordination

01:08:59.360 --> 01:09:03.047
with our County and State Emergency Management Officials,

01:09:03.047 --> 01:09:07.980
and we've prioritized healthcare outreach and facilities,

01:09:07.980 --> 01:09:09.938
and touched on that a little bit.

01:09:09.938 --> 01:09:11.944
So I just wanna say this is an area

01:09:11.944 --> 01:09:16.026
where we have spent a lot of time, rightly and importantly,

01:09:16.026 --> 01:09:17.625
because we think it's absolutely critical

01:09:17.625 --> 01:09:20.220
that we hear the feedback from our customers,

01:09:20.220 --> 01:09:22.950
from our communities, from our agency partners

01:09:22.950 --> 01:09:26.200
to help us really do better here.

01:09:26.200 --> 01:09:28.570
So maybe we can hit the last slide

01:09:28.570 --> 01:09:30.143
and then we're ready for questions.

01:09:32.470 --> 01:09:36.580
So again, we've got some of the highlights here

01:09:36.580 --> 01:09:37.510
of our activity.

01:09:37.510 --> 01:09:42.353
I just wanna say we are absolutely focused on really

01:09:43.592 --> 01:09:47.004
improving all phases of the wildfire mitigation.

01:09:47.004 --> 01:09:49.123
I've listed some statistics here.

01:09:50.060 --> 01:09:51.730
It's an infrastructure hardening,

01:09:51.730 --> 01:09:54.260
it seems situational awareness,

01:09:54.260 --> 01:09:58.040
I think what I really wanna leave everyone with

01:09:58.040 --> 01:10:01.270
is the absolute commitment from me,

01:10:01.270 --> 01:10:03.060
from Southern California Edison,

01:10:03.060 --> 01:10:05.110
that we are absolutely committed to get this right.

01:10:05.110 --> 01:10:08.250
And we in a better place than we were last year,

01:10:08.250 --> 01:10:11.820
we learned something with every single PSPS event

01:10:11.820 --> 01:10:13.540
and we will continue to do so.

01:10:13.540 --> 01:10:14.610
None are the same,

01:10:14.610 --> 01:10:17.306
everyone has learnings that we can benefit from.

01:10:17.306 --> 01:10:18.722
We're committed to improving this,

01:10:18.722 --> 01:10:21.050
we're committed to getting this right.

01:10:21.050 --> 01:10:23.543
This is absolutely important that we do that.

01:10:24.490 --> 01:10:26.940
I think based on the work we've done,

01:10:26.940 --> 01:10:29.570
the lessons we've learned, our engagement with you,

01:10:29.570 --> 01:10:31.958
customers or cities or first responders,

01:10:31.958 --> 01:10:34.740
we are confronting this next fire season with new tools,

01:10:34.740 --> 01:10:38.070
new technologies, and what I feel are much better approaches

01:10:38.070 --> 01:10:40.550
to managing disruptions to our customers.

01:10:40.550 --> 01:10:42.110
When our concern for public safety

01:10:42.110 --> 01:10:44.060
requires us to power down,

01:10:44.060 --> 01:10:45.960
we don't take this lightly.

01:10:45.960 --> 01:10:49.029
I hope that is not the impression that anybody has.

01:10:49.029 --> 01:10:51.860
This is about public safety.

01:10:51.860 --> 01:10:55.020
It is what keeps all of us up at night,

01:10:55.020 --> 01:10:58.810
It is how do we keep our community safe, full stop.

01:10:58.810 --> 01:11:00.860
That's what it amounts to for us.

01:11:00.860 --> 01:11:02.467
So I really wanna thank you

01:11:02.467 --> 01:11:04.263
for the opportunity to be here.

01:11:05.350 --> 01:11:07.480
We know how important this is to you,

01:11:07.480 --> 01:11:10.010
everybody on this call, the community to be served.

01:11:10.010 --> 01:11:13.370
We are committed, absolutely listening to learning,

01:11:13.370 --> 01:11:16.244
and we will always focus on improving.

01:11:16.244 --> 01:11:17.963
So thank you, President Batjer,

01:11:17.963 --> 01:11:19.440
thank you Commission, thank you everyone.

01:11:19.440 --> 01:11:20.620
And I'm really looking forward,

01:11:20.620 --> 01:11:22.720
we're looking forward to answering your

01:11:22.720 --> 01:11:26.100
and the community additional questions that you may have.

01:11:26.100 --> 01:11:30.334
<v ->Okay, I know we all have some additional questions,</v>

01:11:30.334 --> 01:11:34.910
real quickly on the Community Resource Expansion.

01:11:34.910 --> 01:11:38.140
Can you tell us what hours you're going

01:11:38.140 --> 01:11:42.210
to be conducting operations as a community resource?

01:11:42.210 --> 01:11:44.530
And there's an exactly what are the things

01:11:44.530 --> 01:11:46.710
that you're going to be offering?

01:11:46.710 --> 01:11:48.490
What services will you be offering?

01:11:48.490 --> 01:11:51.480
And I do appreciate that you're doing social distancing

01:11:51.480 --> 01:11:56.040
and being mindful of all of the practices of COVID-19,

01:11:56.040 --> 01:11:59.910
but wanna know what you've done

01:11:59.910 --> 01:12:03.680
to expand the actual services of the CRCs.

01:12:03.680 --> 01:12:05.040
<v ->Sure, I'll take a start,</v>

01:12:05.040 --> 01:12:09.653
and then Eric and Marc can jump in as well.

01:12:10.780 --> 01:12:12.790
As far as hours are concerned,

01:12:12.790 --> 01:12:17.790
we are complying as where we can with the extended hours

01:12:18.350 --> 01:12:21.580
that the Commission has directed us to do

01:12:21.580 --> 01:12:25.690
to make perfect sense, longer hours, much more useful.

01:12:25.690 --> 01:12:27.520
Some of the CRCs is one of the reasons

01:12:27.520 --> 01:12:29.115
we stand in our footprints.

01:12:29.115 --> 01:12:34.050
CRCs just have not made their facilities available

01:12:34.050 --> 01:12:38.070
to us for the full hours that we would like them to have.

01:12:38.070 --> 01:12:43.070
So, again, right now we've got 40 CRCs contracting today,

01:12:43.310 --> 01:12:47.130
22 of them already have the 8:00 a.m to 10:00 p.m hours.

01:12:47.130 --> 01:12:49.097
That's great, we're gonna continue to work

01:12:49.097 --> 01:12:54.097
and expand that, we provide go bags, which contains snacks.

01:12:54.498 --> 01:12:57.243
They contain charging devices,

01:12:59.950 --> 01:13:02.990
we also will provide Ais, Additional Information,

01:13:02.990 --> 01:13:05.184
we put this in a bag.

01:13:05.184 --> 01:13:08.650
This is information that our customers may find useful.

01:13:08.650 --> 01:13:11.420
Again, one of the most important things you provide at a CRC

01:13:11.420 --> 01:13:16.420
or Community Crew Vehicles is information about the events,

01:13:16.640 --> 01:13:18.340
and so that's absolutely something

01:13:18.340 --> 01:13:20.380
that we think is important.

01:13:20.380 --> 01:13:23.140
It's even in the events that we just had recently,

01:13:23.140 --> 01:13:24.710
as small as they work,

01:13:24.710 --> 01:13:26.700
we had a number of folks showing up

01:13:26.700 --> 01:13:29.510
to our Community Crew Vehicle locations.

01:13:29.510 --> 01:13:31.050
Marc and Eric,

01:13:31.050 --> 01:13:33.063
is there anything that I missed

01:13:33.063 --> 01:13:35.223
that's significant that we can share?

01:13:36.868 --> 01:13:37.810
<v Marc>This is Marc,</v>

01:13:37.810 --> 01:13:42.460
yeah, so you got most all that absolutely correct there.

01:13:42.460 --> 01:13:45.220
One thing, for any new CRC

01:13:45.220 --> 01:13:46.740
that we're contracting with today,

01:13:46.740 --> 01:13:51.740
they will meet the hours, the 8:00a.m to 10:00 p.m hours.

01:13:52.133 --> 01:13:54.560
But as Phil said,

01:13:54.560 --> 01:13:57.555
we have 22 that have converted that we already had

01:13:57.555 --> 01:13:59.780
in our contract that we have agreed

01:13:59.780 --> 01:14:01.890
to keep the eight to 10 hours.

01:14:01.890 --> 01:14:06.160
But that means we have roughly 18 or so

01:14:06.160 --> 01:14:07.750
that are still pending.

01:14:07.750 --> 01:14:09.210
And some of them have told us that

01:14:09.210 --> 01:14:12.210
they will not be able to meet our hours.

01:14:12.210 --> 01:14:15.423
So we're at a struggle of what to do with those CRCs.

01:14:17.050 --> 01:14:20.960
The other thing is we are continually exploring.

01:14:20.960 --> 01:14:23.150
I was incident commander last weekend,

01:14:23.150 --> 01:14:27.900
when we had the de-energization of the 17 customers,

01:14:27.900 --> 01:14:30.580
they were without power for about 24 hours

01:14:30.580 --> 01:14:33.630
'cause the wind conditions had not subsided,

01:14:33.630 --> 01:14:36.640
but we saw a six hour window where it was going to subside,

01:14:36.640 --> 01:14:39.720
and we thought we could reenergize them for a little bit,

01:14:39.720 --> 01:14:43.180
but the wind was gonna come back up shortly after.

01:14:43.180 --> 01:14:44.710
The winds came in early

01:14:44.710 --> 01:14:49.710
and we were not able to re-energize them.

01:14:49.920 --> 01:14:53.910
And so we actually sent a field service rep to the homes

01:14:53.910 --> 01:14:58.910
to drop off, go bags and AIs to these 17 customers.

01:14:59.840 --> 01:15:02.720
It's not something that I think we could really do at scale,

01:15:02.720 --> 01:15:04.930
but we're exploring all types of opportunities

01:15:04.930 --> 01:15:06.311
to be able to do that.

01:15:06.311 --> 01:15:10.580
Of the 17, only three customers were home at the time.

01:15:10.580 --> 01:15:13.540
They were very appreciative of our approach,

01:15:13.540 --> 01:15:16.085
but we were trying to make that service

01:15:16.085 --> 01:15:19.690
a little bit more local to the de-energized customers.

01:15:19.690 --> 01:15:22.780
So we're continuing to explore, but as Phil said,

01:15:22.780 --> 01:15:25.690
I think he got all the contents and the go bag correct,

01:15:25.690 --> 01:15:29.600
as well as the hours of operation and occurrence status.

01:15:29.600 --> 01:15:32.250
And I'm not sure if Eric, you wanted to add anything?

01:15:33.438 --> 01:15:35.020
<v Eric>He might've said this before,</v>

01:15:35.020 --> 01:15:36.220
and I apologize if he did,

01:15:36.220 --> 01:15:38.950
but of the 40 CRCs we have contracted to date,

01:15:38.950 --> 01:15:43.400
22 of them have 8:00 a.m to 10:00 p.m hours.

01:15:43.400 --> 01:15:45.160
<v ->Right, I sure hope that you're able</v>

01:15:45.160 --> 01:15:49.850
to get the expanded hours and the rest of those,

01:15:49.850 --> 01:15:52.410
'cause that's just only half your CRCs.

01:15:52.410 --> 01:15:55.117
And appreciate you working hard on that,

01:15:55.117 --> 01:15:58.680
but as we all know, we're in the fire season now,

01:15:58.680 --> 01:16:00.320
I don't want to belabor the point,

01:16:00.320 --> 01:16:02.400
but I know your more rural areas

01:16:02.400 --> 01:16:05.420
as Eric Lamoreaux mentioned earlier,

01:16:05.420 --> 01:16:07.720
when you get out into Mono County and Inyo,

01:16:07.720 --> 01:16:11.550
you're really talking about a long way to travel for folks.

01:16:11.550 --> 01:16:14.570
So I'm hoping you've taken into consideration

01:16:14.570 --> 01:16:17.470
where you're placing the CRCs.

01:16:17.470 --> 01:16:19.210
And if you can't find brick and mortar

01:16:19.210 --> 01:16:21.320
that you're attempting of some sort

01:16:21.320 --> 01:16:26.120
that you're providing CRC within in a reasonable distance,

01:16:26.120 --> 01:16:30.920
we've have had quite a few of the rural counties mention

01:16:30.920 --> 01:16:35.280
to us how difficult it was for people to drive, limited gas,

01:16:35.280 --> 01:16:40.280
worried about their fuel usage, driving miles

01:16:40.530 --> 01:16:44.283
and miles to get to the the charging station, for example.

01:16:46.460 --> 01:16:48.053
<v ->Yeah, President Batjer,</v>

01:16:48.053 --> 01:16:50.100
just to add on, I think Marc you may have mentioned this,

01:16:50.100 --> 01:16:53.340
but if not, I completely agree for one thing,

01:16:53.340 --> 01:16:57.840
we are really focused on located these as close to the areas

01:16:57.840 --> 01:17:01.510
where we expect the PSPS events to be occurring as possible.

01:17:01.510 --> 01:17:04.120
It is one area where we are leveraging

01:17:04.120 --> 01:17:05.550
our Community Crew Vehicles,

01:17:05.550 --> 01:17:07.490
it's one of the reasons we felt that was important,

01:17:07.490 --> 01:17:10.650
especially given our service area.

01:17:10.650 --> 01:17:12.190
A large distance to cover,

01:17:12.190 --> 01:17:14.133
and pre-positioning those four events

01:17:14.133 --> 01:17:17.410
as an augmentation to the CCRs.

01:17:20.760 --> 01:17:23.330
So they have a lot of the capabilities,

01:17:23.330 --> 01:17:25.604
we do hand out the go bags

01:17:25.604 --> 01:17:27.457
and they have charging capability,

01:17:27.457 --> 01:17:30.063
and of course the information is shared

01:17:30.063 --> 01:17:34.083
at those locations as well when the vehicle shows up.

01:17:35.120 --> 01:17:37.810
<v ->I have one more question that I wanna ask,</v>

01:17:37.810 --> 01:17:38.850
and then I'm going to turn back

01:17:38.850 --> 01:17:41.870
to my fellow diocese members.

01:17:41.870 --> 01:17:44.260
And that is, I know we didn't get to really looking

01:17:44.260 --> 01:17:45.093
at your maps,

01:17:45.093 --> 01:17:48.530
but one of the things that the telecommunications companies

01:17:48.530 --> 01:17:53.530
have indicated to us during a PSPS event,

01:17:54.030 --> 01:17:56.660
oftentimes their services are degraded.

01:17:56.660 --> 01:18:00.050
So if you are pointing your customers to your website,

01:18:00.050 --> 01:18:04.220
to look at maps and evacuation information

01:18:05.670 --> 01:18:09.710
and fire information, et cetera,

01:18:09.710 --> 01:18:12.580
are you also looking at how you can provide your,

01:18:12.580 --> 01:18:16.842
how you can have your website provide low bandwidth versions

01:18:16.842 --> 01:18:20.560
of those types of things, that information

01:18:20.560 --> 01:18:23.820
that is a higher data requirement?

01:18:23.820 --> 01:18:27.040
<v ->Absolutely president, we have really designed it</v>

01:18:27.040 --> 01:18:30.963
with a mobile first philosophy in mind.

01:18:31.800 --> 01:18:33.260
There's no streaming videos,

01:18:33.260 --> 01:18:36.040
there's no high content downloads,

01:18:36.040 --> 01:18:38.970
maybe a little bit different than it was before.

01:18:38.970 --> 01:18:42.460
So I think, we have really designed this in mind

01:18:42.460 --> 01:18:45.990
with being able to use a mobile device

01:18:45.990 --> 01:18:48.540
and not being reliant on a computer.

01:18:48.540 --> 01:18:51.500
So that's definitely part of the program.

01:18:51.500 --> 01:18:54.340
And we did fix some of these when we saw these issues.

01:18:54.340 --> 01:18:57.790
But again, I think the mobile service design,

01:18:59.357 --> 01:19:00.468
it goes into the foundation

01:19:00.468 --> 01:19:04.191
of how we're planning our website and the information

01:19:04.191 --> 01:19:07.153
that we're sharing with our customers.

01:19:07.153 --> 01:19:07.986
<v ->Okay, thanks.</v>

01:19:07.986 --> 01:19:11.921
I'll let my fellow Commissioners and Eric and Daniel.

01:19:11.921 --> 01:19:14.088
Yes, Commissioner Shiroma.

01:19:15.487 --> 01:19:17.077
<v ->Thank you, president Batjer.</v>

01:19:17.077 --> 01:19:20.790
Wanted to follow up on where your slide you referred to

01:19:20.790 --> 01:19:23.140
coordination with tribal governments (mumbles).

01:19:24.320 --> 01:19:27.000
Tell us a little bit more about

01:19:27.000 --> 01:19:31.680
what does that entail in terms of coordinating closely

01:19:31.680 --> 01:19:33.060
with tribal governments

01:19:33.060 --> 01:19:37.123
within your utility territory and these zones?

01:19:38.241 --> 01:19:40.363
<v ->Yeah, thank you Commissioner.</v>

01:19:42.930 --> 01:19:45.180
We have used tribal governments,

01:19:45.180 --> 01:19:47.362
in fact, we had the same kind of outreach

01:19:47.362 --> 01:19:50.830
with tribal governments, as we do with all of our counties,

01:19:50.830 --> 01:19:53.470
we have representatives assigned to them.

01:19:53.470 --> 01:19:56.960
And so as far as outreach is concerned,

01:19:56.960 --> 01:20:00.390
reaching out regarding CRCs so far,

01:20:00.390 --> 01:20:02.030
they've not asked for any,

01:20:02.030 --> 01:20:05.410
or not take us up on the offer to cook one

01:20:06.746 --> 01:20:08.010
on their other territory.

01:20:08.010 --> 01:20:11.370
But we have established contacts

01:20:11.370 --> 01:20:14.517
across our entire service area.

01:20:14.517 --> 01:20:16.877
It is part of our customer service

01:20:16.877 --> 01:20:18.810
and Local Public Affairs program,

01:20:18.810 --> 01:20:21.960
so we have made contact and continue to do that

01:20:21.960 --> 01:20:25.840
as part of our wildfire resiliency run out.

01:20:25.840 --> 01:20:27.430
So I think Marc,

01:20:27.430 --> 01:20:30.910
you might have some of the customer service aspects of that.

01:20:30.910 --> 01:20:33.710
Is there anything you would care to share there or Eric?

01:20:34.880 --> 01:20:38.300
<v Marc>Yeah Phil, this is Marc, you're correct.</v>

01:20:38.300 --> 01:20:42.240
Local public affairs has a dedicated individuals

01:20:42.240 --> 01:20:44.510
in there certain areas

01:20:44.510 --> 01:20:46.620
as well as the business customer division does

01:20:46.620 --> 01:20:48.950
to make sure that we're coordinated

01:20:48.950 --> 01:20:51.010
with our tribal governments.

01:20:51.010 --> 01:20:53.870
Also during a PSPS event,

01:20:53.870 --> 01:20:58.130
we hold two daily briefings in County coordination calls,

01:20:58.130 --> 01:21:01.500
and they're invited the general public is not,

01:21:01.500 --> 01:21:03.680
but our partner agencies are invited,

01:21:03.680 --> 01:21:05.330
including the tribal governments.

01:21:07.552 --> 01:21:08.385
<v ->Thank you.</v>

01:21:11.550 --> 01:21:14.267
<v ->Yes, Commissioner Rechtschaffen.</v>

01:21:14.267 --> 01:21:17.397
<v ->Can I just follow up on Commissioner Shiroma's question,</v>

01:21:17.397 --> 01:21:18.640
and your response was

01:21:18.640 --> 01:21:21.620
none of the tribes have requested CRCs,

01:21:21.620 --> 01:21:22.980
include your tribe,

01:21:22.980 --> 01:21:26.413
I know Edison has its dedicated tribal liaison, right?

01:21:31.730 --> 01:21:34.760
<v ->We have a number of folks Commissioner.</v>

01:21:34.760 --> 01:21:37.040
I'm sorry, Marc, you were trying to get it.

01:21:37.040 --> 01:21:38.640
<v Marc>Nope, that's it.</v>

01:21:38.640 --> 01:21:42.980
We don't have a single individual that does all tribes.

01:21:42.980 --> 01:21:45.930
We have individuals in certain regions

01:21:45.930 --> 01:21:48.253
that handle different tribes.

01:21:49.460 --> 01:21:52.030
<v ->Well, I would be interested in following up offline</v>

01:21:52.030 --> 01:21:57.030
with whoever the pertinent tribal liaisons are in the areas

01:21:57.330 --> 01:21:59.810
the tribal areas that have been affected by PSPS

01:21:59.810 --> 01:22:03.907
is to find out about their potential interest in CRCs,

01:22:03.907 --> 01:22:06.680
and if they adequately communicated it,

01:22:06.680 --> 01:22:11.063
there is a desire for them in any tribal territory.

01:22:13.920 --> 01:22:15.782
<v ->Yeah, we certainly can mention it,</v>

01:22:15.782 --> 01:22:18.943
we'd be happy to facilitate that.

01:22:19.860 --> 01:22:22.030
We'll take that as an action item.

01:22:22.030 --> 01:22:24.400
<v ->Thank you, I take it that the pilots</v>

01:22:24.400 --> 01:22:25.676
for the resiliency zones,

01:22:25.676 --> 01:22:28.473
none of them are in tribal areas at this point.

01:22:29.615 --> 01:22:31.200
<v ->No, they are not.</v>

01:22:31.200 --> 01:22:32.033
That's correct.

01:22:33.320 --> 01:22:35.599
We did also provided,

01:22:35.599 --> 01:22:38.840
we had a kind of PSPS workshop for tribes,

01:22:38.840 --> 01:22:41.990
so actually on our wildfire mitigation plan very recently,

01:22:41.990 --> 01:22:45.797
I think that was within the last month or two.

01:22:48.330 --> 01:22:49.840
We hold workshops much like we do

01:22:49.840 --> 01:22:51.390
with our other agency partners.

01:22:52.250 --> 01:22:54.383
<v ->Daniel, I saw your hand come up.</v>

01:22:55.280 --> 01:22:56.180
<v ->Thank you president,</v>

01:22:56.180 --> 01:22:58.180
and Phil, it's good to finally now get to see you

01:22:58.180 --> 01:22:59.980
as I'm now joined here.

01:22:59.980 --> 01:23:01.660
So couple questions for you,

01:23:01.660 --> 01:23:05.120
first, what if anything, are you guys doing this year

01:23:05.120 --> 01:23:08.870
as far as providing notifications to state agencies

01:23:08.870 --> 01:23:10.303
and emergency departments?

01:23:12.540 --> 01:23:17.540
<v ->So we have a really refined a lot of the contacts</v>

01:23:17.570 --> 01:23:19.950
we were making with state agencies.

01:23:19.950 --> 01:23:23.100
I can say one of our lessons learned is

01:23:23.100 --> 01:23:26.543
candidly, some of the contact information wasn't right.

01:23:30.000 --> 01:23:31.960
I don't wanna finesse that too much,

01:23:31.960 --> 01:23:33.430
and working with the agencies also,

01:23:33.430 --> 01:23:35.713
so we understand who the right people are,

01:23:35.713 --> 01:23:39.550
whether it's CAL FIRE or Cal OES, or other sub agencies

01:23:39.550 --> 01:23:41.160
that need to be communicated with.

01:23:41.160 --> 01:23:43.700
So we have really worked hard

01:23:43.700 --> 01:23:45.453
to make sure we've got that right.

01:23:46.550 --> 01:23:48.550
I do want to see this off,

01:23:48.550 --> 01:23:51.559
'cause this was an area of focused for Erik Takayesu

01:23:51.559 --> 01:23:53.770
and the PSPS readiness team.

01:23:53.770 --> 01:23:55.290
Erik, am I missing something there?

01:23:55.290 --> 01:23:59.800
That's we do contact, I know, County emergency managers,

01:23:59.800 --> 01:24:03.280
fire, a lot of other officials, daily during events?

01:24:03.280 --> 01:24:07.870
By the way, I think Marc mentioned the twice daily calls,

01:24:07.870 --> 01:24:09.410
so when we have an event,

01:24:09.410 --> 01:24:12.350
we have a call with county agencies and state agencies

01:24:13.200 --> 01:24:16.966
where the incident commander debriefs the events

01:24:16.966 --> 01:24:18.910
essentially in real time.

01:24:18.910 --> 01:24:23.700
And one thing I'll also add is we invite our agency partners

01:24:23.700 --> 01:24:27.333
to come to the EOC, we stopped for now in COVID,

01:24:28.250 --> 01:24:31.130
but that invitation stands to have

01:24:31.130 --> 01:24:35.980
representatives participate with us in the PSPS event.

01:24:35.980 --> 01:24:39.380
So that's something we really encourage it,

01:24:39.380 --> 01:24:42.150
I think that makes the communication flow even better

01:24:42.150 --> 01:24:45.000
and helps in understanding of how we're making decisions.

01:24:46.030 --> 01:24:48.560
Sorry, I got right when you're try to jump in there Eric,

01:24:48.560 --> 01:24:50.360
is there anything you'd like to add?

01:24:51.280 --> 01:24:52.690
<v Erik>I think you pretty much said</v>

01:24:52.690 --> 01:24:54.100
exactly what I would've said.

01:24:54.100 --> 01:24:55.450
So you covered it well,

01:24:55.450 --> 01:24:57.400
the only thing I would add is I know that

01:24:57.400 --> 01:25:00.530
our director of business resiliency is also met,

01:25:00.530 --> 01:25:03.360
preemptively with each of the county executive managers

01:25:03.360 --> 01:25:06.947
to discuss the COVID intersection with PSPS

01:25:06.947 --> 01:25:10.490
and any concerns that may have been raised, yeah.

01:25:10.490 --> 01:25:12.027
<v ->Thank you, Eric.</v>

01:25:12.027 --> 01:25:13.350
<v ->Great, appreciate that,</v>

01:25:13.350 --> 01:25:15.380
and obviously, I mean,

01:25:15.380 --> 01:25:17.059
I hope it goes without being said that

01:25:17.059 --> 01:25:19.680
if there's work at the state agencies,

01:25:19.680 --> 01:25:22.430
we can do to help ensure that that coordination

01:25:22.430 --> 01:25:24.310
and that connection is there.

01:25:24.310 --> 01:25:25.750
That that is communicated

01:25:25.750 --> 01:25:28.480
from your end to our end, immediately

01:25:28.480 --> 01:25:30.600
so that we can make those connections,

01:25:30.600 --> 01:25:31.550
so appreciate that.

01:25:32.421 --> 01:25:33.830
So one more last question for you,

01:25:33.830 --> 01:25:36.390
heading into this kind of peak fire season.

01:25:36.390 --> 01:25:39.860
What do you see for SoCalGas as being the biggest concern

01:25:39.860 --> 01:25:41.963
and what are you guys doing to address it?

01:25:45.570 --> 01:25:50.133
<v ->The biggest challenge I see right now is</v>

01:25:50.133 --> 01:25:52.680
it will be the big events, right?

01:25:52.680 --> 01:25:56.548
So managing multiple events

01:25:56.548 --> 01:25:59.333
that are occurring across our service area,

01:26:00.340 --> 01:26:02.643
where lighting resources will be challenged,

01:26:03.550 --> 01:26:06.440
where our own resources may be challenged.

01:26:06.440 --> 01:26:09.134
Those are the events I think we are

01:26:09.134 --> 01:26:11.082
most concerned about happening.

01:26:11.082 --> 01:26:13.780
The things we have done about it,

01:26:13.780 --> 01:26:17.223
it's one of the elements of the PSPS readiness team.

01:26:18.320 --> 01:26:21.033
There are several layers to this,

01:26:21.033 --> 01:26:23.060
maybe even taking a step back,

01:26:23.060 --> 01:26:24.430
all the infrastructure harding,

01:26:24.430 --> 01:26:28.390
everything we have done is to preclude the need

01:26:28.390 --> 01:26:31.499
for a PSPS event, so I want to underscore that

01:26:31.499 --> 01:26:33.880
for everyone here.

01:26:33.880 --> 01:26:35.440
This is not something we seek,

01:26:35.440 --> 01:26:38.200
this is truly, it's the thing at the end of the line,

01:26:38.200 --> 01:26:41.410
when we feel our system and weather conditions

01:26:41.410 --> 01:26:43.970
are such that we feel public safety

01:26:43.970 --> 01:26:46.460
really is best served by de-energization,

01:26:46.460 --> 01:26:47.560
so we're at that point now.

01:26:47.560 --> 01:26:50.920
So assume that they have many events going on

01:26:50.920 --> 01:26:54.043
on a service line area, lots of areas.

01:26:55.010 --> 01:26:58.120
We've done drills, and we're continuing to do drills.

01:26:58.120 --> 01:27:00.070
We have enhanced our tools,

01:27:00.070 --> 01:27:03.260
and if you haven't been able to see a demonstration

01:27:03.260 --> 01:27:05.860
then our team would love to walk you through this,

01:27:07.630 --> 01:27:11.460
the dashboards we're using now have automated this,

01:27:11.460 --> 01:27:13.440
the playbooks we put in place,

01:27:13.440 --> 01:27:16.790
so I would say pre preparation has been really key for us.

01:27:16.790 --> 01:27:20.350
If I look back to the big events of last year,

01:27:20.350 --> 01:27:22.220
some of the things we were doing in event,

01:27:22.220 --> 01:27:24.764
I mentioned circuit place, switching playbooks.

01:27:24.764 --> 01:27:27.499
We had a room of dedicated people

01:27:27.499 --> 01:27:30.830
looking at what we could do with any given circuit.

01:27:30.830 --> 01:27:34.080
And that would take sometimes hours to figure out

01:27:34.080 --> 01:27:36.830
how we could reconfigure any individual circuit.

01:27:36.830 --> 01:27:38.450
But we have literally a book

01:27:38.450 --> 01:27:39.620
that has these are all the ways

01:27:39.620 --> 01:27:41.300
you can re configured a circuit.

01:27:41.300 --> 01:27:44.940
That's all done in advance, so when a big event happens,

01:27:44.940 --> 01:27:46.850
we're able to respond quickly

01:27:46.850 --> 01:27:48.920
and efficiently deploy our resources.

01:27:48.920 --> 01:27:51.420
So everything we've done has been mindful

01:27:51.420 --> 01:27:54.183
of rapid ramp up to a larger events,

01:27:55.430 --> 01:27:58.920
quickly scaling to be able to do the events,

01:27:58.920 --> 01:28:00.759
and frankly, I'd also say the improvements we've made

01:28:00.759 --> 01:28:03.420
to our weather forecasting and technology and tools

01:28:04.620 --> 01:28:08.190
have led us to a place where we think

01:28:08.190 --> 01:28:10.120
our forecasting is much better.

01:28:10.120 --> 01:28:13.030
So we'll be able, I'd say to dial in if you will,

01:28:13.030 --> 01:28:15.420
be more precise with our PSPS,

01:28:15.420 --> 01:28:20.050
for the same level of risk reduction, fewer notifications,

01:28:20.050 --> 01:28:22.429
all of these things help with scalability.

01:28:22.429 --> 01:28:26.000
And the last thing is we created a dedicated PSPS team.

01:28:26.000 --> 01:28:31.000
So we have full timers now that are solely focused on PSPS.

01:28:31.120 --> 01:28:32.760
When there's blue sky events,

01:28:32.760 --> 01:28:34.820
they're working to make the process better.

01:28:34.820 --> 01:28:35.980
It's their full time job,

01:28:35.980 --> 01:28:39.340
it's not just a PMO or an IMT, which we do have,

01:28:39.340 --> 01:28:40.870
we stand those up,

01:28:40.870 --> 01:28:44.860
we have full timers, there're really dozens of full-timers

01:28:44.860 --> 01:28:48.570
focused on PSPS operations, notifications

01:28:48.570 --> 01:28:50.040
and community engagement,

01:28:50.040 --> 01:28:53.050
to be able to handle the big events seamlessly.

01:28:53.050 --> 01:28:56.890
So big events, I think that's one of my concerns

01:28:58.120 --> 01:29:00.930
and we've really focused on many levels,

01:29:00.930 --> 01:29:03.522
many tiers to address that.

01:29:03.522 --> 01:29:05.210
So I appreciate the question.

01:29:05.210 --> 01:29:08.078
Erik, you've been leading some of the efforts there,

01:29:08.078 --> 01:29:10.978
anything else you would add to that mix before we move on?

01:29:11.980 --> 01:29:13.377
<v Erik>Yeah, thank you.</v>

01:29:14.844 --> 01:29:17.505
<v ->Thank you for the question by the way.</v>

01:29:17.505 --> 01:29:19.805
<v Erik>Yeah, I think the,</v>

01:29:19.805 --> 01:29:22.790
so I agree with wholeheartedly

01:29:22.790 --> 01:29:25.532
and that is about both scale and complexity.

01:29:25.532 --> 01:29:27.663
And the biggest challenge

01:29:27.663 --> 01:29:31.490
that I think I see is when multiple large events

01:29:31.490 --> 01:29:34.270
also come together simultaneously.

01:29:34.270 --> 01:29:36.850
So it increases both scale and complexity

01:29:36.850 --> 01:29:40.190
as if we having to deal with significant wildfires

01:29:40.190 --> 01:29:41.670
at the same time.

01:29:41.670 --> 01:29:44.490
And if there are other natural events that

01:29:46.062 --> 01:29:50.330
enabled us to have to respond in a much larger way,

01:29:50.330 --> 01:29:53.000
I do believe and we've exercised

01:29:53.000 --> 01:29:55.560
and it's those points of JoVE that we've conducted,

01:29:55.560 --> 01:29:58.630
we're about as ready as we can be.

01:29:58.630 --> 01:30:02.890
The pre design or pre engineering of a PSPS plan

01:30:02.890 --> 01:30:07.230
are pretty much about understanding what can be preemptively

01:30:07.230 --> 01:30:10.670
done prior to an event actually coming in,

01:30:10.670 --> 01:30:15.670
when we see it coming and then having a efficient execution,

01:30:16.550 --> 01:30:18.350
leveraging all of the technologies,

01:30:18.350 --> 01:30:21.860
and I think we're gonna do our best

01:30:21.860 --> 01:30:25.130
to manage as many of these events as we can,

01:30:25.130 --> 01:30:28.770
in a COVID safe way to manage them remotely.

01:30:28.770 --> 01:30:30.090
But if push comes to shove,

01:30:30.090 --> 01:30:32.440
and we get into a much larger event,

01:30:32.440 --> 01:30:35.470
we have also defined our emergency operations center

01:30:35.470 --> 01:30:38.547
to be able to accommodate more staff

01:30:38.547 --> 01:30:41.623
in a very COVID safe manner.

01:30:43.290 --> 01:30:45.240
<v ->Okay, Eric Lamoreaux,</v>

01:30:45.240 --> 01:30:47.653
you've been trying to ask a question, I believe.

01:30:49.050 --> 01:30:50.970
<v ->I have, thank you president.</v>

01:30:50.970 --> 01:30:53.720
I've got a couple quick comments I wanna make.

01:30:53.720 --> 01:30:56.670
And then I've got a question I'd like,

01:30:56.670 --> 01:30:57.700
had a similar response to.

01:30:57.700 --> 01:31:00.123
One, on the telecom piece from earlier,

01:31:01.140 --> 01:31:03.160
appreciated the comments from Edison

01:31:03.160 --> 01:31:05.370
that the telecoms have a responsibility

01:31:05.370 --> 01:31:06.723
for their resiliency.

01:31:08.120 --> 01:31:09.650
Agreed.

01:31:09.650 --> 01:31:12.320
The communication to them is critically important

01:31:12.320 --> 01:31:14.320
for that downstream consequence.

01:31:14.320 --> 01:31:18.080
What we need to know from the telecoms sooner than later,

01:31:18.080 --> 01:31:20.647
when we've got an outage, what is that outage?

01:31:20.647 --> 01:31:24.450
What does that impact look like in terms of the customers

01:31:24.450 --> 01:31:28.180
that might normally be taking advantage of that power?

01:31:28.180 --> 01:31:30.580
So the sooner that they can understand

01:31:30.580 --> 01:31:32.200
where the outage is occurring,

01:31:32.200 --> 01:31:33.670
then they could get back to us

01:31:33.670 --> 01:31:35.140
on what that impact looks like.

01:31:35.140 --> 01:31:37.150
So appreciate the work on that.

01:31:37.150 --> 01:31:40.070
You mentioned having access and functional needs rep

01:31:40.070 --> 01:31:41.910
on your IMT,

01:31:41.910 --> 01:31:43.950
we certainly appreciate that.

01:31:43.950 --> 01:31:45.172
I think it's important that

01:31:45.172 --> 01:31:48.400
that individual serves on your team,

01:31:48.400 --> 01:31:51.300
but that also is culturally something

01:31:51.300 --> 01:31:53.670
that's integrated into all that you do.

01:31:53.670 --> 01:31:56.980
And I know that as an organization, you understand that,

01:31:56.980 --> 01:32:00.040
but it's important that AFN

01:32:00.040 --> 01:32:01.408
and addressing the needs of the access

01:32:01.408 --> 01:32:03.190
and functional community,

01:32:03.190 --> 01:32:05.500
isn't something we think about just during that moment,

01:32:05.500 --> 01:32:08.360
but it's something that's integrated into our process.

01:32:08.360 --> 01:32:13.360
And then, would like to know offline,

01:32:14.360 --> 01:32:17.170
what specifically you do to coordinate

01:32:17.170 --> 01:32:19.590
with our Southern California Geographic Area

01:32:19.590 --> 01:32:23.570
Coordination center, when you weren't proposing into that.

01:32:23.570 --> 01:32:25.476
I know that you've got a robust set of tools

01:32:25.476 --> 01:32:27.100
that you're using,

01:32:27.100 --> 01:32:32.100
and you are doing very precise considerations

01:32:32.170 --> 01:32:36.060
for PSPS events, but I'd like to understand better offline,

01:32:36.060 --> 01:32:38.050
what specifically that coordination

01:32:38.050 --> 01:32:40.720
with the GAC in Southern California looks like.

01:32:40.720 --> 01:32:42.630
And then if you could answer for me here

01:32:42.630 --> 01:32:47.630
and appreciate the time on the restoration of your events,

01:32:48.250 --> 01:32:52.410
what are the mutual aid capabilities that you have to bring

01:32:52.410 --> 01:32:56.330
personnel or other resources in to expedite

01:32:56.330 --> 01:32:59.160
that restoration following an event,

01:32:59.160 --> 01:33:01.670
what are you prepared to do this year?

01:33:01.670 --> 01:33:03.910
<v ->Oh, thank you deputy.</v>

01:33:03.910 --> 01:33:06.201
We, as far as restoration,

01:33:06.201 --> 01:33:09.420
again, it would all flow from what level of damage

01:33:09.420 --> 01:33:11.480
or how many circuits were de-energized

01:33:11.480 --> 01:33:13.510
and require inspections.

01:33:13.510 --> 01:33:16.310
We've actually built a series of

01:33:18.449 --> 01:33:21.140
a key contract support parties to leverage additional

01:33:21.140 --> 01:33:23.043
resources as necessary,

01:33:23.960 --> 01:33:28.270
to help us with food inspections, if required.

01:33:28.270 --> 01:33:31.693
So again, when we have an event, the circus de-energize,

01:33:32.770 --> 01:33:36.300
we are looking to have our qualified electrical workers

01:33:36.300 --> 01:33:38.840
inspect those lines, identify damage,

01:33:38.840 --> 01:33:42.911
obviously we don't want to reenergize into a bad situation.

01:33:42.911 --> 01:33:47.133
So, to do that, we first use our own crews.

01:33:48.010 --> 01:33:53.010
Next, we step it up to a layer of contractor crews,

01:33:53.090 --> 01:33:55.680
are also qualified electrical workers.

01:33:55.680 --> 01:33:58.770
To the extent that the event was very big,

01:33:58.770 --> 01:34:02.490
we would be prepared to reach out to our mutual aid system,

01:34:02.490 --> 01:34:07.490
either through PGD, SDGE and other Western utilities.

01:34:09.900 --> 01:34:11.560
We have supported each other,

01:34:11.560 --> 01:34:14.700
I should point out during some of the bigger fires,

01:34:14.700 --> 01:34:18.680
we have each sent our own crews up to a restoration

01:34:18.680 --> 01:34:22.124
after major events, to the extent we needed to do that,

01:34:22.124 --> 01:34:23.610
we'd be prepared to do that,

01:34:23.610 --> 01:34:27.800
if that would significantly expedite our restoration times.

01:34:27.800 --> 01:34:31.680
So far, given the time it takes to get those crews on board,

01:34:31.680 --> 01:34:35.200
usually it's within our own teams first,

01:34:35.200 --> 01:34:38.490
and then augmented by contractor teams,

01:34:38.490 --> 01:34:40.403
that get us the quickest response.

01:34:43.380 --> 01:34:45.930
I'm not sure deputy, if that answers your question?

01:34:47.620 --> 01:34:48.453
<v ->Well, it does.</v>

01:34:48.453 --> 01:34:52.740
I would caution the reliance on mutual aid from PGE

01:34:52.740 --> 01:34:54.700
and San Diego Gas and Electric,

01:34:54.700 --> 01:34:57.141
especially if we find ourselves in October,

01:34:57.141 --> 01:34:59.210
an event like we had last October,

01:34:59.210 --> 01:35:02.390
where everybody is in the middle of PSPS,

01:35:02.390 --> 01:35:05.570
those resources are likely not going to be available to you.

01:35:05.570 --> 01:35:07.558
I know PGE was challenged to get resources in

01:35:07.558 --> 01:35:09.700
from out of State last year as well,

01:35:09.700 --> 01:35:12.610
so continuing to work on refining,

01:35:12.610 --> 01:35:14.513
what that expanded capability looks like,

01:35:14.513 --> 01:35:16.350
I think is important.

01:35:16.350 --> 01:35:17.840
<v ->Yeah, I thank you deputy,</v>

01:35:17.840 --> 01:35:20.840
I also understand that our CEO,

01:35:20.840 --> 01:35:23.430
Kevin Payne and Head of Business Resiliency,

01:35:23.430 --> 01:35:26.290
met with the Western utilities as well.

01:35:26.290 --> 01:35:28.766
'Cause we agree it's most likely

01:35:28.766 --> 01:35:32.290
that is something's hitting the California utilities,

01:35:32.290 --> 01:35:33.610
many of us at the same time.

01:35:33.610 --> 01:35:36.570
So we probably would be leveraging other folks in the West

01:35:36.570 --> 01:35:39.020
first to pull additional resources if we need to.

01:35:40.980 --> 01:35:44.510
<v ->Okay, we're way over time, and we have public,</v>

01:35:44.510 --> 01:35:46.710
I'm assuming we have members of the public

01:35:46.710 --> 01:35:48.073
waiting in the queue.

01:35:49.120 --> 01:35:52.480
I really wanna thank Phil, you and your team

01:35:52.480 --> 01:35:54.628
for your presentation today.

01:35:54.628 --> 01:35:57.330
And I know I have more questions,

01:35:57.330 --> 01:35:59.150
I think my fellow Commissioners do as well,

01:35:59.150 --> 01:36:01.460
but we really need to move on now

01:36:01.460 --> 01:36:05.863
to opening the lines to the public.

01:36:05.863 --> 01:36:07.520
So for the public who is waiting,

01:36:07.520 --> 01:36:12.007
I just want to remind you to dial (800) 857-1917

01:36:14.594 --> 01:36:19.594
and answer 989 9501 and press star one,

01:36:19.727 --> 01:36:21.427
and you'll be placed in the queue.

01:36:22.950 --> 01:36:26.660
Wait for the operator to call your name,

01:36:26.660 --> 01:36:29.020
be patient, stay on the line.

01:36:29.020 --> 01:36:32.240
And each caller today will have three minutes

01:36:32.240 --> 01:36:37.240
to speak to us and ask questions.

01:36:37.540 --> 01:36:40.540
You will hear a bell sound when your time's up.

01:36:40.540 --> 01:36:43.060
So with that, I'm going to turn to the operator

01:36:43.060 --> 01:36:43.970
and operator,

01:36:43.970 --> 01:36:46.520
can you notice now how many people are on the line?

01:36:50.060 --> 01:36:50.893
<v Operator>Thank you,</v>

01:36:50.893 --> 01:36:52.430
at this time, no one has queued up,

01:36:52.430 --> 01:36:55.650
once again, if you have a comment, please press star,

01:36:55.650 --> 01:36:58.640
then one, unmute your phone and record your name clearly

01:36:58.640 --> 01:37:01.370
when prompted, if you would like to withdraw your comments,

01:37:01.370 --> 01:37:03.973
press star, then two, one moment.

01:37:14.339 --> 01:37:18.585
<v ->Wait a few moments to see if people join in,</v>

01:37:18.585 --> 01:37:20.723
a bit over time, I hope we didn't lose anyone.

01:37:33.950 --> 01:37:35.383
Operator, is anybody joined?

01:37:37.900 --> 01:37:40.160
<v Operator>The first question comes from Melissa</v>

01:37:40.160 --> 01:37:41.663
Kristine, your line is open.

01:37:44.590 --> 01:37:46.210
<v Melissa>Thank you, this is Melissa Kristine</v>

01:37:46.210 --> 01:37:48.767
from the Center for Accessible Technology.

01:37:48.767 --> 01:37:51.990
I have a number of questions, and so in my time,

01:37:51.990 --> 01:37:54.540
I'd like to sort of put them forward briefly

01:37:54.540 --> 01:37:57.560
and hopefully many as possible can be answered.

01:37:57.560 --> 01:38:00.970
And I'm referencing the slide presentation that was given.

01:38:00.970 --> 01:38:03.780
First of all, the slides don't speak at all

01:38:03.780 --> 01:38:07.650
to efforts by SCE to identify people with access

01:38:07.650 --> 01:38:11.560
and functional needs outside of not just medical baseline,

01:38:11.560 --> 01:38:14.840
but your limited definition of critical care.

01:38:14.840 --> 01:38:17.130
I'd like to understand what SCE is doing

01:38:17.130 --> 01:38:20.150
to better understand and identify its population

01:38:20.150 --> 01:38:22.540
of access and functional needs customers

01:38:22.540 --> 01:38:25.360
who are not enrolled in the medical baseline program,

01:38:25.360 --> 01:38:26.830
which is something that was required

01:38:26.830 --> 01:38:28.343
by the phase two decision.

01:38:29.780 --> 01:38:31.870
Then on the slides directly,

01:38:31.870 --> 01:38:34.170
side four on decision points,

01:38:34.170 --> 01:38:37.530
doesn't include any considerations of risks to communities

01:38:37.530 --> 01:38:39.440
that would be de-energized.

01:38:39.440 --> 01:38:42.030
And I would like to understand how that's being factored

01:38:42.030 --> 01:38:43.720
into the decision making.

01:38:43.720 --> 01:38:45.930
It only looks at risks of wildfire,

01:38:45.930 --> 01:38:47.580
which is of course important,

01:38:47.580 --> 01:38:49.443
but nothing on the community side.

01:38:51.360 --> 01:38:55.090
Turning to slide five, on reduction of impact.

01:38:55.090 --> 01:38:57.370
Your slide doesn't include any consideration

01:38:57.370 --> 01:38:59.560
of customers whose medical needs

01:38:59.560 --> 01:39:01.980
are not immediately life threatening.

01:39:01.980 --> 01:39:05.620
And you confirmed that you're only providing support

01:39:05.620 --> 01:39:08.060
for customers who are critical care,

01:39:08.060 --> 01:39:10.540
but a number of issues that aren't life-threatening

01:39:10.540 --> 01:39:13.920
within two hours can cause ongoing health,

01:39:13.920 --> 01:39:16.110
safety or mobility impacts

01:39:16.110 --> 01:39:17.590
if a customer is without power

01:39:17.590 --> 01:39:19.620
for an extended amount of time,

01:39:19.620 --> 01:39:21.480
for example, someone will lose mobility

01:39:21.480 --> 01:39:24.030
if they can't charge their power wheelchair,

01:39:24.030 --> 01:39:25.410
and someone with sleep apnea

01:39:25.410 --> 01:39:27.550
who can't use their CPAP machine

01:39:27.550 --> 01:39:30.540
is unlikely to go into immediate distress,

01:39:30.540 --> 01:39:32.903
but their overall health might be compromised.

01:39:34.100 --> 01:39:37.150
On slide six, for communications.

01:39:37.150 --> 01:39:40.310
I'd like to understand what SCE has considered

01:39:40.310 --> 01:39:43.010
in terms of web accessibility

01:39:43.010 --> 01:39:45.900
and meeting web access standards.

01:39:45.900 --> 01:39:47.880
The sample maps that are in the appendix

01:39:47.880 --> 01:39:50.500
have obvious issues with color contrast,

01:39:50.500 --> 01:39:52.040
and would be a very limited value

01:39:52.040 --> 01:39:55.060
to someone with low vision trying to look at them.

01:39:55.060 --> 01:39:58.000
Similarly, it's unclear what information

01:39:58.000 --> 01:40:00.140
is gonna be available in language,

01:40:00.140 --> 01:40:02.540
particularly for those customers who speak languages

01:40:02.540 --> 01:40:04.203
that aren't directly supported.

01:40:05.200 --> 01:40:07.850
And my final slide about backup generation,

01:40:07.850 --> 01:40:09.440
I know there were a number of questions

01:40:09.440 --> 01:40:11.820
about this from the panel,

01:40:11.820 --> 01:40:15.150
but I'd like to understand better how it's being publicized

01:40:15.150 --> 01:40:19.070
and how the utility expects to really get the devices

01:40:19.070 --> 01:40:22.710
that it's seeking to deploy in place this year,

01:40:22.710 --> 01:40:24.210
when the batteries aren't even set

01:40:24.210 --> 01:40:26.420
to arrive until September.

01:40:26.420 --> 01:40:28.730
I'd appreciate as much a response to these questions

01:40:28.730 --> 01:40:31.330
as I can in the time available, thank you very much.

01:40:32.680 --> 01:40:34.740
<v ->Thanks Melissa very much for your questions,</v>

01:40:34.740 --> 01:40:36.630
I'm very happy that you covered

01:40:36.630 --> 01:40:41.060
the phase two PSPS guidelines decision.

01:40:41.060 --> 01:40:43.090
It was a question I was going to ask as well,

01:40:43.090 --> 01:40:45.410
but I was worried about running out of time.

01:40:45.410 --> 01:40:50.410
So I hope that Edison can answer those questions.

01:40:50.448 --> 01:40:51.865
Thanks, Melissa.

01:40:54.975 --> 01:40:57.350
<v Melissa>We'll reiterate any of those questions</v>

01:40:57.350 --> 01:40:59.886
'cause I know I covered a lot of ground there.

01:40:59.886 --> 01:41:02.512
<v ->Okay, I'm going to parse these up,</v>

01:41:02.512 --> 01:41:04.510
but that might be the most efficient way to do it,

01:41:04.510 --> 01:41:06.640
so we're not playing tag team here.

01:41:06.640 --> 01:41:11.640
I will note that we commented on

01:41:11.640 --> 01:41:15.320
our access essential need customers and made reference to,

01:41:15.320 --> 01:41:16.750
again, one adding specialist

01:41:16.750 --> 01:41:19.310
on the PSPS incident management team.

01:41:19.310 --> 01:41:21.667
And I know there's a lot more to it than that, of course,

01:41:21.667 --> 01:41:25.100
and then participating in the Statewide Advisory Council

01:41:25.100 --> 01:41:26.800
to help us understand,

01:41:26.800 --> 01:41:29.903
and we're working a number different levels

01:41:29.903 --> 01:41:33.310
to help understand the needs of our AFN customers,

01:41:33.310 --> 01:41:37.291
and also frankly, the scope of our AFN customers.

01:41:37.291 --> 01:41:41.220
I'll ask Marc in a moment to elaborate on that.

01:41:41.220 --> 01:41:43.202
You'll have some more detail to share.

01:41:43.202 --> 01:41:48.202
I do wanna comment before I turn this over to he and Eric,

01:41:48.650 --> 01:41:52.500
to answer some of these questions about the consideration

01:41:52.500 --> 01:41:54.870
of impact to the community.

01:41:54.870 --> 01:41:59.770
You're right, we only cited a few of the conditions

01:41:59.770 --> 01:42:02.613
that go into our consideration of a PSPS event,

01:42:03.447 --> 01:42:08.440
I wanna make sure that I don't leave you

01:42:08.440 --> 01:42:12.560
with the impression that we are not laser-focused

01:42:12.560 --> 01:42:15.410
on community safety and public safety

01:42:15.410 --> 01:42:17.930
when we execute a PSPS,

01:42:17.930 --> 01:42:21.952
it is why the outreach to our County OES,

01:42:21.952 --> 01:42:26.253
our State OES, our fire agency partners,

01:42:28.359 --> 01:42:31.810
our city and County government representatives,

01:42:31.810 --> 01:42:34.530
and the people that we send

01:42:34.530 --> 01:42:35.667
to their incident command centers,

01:42:35.667 --> 01:42:38.580
and we do staff those with our own people,

01:42:38.580 --> 01:42:41.770
during events to make sure we understand

01:42:41.770 --> 01:42:43.699
the conditions on the ground.

01:42:43.699 --> 01:42:45.950
There are a number of other considerations,

01:42:45.950 --> 01:42:49.823
the impact on traffic lights, ingress and egress,

01:42:50.775 --> 01:42:54.790
critical needs for firefighters during an event.

01:42:54.790 --> 01:42:56.480
These are all things that go into,

01:42:56.480 --> 01:43:01.480
and its why the question of a formulaic answer

01:43:02.280 --> 01:43:04.900
to a PSPS is so difficult

01:43:04.900 --> 01:43:07.130
because there are so many conditions.

01:43:07.130 --> 01:43:10.960
And it's why we build this Incident Command System,

01:43:10.960 --> 01:43:15.580
and it's why we have a very robust ICS system

01:43:15.580 --> 01:43:17.030
with instant commanders.

01:43:17.030 --> 01:43:22.030
And again, I fully trained and fully engaged a workforce

01:43:22.900 --> 01:43:25.020
that is evaluating these conditions,

01:43:25.020 --> 01:43:25.853
but more importantly,

01:43:25.853 --> 01:43:28.660
working with our communities to understand the trade offs

01:43:28.660 --> 01:43:30.263
that are happening in the event.

01:43:31.410 --> 01:43:35.300
Our goal is to increase and enhance public safety

01:43:35.300 --> 01:43:37.400
when we do a PSPS event.

01:43:37.400 --> 01:43:39.410
We understand that there are trade offs.

01:43:39.410 --> 01:43:41.500
Some of these answers are not simple,

01:43:41.500 --> 01:43:45.860
but we are absolutely considering the impact of a PSPS.

01:43:45.860 --> 01:43:49.860
The fact that garage door openers don't work in PSPS events,

01:43:49.860 --> 01:43:53.060
that may a gated communities,

01:43:53.060 --> 01:43:55.020
may have difficulty with egress ingress.

01:43:55.020 --> 01:43:56.640
These are all things that are going

01:43:56.640 --> 01:43:58.250
through the incident commander's minds

01:43:58.250 --> 01:44:00.530
as we go through these decision making processes.

01:44:00.530 --> 01:44:05.190
So it is very complicated but we do consider those things.

01:44:05.190 --> 01:44:08.323
And it's why there's no formulaic response to the PSPS.

01:44:08.323 --> 01:44:11.200
Now, I'd like to T the community,

01:44:11.200 --> 01:44:14.636
sort of the ASN or elaborate on the ASN,

01:44:14.636 --> 01:44:17.400
and the non life threatening customers.

01:44:17.400 --> 01:44:19.950
Marc, you may be able to elaborate on that

01:44:19.950 --> 01:44:23.490
and the other questions on backup generation

01:44:23.490 --> 01:44:25.770
and communications 'cause I think those all

01:44:25.770 --> 01:44:27.141
hit the customer dimension

01:44:27.141 --> 01:44:29.450
that your team has been focused on.

01:44:29.450 --> 01:44:31.230
And Eric, please fill in if there's other things

01:44:31.230 --> 01:44:33.460
that you think need to be addressed

01:44:33.460 --> 01:44:35.870
to adequately answer the questions.

01:44:35.870 --> 01:44:38.950
<v Marc>Yes sir, thank you, Phil, and thank you,</v>

01:44:38.950 --> 01:44:43.950
Melissa Kristine is one of our AFN Advisory Board Members.

01:44:45.150 --> 01:44:49.850
She is always making sure that we are thinking about

01:44:49.850 --> 01:44:51.707
not just the majority of the population

01:44:51.707 --> 01:44:52.840
and how to handle them,

01:44:52.840 --> 01:44:57.260
but also folks that are not as populous.

01:44:57.260 --> 01:45:00.870
So the first question that I got,

01:45:00.870 --> 01:45:02.320
I tried to get all of them

01:45:02.320 --> 01:45:05.680
and I'll try to do this rapid fire to get them answered,

01:45:05.680 --> 01:45:07.940
identify AFN outreach.

01:45:07.940 --> 01:45:11.670
The phase two PSPS decision requires that the IOUs use data

01:45:11.670 --> 01:45:15.380
that is one of three households that self identify

01:45:15.380 --> 01:45:17.510
to receive in person visits,

01:45:17.510 --> 01:45:20.350
receive utility comms in a non standard format,

01:45:20.350 --> 01:45:23.720
or self identifying as a person with disability.

01:45:23.720 --> 01:45:25.760
First thing with that, we think that's a good start,

01:45:25.760 --> 01:45:26.622
we're not sure that's enough,

01:45:26.622 --> 01:45:29.150
so we're going above and beyond that,

01:45:29.150 --> 01:45:34.150
anyone that identifies to our of our reps,

01:45:35.220 --> 01:45:40.090
that they are have access and functional needs support,

01:45:40.090 --> 01:45:41.720
we profile those customers now

01:45:41.720 --> 01:45:44.670
and start to market to them

01:45:44.670 --> 01:45:47.610
and provide information to them about other programs.

01:45:47.610 --> 01:45:50.620
So as you observed,

01:45:50.620 --> 01:45:53.430
I did say that with the battery backup systems

01:45:53.430 --> 01:45:57.000
is for income qualified and critical care customers,

01:45:57.000 --> 01:46:00.640
that does not mean we're leaving the non-critical medical

01:46:00.640 --> 01:46:04.280
equipment, such as wheelchairs or CPAP machines behind.

01:46:04.280 --> 01:46:06.880
We do have a rebate program

01:46:06.880 --> 01:46:09.230
where these customers can get battery backups,

01:46:09.230 --> 01:46:11.285
clean battery backup systems,

01:46:11.285 --> 01:46:13.600
and we will provide a rebate for them.

01:46:13.600 --> 01:46:16.100
So the difference between the program is,

01:46:16.100 --> 01:46:17.020
in one regard in,

01:46:17.020 --> 01:46:19.330
in the first one where they're low income critical care,

01:46:19.330 --> 01:46:21.900
we pay for everything a hundred percent upfront,

01:46:21.900 --> 01:46:22.945
in the second one,

01:46:22.945 --> 01:46:24.540
we're not paying up front

01:46:24.540 --> 01:46:26.540
where a customer has to put out money first,

01:46:26.540 --> 01:46:30.980
and then we give them rebates for the battery

01:46:30.980 --> 01:46:32.110
for their medical equipment,

01:46:32.110 --> 01:46:35.660
which will be not non life threatening medical equipment.

01:46:35.660 --> 01:46:40.150
In fact, that program is available to any customer

01:46:40.150 --> 01:46:45.000
in high fire risk area that needs a battery backup.

01:46:45.000 --> 01:46:48.297
So the things that we are doing to identify

01:46:48.297 --> 01:46:50.240
additional AFN customers,

01:46:50.240 --> 01:46:52.970
and remember the definition of AFN is really large.

01:46:52.970 --> 01:46:57.970
As Edison looked at the definition of AFN customers,

01:46:58.480 --> 01:47:01.520
roughly 70, a little bit higher than 70%

01:47:01.520 --> 01:47:05.350
of all of our customers fit in the AFN definition.

01:47:05.350 --> 01:47:07.940
So there's only 30% of our customers that do not.

01:47:07.940 --> 01:47:11.780
So we have lots of customers that are in this definition,

01:47:11.780 --> 01:47:14.110
but what we're trying to do is make sure we get the right

01:47:14.110 --> 01:47:15.993
resources to the right level of customers.

01:47:15.993 --> 01:47:18.683
And that's why we do differentiate a little bit.

01:47:23.116 --> 01:47:27.410
So we do outreach to customers each year on our programs,

01:47:27.410 --> 01:47:31.980
both for care, fairer medical baseline, and critical care,

01:47:31.980 --> 01:47:34.840
and so every customer in our service targets those.

01:47:34.840 --> 01:47:36.590
We also have dear neighbor letters

01:47:36.590 --> 01:47:38.240
that we send to our customers,

01:47:38.240 --> 01:47:40.210
every customer will get a dear neighbor letter

01:47:40.210 --> 01:47:42.710
whether in a high fire risk or not.

01:47:42.710 --> 01:47:45.956
And those programs and opportunities will be identified

01:47:45.956 --> 01:47:49.470
for them and will request that they identify to us

01:47:49.470 --> 01:47:51.690
if they believe they have a disability

01:47:51.690 --> 01:47:54.000
in the home medical device

01:47:54.000 --> 01:47:57.030
or any other particular characteristic

01:47:57.030 --> 01:47:58.510
that might make them more vulnerable

01:47:58.510 --> 01:48:00.160
during events like this.

01:48:00.160 --> 01:48:03.440
And then this is how we develop our circuit,

01:48:03.440 --> 01:48:06.410
by circuit level customer care plans,

01:48:06.410 --> 01:48:08.039
with this type of information.

01:48:08.039 --> 01:48:10.860
In addition, we also use Axiom data,

01:48:10.860 --> 01:48:12.410
which is third party data

01:48:12.410 --> 01:48:15.720
that helps us try to identify areas of information

01:48:15.720 --> 01:48:18.320
about customers that we don't already have.

01:48:18.320 --> 01:48:21.580
And that also helps us identify

01:48:21.580 --> 01:48:24.250
not just the needs for a medical,

01:48:24.250 --> 01:48:27.220
but also limited English speaking

01:48:27.220 --> 01:48:29.970
and other characteristics like that too,

01:48:29.970 --> 01:48:33.060
which can make someone more vulnerable during these events.

01:48:33.060 --> 01:48:37.767
So I got, I think to one of the other questions was about

01:48:37.767 --> 01:48:40.004
sce.com and language preference.

01:48:40.004 --> 01:48:43.558
Today, we or historically we have been doing

01:48:43.558 --> 01:48:47.810
language communications and website translations

01:48:47.810 --> 01:48:49.660
in seven different languages.

01:48:49.660 --> 01:48:52.730
We are moving for wildfire communications

01:48:52.730 --> 01:48:55.752
and PSPS communications to 15 languages.

01:48:55.752 --> 01:48:59.390
We've been working with my cop both last year and this year

01:48:59.390 --> 01:49:04.103
to even get indigenous languages converted in addition.

01:49:04.103 --> 01:49:09.103
The comments about folks who have visual limitations

01:49:11.440 --> 01:49:15.100
in the website, we are continually looking at every video,

01:49:15.100 --> 01:49:18.488
having closed caption, even in other languages.

01:49:18.488 --> 01:49:23.310
And in addition to any other functionality

01:49:23.310 --> 01:49:25.370
that is WCAG,

01:49:25.370 --> 01:49:29.287
compliant WCAG is access guidelines

01:49:29.287 --> 01:49:34.211
for customers with disabilities.

01:49:34.211 --> 01:49:36.510
And I missed her second question

01:49:36.510 --> 01:49:38.570
and I missed her fifth question.

01:49:38.570 --> 01:49:41.500
So I'll give it to Eric in case I missed anything.

01:49:41.500 --> 01:49:42.580
Or back to Phil.

01:49:48.166 --> 01:49:49.960
<v Erik>I think he answered all that,</v>

01:49:49.960 --> 01:49:52.793
I don't have anything else to add.

01:49:55.450 --> 01:49:57.830
<v Melissa>This is Melissa again,</v>

01:49:57.830 --> 01:50:00.110
you covered a lot of the questions,

01:50:00.110 --> 01:50:01.810
which I very much appreciate.

01:50:01.810 --> 01:50:03.433
On the web accessibility,

01:50:03.433 --> 01:50:05.827
there's one thing that I pointed out in particular,

01:50:05.827 --> 01:50:09.320
are the sample maps that are attached in your appendix,

01:50:09.320 --> 01:50:11.670
which have very low color contrast.

01:50:11.670 --> 01:50:14.660
And very specifically will not be easy

01:50:14.660 --> 01:50:16.890
for someone with low vision to navigate,

01:50:16.890 --> 01:50:19.770
so I appreciate your note that you're working to comply

01:50:19.770 --> 01:50:21.873
with the WCAG guidelines,

01:50:22.750 --> 01:50:27.750
but I think that there are problems with the maps,

01:50:27.940 --> 01:50:31.020
at least as far as it made it into your PowerPoint.

01:50:31.020 --> 01:50:34.704
And then my other question that didn't really get an answer

01:50:34.704 --> 01:50:38.480
is about publicizing your backup generation

01:50:38.480 --> 01:50:39.770
and deploying it,

01:50:39.770 --> 01:50:41.870
particularly when you said that the batteries

01:50:41.870 --> 01:50:44.400
aren't even going to arrive until September

01:50:44.400 --> 01:50:46.550
and how you expect to install them in time

01:50:46.550 --> 01:50:48.900
for the highest risk period for shut off event.

01:50:50.030 --> 01:50:52.813
<v Marc>Okay, Phil, do you want me to tackle that?</v>

01:50:53.740 --> 01:50:54.950
<v ->Yeah, I do.</v>

01:50:54.950 --> 01:50:59.010
Just one, one note about the de-generation we mentioned,

01:50:59.010 --> 01:51:01.350
we've spoken about a couple of different generations,

01:51:01.350 --> 01:51:05.350
we mentioned the 17 megawatts that's larger scale,

01:51:05.350 --> 01:51:07.130
that's not individual residents.

01:51:07.130 --> 01:51:09.190
I know Melissa you weren't referring to that,

01:51:09.190 --> 01:51:14.190
just to make sure that's a different bucket of generations.

01:51:14.470 --> 01:51:16.790
So yeah Marc, why don't you go ahead

01:51:16.790 --> 01:51:18.433
to de-generator program please?

01:51:19.385 --> 01:51:20.218
<v Marc>Oh yeah, I'll do that.</v>

01:51:20.218 --> 01:51:24.150
And I'll start actually with a sample maps and the contrast,

01:51:24.150 --> 01:51:25.870
Melissa, I think that's great feedback,

01:51:25.870 --> 01:51:28.890
and we'll take that and see what we can do to improve that

01:51:28.890 --> 01:51:31.230
and see how we can make sure it continues

01:51:31.230 --> 01:51:33.080
to meet the WCAG requirements.

01:51:33.080 --> 01:51:36.643
On the generation, the backup batteries,

01:51:36.643 --> 01:51:41.643
as I said earlier, we had roughly 250 batteries already.

01:51:42.100 --> 01:51:45.200
The reason that they're not coming in September was twofold.

01:51:45.200 --> 01:51:50.200
One was we negotiated an extended warranty,

01:51:50.300 --> 01:51:51.920
a three year warranty as opposed to one,

01:51:51.920 --> 01:51:53.800
but the second was quite honestly,

01:51:53.800 --> 01:51:56.250
our manufacturers got impacted by COVID

01:51:56.250 --> 01:51:59.229
in March, April and May, and their production was shut down.

01:51:59.229 --> 01:52:01.520
So that's about three weeks from now

01:52:01.520 --> 01:52:04.950
that we believe we'll get those batteries

01:52:04.950 --> 01:52:07.223
for other critical care customers.

01:52:07.223 --> 01:52:10.110
And installation, we hope to get down

01:52:10.110 --> 01:52:12.760
before the big wildfire season,

01:52:12.760 --> 01:52:16.373
the final 2000 or so customers.

01:52:21.220 --> 01:52:22.910
Think that's it.

01:52:22.910 --> 01:52:23.743
<v ->Okay.</v>

01:52:27.190 --> 01:52:30.330
Operator I could you please check the line,

01:52:30.330 --> 01:52:34.610
we're getting close to our limited time.

01:52:34.610 --> 01:52:35.443
All right.

01:52:36.580 --> 01:52:39.680
<v Operator>Thank you, the next speaker is Den Ja Yung.</v>

01:52:39.680 --> 01:52:40.703
Your line is open.

01:52:42.710 --> 01:52:45.960
<v Den>Hi, I'm a dependent Canyon resident</v>

01:52:45.960 --> 01:52:48.780
and I have two simple questions.

01:52:48.780 --> 01:52:50.790
We're a high fire threat district,

01:52:50.790 --> 01:52:55.370
we're rural, about 10,000 people and we have no cell towers.

01:52:55.370 --> 01:52:59.160
So like paradise, we also have limited access,

01:52:59.160 --> 01:53:01.780
like three roads for evacuation.

01:53:01.780 --> 01:53:04.230
With no cell towers, we lose power.

01:53:04.230 --> 01:53:07.810
Most of us rely on WiFi cell service.

01:53:07.810 --> 01:53:11.130
So unlike needing something to be life sustaining,

01:53:11.130 --> 01:53:12.900
because it's a breathing machine,

01:53:12.900 --> 01:53:17.070
we need to know when to evacuate and which road to take.

01:53:17.070 --> 01:53:20.720
And so communications loss can be life threatening.

01:53:20.720 --> 01:53:23.640
So I get that you have eight

01:53:23.640 --> 01:53:26.840
of these Community Crew Vehicles,

01:53:26.840 --> 01:53:30.030
and it would be really nice to know if one of them could

01:53:30.030 --> 01:53:33.300
maybe be earmarked for Topanaga,

01:53:33.300 --> 01:53:37.520
to bring a cell service perhaps via a satellite tower.

01:53:37.520 --> 01:53:39.420
So that's kind of question number one,

01:53:39.420 --> 01:53:43.730
can you maybe put that on your to do list?

01:53:43.730 --> 01:53:48.380
And number two is one thing that strikes me is,

01:53:48.380 --> 01:53:50.130
last year at Woolsey,

01:53:50.130 --> 01:53:55.130
Topanga lost all power for 30 hours and it wasn't a PSPS,

01:53:56.570 --> 01:53:58.950
but it was because somewhere down the line,

01:53:58.950 --> 01:54:01.210
some big thing burned down.

01:54:01.210 --> 01:54:05.595
So whether it's PSPS or whether it's because of a fire

01:54:05.595 --> 01:54:08.200
during the evacuation period,

01:54:08.200 --> 01:54:11.870
we had no way to hear that if you didn't have like some

01:54:11.870 --> 01:54:15.193
of us have Tesla backup batteries, but a lot don't.

01:54:15.193 --> 01:54:18.290
If you could also institute the thought

01:54:18.290 --> 01:54:20.310
that if an area loses power,

01:54:20.310 --> 01:54:25.310
they also might need the CCV,

01:54:25.530 --> 01:54:28.673
even if it isn't an official PSPS, that's it.

01:54:30.057 --> 01:54:32.637
<v ->Thank you very much.</v>

01:54:32.637 --> 01:54:34.044
<v ->Yes, thank you very much.</v>

01:54:34.044 --> 01:54:36.105
I'll respond to that,

01:54:36.105 --> 01:54:38.270
by the way I appreciate the suggestions.

01:54:38.270 --> 01:54:40.820
I'm very familiar, obviously with Topanga Canyon

01:54:40.820 --> 01:54:43.420
and some of the unique features there

01:54:43.420 --> 01:54:45.654
that they can deliver challenges.

01:54:45.654 --> 01:54:49.700
The events outside of PSPS that you've referenced,

01:54:49.700 --> 01:54:51.183
and I do look all those.

01:54:52.890 --> 01:54:55.890
Obviously, that's one reason that our system hardening

01:54:55.890 --> 01:54:56.940
is so important,

01:54:56.940 --> 01:55:00.270
I'm gonna come back to that as one of the mechanisms

01:55:00.270 --> 01:55:03.790
that prevents a loss of infrastructure

01:55:03.790 --> 01:55:07.330
that causes a loss of power that is not PSPS related.

01:55:07.330 --> 01:55:09.980
So, and most of the infrastructure in there

01:55:09.980 --> 01:55:11.090
has been rebuilt,

01:55:11.090 --> 01:55:13.950
or it has a candidate for a cover conductor,

01:55:13.950 --> 01:55:16.072
but hasn't already been done so far.

01:55:16.072 --> 01:55:19.901
As far as the additional resources,

01:55:19.901 --> 01:55:22.780
I think this is something that our team will take back

01:55:22.780 --> 01:55:26.010
and make sure that we're discussing with telcos in terms of,

01:55:26.010 --> 01:55:28.369
do we have backup generation there?

01:55:28.369 --> 01:55:32.860
I do understand the point of losing communication.

01:55:32.860 --> 01:55:36.031
As far as the capability of the Community Crew Vehicles,

01:55:36.031 --> 01:55:38.930
I personally hadn't thought of that as an application

01:55:38.930 --> 01:55:40.690
for them, but it's something that

01:55:40.690 --> 01:55:42.410
we'll ask the team to take a look at.

01:55:42.410 --> 01:55:45.973
And I really want to thank you for the feedback today.

01:55:50.640 --> 01:55:51.540
<v Den>Thank you.</v>

01:55:52.970 --> 01:55:54.550
<v ->Okay.</v>

01:55:54.550 --> 01:55:57.570
I think we have time for one more caller.

01:55:57.570 --> 01:55:59.973
Operator, do we have anybody on the line?

01:56:00.990 --> 01:56:03.440
<v Operator>We do, the last comment comes from John Mahler.</v>

01:56:03.440 --> 01:56:05.130
Your line is open.

01:56:05.130 --> 01:56:06.350
<v John>Thank you.</v>

01:56:06.350 --> 01:56:10.893
I'm also a former member of the Topanga City County Council,

01:56:12.114 --> 01:56:15.720
and I share some of the same sediments of your prior caller,

01:56:15.720 --> 01:56:18.030
but I have two slightly different questions.

01:56:18.030 --> 01:56:22.760
One with respect to these CRCs that you've identified

01:56:22.760 --> 01:56:25.000
and contracted with to date,

01:56:25.000 --> 01:56:28.160
you say that you have 40 of them at this time

01:56:28.160 --> 01:56:30.890
for the entire Edison service area,

01:56:30.890 --> 01:56:35.590
which seems to be a vastly under a smaller number

01:56:36.760 --> 01:56:41.760
than necessary to address any significant PSPS event.

01:56:42.050 --> 01:56:44.160
Even if it's a localized item.

01:56:44.160 --> 01:56:46.910
For instance, from the center of Topanga,

01:56:46.910 --> 01:56:51.680
to either of the closest CRCs that are identified,

01:56:51.680 --> 01:56:54.510
it would be roughly 33 miles,

01:56:54.510 --> 01:56:56.460
but someone would have to travel

01:56:56.460 --> 01:56:58.920
just to go to charge a battery.

01:56:58.920 --> 01:57:02.060
What is being done, if anything

01:57:02.060 --> 01:57:06.840
to identify additional CRCs that are closer

01:57:06.840 --> 01:57:11.840
to where PSPS are likely to take place?

01:57:11.930 --> 01:57:15.380
And the Santa Monica Mountains areas is clearly an area

01:57:15.380 --> 01:57:17.940
which over the years is an area that is likely

01:57:17.940 --> 01:57:21.540
to have many PSPS events.

01:57:21.540 --> 01:57:26.280
And secondly, with respect to Community Crew Vehicles,

01:57:26.280 --> 01:57:28.210
if you only have eight of them again,

01:57:28.210 --> 01:57:30.430
to supplement the CRCs,

01:57:30.430 --> 01:57:33.480
where are they going to be pre-positioned?

01:57:33.480 --> 01:57:37.850
How are the pre-positioning locations to be communicated

01:57:37.850 --> 01:57:41.400
during a time where there is limited cell availability

01:57:41.400 --> 01:57:44.150
for anyone to be able to hear and respond

01:57:44.150 --> 01:57:48.170
or to know where those limited resources are?

01:57:48.170 --> 01:57:50.136
Those are my questions.

01:57:50.136 --> 01:57:51.310
<v ->Okay, thank you very much John.</v>

01:57:51.310 --> 01:57:54.500
I tell you what, I'll start very quickly

01:57:54.500 --> 01:57:56.710
with a couple of answers.

01:57:56.710 --> 01:57:59.280
And then I think Marc then will have some information

01:57:59.280 --> 01:58:00.690
on the CRCs.

01:58:00.690 --> 01:58:03.670
On Community Crew vehicles,

01:58:03.670 --> 01:58:07.030
the pre-positioning obviously depends on our forecast

01:58:09.523 --> 01:58:10.356
of the event.

01:58:10.356 --> 01:58:13.360
So, based on what we see coming in,

01:58:13.360 --> 01:58:16.080
it will dictate our pre-positioning.

01:58:16.080 --> 01:58:18.804
We will move those in advance and in placement,

01:58:18.804 --> 01:58:20.780
sometimes days in advance,

01:58:20.780 --> 01:58:23.910
depending on how quick could we see the events unfolding.

01:58:23.910 --> 01:58:28.910
And by the way, the absence of a CRC

01:58:28.970 --> 01:58:30.620
will be one of the things that influences

01:58:30.620 --> 01:58:31.923
the placement of those.

01:58:32.961 --> 01:58:35.250
On a broad level, I will say, and by the way,

01:58:35.250 --> 01:58:37.150
thank you also for your continued partnership.

01:58:37.150 --> 01:58:41.356
I know we've Edison has worked with Topanga quite bit

01:58:41.356 --> 01:58:45.030
and wanna thank you for the continued partnership

01:58:45.030 --> 01:58:46.834
and feedback 'cause this is the only way

01:58:46.834 --> 01:58:48.610
we're gonna get better.

01:58:48.610 --> 01:58:52.135
But CRC is at 40, we're gonna continue to expand that,

01:58:52.135 --> 01:58:54.760
we're expanding as rapidly

01:58:54.760 --> 01:58:57.830
as we feel we can get these pulled into the system.

01:58:57.830 --> 01:59:01.540
We've targeted areas we think are most important.

01:59:01.540 --> 01:59:04.550
Again, to have the CRC is available,

01:59:04.550 --> 01:59:06.530
Marc you're in the middle of that ramp up program,

01:59:06.530 --> 01:59:07.760
by adjusting your wheelhouse,

01:59:07.760 --> 01:59:10.007
so why don't you address that one

01:59:10.007 --> 01:59:11.930
a little bit more specifically, please?

01:59:11.930 --> 01:59:15.680
<v Marc>Sure, I'll give about 30 seconds or a minute here.</v>

01:59:15.680 --> 01:59:16.880
So just to give you a flavor

01:59:16.880 --> 01:59:18.630
of what the CRCs looked like these,

01:59:18.630 --> 01:59:23.630
and some cases they're like Sears, a couple of hotels,

01:59:24.560 --> 01:59:25.860
but in addition to that,

01:59:25.860 --> 01:59:30.690
we're talking about boys and girls clubs, community centers,

01:59:30.690 --> 01:59:34.180
we're talking about disability community centers

01:59:34.180 --> 01:59:35.280
and other things like that.

01:59:35.280 --> 01:59:37.970
We don't have a lot of control over them.

01:59:37.970 --> 01:59:41.100
We have been doing negotiations

01:59:41.100 --> 01:59:45.930
with over 200 Community Resource Centers all over the place.

01:59:45.930 --> 01:59:48.280
We're still negotiating with a hundred of them

01:59:49.180 --> 01:59:52.090
and we're trying to place them as much as possible

01:59:52.090 --> 01:59:55.969
near areas that are remote, like Topanga Canyon.

01:59:55.969 --> 02:00:00.900
But we also are with regard to CCV placement,

02:00:00.900 --> 02:00:02.700
our Community Crew Vehicles.

02:00:02.700 --> 02:00:05.670
We also are conscious not to place vehicles

02:00:07.890 --> 02:00:10.800
or other Community Resource Centers

02:00:10.800 --> 02:00:15.330
that would not be able to serve the community

02:00:15.330 --> 02:00:20.330
if they got overtaken by a wildfire or did not have power.

02:00:21.220 --> 02:00:24.950
So lots of the CRCs, not only do you have to negotiate

02:00:24.950 --> 02:00:28.180
that they will be open for you,

02:00:28.180 --> 02:00:29.817
you have to negotiate they'll be open for you

02:00:29.817 --> 02:00:31.810
for the full hours, eight to 10.

02:00:31.810 --> 02:00:36.000
And are they also willing to explore?

02:00:36.000 --> 02:00:37.370
Putting in transfer switches

02:00:37.370 --> 02:00:41.420
so that we could provide generation and backup power

02:00:41.420 --> 02:00:45.030
so that it's very complicated to get these in the right spot

02:00:45.030 --> 02:00:46.900
because you don't wanna put them on the same circuit,

02:00:46.900 --> 02:00:48.050
you just de-energize,

02:00:48.050 --> 02:00:51.120
or you're gonna have to have a backup plan for generation.

02:00:51.120 --> 02:00:55.160
So that prolongs the negotiations with the CRCs.

02:00:55.160 --> 02:00:58.010
But Mr. Mahler, thank you for your feedback.

02:00:58.010 --> 02:01:01.010
We will continue to build out our CRCs

02:01:02.080 --> 02:01:04.093
as well as our Community Crew Vehicles.

02:01:05.410 --> 02:01:07.520
<v John>One followup if I might,</v>

02:01:07.520 --> 02:01:10.460
one thing that you might take into consideration

02:01:10.460 --> 02:01:15.460
and explore is hooking up with either LA County or Caltrans,

02:01:16.110 --> 02:01:20.150
both of which have facilities that tend to be proximate

02:01:20.150 --> 02:01:23.619
to a variety of places which are in high fire areas

02:01:23.619 --> 02:01:26.939
and their facilities ought to be available

02:01:26.939 --> 02:01:31.573
for Community Crew Vehicles, if not for CRCs themselves.

02:01:32.420 --> 02:01:33.820
<v Marc>Yes, and we are doing that,</v>

02:01:33.820 --> 02:01:35.170
not just with LA County,

02:01:35.170 --> 02:01:38.090
but all the counties in our territory.

02:01:38.090 --> 02:01:41.810
And like you said, we have been using in this last event,

02:01:41.810 --> 02:01:46.810
we use the CCB in the parking lot of one of the CRCs,

02:01:46.940 --> 02:01:49.330
was not able to open.

02:01:49.330 --> 02:01:51.620
So it became a popup CRC, if you will.

02:01:51.620 --> 02:01:55.210
And we are looking to expand the CCV vehicles

02:01:55.210 --> 02:01:59.313
so that we can put a resource wherever we need,

02:02:00.650 --> 02:02:02.510
I'm sorry, we're a little bit overtime.

02:02:02.510 --> 02:02:04.540
<v ->That's okay, and Mr Mahler,</v>

02:02:04.540 --> 02:02:06.630
thank you so much for the input.

02:02:06.630 --> 02:02:08.420
<v John>You're welcome, thank you.</v>

02:02:08.420 --> 02:02:10.710
<v ->Thanks for calling in, appreciate it.</v>

02:02:10.710 --> 02:02:12.960
Operator, is there anybody else on the line?

02:02:14.080 --> 02:02:17.180
<v Operator>At the time, I'm showing no further comment.</v>

02:02:17.180 --> 02:02:19.030
<v ->Okay, thank you operator.</v>

02:02:19.030 --> 02:02:20.540
No more public on the line,

02:02:20.540 --> 02:02:23.260
the public comment period is now closed.

02:02:23.260 --> 02:02:25.710
Once again, I wanna thank Mr. Harrington

02:02:25.710 --> 02:02:29.090
and your team from Edison

02:02:29.090 --> 02:02:33.110
for such a thorough briefing today.

02:02:33.110 --> 02:02:36.333
Thank you for allowing us to go a little bit over time

02:02:36.333 --> 02:02:38.190
appreciate that,

02:02:38.190 --> 02:02:40.330
and let's just hope

02:02:40.330 --> 02:02:44.310
that we have a lot fewer PSPS events this year.

02:02:44.310 --> 02:02:46.440
And maybe even none.

02:02:46.440 --> 02:02:50.210
Thank you very much for your participation to the public.

02:02:50.210 --> 02:02:54.354
And thank you, Eric and Daniel for your participation

02:02:54.354 --> 02:02:56.700
with my fellow Commissioners,

02:02:56.700 --> 02:02:58.780
appreciate your time very, very much.

02:02:58.780 --> 02:02:59.620
Thank you all.

02:02:59.620 --> 02:03:04.133
Have a very safe and healthy rest of your day.

02:03:05.734 --> 02:03:06.748
<v ->Thank you President Batjer,</v>

02:03:06.748 --> 02:03:07.710
thank you all Commissioners,

02:03:07.710 --> 02:03:09.418
thank you all.

02:03:09.418 --> 02:03:10.836
<v ->Thank you.</v>

02:03:10.836 --> 02:03:12.509
<v ->Thank you.</v>

02:03:12.509 --> 02:03:13.509
<v ->Thank you.</v>