No Moss 3 Landfill Online Library YouTube Archive @VADMME 2023-11-21-Solar Energy Development and Energy Storage Authority Meeting - July 26, 2023

Solar Energy Development and Energy Storage Authority Meeting - July 26, 2023

This is the recording of the virtual meeting of the Solar Energy Development and Energy Storage Authority on July 26, 2023.

View Original: Solar Energy Development and Energy Storage Authority Meeting - July 26, 2023 (Video) | Virginia Energy (Channel) | Virginia Energy (Uploader)

Download/View: Video (.mkv) | Subtitles (.vtt)

^ Back to top of page.

Video Transcript (approximately)

This transcript may contain automatically generated subtitles as generated using YouTube's automatic subtitles feature. They may not be correct. No effort has been made to correct them (so far). These transcripts, whether or not generated, are also used in the site's Search feature. Please review the Search Policy for details about the site features.

WEBVTT
Kind: captions
Language: en

00:00:41.800 --> 00:00:44.510 align:start position:0%
 
okay<00:00:42.800> technical<00:00:43.520> issues<00:00:43.960> can<00:00:44.079> you<00:00:44.160> all<00:00:44.320> hear

00:00:44.510 --> 00:00:44.520 align:start position:0%
okay technical issues can you all hear
 

00:00:44.520 --> 00:00:47.430 align:start position:0%
okay technical issues can you all hear
Us

00:00:47.430 --> 00:00:47.440 align:start position:0%
 
 

00:00:47.440 --> 00:00:51.670 align:start position:0%
 
online<00:00:48.440> okay<00:00:49.079> all<00:00:49.760> right<00:00:50.760> it's<00:00:50.879> all<00:00:51.079> yours

00:00:51.670 --> 00:00:51.680 align:start position:0%
online okay all right it's all yours
 

00:00:51.680 --> 00:00:53.750 align:start position:0%
online okay all right it's all yours
excellent<00:00:52.440> all<00:00:52.600> right<00:00:52.800> well<00:00:53.000> thank<00:00:53.199> you<00:00:53.440> all

00:00:53.750 --> 00:00:53.760 align:start position:0%
excellent all right well thank you all
 

00:00:53.760 --> 00:00:56.029 align:start position:0%
excellent all right well thank you all
for<00:00:54.079> joing<00:00:54.480> us<00:00:54.680> this<00:00:54.800> morning<00:00:55.199> apologies<00:00:55.760> for

00:00:56.029 --> 00:00:56.039 align:start position:0%
for joing us this morning apologies for
 

00:00:56.039 --> 00:00:59.910 align:start position:0%
for joing us this morning apologies for
the<00:00:56.840> slight<00:00:57.280> delay<00:00:58.199> um<00:00:58.680> like<00:00:58.840> to<00:00:59.000> call<00:00:59.359> this<00:00:59.680> me

00:00:59.910 --> 00:00:59.920 align:start position:0%
the slight delay um like to call this me
 

00:00:59.920 --> 00:01:03.750 align:start position:0%
the slight delay um like to call this me
meeting<00:01:00.199> to<00:01:00.879> order<00:01:01.879> um<00:01:02.840> feel<00:01:03.239> like<00:01:03.440> we<00:01:03.519> should

00:01:03.750 --> 00:01:03.760 align:start position:0%
meeting to order um feel like we should
 

00:01:03.760 --> 00:01:05.270 align:start position:0%
meeting to order um feel like we should
probably<00:01:04.040> go<00:01:04.199> around<00:01:04.640> say<00:01:04.879> our<00:01:05.000> names

00:01:05.270 --> 00:01:05.280 align:start position:0%
probably go around say our names
 

00:01:05.280 --> 00:01:08.350 align:start position:0%
probably go around say our names
introduce<00:01:05.799> ourselves<00:01:06.799> and<00:01:07.360> we<00:01:07.520> will<00:01:07.960> ask<00:01:08.200> him

00:01:08.350 --> 00:01:08.360 align:start position:0%
introduce ourselves and we will ask him
 

00:01:08.360 --> 00:01:12.190 align:start position:0%
introduce ourselves and we will ask him
if<00:01:08.479> we<00:01:08.680> have<00:01:09.040> a<00:01:09.560> for<00:01:10.560> U<00:01:10.880> I'm<00:01:11.119> for<00:01:11.360> Sky<00:01:11.720> I'm<00:01:12.000> very

00:01:12.190 --> 00:01:12.200 align:start position:0%
if we have a for U I'm for Sky I'm very
 

00:01:12.200 --> 00:01:14.469 align:start position:0%
if we have a for U I'm for Sky I'm very
happy<00:01:12.400> to<00:01:12.479> be<00:01:12.880> starting<00:01:13.360> out<00:01:13.799> first<00:01:14.080> meeting

00:01:14.469 --> 00:01:14.479 align:start position:0%
happy to be starting out first meeting
 

00:01:14.479 --> 00:01:19.469 align:start position:0%
happy to be starting out first meeting
as<00:01:14.759> chair<00:01:15.759> pa

00:01:19.469 --> 00:01:19.479 align:start position:0%
 
 

00:01:19.479 --> 00:01:23.149 align:start position:0%
 
pa<00:01:20.479> special<00:01:20.840> guest<00:01:21.400> AJ

00:01:23.149 --> 00:01:23.159 align:start position:0%
pa special guest AJ
 

00:01:23.159 --> 00:01:26.630 align:start position:0%
pa special guest AJ
Hall

00:01:26.630 --> 00:01:26.640 align:start position:0%
 
 

00:01:26.640 --> 00:01:30.310 align:start position:0%
 
John<00:01:27.640> no<00:01:27.799> long<00:01:28.119> CEO<00:01:28.720> but<00:01:28.880> I<00:01:28.960> am<00:01:29.240> also<00:01:30.000> chairman

00:01:30.310 --> 00:01:30.320 align:start position:0%
John no long CEO but I am also chairman
 

00:01:30.320 --> 00:01:33.710 align:start position:0%
John no long CEO but I am also chairman
of<00:01:30.439> the<00:01:30.520> board<00:01:30.960> of<00:01:31.159> shine<00:01:31.880> so<00:01:32.360> um<00:01:33.280> Workforce

00:01:33.710 --> 00:01:33.720 align:start position:0%
of the board of shine so um Workforce
 

00:01:33.720 --> 00:01:35.749 align:start position:0%
of the board of shine so um Workforce
Development<00:01:34.200> issue<00:01:34.560> for<00:01:34.759> utility<00:01:35.119> SC<00:01:35.360> solar

00:01:35.749 --> 00:01:35.759 align:start position:0%
Development issue for utility SC solar
 

00:01:35.759 --> 00:01:40.429 align:start position:0%
Development issue for utility SC solar
in<00:01:36.320> Virginia<00:01:37.320> paie<00:01:37.680> Leon<00:01:38.600> um<00:01:39.159> a<00:01:40.159> market

00:01:40.429 --> 00:01:40.439 align:start position:0%
in Virginia paie Leon um a market
 

00:01:40.439 --> 00:01:43.030 align:start position:0%
in Virginia paie Leon um a market
development<00:01:41.040> director<00:01:42.040> re<00:01:42.320> beep<00:01:42.560> attorney<00:01:42.880> at

00:01:43.030 --> 00:01:43.040 align:start position:0%
development director re beep attorney at
 

00:01:43.040 --> 00:01:44.870 align:start position:0%
development director re beep attorney at
Gentry<00:01:43.399> lock<00:01:43.560> and<00:01:43.720> president<00:01:44.040> Gentry<00:01:44.360> lock

00:01:44.870 --> 00:01:44.880 align:start position:0%
Gentry lock and president Gentry lock
 

00:01:44.880 --> 00:01:47.030 align:start position:0%
Gentry lock and president Gentry lock
consultant<00:01:45.880> Ben<00:01:46.079> German<00:01:46.600> Virginia

00:01:47.030 --> 00:01:47.040 align:start position:0%
consultant Ben German Virginia
 

00:01:47.040 --> 00:01:51.069 align:start position:0%
consultant Ben German Virginia
Department<00:01:47.360> of<00:01:47.840> energy<00:01:48.840> mik<00:01:49.079> wsh<00:01:49.640> Sherman<00:01:50.000> and

00:01:51.069 --> 00:01:51.079 align:start position:0%
Department of energy mik wsh Sherman and
 

00:01:51.079 --> 00:01:53.510 align:start position:0%
Department of energy mik wsh Sherman and
Sterling<00:01:52.079> and<00:01:52.280> Ken<00:01:52.600> appear<00:01:53.000> do<00:01:53.159> not<00:01:53.360> have

00:01:53.510 --> 00:01:53.520 align:start position:0%
Sterling and Ken appear do not have
 

00:01:53.520 --> 00:01:55.670 align:start position:0%
Sterling and Ken appear do not have
porum<00:01:53.880> is<00:01:53.960> that<00:01:54.119> correct<00:01:54.560> correct<00:01:55.320> so<00:01:55.520> would

00:01:55.670 --> 00:01:55.680 align:start position:0%
porum is that correct correct so would
 

00:01:55.680 --> 00:01:58.469 align:start position:0%
porum is that correct correct so would
you<00:01:55.880> mind<00:01:56.479> remind<00:01:57.119> the<00:01:57.280> members<00:01:57.880> present<00:01:58.280> and

00:01:58.469 --> 00:01:58.479 align:start position:0%
you mind remind the members present and
 

00:01:58.479 --> 00:02:01.389 align:start position:0%
you mind remind the members present and
folks<00:01:59.000> online<00:01:59.680> what<00:01:59.960> we're<00:02:00.240> able<00:02:00.520> to<00:02:00.759> do<00:02:01.200> and

00:02:01.389 --> 00:02:01.399 align:start position:0%
folks online what we're able to do and
 

00:02:01.399 --> 00:02:04.429 align:start position:0%
folks online what we're able to do and
not<00:02:01.680> do<00:02:02.079> today<00:02:02.479> without<00:02:02.640> a<00:02:02.799> quum<00:02:03.759> we<00:02:03.880> can<00:02:04.119> do

00:02:04.429 --> 00:02:04.439 align:start position:0%
not do today without a quum we can do
 

00:02:04.439 --> 00:02:07.229 align:start position:0%
not do today without a quum we can do
anything<00:02:05.000> you<00:02:05.200> can<00:02:05.360> do<00:02:05.600> anything<00:02:06.079> except<00:02:06.560> vote

00:02:07.229 --> 00:02:07.239 align:start position:0%
anything you can do anything except vote
 

00:02:07.239 --> 00:02:10.990 align:start position:0%
anything you can do anything except vote
on<00:02:08.239> material<00:02:08.679> matters<00:02:09.000> like<00:02:09.200> minutes<00:02:10.000> or

00:02:10.990 --> 00:02:11.000 align:start position:0%
on material matters like minutes or
 

00:02:11.000 --> 00:02:13.070 align:start position:0%
on material matters like minutes or
resolutions<00:02:11.720> or<00:02:11.920> anything<00:02:12.280> like<00:02:12.480> that

00:02:13.070 --> 00:02:13.080 align:start position:0%
resolutions or anything like that
 

00:02:13.080 --> 00:02:15.270 align:start position:0%
resolutions or anything like that
excellent<00:02:13.480> so<00:02:13.680> we<00:02:13.920> still<00:02:14.160> will<00:02:14.280> be<00:02:14.440> able<00:02:14.680> to

00:02:15.270 --> 00:02:15.280 align:start position:0%
excellent so we still will be able to
 

00:02:15.280 --> 00:02:18.509 align:start position:0%
excellent so we still will be able to
take<00:02:15.560> minutes<00:02:16.160> today<00:02:17.000> take<00:02:17.400> testimony<00:02:18.080> and

00:02:18.509 --> 00:02:18.519 align:start position:0%
take minutes today take testimony and
 

00:02:18.519 --> 00:02:20.949 align:start position:0%
take minutes today take testimony and
absolutely<00:02:19.519> discuss<00:02:19.920> future<00:02:20.200> meetings

00:02:20.949 --> 00:02:20.959 align:start position:0%
absolutely discuss future meetings
 

00:02:20.959 --> 00:02:23.710 align:start position:0%
absolutely discuss future meetings
absolutely<00:02:21.560> and<00:02:22.000> are<00:02:22.200> there<00:02:22.360> any<00:02:22.599> members

00:02:23.710 --> 00:02:23.720 align:start position:0%
absolutely and are there any members
 

00:02:23.720 --> 00:02:27.470 align:start position:0%
absolutely and are there any members
online<00:02:24.720> right<00:02:24.920> now<00:02:25.239> I<00:02:25.360> can't<00:02:25.800> read<00:02:26.400> those<00:02:27.400> I

00:02:27.470 --> 00:02:27.480 align:start position:0%
online right now I can't read those I
 

00:02:27.480 --> 00:02:29.350 align:start position:0%
online right now I can't read those I
know<00:02:27.640> a<00:02:27.760> couple<00:02:28.040> folks<00:02:28.280> said<00:02:28.560> they<00:02:28.680> wanted<00:02:29.040> to

00:02:29.350 --> 00:02:29.360 align:start position:0%
know a couple folks said they wanted to
 

00:02:29.360 --> 00:02:35.509 align:start position:0%
know a couple folks said they wanted to
call<00:02:29.599> in

00:02:35.509 --> 00:02:35.519 align:start position:0%
 
 

00:02:35.519 --> 00:02:38.949 align:start position:0%
 
doesn't<00:02:35.879> appear<00:02:36.480> so<00:02:37.360> okay<00:02:38.360> but<00:02:38.560> would<00:02:38.720> like<00:02:38.840> to

00:02:38.949 --> 00:02:38.959 align:start position:0%
doesn't appear so okay but would like to
 

00:02:38.959 --> 00:02:40.350 align:start position:0%
doesn't appear so okay but would like to
remind<00:02:39.280> folks<00:02:39.519> who<00:02:39.680> are<00:02:39.879> joining<00:02:40.200> us

00:02:40.350 --> 00:02:40.360 align:start position:0%
remind folks who are joining us
 

00:02:40.360 --> 00:02:42.149 align:start position:0%
remind folks who are joining us
electronically<00:02:41.040> we<00:02:41.159> will<00:02:41.360> have<00:02:41.560> time<00:02:41.800> for

00:02:42.149 --> 00:02:42.159 align:start position:0%
electronically we will have time for
 

00:02:42.159 --> 00:02:43.630 align:start position:0%
electronically we will have time for
public<00:02:42.480> comments<00:02:42.920> at<00:02:43.080> the<00:02:43.239> close<00:02:43.440> of<00:02:43.560> the

00:02:43.630 --> 00:02:43.640 align:start position:0%
public comments at the close of the
 

00:02:43.640 --> 00:02:46.670 align:start position:0%
public comments at the close of the
meeting<00:02:44.040> so<00:02:44.360> appreciate<00:02:45.360> virally<00:02:46.319> and<00:02:46.560> uh

00:02:46.670 --> 00:02:46.680 align:start position:0%
meeting so appreciate virally and uh
 

00:02:46.680 --> 00:02:48.030 align:start position:0%
meeting so appreciate virally and uh
looking<00:02:46.959> forward<00:02:47.200> to<00:02:47.319> hearing<00:02:47.560> from<00:02:47.720> some<00:02:47.920> of

00:02:48.030 --> 00:02:48.040 align:start position:0%
looking forward to hearing from some of
 

00:02:48.040 --> 00:02:49.470 align:start position:0%
looking forward to hearing from some of
of<00:02:48.120> you<00:02:48.239> all<00:02:48.400> if<00:02:48.480> you'd<00:02:48.640> like<00:02:48.760> to<00:02:48.879> share<00:02:49.159> some

00:02:49.470 --> 00:02:49.480 align:start position:0%
of you all if you'd like to share some
 

00:02:49.480 --> 00:02:52.869 align:start position:0%
of you all if you'd like to share some
thoughts<00:02:49.959> with<00:02:50.159> the<00:02:50.599> authority<00:02:51.599> um<00:02:51.800> we<00:02:51.920> will

00:02:52.869 --> 00:02:52.879 align:start position:0%
thoughts with the authority um we will
 

00:02:52.879 --> 00:02:55.830 align:start position:0%
thoughts with the authority um we will
skip<00:02:53.800> item<00:02:54.120> number<00:02:54.400> two<00:02:54.879> and<00:02:55.080> before<00:02:55.400> we<00:02:55.560> move

00:02:55.830 --> 00:02:55.840 align:start position:0%
skip item number two and before we move
 

00:02:55.840 --> 00:02:59.509 align:start position:0%
skip item number two and before we move
on<00:02:56.120> to<00:02:56.720> uh<00:02:57.000> presentation<00:02:57.640> on<00:02:58.480> grid<00:02:58.959> enhancing

00:02:59.509 --> 00:02:59.519 align:start position:0%
on to uh presentation on grid enhancing
 

00:02:59.519 --> 00:03:01.830 align:start position:0%
on to uh presentation on grid enhancing
Tech<00:02:59.760> Technologies<00:03:00.680> I'd<00:03:00.840> like<00:03:00.959> to<00:03:01.200> add<00:03:01.599> a

00:03:01.830 --> 00:03:01.840 align:start position:0%
Tech Technologies I'd like to add a
 

00:03:01.840 --> 00:03:05.229 align:start position:0%
Tech Technologies I'd like to add a
couple<00:03:02.400> items<00:03:03.000> to<00:03:03.480> the<00:03:03.720> agenda<00:03:04.720> uh<00:03:04.920> first

00:03:05.229 --> 00:03:05.239 align:start position:0%
couple items to the agenda uh first
 

00:03:05.239 --> 00:03:08.030 align:start position:0%
couple items to the agenda uh first
would<00:03:05.440> like<00:03:05.599> to<00:03:05.920> add<00:03:06.599> uh<00:03:07.080> a<00:03:07.280> discussion<00:03:07.840> of

00:03:08.030 --> 00:03:08.040 align:start position:0%
would like to add uh a discussion of
 

00:03:08.040 --> 00:03:10.949 align:start position:0%
would like to add uh a discussion of
future<00:03:08.319> meeting<00:03:08.640> dates<00:03:09.440> and<00:03:10.319> um<00:03:10.599> hopefully

00:03:10.949 --> 00:03:10.959 align:start position:0%
future meeting dates and um hopefully
 

00:03:10.959 --> 00:03:13.350 align:start position:0%
future meeting dates and um hopefully
get<00:03:11.159> a<00:03:11.319> schedule<00:03:11.720> for<00:03:11.920> 2024<00:03:12.720> in<00:03:12.840> the<00:03:12.959> books

00:03:13.350 --> 00:03:13.360 align:start position:0%
get a schedule for 2024 in the books
 

00:03:13.360 --> 00:03:16.110 align:start position:0%
get a schedule for 2024 in the books
with<00:03:13.519> some<00:03:13.799> venues<00:03:14.319> locked<00:03:14.720> down<00:03:15.560> for

00:03:16.110 --> 00:03:16.120 align:start position:0%
with some venues locked down for
 

00:03:16.120 --> 00:03:19.110 align:start position:0%
with some venues locked down for
everyone's<00:03:17.000> benefit<00:03:17.519> in<00:03:17.680> the<00:03:17.879> long<00:03:18.120> term<00:03:18.799> and

00:03:19.110 --> 00:03:19.120 align:start position:0%
everyone's benefit in the long term and
 

00:03:19.120 --> 00:03:22.070 align:start position:0%
everyone's benefit in the long term and
we<00:03:19.440> also<00:03:19.920> like<00:03:20.159> to<00:03:20.640> discuss<00:03:21.560> well<00:03:21.799> actually

00:03:22.070 --> 00:03:22.080 align:start position:0%
we also like to discuss well actually
 

00:03:22.080 --> 00:03:24.110 align:start position:0%
we also like to discuss well actually
just<00:03:22.239> have<00:03:22.360> an<00:03:22.480> open<00:03:22.760> discussion<00:03:23.440> in<00:03:23.640> case

00:03:24.110 --> 00:03:24.120 align:start position:0%
just have an open discussion in case
 

00:03:24.120 --> 00:03:25.670 align:start position:0%
just have an open discussion in case
folks<00:03:24.400> on<00:03:24.519> the<00:03:24.640> authority<00:03:25.000> want<00:03:25.159> to<00:03:25.280> share

00:03:25.670 --> 00:03:25.680 align:start position:0%
folks on the authority want to share
 

00:03:25.680 --> 00:03:28.670 align:start position:0%
folks on the authority want to share
thoughts<00:03:26.080> on<00:03:26.360> activities<00:03:26.959> so<00:03:27.280> far<00:03:28.040> and<00:03:28.319> uh<00:03:28.439> any

00:03:28.670 --> 00:03:28.680 align:start position:0%
thoughts on activities so far and uh any
 

00:03:28.680 --> 00:03:31.830 align:start position:0%
thoughts on activities so far and uh any
other<00:03:28.959> matters<00:03:29.799> so<00:03:30.640> um<00:03:30.959> do<00:03:31.120> I<00:03:31.200> need<00:03:31.360> a<00:03:31.519> motion

00:03:31.830 --> 00:03:31.840 align:start position:0%
other matters so um do I need a motion
 

00:03:31.840 --> 00:03:34.630 align:start position:0%
other matters so um do I need a motion
to<00:03:32.040> do<00:03:32.200> so<00:03:32.640> Ken<00:03:32.959> I<00:03:33.040> don't<00:03:33.239> think<00:03:33.439> so<00:03:34.000> uh<00:03:34.159> one

00:03:34.630 --> 00:03:34.640 align:start position:0%
to do so Ken I don't think so uh one
 

00:03:34.640 --> 00:03:37.789 align:start position:0%
to do so Ken I don't think so uh one
note<00:03:35.120> though<00:03:35.400> on<00:03:36.000> meeting<00:03:36.480> venues<00:03:37.480> if<00:03:37.599> we're

00:03:37.789 --> 00:03:37.799 align:start position:0%
note though on meeting venues if we're
 

00:03:37.799 --> 00:03:39.589 align:start position:0%
note though on meeting venues if we're
going<00:03:37.879> to<00:03:38.040> continue<00:03:38.360> to<00:03:38.519> use<00:03:38.760> the<00:03:38.920> libraries

00:03:39.589 --> 00:03:39.599 align:start position:0%
going to continue to use the libraries
 

00:03:39.599 --> 00:03:41.190 align:start position:0%
going to continue to use the libraries
which<00:03:39.720> is<00:03:40.080> what<00:03:40.239> we've<00:03:40.480> historically<00:03:40.959> done

00:03:41.190 --> 00:03:41.200 align:start position:0%
which is what we've historically done
 

00:03:41.200 --> 00:03:43.229 align:start position:0%
which is what we've historically done
you<00:03:41.360> can't<00:03:41.640> book<00:03:41.920> them<00:03:42.080> more<00:03:42.239> than<00:03:42.439> 30<00:03:42.799> days<00:03:43.000> in

00:03:43.229 --> 00:03:43.239 align:start position:0%
you can't book them more than 30 days in
 

00:03:43.239 --> 00:03:44.670 align:start position:0%
you can't book them more than 30 days in
advance<00:03:43.640> so<00:03:43.840> that<00:03:44.000> becomes<00:03:44.239> a<00:03:44.319> little

00:03:44.670 --> 00:03:44.680 align:start position:0%
advance so that becomes a little
 

00:03:44.680 --> 00:03:47.190 align:start position:0%
advance so that becomes a little
problematic<00:03:45.200> so<00:03:45.400> unless<00:03:45.720> I<00:03:45.840> can<00:03:46.000> find<00:03:47.000> a

00:03:47.190 --> 00:03:47.200 align:start position:0%
problematic so unless I can find a
 

00:03:47.200 --> 00:03:49.670 align:start position:0%
problematic so unless I can find a
location<00:03:47.920> that<00:03:48.080> we<00:03:48.200> can<00:03:48.640> use<00:03:49.080> consistently

00:03:49.670 --> 00:03:49.680 align:start position:0%
location that we can use consistently
 

00:03:49.680 --> 00:03:52.149 align:start position:0%
location that we can use consistently
and<00:03:50.319> regularly<00:03:51.319> um<00:03:51.480> we<00:03:51.560> can<00:03:51.680> lock<00:03:51.879> in<00:03:52.040> the

00:03:52.149 --> 00:03:52.159 align:start position:0%
and regularly um we can lock in the
 

00:03:52.159 --> 00:03:54.270 align:start position:0%
and regularly um we can lock in the
dates<00:03:52.680> but<00:03:53.120> the<00:03:53.400> locations<00:03:53.959> might<00:03:54.120> be<00:03:54.200> a

00:03:54.270 --> 00:03:54.280 align:start position:0%
dates but the locations might be a
 

00:03:54.280 --> 00:03:57.670 align:start position:0%
dates but the locations might be a
little<00:03:54.519> more<00:03:55.159> problematic<00:03:56.480> excellent<00:03:57.480> well

00:03:57.670 --> 00:03:57.680 align:start position:0%
little more problematic excellent well
 

00:03:57.680 --> 00:04:00.270 align:start position:0%
little more problematic excellent well
thank<00:03:57.799> you<00:03:58.000> Ken<00:03:58.439> I<00:03:58.599> will<00:03:58.840> Reserve<00:03:59.360> time<00:04:00.040> the

00:04:00.270 --> 00:04:00.280 align:start position:0%
thank you Ken I will Reserve time the
 

00:04:00.280 --> 00:04:03.190 align:start position:0%
thank you Ken I will Reserve time the
close<00:04:00.680> for<00:04:00.959> those<00:04:01.200> two<00:04:01.680> items<00:04:02.680> um<00:04:02.879> without

00:04:03.190 --> 00:04:03.200 align:start position:0%
close for those two items um without
 

00:04:03.200 --> 00:04:05.949 align:start position:0%
close for those two items um without
further<00:04:03.519> Ado<00:04:04.200> I'm<00:04:04.519> happy<00:04:04.760> to<00:04:04.959> introduce<00:04:05.519> AJ

00:04:05.949 --> 00:04:05.959 align:start position:0%
further Ado I'm happy to introduce AJ
 

00:04:05.959 --> 00:04:08.149 align:start position:0%
further Ado I'm happy to introduce AJ
Hall<00:04:06.640> I'd<00:04:06.840> like<00:04:06.920> to<00:04:07.040> thank<00:04:07.200> hen<00:04:07.640> for<00:04:07.799> making

00:04:08.149 --> 00:04:08.159 align:start position:0%
Hall I'd like to thank hen for making
 

00:04:08.159 --> 00:04:10.630 align:start position:0%
Hall I'd like to thank hen for making
this<00:04:08.480> happen<00:04:09.120> uh<00:04:09.319> this<00:04:09.480> first<00:04:09.760> suggestion<00:04:10.360> at

00:04:10.630 --> 00:04:10.640 align:start position:0%
this happen uh this first suggestion at
 

00:04:10.640 --> 00:04:13.110 align:start position:0%
this happen uh this first suggestion at
the<00:04:11.000> most<00:04:11.239> recent<00:04:11.560> meeting<00:04:12.519> uh<00:04:12.640> to<00:04:12.840> have<00:04:13.000> a

00:04:13.110 --> 00:04:13.120 align:start position:0%
the most recent meeting uh to have a
 

00:04:13.120 --> 00:04:15.509 align:start position:0%
the most recent meeting uh to have a
grid<00:04:13.360> enhancing<00:04:13.920> Technologies<00:04:14.640> presentation

00:04:15.509 --> 00:04:15.519 align:start position:0%
grid enhancing Technologies presentation
 

00:04:15.519 --> 00:04:17.430 align:start position:0%
grid enhancing Technologies presentation
so<00:04:15.840> AJ<00:04:16.160> thank<00:04:16.280> you<00:04:16.359> for<00:04:16.519> making<00:04:16.720> the<00:04:16.840> trip<00:04:17.120> down

00:04:17.430 --> 00:04:17.440 align:start position:0%
so AJ thank you for making the trip down
 

00:04:17.440 --> 00:04:19.990 align:start position:0%
so AJ thank you for making the trip down
from<00:04:17.759> Indiana<00:04:18.560> thanks<00:04:18.919> and<00:04:19.040> then<00:04:19.199> down<00:04:19.400> 95

00:04:19.990 --> 00:04:20.000 align:start position:0%
from Indiana thanks and then down 95
 

00:04:20.000 --> 00:04:21.909 align:start position:0%
from Indiana thanks and then down 95
today<00:04:20.840> uh<00:04:21.000> but<00:04:21.199> excited<00:04:21.519> to<00:04:21.600> hear<00:04:21.759> what<00:04:21.840> you

00:04:21.909 --> 00:04:21.919 align:start position:0%
today uh but excited to hear what you
 

00:04:21.919 --> 00:04:24.510 align:start position:0%
today uh but excited to hear what you
have<00:04:22.040> to<00:04:22.120> share<00:04:22.880> yeah<00:04:23.160> oh<00:04:23.440> great<00:04:23.800> thank<00:04:23.960> you

00:04:24.510 --> 00:04:24.520 align:start position:0%
have to share yeah oh great thank you
 

00:04:24.520 --> 00:04:27.110 align:start position:0%
have to share yeah oh great thank you
love<00:04:24.880> you<00:04:25.880> presentation<00:04:26.400> and<00:04:26.639> I'll<00:04:26.840> need<00:04:26.960> to

00:04:27.110 --> 00:04:27.120 align:start position:0%
love you presentation and I'll need to
 

00:04:27.120 --> 00:04:28.590 align:start position:0%
love you presentation and I'll need to
share<00:04:27.600> my

00:04:28.590 --> 00:04:28.600 align:start position:0%
share my
 

00:04:28.600 --> 00:04:40.790 align:start position:0%
share my
screen

00:04:40.790 --> 00:04:40.800 align:start position:0%
 
 

00:04:40.800 --> 00:04:43.110 align:start position:0%
 
okay<00:04:41.800> okay<00:04:41.960> I<00:04:42.039> want<00:04:42.160> to<00:04:42.280> confirm<00:04:42.680> for<00:04:42.840> everyone

00:04:43.110 --> 00:04:43.120 align:start position:0%
okay okay I want to confirm for everyone
 

00:04:43.120 --> 00:04:46.510 align:start position:0%
okay okay I want to confirm for everyone
online<00:04:43.720> can<00:04:43.919> everyone<00:04:44.600> see<00:04:45.600> screen<00:04:46.039> it<00:04:46.199> looks

00:04:46.510 --> 00:04:46.520 align:start position:0%
online can everyone see screen it looks
 

00:04:46.520 --> 00:04:49.550 align:start position:0%
online can everyone see screen it looks
like<00:04:47.039> yep<00:04:47.680> okay<00:04:48.280> yeah

00:04:49.550 --> 00:04:49.560 align:start position:0%
like yep okay yeah
 

00:04:49.560 --> 00:04:53.029 align:start position:0%
like yep okay yeah
perfect<00:04:50.560> okay<00:04:51.080> so<00:04:52.080> um<00:04:52.360> being<00:04:52.639> that<00:04:52.800> this<00:04:52.880> is

00:04:53.029 --> 00:04:53.039 align:start position:0%
perfect okay so um being that this is
 

00:04:53.039 --> 00:04:55.909 align:start position:0%
perfect okay so um being that this is
the<00:04:53.120> only<00:04:53.360> presentation<00:04:53.960> today<00:04:54.919> um<00:04:55.400> you<00:04:55.560> know

00:04:55.909 --> 00:04:55.919 align:start position:0%
the only presentation today um you know
 

00:04:55.919 --> 00:04:58.310 align:start position:0%
the only presentation today um you know
I'm<00:04:56.160> happy<00:04:56.400> to<00:04:56.520> take<00:04:56.840> questions<00:04:57.759> during<00:04:58.120> the

00:04:58.310 --> 00:04:58.320 align:start position:0%
I'm happy to take questions during the
 

00:04:58.320 --> 00:05:00.230 align:start position:0%
I'm happy to take questions during the
presentation<00:04:59.240> um<00:04:59.400> and<00:04:59.759> there's<00:04:59.960> something

00:05:00.230 --> 00:05:00.240 align:start position:0%
presentation um and there's something
 

00:05:00.240 --> 00:05:01.510 align:start position:0%
presentation um and there's something
interesting<00:05:00.639> that<00:05:00.800> comes<00:05:01.000> up<00:05:01.160> and<00:05:01.280> someone

00:05:01.510 --> 00:05:01.520 align:start position:0%
interesting that comes up and someone
 

00:05:01.520 --> 00:05:03.870 align:start position:0%
interesting that comes up and someone
wants<00:05:01.680> to<00:05:01.800> just<00:05:01.960> raise<00:05:02.199> your<00:05:02.400> hand<00:05:02.880> or

00:05:03.870 --> 00:05:03.880 align:start position:0%
wants to just raise your hand or
 

00:05:03.880 --> 00:05:05.990 align:start position:0%
wants to just raise your hand or
interrupt<00:05:04.440> happy<00:05:04.680> to<00:05:04.840> do<00:05:05.120> that<00:05:05.639> and<00:05:05.720> then<00:05:05.840> I'll

00:05:05.990 --> 00:05:06.000 align:start position:0%
interrupt happy to do that and then I'll
 

00:05:06.000 --> 00:05:09.990 align:start position:0%
interrupt happy to do that and then I'll
try<00:05:06.199> to<00:05:06.720> pause<00:05:07.720> uh<00:05:07.960> through<00:05:08.639> Midway<00:05:09.160> through<00:05:09.880> U

00:05:09.990 --> 00:05:10.000 align:start position:0%
try to pause uh through Midway through U
 

00:05:10.000 --> 00:05:11.710 align:start position:0%
try to pause uh through Midway through U
to<00:05:10.160> take<00:05:10.479> questions<00:05:10.880> and<00:05:11.160> of<00:05:11.280> course<00:05:11.440> do

00:05:11.710 --> 00:05:11.720 align:start position:0%
to take questions and of course do
 

00:05:11.720 --> 00:05:14.710 align:start position:0%
to take questions and of course do
questions<00:05:12.160> at<00:05:12.320> the<00:05:12.759> end<00:05:13.759> but<00:05:13.960> anyway<00:05:14.240> so<00:05:14.479> as

00:05:14.710 --> 00:05:14.720 align:start position:0%
questions at the end but anyway so as
 

00:05:14.720 --> 00:05:16.870 align:start position:0%
questions at the end but anyway so as
Skyler<00:05:15.240> introduced<00:05:15.759> my<00:05:15.880> name<00:05:15.960> is<00:05:16.080> AJ<00:05:16.440> Paul<00:05:16.759> I'm

00:05:16.870 --> 00:05:16.880 align:start position:0%
Skyler introduced my name is AJ Paul I'm
 

00:05:16.880 --> 00:05:19.870 align:start position:0%
Skyler introduced my name is AJ Paul I'm
a<00:05:17.000> portfolio<00:05:17.520> management<00:05:17.960> director<00:05:18.520> at<00:05:18.880> AES

00:05:19.870 --> 00:05:19.880 align:start position:0%
a portfolio management director at AES
 

00:05:19.880 --> 00:05:21.550 align:start position:0%
a portfolio management director at AES
and<00:05:20.080> this<00:05:20.280> presentation<00:05:20.919> is<00:05:21.080> on<00:05:21.360> grid

00:05:21.550 --> 00:05:21.560 align:start position:0%
and this presentation is on grid
 

00:05:21.560 --> 00:05:23.629 align:start position:0%
and this presentation is on grid
enhancing<00:05:22.000> Technologies<00:05:22.600> and<00:05:22.759> how<00:05:22.960> AF<00:05:23.400> is

00:05:23.629 --> 00:05:23.639 align:start position:0%
enhancing Technologies and how AF is
 

00:05:23.639 --> 00:05:27.230 align:start position:0%
enhancing Technologies and how AF is
exploring<00:05:24.319> a<00:05:24.800> suite<00:05:25.800> of<00:05:26.680> flexible

00:05:27.230 --> 00:05:27.240 align:start position:0%
exploring a suite of flexible
 

00:05:27.240 --> 00:05:29.790 align:start position:0%
exploring a suite of flexible
technologies<00:05:27.880> that<00:05:28.000> we<00:05:28.120> think<00:05:28.240> can<00:05:28.479> unlock

00:05:29.790 --> 00:05:29.800 align:start position:0%
technologies that we think can unlock
 

00:05:29.800 --> 00:05:32.150 align:start position:0%
technologies that we think can unlock
transmission<00:05:30.440> capacity<00:05:31.400> or<00:05:31.639> the<00:05:31.759> energy

00:05:32.150 --> 00:05:32.160 align:start position:0%
transmission capacity or the energy
 

00:05:32.160 --> 00:05:34.550 align:start position:0%
transmission capacity or the energy
Transit

00:05:34.550 --> 00:05:34.560 align:start position:0%
Transit
 

00:05:34.560 --> 00:05:36.790 align:start position:0%
Transit
transition<00:05:35.560> okay<00:05:35.680> so<00:05:35.919> first<00:05:36.199> a<00:05:36.319> little<00:05:36.520> bit

00:05:36.790 --> 00:05:36.800 align:start position:0%
transition okay so first a little bit
 

00:05:36.800 --> 00:05:37.790 align:start position:0%
transition okay so first a little bit
about

00:05:37.790 --> 00:05:37.800 align:start position:0%
about
 

00:05:37.800 --> 00:05:40.990 align:start position:0%
about
as<00:05:38.800> so<00:05:39.160> first<00:05:39.840> headquartered<00:05:40.280> in

00:05:40.990 --> 00:05:41.000 align:start position:0%
as so first headquartered in
 

00:05:41.000 --> 00:05:43.309 align:start position:0%
as so first headquartered in
Virginia<00:05:42.000> uh<00:05:42.160> so<00:05:42.440> you<00:05:42.560> know<00:05:42.759> it<00:05:42.840> was<00:05:43.000> about<00:05:43.199> an

00:05:43.309 --> 00:05:43.319 align:start position:0%
Virginia uh so you know it was about an
 

00:05:43.319 --> 00:05:46.510 align:start position:0%
Virginia uh so you know it was about an
hour<00:05:43.520> down<00:05:43.720> 95<00:05:44.160> to<00:05:44.280> get<00:05:44.520> here<00:05:44.880> this<00:05:45.360> morning<00:05:46.360> um

00:05:46.510 --> 00:05:46.520 align:start position:0%
hour down 95 to get here this morning um
 

00:05:46.520 --> 00:05:48.870 align:start position:0%
hour down 95 to get here this morning um
we're<00:05:46.720> a<00:05:46.840> global<00:05:47.120> Energy<00:05:47.520> company<00:05:48.479> and<00:05:48.680> what's

00:05:48.870 --> 00:05:48.880 align:start position:0%
we're a global Energy company and what's
 

00:05:48.880 --> 00:05:51.309 align:start position:0%
we're a global Energy company and what's
unique<00:05:49.160> about<00:05:49.400> ases<00:05:49.840> is<00:05:50.039> we<00:05:50.360> not<00:05:50.560> only<00:05:50.880> have

00:05:51.309 --> 00:05:51.319 align:start position:0%
unique about ases is we not only have
 

00:05:51.319 --> 00:05:53.790 align:start position:0%
unique about ases is we not only have
you<00:05:51.400> know<00:05:51.520> mostly<00:05:51.960> generation<00:05:52.479> so<00:05:52.960> you<00:05:53.039> know

00:05:53.790 --> 00:05:53.800 align:start position:0%
you know mostly generation so you know
 

00:05:53.800 --> 00:05:57.189 align:start position:0%
you know mostly generation so you know
32<00:05:54.800> uh<00:05:55.080> gws<00:05:55.560> in<00:05:55.720> operation<00:05:56.199> in<00:05:56.360> a<00:05:56.560> pipeline<00:05:57.000> of

00:05:57.189 --> 00:05:57.199 align:start position:0%
32 uh gws in operation in a pipeline of
 

00:05:57.199 --> 00:06:00.070 align:start position:0%
32 uh gws in operation in a pipeline of
another<00:05:57.919> 5.4<00:05:58.800> under<00:05:59.080> construction

00:06:00.070 --> 00:06:00.080 align:start position:0%
another 5.4 under construction
 

00:06:00.080 --> 00:06:02.870 align:start position:0%
another 5.4 under construction
but<00:06:00.199> we<00:06:00.319> also<00:06:00.479> have<00:06:01.120> utilities<00:06:02.120> so<00:06:02.280> we<00:06:02.360> can<00:06:02.520> see

00:06:02.870 --> 00:06:02.880 align:start position:0%
but we also have utilities so we can see
 

00:06:02.880 --> 00:06:05.629 align:start position:0%
but we also have utilities so we can see
both<00:06:03.080> sides<00:06:03.280> of<00:06:03.400> the<00:06:03.759> energy<00:06:04.440> transition<00:06:05.440> we

00:06:05.629 --> 00:06:05.639 align:start position:0%
both sides of the energy transition we
 

00:06:05.639 --> 00:06:07.270 align:start position:0%
both sides of the energy transition we
have<00:06:05.880> two<00:06:06.120> utilities<00:06:06.520> that<00:06:06.639> serve<00:06:06.840> a<00:06:06.960> million

00:06:07.270 --> 00:06:07.280 align:start position:0%
have two utilities that serve a million
 

00:06:07.280 --> 00:06:10.189 align:start position:0%
have two utilities that serve a million
customers<00:06:07.680> in<00:06:08.160> Ohio<00:06:09.160> and<00:06:09.280> then<00:06:09.520> serve<00:06:09.840> most<00:06:10.039> of

00:06:10.189 --> 00:06:10.199 align:start position:0%
customers in Ohio and then serve most of
 

00:06:10.199 --> 00:06:11.830 align:start position:0%
customers in Ohio and then serve most of
the<00:06:10.319> country<00:06:10.560> of<00:06:10.720> El<00:06:10.960> Salvador<00:06:11.479> with<00:06:11.599> another

00:06:11.830 --> 00:06:11.840 align:start position:0%
the country of El Salvador with another
 

00:06:11.840 --> 00:06:16.909 align:start position:0%
the country of El Salvador with another
four<00:06:12.199> utilities<00:06:12.639> and<00:06:12.840> another<00:06:13.080> 1.5

00:06:16.909 --> 00:06:16.919 align:start position:0%
 
 

00:06:16.919 --> 00:06:19.110 align:start position:0%
 
customers<00:06:17.919> okay<00:06:18.080> so<00:06:18.240> jumping<00:06:18.560> into<00:06:18.840> the

00:06:19.110 --> 00:06:19.120 align:start position:0%
customers okay so jumping into the
 

00:06:19.120 --> 00:06:21.790 align:start position:0%
customers okay so jumping into the
presentation<00:06:20.120> what<00:06:20.240> are<00:06:20.360> the<00:06:20.479> key

00:06:21.790 --> 00:06:21.800 align:start position:0%
presentation what are the key
 

00:06:21.800 --> 00:06:25.189 align:start position:0%
presentation what are the key
takeaways<00:06:23.039> so<00:06:24.039> energy<00:06:24.440> demand<00:06:24.880> and

00:06:25.189 --> 00:06:25.199 align:start position:0%
takeaways so energy demand and
 

00:06:25.199 --> 00:06:27.670 align:start position:0%
takeaways so energy demand and
especially<00:06:26.039> it<00:06:26.160> was<00:06:26.520> really<00:06:27.280> uh<00:06:27.479> really

00:06:27.670 --> 00:06:27.680 align:start position:0%
especially it was really uh really
 

00:06:27.680 --> 00:06:29.990 align:start position:0%
especially it was really uh really
appreciate<00:06:28.039> this<00:06:28.240> opportunity<00:06:28.680> so<00:06:29.479> got<00:06:29.680> me

00:06:29.990 --> 00:06:30.000 align:start position:0%
appreciate this opportunity so got me
 

00:06:30.000 --> 00:06:33.830 align:start position:0%
appreciate this opportunity so got me
the<00:06:30.240> opportunity<00:06:30.840> to<00:06:31.840> look<00:06:32.120> into<00:06:32.840> the

00:06:33.830 --> 00:06:33.840 align:start position:0%
the opportunity to look into the
 

00:06:33.840 --> 00:06:35.550 align:start position:0%
the opportunity to look into the
interesting<00:06:34.240> low<00:06:34.560> grow<00:06:34.800> story<00:06:35.080> here<00:06:35.199> in

00:06:35.550 --> 00:06:35.560 align:start position:0%
interesting low grow story here in
 

00:06:35.560 --> 00:06:37.909 align:start position:0%
interesting low grow story here in
Virginia<00:06:36.560> um<00:06:36.919> but<00:06:37.120> demand<00:06:37.440> is<00:06:37.560> growing

00:06:37.909 --> 00:06:37.919 align:start position:0%
Virginia um but demand is growing
 

00:06:37.919 --> 00:06:40.629 align:start position:0%
Virginia um but demand is growing
rapidly<00:06:38.680> and<00:06:39.000> Supply<00:06:39.400> is<00:06:39.599> queuing<00:06:40.039> up<00:06:40.280> to<00:06:40.400> meet

00:06:40.629 --> 00:06:40.639 align:start position:0%
rapidly and Supply is queuing up to meet
 

00:06:40.639 --> 00:06:42.710 align:start position:0%
rapidly and Supply is queuing up to meet
that<00:06:40.759> demand<00:06:41.080> renewable<00:06:41.599> Supply<00:06:42.400> so<00:06:42.520> we'll

00:06:42.710 --> 00:06:42.720 align:start position:0%
that demand renewable Supply so we'll
 

00:06:42.720 --> 00:06:45.629 align:start position:0%
that demand renewable Supply so we'll
talk<00:06:42.919> about<00:06:43.240> that<00:06:43.759> but<00:06:43.919> really<00:06:44.639> transmission

00:06:45.629 --> 00:06:45.639 align:start position:0%
talk about that but really transmission
 

00:06:45.639 --> 00:06:49.390 align:start position:0%
talk about that but really transmission
compe<00:06:46.120> city<00:06:46.560> is<00:06:46.680> a<00:06:46.960> major<00:06:47.599> bottleneck<00:06:48.599> in<00:06:48.919> inte

00:06:49.390 --> 00:06:49.400 align:start position:0%
compe city is a major bottleneck in inte
 

00:06:49.400 --> 00:06:52.830 align:start position:0%
compe city is a major bottleneck in inte
in<00:06:49.560> delivering<00:06:50.199> that<00:06:51.039> uh<00:06:51.240> supply<00:06:52.199> to<00:06:52.680> the

00:06:52.830 --> 00:06:52.840 align:start position:0%
in delivering that uh supply to the
 

00:06:52.840 --> 00:06:56.950 align:start position:0%
in delivering that uh supply to the
growing<00:06:53.639> demand<00:06:54.639> and<00:06:54.840> so<00:06:55.680> asc's<00:06:56.680> great

00:06:56.950 --> 00:06:56.960 align:start position:0%
growing demand and so asc's great
 

00:06:56.960 --> 00:06:59.589 align:start position:0%
growing demand and so asc's great
enhancing<00:06:57.440> Technologies<00:06:58.120> or<00:06:58.520> gets<00:06:59.240> as<00:06:59.400> as<00:06:59.479> is

00:06:59.589 --> 00:06:59.599 align:start position:0%
enhancing Technologies or gets as as is
 

00:06:59.599 --> 00:07:02.350 align:start position:0%
enhancing Technologies or gets as as is
know<00:06:59.759> in<00:06:59.840> the<00:07:00.000> industry<00:07:01.000> um<00:07:01.280> as<00:07:01.440> a<00:07:01.800> solution<00:07:02.160> to

00:07:02.350 --> 00:07:02.360 align:start position:0%
know in the industry um as a solution to
 

00:07:02.360 --> 00:07:05.150 align:start position:0%
know in the industry um as a solution to
unlock<00:07:02.720> this<00:07:02.879> transition<00:07:03.759> uh<00:07:03.919> this

00:07:05.150 --> 00:07:05.160 align:start position:0%
unlock this transition uh this
 

00:07:05.160 --> 00:07:07.070 align:start position:0%
unlock this transition uh this
transmission<00:07:06.160> and<00:07:06.280> then<00:07:06.560> we'll<00:07:06.759> look<00:07:07.000> a

00:07:07.070 --> 00:07:07.080 align:start position:0%
transmission and then we'll look a
 

00:07:07.080 --> 00:07:08.790 align:start position:0%
transmission and then we'll look a
little<00:07:07.319> bit<00:07:07.520> further<00:07:07.879> into<00:07:08.560> some

00:07:08.790 --> 00:07:08.800 align:start position:0%
little bit further into some
 

00:07:08.800 --> 00:07:10.589 align:start position:0%
little bit further into some
applications<00:07:09.280> for<00:07:09.520> dynamic<00:07:09.879> line<00:07:10.120> rating<00:07:10.440> or

00:07:10.589 --> 00:07:10.599 align:start position:0%
applications for dynamic line rating or
 

00:07:10.599 --> 00:07:13.070 align:start position:0%
applications for dynamic line rating or
drr<00:07:11.599> and<00:07:11.720> then<00:07:11.879> storage<00:07:12.240> is

00:07:13.070 --> 00:07:13.080 align:start position:0%
drr and then storage is
 

00:07:13.080 --> 00:07:15.629 align:start position:0%
drr and then storage is
transmission<00:07:14.080> um<00:07:14.240> and<00:07:14.360> then<00:07:14.560> finally<00:07:15.360> finish

00:07:15.629 --> 00:07:15.639 align:start position:0%
transmission um and then finally finish
 

00:07:15.639 --> 00:07:18.270 align:start position:0%
transmission um and then finally finish
with<00:07:15.800> some<00:07:15.960> recommendations<00:07:16.680> on<00:07:17.280> how

00:07:18.270 --> 00:07:18.280 align:start position:0%
with some recommendations on how
 

00:07:18.280 --> 00:07:20.230 align:start position:0%
with some recommendations on how
integrating<00:07:18.840> prens<00:07:19.520> Technologies<00:07:20.039> can

00:07:20.230 --> 00:07:20.240 align:start position:0%
integrating prens Technologies can
 

00:07:20.240 --> 00:07:25.029 align:start position:0%
integrating prens Technologies can
position<00:07:20.800> Virginia<00:07:21.199> as<00:07:21.280> a<00:07:21.400> lader<00:07:21.639> in<00:07:21.840> energy

00:07:25.029 --> 00:07:25.039 align:start position:0%
 
 

00:07:25.039 --> 00:07:28.510 align:start position:0%
 
transition<00:07:26.039> okay<00:07:26.560> so<00:07:26.800> this<00:07:27.080> demand<00:07:27.520> story

00:07:28.510 --> 00:07:28.520 align:start position:0%
transition okay so this demand story
 

00:07:28.520 --> 00:07:30.550 align:start position:0%
transition okay so this demand story
this<00:07:28.599> is<00:07:28.759> really<00:07:28.960> interesting<00:07:29.440> so<00:07:29.840> you<00:07:30.000> know

00:07:30.550 --> 00:07:30.560 align:start position:0%
this is really interesting so you know
 

00:07:30.560 --> 00:07:32.749 align:start position:0%
this is really interesting so you know
and<00:07:30.759> I'm<00:07:30.919> sure<00:07:31.440> as<00:07:31.879> many<00:07:32.120> folks<00:07:32.280> in<00:07:32.400> Virginia

00:07:32.749 --> 00:07:32.759 align:start position:0%
and I'm sure as many folks in Virginia
 

00:07:32.759 --> 00:07:34.710 align:start position:0%
and I'm sure as many folks in Virginia
are<00:07:32.879> well<00:07:33.039> aware<00:07:33.440> the<00:07:33.639> the<00:07:33.800> data<00:07:34.039> center<00:07:34.319> Hub

00:07:34.710 --> 00:07:34.720 align:start position:0%
are well aware the the data center Hub
 

00:07:34.720 --> 00:07:38.629 align:start position:0%
are well aware the the data center Hub
in<00:07:34.879> M<00:07:35.199> County<00:07:35.479> and<00:07:35.919> data<00:07:36.160> center<00:07:36.440> alley<00:07:37.280> um<00:07:38.080> pjm

00:07:38.629 --> 00:07:38.639 align:start position:0%
in M County and data center alley um pjm
 

00:07:38.639 --> 00:07:41.350 align:start position:0%
in M County and data center alley um pjm
recently<00:07:39.000> revised<00:07:39.360> its<00:07:39.919> forecast<00:07:40.919> uh<00:07:41.280> you

00:07:41.350 --> 00:07:41.360 align:start position:0%
recently revised its forecast uh you
 

00:07:41.360 --> 00:07:44.550 align:start position:0%
recently revised its forecast uh you
know<00:07:41.440> the<00:07:41.560> grid<00:07:41.800> operator<00:07:42.560> for<00:07:43.280> Virginia<00:07:44.280> um

00:07:44.550 --> 00:07:44.560 align:start position:0%
know the grid operator for Virginia um
 

00:07:44.560 --> 00:07:47.629 align:start position:0%
know the grid operator for Virginia um
for<00:07:44.759> the<00:07:44.919> Dominion<00:07:45.520> area<00:07:46.039> a<00:07:46.240> four<00:07:46.560> to<00:07:46.800> 5%<00:07:47.319> low

00:07:47.629 --> 00:07:47.639 align:start position:0%
for the Dominion area a four to 5% low
 

00:07:47.639 --> 00:07:50.589 align:start position:0%
for the Dominion area a four to 5% low
growth<00:07:48.280> over<00:07:48.520> the<00:07:48.720> next<00:07:49.560> 15

00:07:50.589 --> 00:07:50.599 align:start position:0%
growth over the next 15
 

00:07:50.599 --> 00:07:54.790 align:start position:0%
growth over the next 15
years<00:07:51.599> and<00:07:52.440> this<00:07:52.560> was<00:07:52.680> in<00:07:52.919> January<00:07:53.720> and<00:07:54.280> and

00:07:54.790 --> 00:07:54.800 align:start position:0%
years and this was in January and and
 

00:07:54.800 --> 00:07:57.309 align:start position:0%
years and this was in January and and
most<00:07:55.000> of<00:07:55.199> it<00:07:55.520> is<00:07:55.720> driven<00:07:56.120> by<00:07:56.319> data<00:07:56.560> centers<00:07:57.159> so

00:07:57.309 --> 00:07:57.319 align:start position:0%
most of it is driven by data centers so
 

00:07:57.319 --> 00:07:59.790 align:start position:0%
most of it is driven by data centers so
you<00:07:57.400> can<00:07:57.560> see<00:07:57.840> there<00:07:58.080> you<00:07:58.199> know<00:07:58.680> was<00:07:58.800> a<00:07:59.000> peak<00:07:59.440> of

00:07:59.790 --> 00:07:59.800 align:start position:0%
you can see there you know was a peak of
 

00:07:59.800 --> 00:08:01.309 align:start position:0%
you can see there you know was a peak of
almost<00:08:00.039> three<00:08:00.319> gigs<00:08:00.680> last<00:08:00.879> year<00:08:01.159> they're

00:08:01.309 --> 00:08:01.319 align:start position:0%
almost three gigs last year they're
 

00:08:01.319 --> 00:08:03.110 align:start position:0%
almost three gigs last year they're
looking<00:08:01.639> to<00:08:01.960> almost<00:08:02.199> double<00:08:02.520> that<00:08:02.680> Peak<00:08:02.960> by

00:08:03.110 --> 00:08:03.120 align:start position:0%
looking to almost double that Peak by
 

00:08:03.120 --> 00:08:06.990 align:start position:0%
looking to almost double that Peak by
2030<00:08:03.879> for<00:08:04.039> data<00:08:04.240> center<00:08:04.960> load<00:08:05.960> and<00:08:06.080> this<00:08:06.199> is

00:08:06.990 --> 00:08:07.000 align:start position:0%
2030 for data center load and this is
 

00:08:07.000 --> 00:08:10.230 align:start position:0%
2030 for data center load and this is
before<00:08:08.000> AI<00:08:08.560> really<00:08:08.800> rolled<00:08:09.159> out<00:08:09.680> in<00:08:10.080> in

00:08:10.230 --> 00:08:10.240 align:start position:0%
before AI really rolled out in in
 

00:08:10.240 --> 00:08:13.149 align:start position:0%
before AI really rolled out in in
Earnest<00:08:11.000> right<00:08:11.199> before<00:08:11.560> J<00:08:11.879> GPT<00:08:12.560> and<00:08:12.680> all<00:08:12.960> those

00:08:13.149 --> 00:08:13.159 align:start position:0%
Earnest right before J GPT and all those
 

00:08:13.159 --> 00:08:14.510 align:start position:0%
Earnest right before J GPT and all those
things<00:08:13.360> that<00:08:13.479> are<00:08:13.599> going<00:08:13.680> to<00:08:13.800> drive<00:08:14.199> data

00:08:14.510 --> 00:08:14.520 align:start position:0%
things that are going to drive data
 

00:08:14.520 --> 00:08:17.350 align:start position:0%
things that are going to drive data
center<00:08:14.960> load<00:08:15.960> um<00:08:16.440> so<00:08:16.680> I<00:08:16.759> could<00:08:16.879> see<00:08:17.120> that

00:08:17.350 --> 00:08:17.360 align:start position:0%
center load um so I could see that
 

00:08:17.360 --> 00:08:20.029 align:start position:0%
center load um so I could see that
dotted<00:08:17.759> line<00:08:18.120> there<00:08:18.240> on<00:08:18.440> the<00:08:18.639> right<00:08:18.919> hand<00:08:19.240> side

00:08:20.029 --> 00:08:20.039 align:start position:0%
dotted line there on the right hand side
 

00:08:20.039 --> 00:08:21.950 align:start position:0%
dotted line there on the right hand side
going<00:08:20.360> up<00:08:20.680> even

00:08:21.950 --> 00:08:21.960 align:start position:0%
going up even
 

00:08:21.960 --> 00:08:24.710 align:start position:0%
going up even
more<00:08:22.960> and<00:08:23.120> then<00:08:23.440> in<00:08:23.520> the<00:08:23.680> out<00:08:23.960> years<00:08:24.240> you<00:08:24.520> after

00:08:24.710 --> 00:08:24.720 align:start position:0%
more and then in the out years you after
 

00:08:24.720 --> 00:08:27.629 align:start position:0%
more and then in the out years you after
2030<00:08:25.360> we're<00:08:25.479> seeing<00:08:25.879> and<00:08:26.120> just<00:08:27.039> say<00:08:27.360> similar

00:08:27.629 --> 00:08:27.639 align:start position:0%
2030 we're seeing and just say similar
 

00:08:27.639 --> 00:08:29.270 align:start position:0%
2030 we're seeing and just say similar
Trends<00:08:27.919> across<00:08:28.159> the<00:08:28.280> country<00:08:28.879> more

00:08:29.270 --> 00:08:29.280 align:start position:0%
Trends across the country more
 

00:08:29.280 --> 00:08:31.189 align:start position:0%
Trends across the country more
electrification<00:08:30.000> from<00:08:30.520> uh<00:08:30.639> transportation

00:08:31.189 --> 00:08:31.199 align:start position:0%
electrification from uh transportation
 

00:08:31.199 --> 00:08:34.070 align:start position:0%
electrification from uh transportation
to<00:08:31.400> EVs<00:08:31.960> and<00:08:32.719> and<00:08:32.880> then<00:08:33.039> you<00:08:33.159> know<00:08:33.599> heat<00:08:33.839> pumps

00:08:34.070 --> 00:08:34.080 align:start position:0%
to EVs and and then you know heat pumps
 

00:08:34.080 --> 00:08:36.550 align:start position:0%
to EVs and and then you know heat pumps
and<00:08:34.279> other<00:08:34.959> electrification<00:08:35.959> of<00:08:36.200> of<00:08:36.360> Home

00:08:36.550 --> 00:08:36.560 align:start position:0%
and other electrification of of Home
 

00:08:36.560 --> 00:08:38.829 align:start position:0%
and other electrification of of Home
devices<00:08:36.959> really<00:08:37.279> kind<00:08:37.399> of<00:08:37.800> tell<00:08:38.080> the<00:08:38.240> story

00:08:38.829 --> 00:08:38.839 align:start position:0%
devices really kind of tell the story
 

00:08:38.839 --> 00:08:43.550 align:start position:0%
devices really kind of tell the story
later<00:08:39.120> on<00:08:39.399> in<00:08:39.560> pjf<00:08:40.080> load

00:08:43.550 --> 00:08:43.560 align:start position:0%
 
 

00:08:43.560 --> 00:08:46.630 align:start position:0%
 
forecast<00:08:44.560> so<00:08:44.839> Supply<00:08:45.519> is<00:08:45.680> queuing<00:08:46.040> up<00:08:46.240> to<00:08:46.399> meet

00:08:46.630 --> 00:08:46.640 align:start position:0%
forecast so Supply is queuing up to meet
 

00:08:46.640 --> 00:08:48.750 align:start position:0%
forecast so Supply is queuing up to meet
that<00:08:46.839> demand<00:08:47.320> you<00:08:47.440> can<00:08:47.600> see<00:08:47.880> the<00:08:48.120> cumulative

00:08:48.750 --> 00:08:48.760 align:start position:0%
that demand you can see the cumulative
 

00:08:48.760 --> 00:08:50.910 align:start position:0%
that demand you can see the cumulative
growth<00:08:49.279> of<00:08:49.440> the<00:08:49.600> pjm

00:08:50.910 --> 00:08:50.920 align:start position:0%
growth of the pjm
 

00:08:50.920 --> 00:08:53.509 align:start position:0%
growth of the pjm
interconnection<00:08:51.920> queue<00:08:52.480> here<00:08:53.240> and<00:08:53.360> it's

00:08:53.509 --> 00:08:53.519 align:start position:0%
interconnection queue here and it's
 

00:08:53.519 --> 00:08:55.350 align:start position:0%
interconnection queue here and it's
mostly<00:08:53.839> renewable<00:08:54.560> you<00:08:54.640> can<00:08:54.760> see<00:08:54.959> Virginia

00:08:55.350 --> 00:08:55.360 align:start position:0%
mostly renewable you can see Virginia
 

00:08:55.360 --> 00:08:58.150 align:start position:0%
mostly renewable you can see Virginia
has<00:08:55.519> 90<00:08:55.880> gaw<00:08:56.880> um<00:08:57.200> which<00:08:57.360> is<00:08:57.680> you<00:08:57.760> know<00:08:57.959> almost

00:08:58.150 --> 00:08:58.160 align:start position:0%
has 90 gaw um which is you know almost
 

00:08:58.160 --> 00:09:00.389 align:start position:0%
has 90 gaw um which is you know almost
90%<00:08:58.800> renewable

00:09:00.389 --> 00:09:00.399 align:start position:0%
90% renewable
 

00:09:00.399 --> 00:09:03.269 align:start position:0%
90% renewable
um<00:09:00.920> and<00:09:01.160> the<00:09:02.079> major<00:09:02.560> growth<00:09:02.920> that<00:09:03.040> we're

00:09:03.269 --> 00:09:03.279 align:start position:0%
um and the major growth that we're
 

00:09:03.279 --> 00:09:06.430 align:start position:0%
um and the major growth that we're
seeing<00:09:03.880> in<00:09:04.200> solar<00:09:05.079> solar<00:09:05.760> you<00:09:05.839> know<00:09:06.040> hybrids

00:09:06.430 --> 00:09:06.440 align:start position:0%
seeing in solar solar you know hybrids
 

00:09:06.440 --> 00:09:08.910 align:start position:0%
seeing in solar solar you know hybrids
solar<00:09:06.800> storage<00:09:07.320> and<00:09:07.480> then<00:09:08.120> finally<00:09:08.399> standin

00:09:08.910 --> 00:09:08.920 align:start position:0%
solar storage and then finally standin
 

00:09:08.920 --> 00:09:11.710 align:start position:0%
solar storage and then finally standin
storage<00:09:09.200> at<00:09:09.399> 50<00:09:09.720> times<00:09:09.959> increase<00:09:10.480> from<00:09:10.720> 2018

00:09:11.710 --> 00:09:11.720 align:start position:0%
storage at 50 times increase from 2018
 

00:09:11.720 --> 00:09:14.590 align:start position:0%
storage at 50 times increase from 2018
in<00:09:11.880> the<00:09:12.519> que<00:09:13.519> which<00:09:13.640> is<00:09:13.920> the<00:09:14.040> storage<00:09:14.399> is<00:09:14.480> in

00:09:14.590 --> 00:09:14.600 align:start position:0%
in the que which is the storage is in
 

00:09:14.600 --> 00:09:16.030 align:start position:0%
in the que which is the storage is in
the<00:09:14.720> purple<00:09:15.000> bars<00:09:15.360> there<00:09:15.519> it's<00:09:15.680> kind<00:09:15.760> of<00:09:15.880> hard

00:09:16.030 --> 00:09:16.040 align:start position:0%
the purple bars there it's kind of hard
 

00:09:16.040 --> 00:09:19.030 align:start position:0%
the purple bars there it's kind of hard
to<00:09:16.200> see<00:09:16.399> on<00:09:16.600> that<00:09:17.440> graph<00:09:18.040> yeah<00:09:18.240> so<00:09:18.600> you<00:09:18.760> got

00:09:19.030 --> 00:09:19.040 align:start position:0%
to see on that graph yeah so you got
 

00:09:19.040 --> 00:09:22.030 align:start position:0%
to see on that graph yeah so you got
2013<00:09:19.560> and<00:09:19.800> 2022<00:09:20.800> yes<00:09:21.200> I<00:09:21.279> would<00:09:21.480> assume<00:09:21.839> that

00:09:22.030 --> 00:09:22.040 align:start position:0%
2013 and 2022 yes I would assume that
 

00:09:22.040 --> 00:09:24.430 align:start position:0%
2013 and 2022 yes I would assume that
going<00:09:22.279> back<00:09:22.440> to<00:09:22.640> like<00:09:22.800> 2019<00:09:23.519> and<00:09:23.680> earlier<00:09:24.120> is

00:09:24.430 --> 00:09:24.440 align:start position:0%
going back to like 2019 and earlier is
 

00:09:24.440 --> 00:09:26.750 align:start position:0%
going back to like 2019 and earlier is
actual<00:09:25.440> not<00:09:25.680> just<00:09:25.800> what's<00:09:25.959> in<00:09:26.079> the<00:09:26.279> queue<00:09:26.560> it's

00:09:26.750 --> 00:09:26.760 align:start position:0%
actual not just what's in the queue it's
 

00:09:26.760 --> 00:09:29.310 align:start position:0%
actual not just what's in the queue it's
what's<00:09:26.959> been<00:09:27.680> installed<00:09:28.480> is<00:09:28.600> that<00:09:28.839> correct

00:09:29.310 --> 00:09:29.320 align:start position:0%
what's been installed is that correct
 

00:09:29.320 --> 00:09:31.670 align:start position:0%
what's been installed is that correct
was<00:09:29.519> that<00:09:29.959> this<00:09:30.120> is<00:09:30.560> this<00:09:30.680> is<00:09:30.959> capacity<00:09:31.399> in<00:09:31.519> the

00:09:31.670 --> 00:09:31.680 align:start position:0%
was that this is this is capacity in the
 

00:09:31.680 --> 00:09:34.710 align:start position:0%
was that this is this is capacity in the
queue<00:09:32.200> only<00:09:33.120> so<00:09:33.360> this<00:09:33.480> is<00:09:33.720> not<00:09:34.240> this<00:09:34.360> is<00:09:34.480> not

00:09:34.710 --> 00:09:34.720 align:start position:0%
queue only so this is not this is not
 

00:09:34.720 --> 00:09:37.470 align:start position:0%
queue only so this is not this is not
looking<00:09:35.079> at<00:09:35.399> install<00:09:35.959> base<00:09:36.519> in<00:09:36.720> this<00:09:36.920> graph

00:09:37.470 --> 00:09:37.480 align:start position:0%
looking at install base in this graph
 

00:09:37.480 --> 00:09:40.389 align:start position:0%
looking at install base in this graph
this<00:09:37.600> is<00:09:37.800> just<00:09:38.200> oh<00:09:38.399> some<00:09:38.760> some<00:09:38.920> of<00:09:39.040> it<00:09:39.240> is

00:09:40.389 --> 00:09:40.399 align:start position:0%
this is just oh some some of it is
 

00:09:40.399 --> 00:09:44.150 align:start position:0%
this is just oh some some of it is
installed<00:09:41.399> I<00:09:41.440> mean<00:09:41.600> going<00:09:41.880> back<00:09:42.000> to<00:09:42.240> like<00:09:43.040> 2015

00:09:44.150 --> 00:09:44.160 align:start position:0%
installed I mean going back to like 2015
 

00:09:44.160 --> 00:09:46.750 align:start position:0%
installed I mean going back to like 2015
2016<00:09:45.160> you're<00:09:45.279> going<00:09:45.399> to<00:09:45.600> take<00:09:45.920> actual<00:09:46.320> data

00:09:46.750 --> 00:09:46.760 align:start position:0%
2016 you're going to take actual data
 

00:09:46.760 --> 00:09:48.630 align:start position:0%
2016 you're going to take actual data
right<00:09:47.200> that<00:09:47.279> was<00:09:47.440> installed<00:09:47.880> that<00:09:48.000> point<00:09:48.399> yeah

00:09:48.630 --> 00:09:48.640 align:start position:0%
right that was installed that point yeah
 

00:09:48.640 --> 00:09:50.590 align:start position:0%
right that was installed that point yeah
yeah<00:09:48.800> this<00:09:48.920> is<00:09:49.120> this<00:09:49.320> comes<00:09:49.680> from<00:09:50.160> Florence

00:09:50.590 --> 00:09:50.600 align:start position:0%
yeah this is this comes from Florence
 

00:09:50.600 --> 00:09:53.150 align:start position:0%
yeah this is this comes from Florence
Berkeley<00:09:51.320> laboratory<00:09:51.920> to<00:09:52.200> the<00:09:52.440> study<00:09:52.920> on

00:09:53.150 --> 00:09:53.160 align:start position:0%
Berkeley laboratory to the study on
 

00:09:53.160 --> 00:09:54.550 align:start position:0%
Berkeley laboratory to the study on
interconnection<00:09:53.680> cues<00:09:54.000> it's<00:09:54.160> been<00:09:54.320> pretty

00:09:54.550 --> 00:09:54.560 align:start position:0%
interconnection cues it's been pretty
 

00:09:54.560 --> 00:09:56.829 align:start position:0%
interconnection cues it's been pretty
popular<00:09:54.839> in<00:09:54.959> the<00:09:55.160> industry<00:09:55.600> this<00:09:55.800> year<00:09:56.560> um<00:09:56.680> so

00:09:56.829 --> 00:09:56.839 align:start position:0%
popular in the industry this year um so
 

00:09:56.839 --> 00:09:58.630 align:start position:0%
popular in the industry this year um so
this<00:09:57.000> comes<00:09:57.200> from<00:09:57.399> their<00:09:57.600> database<00:09:58.240> so<00:09:58.480> yes

00:09:58.630 --> 00:09:58.640 align:start position:0%
this comes from their database so yes
 

00:09:58.640 --> 00:09:59.870 align:start position:0%
this comes from their database so yes
some<00:09:58.760> of<00:09:58.880> the

00:09:59.870 --> 00:09:59.880 align:start position:0%
some of the
 

00:09:59.880 --> 00:10:02.590 align:start position:0%
some of the
2022<00:10:00.880> uh<00:10:01.160> or<00:10:01.360> 2013<00:10:02.000> projects<00:10:02.360> that<00:10:02.480> are

00:10:02.590 --> 00:10:02.600 align:start position:0%
2022 uh or 2013 projects that are
 

00:10:02.600 --> 00:10:05.470 align:start position:0%
2022 uh or 2013 projects that are
showing<00:10:03.040> far<00:10:03.320> left<00:10:03.680> are<00:10:04.000> in<00:10:04.279> service<00:10:05.279> but

00:10:05.470 --> 00:10:05.480 align:start position:0%
showing far left are in service but
 

00:10:05.480 --> 00:10:07.509 align:start position:0%
showing far left are in service but
likely<00:10:05.839> actually<00:10:06.040> the<00:10:06.120> ones<00:10:06.240> in<00:10:06.360> 2019<00:10:06.800> are

00:10:07.509 --> 00:10:07.519 align:start position:0%
likely actually the ones in 2019 are
 

00:10:07.519 --> 00:10:09.710 align:start position:0%
likely actually the ones in 2019 are
not<00:10:08.519> now<00:10:08.720> a<00:10:08.800> lot<00:10:08.920> of<00:10:09.079> the<00:10:09.200> things<00:10:09.360> that<00:10:09.480> are<00:10:09.600> in

00:10:09.710 --> 00:10:09.720 align:start position:0%
not now a lot of the things that are in
 

00:10:09.720 --> 00:10:11.350 align:start position:0%
not now a lot of the things that are in
the<00:10:09.839> queue<00:10:10.160> though<00:10:10.320> and<00:10:10.480> this<00:10:10.600> is<00:10:10.959> comes<00:10:11.200> from

00:10:11.350 --> 00:10:11.360 align:start position:0%
the queue though and this is comes from
 

00:10:11.360 --> 00:10:13.829 align:start position:0%
the queue though and this is comes from
our<00:10:11.640> past<00:10:11.880> annual<00:10:12.279> reports<00:10:12.839> I<00:10:13.360> I'll<00:10:13.480> do<00:10:13.640> a

00:10:13.829 --> 00:10:13.839 align:start position:0%
our past annual reports I I'll do a
 

00:10:13.839 --> 00:10:16.110 align:start position:0%
our past annual reports I I'll do a
synopsis<00:10:14.399> of<00:10:14.640> what<00:10:15.160> has<00:10:15.360> dropped<00:10:15.720> out<00:10:15.839> of<00:10:16.000> the

00:10:16.110 --> 00:10:16.120 align:start position:0%
synopsis of what has dropped out of the
 

00:10:16.120 --> 00:10:17.829 align:start position:0%
synopsis of what has dropped out of the
queue<00:10:16.399> and<00:10:16.640> quite<00:10:16.839> a<00:10:16.959> bit<00:10:17.200> of<00:10:17.360> what's<00:10:17.560> in<00:10:17.680> the

00:10:17.829 --> 00:10:17.839 align:start position:0%
queue and quite a bit of what's in the
 

00:10:17.839 --> 00:10:20.269 align:start position:0%
queue and quite a bit of what's in the
queue<00:10:18.560> eventually<00:10:18.959> drops<00:10:19.320> out<00:10:19.480> of<00:10:19.600> the<00:10:19.720> queue

00:10:20.269 --> 00:10:20.279 align:start position:0%
queue eventually drops out of the queue
 

00:10:20.279 --> 00:10:22.910 align:start position:0%
queue eventually drops out of the queue
that's<00:10:20.519> so<00:10:20.920> what<00:10:21.040> is<00:10:21.279> the<00:10:22.240> the<00:10:22.399> likelihood

00:10:22.910 --> 00:10:22.920 align:start position:0%
that's so what is the the likelihood
 

00:10:22.920 --> 00:10:25.590 align:start position:0%
that's so what is the the likelihood
that<00:10:23.200> this<00:10:23.360> will<00:10:23.880> actually<00:10:24.200> come<00:10:24.399> to<00:10:24.600> fruition

00:10:25.590 --> 00:10:25.600 align:start position:0%
that this will actually come to fruition
 

00:10:25.600 --> 00:10:28.150 align:start position:0%
that this will actually come to fruition
to<00:10:25.800> that<00:10:26.000> level<00:10:26.600> great<00:10:27.000> question<00:10:27.839> thank<00:10:28.000> you

00:10:28.150 --> 00:10:28.160 align:start position:0%
to that level great question thank you
 

00:10:28.160 --> 00:10:31.069 align:start position:0%
to that level great question thank you
for<00:10:28.440> Le

00:10:31.069 --> 00:10:31.079 align:start position:0%
 
 

00:10:31.079 --> 00:10:34.670 align:start position:0%
 
slide<00:10:32.079> I<00:10:32.200> get<00:10:32.680> so<00:10:33.399> so<00:10:33.760> yeah<00:10:33.920> it's<00:10:34.079> taking<00:10:34.440> five

00:10:34.670 --> 00:10:34.680 align:start position:0%
slide I get so so yeah it's taking five
 

00:10:34.680 --> 00:10:36.350 align:start position:0%
slide I get so so yeah it's taking five
years<00:10:35.000> right<00:10:35.120> to<00:10:35.240> get<00:10:35.360> through<00:10:35.480> the<00:10:35.600> pjm<00:10:36.079> Q

00:10:36.350 --> 00:10:36.360 align:start position:0%
years right to get through the pjm Q
 

00:10:36.360 --> 00:10:38.069 align:start position:0%
years right to get through the pjm Q
right<00:10:36.519> now<00:10:36.880> yeah<00:10:37.200> and<00:10:37.360> in<00:10:37.519> fact<00:10:37.639> the<00:10:37.800> Q<00:10:38.000> has

00:10:38.069 --> 00:10:38.079 align:start position:0%
right now yeah and in fact the Q has
 

00:10:38.079 --> 00:10:40.150 align:start position:0%
right now yeah and in fact the Q has
been<00:10:38.240> paused<00:10:38.760> right<00:10:38.880> for<00:10:39.079> over<00:10:39.279> a<00:10:39.440> year<00:10:40.040> as

00:10:40.150 --> 00:10:40.160 align:start position:0%
been paused right for over a year as
 

00:10:40.160 --> 00:10:41.710 align:start position:0%
been paused right for over a year as
they<00:10:40.279> work<00:10:40.480> on<00:10:40.639> Q<00:10:40.880> reforms<00:10:41.360> and<00:10:41.519> if<00:10:41.600> you

00:10:41.710 --> 00:10:41.720 align:start position:0%
they work on Q reforms and if you
 

00:10:41.720 --> 00:10:43.030 align:start position:0%
they work on Q reforms and if you
submitted<00:10:42.079> a<00:10:42.240> project

00:10:43.030 --> 00:10:43.040 align:start position:0%
submitted a project
 

00:10:43.040 --> 00:10:45.750 align:start position:0%
submitted a project
today<00:10:44.040> it<00:10:44.160> wouldn't<00:10:44.399> even<00:10:44.560> be<00:10:44.839> looked<00:10:45.240> at<00:10:45.519> or

00:10:45.750 --> 00:10:45.760 align:start position:0%
today it wouldn't even be looked at or
 

00:10:45.760 --> 00:10:47.790 align:start position:0%
today it wouldn't even be looked at or
studied<00:10:46.079> by<00:10:46.200> djm<00:10:46.600> until

00:10:47.790 --> 00:10:47.800 align:start position:0%
studied by djm until
 

00:10:47.800 --> 00:10:50.870 align:start position:0%
studied by djm until
2026<00:10:48.800> yeah<00:10:49.600> yeah<00:10:49.760> so<00:10:49.920> it's<00:10:50.120> taking<00:10:50.560> you<00:10:50.639> know

00:10:50.870 --> 00:10:50.880 align:start position:0%
2026 yeah yeah so it's taking you know
 

00:10:50.880 --> 00:10:52.590 align:start position:0%
2026 yeah yeah so it's taking you know
five<00:10:51.079> years<00:10:51.320> it<00:10:51.399> used<00:10:51.560> to<00:10:51.680> take<00:10:51.880> only<00:10:52.160> three

00:10:52.590 --> 00:10:52.600 align:start position:0%
five years it used to take only three
 

00:10:52.600 --> 00:10:54.750 align:start position:0%
five years it used to take only three
back<00:10:52.720> in<00:10:52.839> 2019<00:10:53.320> you<00:10:53.399> get<00:10:53.519> through<00:10:53.680> the<00:10:53.800> queue

00:10:54.750 --> 00:10:54.760 align:start position:0%
back in 2019 you get through the queue
 

00:10:54.760 --> 00:10:56.710 align:start position:0%
back in 2019 you get through the queue
and<00:10:54.920> it's<00:10:55.160> costing<00:10:55.839> these<00:10:56.000> projects<00:10:56.519> why<00:10:56.600> are

00:10:56.710 --> 00:10:56.720 align:start position:0%
and it's costing these projects why are
 

00:10:56.720 --> 00:10:59.030 align:start position:0%
and it's costing these projects why are
they<00:10:56.839> dropping<00:10:57.200> now<00:10:58.000> well<00:10:58.600> you<00:10:58.720> know<00:10:58.880> going

00:10:59.030 --> 00:10:59.040 align:start position:0%
they dropping now well you know going
 

00:10:59.040 --> 00:11:01.269 align:start position:0%
they dropping now well you know going
going<00:10:59.200> back<00:10:59.320> to<00:10:59.399> the<00:10:59.519> transmission<00:11:00.279> capacity

00:11:01.269 --> 00:11:01.279 align:start position:0%
going back to the transmission capacity
 

00:11:01.279 --> 00:11:03.430 align:start position:0%
going back to the transmission capacity
there's<00:11:01.519> not<00:11:01.720> the<00:11:01.920> capacity<00:11:02.320> to<00:11:02.519> connect

00:11:03.430 --> 00:11:03.440 align:start position:0%
there's not the capacity to connect
 

00:11:03.440 --> 00:11:05.750 align:start position:0%
there's not the capacity to connect
these<00:11:03.680> projects<00:11:04.240> so<00:11:04.600> the<00:11:04.880> network<00:11:05.320> upgrade

00:11:05.750 --> 00:11:05.760 align:start position:0%
these projects so the network upgrade
 

00:11:05.760 --> 00:11:07.750 align:start position:0%
these projects so the network upgrade
cost<00:11:05.959> or<00:11:06.120> the<00:11:06.320> cost<00:11:07.000> that<00:11:07.079> the<00:11:07.200> property<00:11:07.519> pays

00:11:07.750 --> 00:11:07.760 align:start position:0%
cost or the cost that the property pays
 

00:11:07.760 --> 00:11:11.069 align:start position:0%
cost or the cost that the property pays
not<00:11:08.000> just<00:11:08.160> to<00:11:08.560> you<00:11:08.680> know<00:11:09.440> the<00:11:09.639> ti<00:11:09.959> line<00:11:10.279> to<00:11:10.680> the

00:11:11.069 --> 00:11:11.079 align:start position:0%
not just to you know the ti line to the
 

00:11:11.079 --> 00:11:13.310 align:start position:0%
not just to you know the ti line to the
transmission<00:11:11.639> but<00:11:11.800> the<00:11:11.959> actual<00:11:12.760> effect<00:11:13.120> of

00:11:13.310 --> 00:11:13.320 align:start position:0%
transmission but the actual effect of
 

00:11:13.320 --> 00:11:15.030 align:start position:0%
transmission but the actual effect of
that<00:11:13.519> generation<00:11:13.959> on<00:11:14.079> the<00:11:14.200> system<00:11:14.480> or<00:11:14.680> network

00:11:15.030 --> 00:11:15.040 align:start position:0%
that generation on the system or network
 

00:11:15.040 --> 00:11:18.430 align:start position:0%
that generation on the system or network
upgrade<00:11:15.440> cost<00:11:16.279> they've<00:11:16.639> ballooned<00:11:17.160> from<00:11:17.560> $29

00:11:18.430 --> 00:11:18.440 align:start position:0%
upgrade cost they've ballooned from $29
 

00:11:18.440 --> 00:11:22.310 align:start position:0%
upgrade cost they've ballooned from $29
a<00:11:18.600> kilowatt<00:11:19.079> in<00:11:19.360> 2019<00:11:19.959> up<00:11:20.120> to<00:11:20.720> 240<00:11:21.720> today<00:11:22.200> and

00:11:22.310 --> 00:11:22.320 align:start position:0%
a kilowatt in 2019 up to 240 today and
 

00:11:22.320 --> 00:11:24.910 align:start position:0%
a kilowatt in 2019 up to 240 today and
that's<00:11:22.480> on<00:11:22.720> average<00:11:23.480> that's<00:11:24.000> active<00:11:24.480> projects

00:11:24.910 --> 00:11:24.920 align:start position:0%
that's on average that's active projects
 

00:11:24.920 --> 00:11:27.470 align:start position:0%
that's on average that's active projects
in<00:11:25.160> the<00:11:25.680> the<00:11:26.160> queue<00:11:26.399> in<00:11:26.519> the<00:11:26.680> previous<00:11:26.959> slide

00:11:27.470 --> 00:11:27.480 align:start position:0%
in the the queue in the previous slide
 

00:11:27.480 --> 00:11:30.230 align:start position:0%
in the the queue in the previous slide
that's<00:11:27.680> the<00:11:27.880> average<00:11:28.200> Network<00:11:28.560> up<00:11:29.160> Coss<00:11:29.639> W<00:11:30.079> but

00:11:30.230 --> 00:11:30.240 align:start position:0%
that's the average Network up Coss W but
 

00:11:30.240 --> 00:11:32.670 align:start position:0%
that's the average Network up Coss W but
of<00:11:30.399> course<00:11:30.680> they<00:11:30.800> can<00:11:31.800> drastically<00:11:32.320> vary<00:11:32.560> a

00:11:32.670 --> 00:11:32.680 align:start position:0%
of course they can drastically vary a
 

00:11:32.680 --> 00:11:33.670 align:start position:0%
of course they can drastically vary a
project<00:11:32.920> that<00:11:33.040> goes<00:11:33.200> through<00:11:33.399> might<00:11:33.519> only

00:11:33.670 --> 00:11:33.680 align:start position:0%
project that goes through might only
 

00:11:33.680 --> 00:11:35.750 align:start position:0%
project that goes through might only
have<00:11:33.800> $5<00:11:34.320> per<00:11:34.519> kilowatt<00:11:35.000> depending<00:11:35.279> on

00:11:35.750 --> 00:11:35.760 align:start position:0%
have $5 per kilowatt depending on
 

00:11:35.760 --> 00:11:38.389 align:start position:0%
have $5 per kilowatt depending on
location<00:11:36.760> um<00:11:37.000> the<00:11:37.279> average<00:11:37.560> for<00:11:37.800> storage<00:11:38.240> for

00:11:38.389 --> 00:11:38.399 align:start position:0%
location um the average for storage for
 

00:11:38.399 --> 00:11:39.430 align:start position:0%
location um the average for storage for
instance<00:11:38.680> is

00:11:39.430 --> 00:11:39.440 align:start position:0%
instance is
 

00:11:39.440 --> 00:11:44.790 align:start position:0%
instance is
$336<00:11:40.440> per<00:11:40.639> KW<00:11:41.600> so<00:11:41.760> it's<00:11:42.160> becoming<00:11:43.160> five<00:11:43.760> 10%<00:11:44.639> of

00:11:44.790 --> 00:11:44.800 align:start position:0%
$336 per KW so it's becoming five 10% of
 

00:11:44.800 --> 00:11:49.069 align:start position:0%
$336 per KW so it's becoming five 10% of
the<00:11:45.079> capital<00:11:45.560> cost<00:11:46.399> for<00:11:46.680> these<00:11:47.440> projects<00:11:48.440> uh

00:11:49.069 --> 00:11:49.079 align:start position:0%
the capital cost for these projects uh
 

00:11:49.079 --> 00:11:51.350 align:start position:0%
the capital cost for these projects uh
just<00:11:49.320> the<00:11:49.480> interconnection

00:11:51.350 --> 00:11:51.360 align:start position:0%
just the interconnection
 

00:11:51.360 --> 00:11:54.470 align:start position:0%
just the interconnection
process<00:11:52.360> and<00:11:52.480> then<00:11:52.720> yeah<00:11:52.880> so<00:11:53.240> why<00:11:53.560> why<00:11:54.320> that's

00:11:54.470 --> 00:11:54.480 align:start position:0%
process and then yeah so why why that's
 

00:11:54.480 --> 00:11:56.990 align:start position:0%
process and then yeah so why why that's
leading<00:11:55.000> you<00:11:55.240> to<00:11:55.480> complete<00:11:56.480> um<00:11:56.680> you<00:11:56.760> know<00:11:56.920> if

00:11:56.990 --> 00:11:57.000 align:start position:0%
leading you to complete um you know if
 

00:11:57.000 --> 00:11:59.310 align:start position:0%
leading you to complete um you know if
you<00:11:57.200> look<00:11:57.399> at<00:11:57.720> just<00:11:58.279> the<00:11:58.480> data<00:11:58.720> from<00:11:59.040> Lawrence

00:11:59.310 --> 00:11:59.320 align:start position:0%
you look at just the data from Lawrence
 

00:11:59.320 --> 00:12:02.949 align:start position:0%
you look at just the data from Lawrence
Berkley<00:12:00.279> 15%<00:12:01.120> of<00:12:01.399> projects<00:12:01.880> requested<00:12:02.800> in

00:12:02.949 --> 00:12:02.959 align:start position:0%
Berkley 15% of projects requested in
 

00:12:02.959 --> 00:12:06.470 align:start position:0%
Berkley 15% of projects requested in
2017<00:12:03.680> have<00:12:03.839> been<00:12:04.360> completed<00:12:05.360> and<00:12:05.680> back<00:12:06.079> in<00:12:06.360> if

00:12:06.470 --> 00:12:06.480 align:start position:0%
2017 have been completed and back in if
 

00:12:06.480 --> 00:12:08.990 align:start position:0%
2017 have been completed and back in if
you<00:12:06.600> had<00:12:06.839> requested<00:12:07.160> a<00:12:07.279> project<00:12:07.519> back<00:12:07.680> in<00:12:08.000> 2012

00:12:08.990 --> 00:12:09.000 align:start position:0%
you had requested a project back in 2012
 

00:12:09.000 --> 00:12:11.470 align:start position:0%
you had requested a project back in 2012
30%<00:12:09.600> chance<00:12:09.839> of<00:12:09.959> completion<00:12:10.399> so<00:12:10.880> less<00:12:11.120> are

00:12:11.470 --> 00:12:11.480 align:start position:0%
30% chance of completion so less are
 

00:12:11.480 --> 00:12:15.230 align:start position:0%
30% chance of completion so less are
completing<00:12:12.480> if<00:12:12.600> you<00:12:12.760> look<00:12:12.920> at<00:12:13.279> pjm's<00:12:14.279> data

00:12:15.230 --> 00:12:15.240 align:start position:0%
completing if you look at pjm's data
 

00:12:15.240 --> 00:12:16.750 align:start position:0%
completing if you look at pjm's data
they're<00:12:15.519> discounting<00:12:16.040> their<00:12:16.240> queue<00:12:16.519> all<00:12:16.680> the

00:12:16.750 --> 00:12:16.760 align:start position:0%
they're discounting their queue all the
 

00:12:16.760 --> 00:12:20.389 align:start position:0%
they're discounting their queue all the
way<00:12:16.920> down<00:12:17.040> to<00:12:17.240> only<00:12:18.000> 5%<00:12:19.000> of<00:12:19.320> projects<00:12:20.000> in<00:12:20.160> their

00:12:20.389 --> 00:12:20.399 align:start position:0%
way down to only 5% of projects in their
 

00:12:20.399 --> 00:12:22.110 align:start position:0%
way down to only 5% of projects in their
queue<00:12:20.880> will

00:12:22.110 --> 00:12:22.120 align:start position:0%
queue will
 

00:12:22.120 --> 00:12:24.110 align:start position:0%
queue will
complete<00:12:23.120> um<00:12:23.240> so<00:12:23.399> that's<00:12:23.600> why<00:12:23.800> the<00:12:23.920> you<00:12:24.000> know

00:12:24.110 --> 00:12:24.120 align:start position:0%
complete um so that's why the you know
 

00:12:24.120 --> 00:12:27.110 align:start position:0%
complete um so that's why the you know
the<00:12:24.279> PGM<00:12:24.720> has<00:12:24.839> been<00:12:25.000> forecasting<00:12:25.880> a<00:12:26.760> um<00:12:27.000> you

00:12:27.110 --> 00:12:27.120 align:start position:0%
the PGM has been forecasting a um you
 

00:12:27.120 --> 00:12:31.710 align:start position:0%
the PGM has been forecasting a um you
know<00:12:27.959> uh<00:12:28.399> resource<00:12:29.199> Stacy<00:12:30.199> U<00:12:30.399> issue<00:12:30.959> with<00:12:31.480> coal

00:12:31.710 --> 00:12:31.720 align:start position:0%
know uh resource Stacy U issue with coal
 

00:12:31.720 --> 00:12:34.829 align:start position:0%
know uh resource Stacy U issue with coal
plants<00:12:32.000> retiring<00:12:32.680> and<00:12:32.920> and<00:12:33.399> uh<00:12:33.680> you

00:12:34.829 --> 00:12:34.839 align:start position:0%
plants retiring and and uh you
 

00:12:34.839 --> 00:12:38.470 align:start position:0%
plants retiring and and uh you
know<00:12:35.839> G<00:12:36.079> gas<00:12:36.240> plants<00:12:36.720> retiring<00:12:37.720> faster<00:12:38.279> than

00:12:38.470 --> 00:12:38.480 align:start position:0%
know G gas plants retiring faster than
 

00:12:38.480 --> 00:12:40.949 align:start position:0%
know G gas plants retiring faster than
they<00:12:38.600> can<00:12:38.839> add<00:12:39.320> Renewables<00:12:40.160> so<00:12:40.519> go<00:12:40.720> back<00:12:40.839> to

00:12:40.949 --> 00:12:40.959 align:start position:0%
they can add Renewables so go back to
 

00:12:40.959 --> 00:12:44.030 align:start position:0%
they can add Renewables so go back to
the<00:12:41.079> previous<00:12:41.360> slide<00:12:41.720> yeah<00:12:41.880> sure<00:12:42.519> So<00:12:43.519> based<00:12:43.800> on

00:12:44.030 --> 00:12:44.040 align:start position:0%
the previous slide yeah sure So based on
 

00:12:44.040 --> 00:12:47.949 align:start position:0%
the previous slide yeah sure So based on
that<00:12:44.279> those<00:12:44.680> I<00:12:45.279> here<00:12:45.440> in<00:12:45.560> 2021

00:12:47.949 --> 00:12:47.959 align:start position:0%
that those I here in 2021
 

00:12:47.959 --> 00:12:49.829 align:start position:0%
that those I here in 2021
2022

00:12:49.829 --> 00:12:49.839 align:start position:0%
2022
 

00:12:49.839 --> 00:12:52.310 align:start position:0%
2022
um<00:12:50.839> are<00:12:51.040> those<00:12:51.320> projects<00:12:51.720> that<00:12:51.959> were

00:12:52.310 --> 00:12:52.320 align:start position:0%
um are those projects that were
 

00:12:52.320 --> 00:12:54.550 align:start position:0%
um are those projects that were
scheduled<00:12:52.880> to<00:12:53.000> be<00:12:53.199> completed<00:12:53.920> from<00:12:54.079> the<00:12:54.199> ENT

00:12:54.550 --> 00:12:54.560 align:start position:0%
scheduled to be completed from the ENT
 

00:12:54.560 --> 00:12:56.389 align:start position:0%
scheduled to be completed from the ENT
the<00:12:54.680> queue<00:12:55.040> or<00:12:55.199> is<00:12:55.399> that<00:12:55.880> is<00:12:56.000> that<00:12:56.279> the

00:12:56.389 --> 00:12:56.399 align:start position:0%
the queue or is that is that the
 

00:12:56.399 --> 00:12:58.389 align:start position:0%
the queue or is that is that the
estimate<00:12:56.720> is<00:12:56.959> now<00:12:57.519> yeah<00:12:57.639> the<00:12:57.760> estimate<00:12:58.120> is<00:12:58.240> so

00:12:58.389 --> 00:12:58.399 align:start position:0%
estimate is now yeah the estimate is so
 

00:12:58.399 --> 00:13:01.550 align:start position:0%
estimate is now yeah the estimate is so
like<00:12:58.560> those<00:12:58.920> bars<00:12:59.240> on<00:12:59.399> the<00:12:59.639> far<00:13:00.040> right<00:13:01.040> uh<00:13:01.399> the

00:13:01.550 --> 00:13:01.560 align:start position:0%
like those bars on the far right uh the
 

00:13:01.560 --> 00:13:03.910 align:start position:0%
like those bars on the far right uh the
estimate<00:13:02.000> would<00:13:02.199> be<00:13:02.839> at<00:13:02.959> least<00:13:03.279> five<00:13:03.519> years<00:13:03.720> so

00:13:03.910 --> 00:13:03.920 align:start position:0%
estimate would be at least five years so
 

00:13:03.920 --> 00:13:05.750 align:start position:0%
estimate would be at least five years so
maybe<00:13:04.160> insert<00:13:04.639> commercial<00:13:05.040> operation<00:13:05.480> dates

00:13:05.750 --> 00:13:05.760 align:start position:0%
maybe insert commercial operation dates
 

00:13:05.760 --> 00:13:10.310 align:start position:0%
maybe insert commercial operation dates
of<00:13:05.959> 2026<00:13:07.320> 2027<00:13:08.320> for<00:13:08.480> this<00:13:08.720> so<00:13:08.920> that<00:13:09.720> so<00:13:10.079> it's

00:13:10.310 --> 00:13:10.320 align:start position:0%
of 2026 2027 for this so that so it's
 

00:13:10.320 --> 00:13:15.750 align:start position:0%
of 2026 2027 for this so that so it's
wider<00:13:10.720> than<00:13:10.839> it<00:13:11.040> looks<00:13:11.320> there<00:13:11.760> yes

00:13:15.750 --> 00:13:15.760 align:start position:0%
 
 

00:13:15.760 --> 00:13:19.430 align:start position:0%
 
yes<00:13:16.760> good<00:13:16.959> question<00:13:17.360> thank

00:13:19.430 --> 00:13:19.440 align:start position:0%
yes good question thank
 

00:13:19.440 --> 00:13:22.150 align:start position:0%
yes good question thank
you<00:13:20.440> okay<00:13:20.959> so<00:13:21.360> you<00:13:21.480> know<00:13:21.600> what<00:13:21.680> is<00:13:21.800> the<00:13:21.880> rec

00:13:22.150 --> 00:13:22.160 align:start position:0%
you okay so you know what is the rec
 

00:13:22.160 --> 00:13:23.629 align:start position:0%
you okay so you know what is the rec
calls<00:13:22.360> of<00:13:22.519> this<00:13:22.639> it's<00:13:22.839> really<00:13:23.120> transmission

00:13:23.629 --> 00:13:23.639 align:start position:0%
calls of this it's really transmission
 

00:13:23.639 --> 00:13:26.590 align:start position:0%
calls of this it's really transmission
capacity<00:13:24.639> transmission<00:13:25.560> capacity<00:13:26.040> has<00:13:26.279> not

00:13:26.590 --> 00:13:26.600 align:start position:0%
capacity transmission capacity has not
 

00:13:26.600 --> 00:13:29.910 align:start position:0%
capacity transmission capacity has not
kept<00:13:26.959> up<00:13:27.839> with<00:13:28.560> the<00:13:28.920> electrification<00:13:29.560> demand

00:13:29.910 --> 00:13:29.920 align:start position:0%
kept up with the electrification demand
 

00:13:29.920 --> 00:13:32.710 align:start position:0%
kept up with the electrification demand
that<00:13:30.040> we<00:13:30.160> see<00:13:31.120> and<00:13:31.600> the<00:13:31.760> r<00:13:32.120> the<00:13:32.240> demand<00:13:32.519> for

00:13:32.710 --> 00:13:32.720 align:start position:0%
that we see and the r the demand for
 

00:13:32.720 --> 00:13:36.150 align:start position:0%
that we see and the r the demand for
Renewables<00:13:33.320> as<00:13:33.600> you<00:13:33.720> know<00:13:34.360> ulatory<00:13:35.360> and<00:13:35.839> um

00:13:36.150 --> 00:13:36.160 align:start position:0%
Renewables as you know ulatory and um
 

00:13:36.160 --> 00:13:39.189 align:start position:0%
Renewables as you know ulatory and um
honestly<00:13:36.519> just<00:13:36.760> the<00:13:37.120> the<00:13:37.440> economics<00:13:38.120> of<00:13:39.040> of

00:13:39.189 --> 00:13:39.199 align:start position:0%
honestly just the the economics of of
 

00:13:39.199 --> 00:13:42.389 align:start position:0%
honestly just the the economics of of
Renewables<00:13:39.680> have<00:13:39.839> come<00:13:40.079> down<00:13:40.920> so<00:13:41.160> much<00:13:42.079> and<00:13:42.240> so

00:13:42.389 --> 00:13:42.399 align:start position:0%
Renewables have come down so much and so
 

00:13:42.399 --> 00:13:44.790 align:start position:0%
Renewables have come down so much and so
a<00:13:42.519> pron<00:13:42.920> study<00:13:43.440> that's<00:13:43.600> been<00:13:44.079> widely<00:13:44.399> used<00:13:44.680> in

00:13:44.790 --> 00:13:44.800 align:start position:0%
a pron study that's been widely used in
 

00:13:44.800 --> 00:13:48.069 align:start position:0%
a pron study that's been widely used in
the<00:13:45.040> industry<00:13:46.199> um<00:13:47.199> seees<00:13:47.480> that<00:13:47.600> we<00:13:47.720> need

00:13:48.069 --> 00:13:48.079 align:start position:0%
the industry um seees that we need
 

00:13:48.079 --> 00:13:50.509 align:start position:0%
the industry um seees that we need
additional<00:13:48.639> 60%<00:13:49.639> of<00:13:49.800> our<00:13:49.959> transmission

00:13:50.509 --> 00:13:50.519 align:start position:0%
additional 60% of our transmission
 

00:13:50.519 --> 00:13:53.949 align:start position:0%
additional 60% of our transmission
capacity<00:13:51.440> by<00:13:51.839> 2030<00:13:52.839> so<00:13:53.000> that's<00:13:53.199> building

00:13:53.949 --> 00:13:53.959 align:start position:0%
capacity by 2030 so that's building
 

00:13:53.959 --> 00:13:56.749 align:start position:0%
capacity by 2030 so that's building
Decades<00:13:54.600> of<00:13:55.000> transmission<00:13:55.759> infrastructure

00:13:56.749 --> 00:13:56.759 align:start position:0%
Decades of transmission infrastructure
 

00:13:56.759 --> 00:13:59.629 align:start position:0%
Decades of transmission infrastructure
in<00:13:56.920> the<00:13:57.040> next<00:13:57.279> seven<00:13:57.759> years<00:13:58.920> um<00:13:59.279> and<00:13:59.399> you<00:13:59.480> can

00:13:59.629 --> 00:13:59.639 align:start position:0%
in the next seven years um and you can
 

00:13:59.639 --> 00:14:01.710 align:start position:0%
in the next seven years um and you can
see<00:14:00.000> you<00:14:00.120> know<00:14:00.240> how<00:14:00.360> do<00:14:00.480> we<00:14:00.600> do<00:14:00.839> that<00:14:01.160> well<00:14:01.519> the

00:14:01.710 --> 00:14:01.720 align:start position:0%
see you know how do we do that well the
 

00:14:01.720 --> 00:14:04.949 align:start position:0%
see you know how do we do that well the
traditional<00:14:02.399> methods<00:14:03.199> are<00:14:03.519> very<00:14:03.959> expensive

00:14:04.949 --> 00:14:04.959 align:start position:0%
traditional methods are very expensive
 

00:14:04.959 --> 00:14:08.230 align:start position:0%
traditional methods are very expensive
and<00:14:05.120> take<00:14:05.320> a<00:14:05.519> long<00:14:05.839> time<00:14:06.600> you<00:14:06.720> know<00:14:06.959> citing<00:14:07.959> and

00:14:08.230 --> 00:14:08.240 align:start position:0%
and take a long time you know citing and
 

00:14:08.240 --> 00:14:10.590 align:start position:0%
and take a long time you know citing and
permitting<00:14:08.759> and<00:14:08.880> building<00:14:09.199> the<00:14:09.600> transmission

00:14:10.590 --> 00:14:10.600 align:start position:0%
permitting and building the transmission
 

00:14:10.600 --> 00:14:13.110 align:start position:0%
permitting and building the transmission
can<00:14:10.839> be<00:14:11.000> as<00:14:11.160> much<00:14:11.360> as<00:14:11.680> you<00:14:11.800> know<00:14:12.639> as<00:14:12.880> if<00:14:13.000> you

00:14:13.110 --> 00:14:13.120 align:start position:0%
can be as much as you know as if you
 

00:14:13.120 --> 00:14:15.430 align:start position:0%
can be as much as you know as if you
look<00:14:13.240> at<00:14:13.480> capacity<00:14:14.040> per<00:14:14.279> mile<00:14:15.120> um<00:14:15.199> you<00:14:15.320> know

00:14:15.430 --> 00:14:15.440 align:start position:0%
look at capacity per mile um you know
 

00:14:15.440 --> 00:14:18.230 align:start position:0%
look at capacity per mile um you know
10,000<00:14:16.040> per<00:14:16.199> MOG<00:14:16.759> Mile<00:14:17.120> and<00:14:17.279> this<00:14:17.360> is<00:14:17.600> based<00:14:17.880> on

00:14:18.230 --> 00:14:18.240 align:start position:0%
10,000 per MOG Mile and this is based on
 

00:14:18.240 --> 00:14:23.069 align:start position:0%
10,000 per MOG Mile and this is based on
data<00:14:19.199> from<00:14:20.079> pjm<00:14:21.079> uh<00:14:21.959> post<00:14:22.480> at<00:14:22.759> project

00:14:23.069 --> 00:14:23.079 align:start position:0%
data from pjm uh post at project
 

00:14:23.079 --> 00:14:26.710 align:start position:0%
data from pjm uh post at project
estimates<00:14:24.240> for<00:14:25.240> um<00:14:25.560> transition<00:14:26.079> Improvement

00:14:26.710 --> 00:14:26.720 align:start position:0%
estimates for um transition Improvement
 

00:14:26.720 --> 00:14:28.910 align:start position:0%
estimates for um transition Improvement
projects<00:14:27.720> that<00:14:28.040> that<00:14:28.120> have<00:14:28.240> been<00:14:28.360> submitted

00:14:28.910 --> 00:14:28.920 align:start position:0%
projects that that have been submitted
 

00:14:28.920 --> 00:14:31.949 align:start position:0%
projects that that have been submitted
so<00:14:29.600> just<00:14:29.720> a<00:14:29.920> rough<00:14:30.160> analysis<00:14:30.639> of<00:14:30.920> those

00:14:31.949 --> 00:14:31.959 align:start position:0%
so just a rough analysis of those
 

00:14:31.959 --> 00:14:34.150 align:start position:0%
so just a rough analysis of those
projects<00:14:32.959> but<00:14:33.120> then<00:14:33.240> you<00:14:33.320> can<00:14:33.480> see<00:14:33.880> some

00:14:34.150 --> 00:14:34.160 align:start position:0%
projects but then you can see some
 

00:14:34.160 --> 00:14:36.069 align:start position:0%
projects but then you can see some
options<00:14:34.480> for<00:14:34.720> Grand<00:14:34.959> caning<00:14:35.320> Technologies

00:14:36.069 --> 00:14:36.079 align:start position:0%
options for Grand caning Technologies
 

00:14:36.079 --> 00:14:38.870 align:start position:0%
options for Grand caning Technologies
below<00:14:37.079> such<00:14:37.240> as<00:14:37.440> Dynamic<00:14:37.800> line<00:14:38.040> reading<00:14:38.720> and

00:14:38.870 --> 00:14:38.880 align:start position:0%
below such as Dynamic line reading and
 

00:14:38.880 --> 00:14:43.069 align:start position:0%
below such as Dynamic line reading and
storage<00:14:39.199> and<00:14:39.720> transmission<00:14:41.120> um<00:14:42.120> can<00:14:42.600> be<00:14:42.759> a

00:14:43.069 --> 00:14:43.079 align:start position:0%
storage and transmission um can be a
 

00:14:43.079 --> 00:14:46.910 align:start position:0%
storage and transmission um can be a
solution<00:14:44.079> uh<00:14:44.399> for<00:14:45.399> much<00:14:45.600> less<00:14:45.880> time<00:14:46.160> and

00:14:46.910 --> 00:14:46.920 align:start position:0%
solution uh for much less time and
 

00:14:46.920 --> 00:14:50.550 align:start position:0%
solution uh for much less time and
then<00:14:47.920> much<00:14:48.120> less<00:14:48.519> cost<00:14:49.519> than

00:14:50.550 --> 00:14:50.560 align:start position:0%
then much less cost than
 

00:14:50.560 --> 00:14:52.470 align:start position:0%
then much less cost than
transmission<00:14:51.560> so<00:14:51.720> it's<00:14:51.880> something<00:14:52.199> that<00:14:52.360> we

00:14:52.470 --> 00:14:52.480 align:start position:0%
transmission so it's something that we
 

00:14:52.480 --> 00:14:55.509 align:start position:0%
transmission so it's something that we
can

00:14:55.509 --> 00:14:55.519 align:start position:0%
 
 

00:14:55.519 --> 00:14:57.670 align:start position:0%
 
consider<00:14:56.519> all<00:14:56.680> right<00:14:57.040> so<00:14:57.279> what<00:14:57.399> are<00:14:57.519> these

00:14:57.670 --> 00:14:57.680 align:start position:0%
consider all right so what are these
 

00:14:57.680 --> 00:14:59.430 align:start position:0%
consider all right so what are these
ghing<00:14:58.279> technology

00:14:59.430 --> 00:14:59.440 align:start position:0%
ghing technology
 

00:14:59.440 --> 00:15:02.710 align:start position:0%
ghing technology
IES<00:15:00.440> so<00:15:00.680> before<00:15:00.839> I<00:15:00.959> kind<00:15:01.079> of<00:15:01.199> get<00:15:01.279> to<00:15:01.560> the<00:15:02.079> the

00:15:02.710 --> 00:15:02.720 align:start position:0%
IES so before I kind of get to the the
 

00:15:02.720 --> 00:15:05.430 align:start position:0%
IES so before I kind of get to the the
text<00:15:03.000> on<00:15:03.160> the<00:15:03.399> left<00:15:04.279> just<00:15:04.600> to

00:15:05.430 --> 00:15:05.440 align:start position:0%
text on the left just to
 

00:15:05.440 --> 00:15:08.350 align:start position:0%
text on the left just to
cover<00:15:06.440> the<00:15:07.160> the<00:15:07.320> different<00:15:07.680> Technologies

00:15:08.350 --> 00:15:08.360 align:start position:0%
cover the the different Technologies
 

00:15:08.360 --> 00:15:12.030 align:start position:0%
cover the the different Technologies
here<00:15:08.600> and<00:15:08.880> and<00:15:09.399> I'll<00:15:09.839> just<00:15:10.120> preface<00:15:10.560> this<00:15:11.040> with

00:15:12.030 --> 00:15:12.040 align:start position:0%
here and and I'll just preface this with
 

00:15:12.040 --> 00:15:13.670 align:start position:0%
here and and I'll just preface this with
there's<00:15:12.320> no<00:15:12.560> standard<00:15:12.959> in<00:15:13.040> the<00:15:13.160> industry<00:15:13.480> on

00:15:13.670 --> 00:15:13.680 align:start position:0%
there's no standard in the industry on
 

00:15:13.680 --> 00:15:15.670 align:start position:0%
there's no standard in the industry on
what<00:15:13.800> is<00:15:13.920> a<00:15:14.120> grid<00:15:14.360> enhancing<00:15:14.839> technology

00:15:15.670 --> 00:15:15.680 align:start position:0%
what is a grid enhancing technology
 

00:15:15.680 --> 00:15:18.670 align:start position:0%
what is a grid enhancing technology
there's<00:15:16.120> some<00:15:16.839> that<00:15:17.000> would<00:15:17.240> only<00:15:18.240> three<00:15:18.480> of

00:15:18.670 --> 00:15:18.680 align:start position:0%
there's some that would only three of
 

00:15:18.680 --> 00:15:21.670 align:start position:0%
there's some that would only three of
these<00:15:19.199> would<00:15:19.880> be<00:15:20.880> you<00:15:21.000> know<00:15:21.160> a<00:15:21.279> technology

00:15:21.670 --> 00:15:21.680 align:start position:0%
these would be you know a technology
 

00:15:21.680 --> 00:15:23.590 align:start position:0%
these would be you know a technology
that<00:15:21.800> can<00:15:21.880> improve<00:15:22.160> transmission<00:15:22.720> capacity

00:15:23.590 --> 00:15:23.600 align:start position:0%
that can improve transmission capacity
 

00:15:23.600 --> 00:15:28.189 align:start position:0%
that can improve transmission capacity
but<00:15:24.839> really<00:15:25.839> I<00:15:25.959> think<00:15:26.320> as<00:15:26.720> takes<00:15:26.920> a<00:15:27.079> broad<00:15:27.399> view

00:15:28.189 --> 00:15:28.199 align:start position:0%
but really I think as takes a broad view
 

00:15:28.199 --> 00:15:31.150 align:start position:0%
but really I think as takes a broad view
and<00:15:28.720> says<00:15:29.600> any<00:15:30.120> flexible<00:15:30.600> technology<00:15:31.040> that

00:15:31.150 --> 00:15:31.160 align:start position:0%
and says any flexible technology that
 

00:15:31.160 --> 00:15:33.030 align:start position:0%
and says any flexible technology that
can<00:15:31.360> alleviate<00:15:31.880> transmission<00:15:32.399> capacity

00:15:33.030 --> 00:15:33.040 align:start position:0%
can alleviate transmission capacity
 

00:15:33.040 --> 00:15:37.590 align:start position:0%
can alleviate transmission capacity
whether<00:15:33.279> that's<00:15:34.000> demand<00:15:34.440> response<00:15:35.440> or<00:15:36.399> um<00:15:36.959> a

00:15:37.590 --> 00:15:37.600 align:start position:0%
whether that's demand response or um a
 

00:15:37.600 --> 00:15:39.590 align:start position:0%
whether that's demand response or um a
something<00:15:37.920> that<00:15:38.000> you<00:15:38.199> put<00:15:38.399> in<00:15:38.560> the<00:15:39.160> aset<00:15:39.440> on

00:15:39.590 --> 00:15:39.600 align:start position:0%
something that you put in the aset on
 

00:15:39.600 --> 00:15:41.230 align:start position:0%
something that you put in the aset on
the<00:15:39.680> transmission<00:15:40.240> system<00:15:40.680> is<00:15:40.839> something<00:15:41.120> we

00:15:41.230 --> 00:15:41.240 align:start position:0%
the transmission system is something we
 

00:15:41.240 --> 00:15:44.069 align:start position:0%
the transmission system is something we
want<00:15:41.360> to<00:15:41.959> explore<00:15:42.959> so<00:15:43.160> starting<00:15:43.480> at<00:15:43.600> the<00:15:43.800> top

00:15:44.069 --> 00:15:44.079 align:start position:0%
want to explore so starting at the top
 

00:15:44.079 --> 00:15:46.629 align:start position:0%
want to explore so starting at the top
left<00:15:44.759> um<00:15:44.959> flexible<00:15:45.839> Alterna<00:15:46.319> current

00:15:46.629 --> 00:15:46.639 align:start position:0%
left um flexible Alterna current
 

00:15:46.639 --> 00:15:49.350 align:start position:0%
left um flexible Alterna current
transmission<00:15:47.199> systems<00:15:47.639> for<00:15:48.079> fast<00:15:49.079> these<00:15:49.240> have

00:15:49.350 --> 00:15:49.360 align:start position:0%
transmission systems for fast these have
 

00:15:49.360 --> 00:15:51.110 align:start position:0%
transmission systems for fast these have
been<00:15:49.560> around<00:15:49.800> for<00:15:50.079> decades<00:15:50.759> right<00:15:50.880> so<00:15:51.000> these

00:15:51.110 --> 00:15:51.120 align:start position:0%
been around for decades right so these
 

00:15:51.120 --> 00:15:53.829 align:start position:0%
been around for decades right so these
are<00:15:51.360> like<00:15:51.720> serious<00:15:52.560> capacitors<00:15:53.560> um<00:15:53.639> that<00:15:53.720> you

00:15:53.829 --> 00:15:53.839 align:start position:0%
are like serious capacitors um that you
 

00:15:53.839 --> 00:15:55.350 align:start position:0%
are like serious capacitors um that you
can<00:15:54.000> put<00:15:54.120> on<00:15:54.199> a<00:15:54.319> long<00:15:54.519> transmission<00:15:54.959> line<00:15:55.160> to

00:15:55.350 --> 00:15:55.360 align:start position:0%
can put on a long transmission line to
 

00:15:55.360 --> 00:15:56.829 align:start position:0%
can put on a long transmission line to
compensate<00:15:55.720> for<00:15:55.880> reative<00:15:56.279> power<00:15:56.560> allowing

00:15:56.829 --> 00:15:56.839 align:start position:0%
compensate for reative power allowing
 

00:15:56.839 --> 00:15:59.710 align:start position:0%
compensate for reative power allowing
you<00:15:56.920> to<00:15:57.079> transfer<00:15:57.920> uh<00:15:58.079> more<00:15:58.279> energy

00:15:59.710 --> 00:15:59.720 align:start position:0%
you to transfer uh more energy
 

00:15:59.720 --> 00:16:01.790 align:start position:0%
you to transfer uh more energy
and<00:15:59.839> then<00:15:59.959> a<00:16:00.120> modern<00:16:00.480> evolution<00:16:00.959> of<00:16:01.240> that<00:16:01.560> with

00:16:01.790 --> 00:16:01.800 align:start position:0%
and then a modern evolution of that with
 

00:16:01.800 --> 00:16:03.189 align:start position:0%
and then a modern evolution of that with
Solid<00:16:02.120> State<00:16:02.399> power<00:16:02.639> Electronics<00:16:03.079> is

00:16:03.189 --> 00:16:03.199 align:start position:0%
Solid State power Electronics is
 

00:16:03.199 --> 00:16:05.590 align:start position:0%
Solid State power Electronics is
powerful<00:16:03.600> control<00:16:04.120> so<00:16:04.319> these<00:16:04.440> are<00:16:05.360> Solid

00:16:05.590 --> 00:16:05.600 align:start position:0%
powerful control so these are Solid
 

00:16:05.600 --> 00:16:06.870 align:start position:0%
powerful control so these are Solid
State<00:16:05.839> power<00:16:06.000> electronics<00:16:06.360> that<00:16:06.440> be<00:16:06.560> located

00:16:06.870 --> 00:16:06.880 align:start position:0%
State power electronics that be located
 

00:16:06.880 --> 00:16:08.430 align:start position:0%
State power electronics that be located
a<00:16:07.000> substation<00:16:07.560> that<00:16:07.680> could<00:16:07.880> kind<00:16:07.959> of<00:16:08.160> push<00:16:08.319> and

00:16:08.430 --> 00:16:08.440 align:start position:0%
a substation that could kind of push and
 

00:16:08.440 --> 00:16:09.590 align:start position:0%
a substation that could kind of push and
pull<00:16:08.720> power<00:16:09.000> away<00:16:09.199> from<00:16:09.360> different

00:16:09.590 --> 00:16:09.600 align:start position:0%
pull power away from different
 

00:16:09.600 --> 00:16:11.990 align:start position:0%
pull power away from different
transmission<00:16:10.360> lines<00:16:11.360> storage<00:16:11.720> and

00:16:11.990 --> 00:16:12.000 align:start position:0%
transmission lines storage and
 

00:16:12.000 --> 00:16:13.949 align:start position:0%
transmission lines storage and
transmission<00:16:13.000> we'll<00:16:13.199> talk<00:16:13.399> a<00:16:13.560> little<00:16:13.720> bit

00:16:13.949 --> 00:16:13.959 align:start position:0%
transmission we'll talk a little bit
 

00:16:13.959 --> 00:16:16.389 align:start position:0%
transmission we'll talk a little bit
about<00:16:14.519> uh<00:16:15.279> later<00:16:15.560> in<00:16:15.680> the

00:16:16.389 --> 00:16:16.399 align:start position:0%
about uh later in the
 

00:16:16.399 --> 00:16:18.710 align:start position:0%
about uh later in the
presentation<00:16:17.399> but<00:16:17.759> suffice<00:16:18.079> to<00:16:18.240> say<00:16:18.440> that

00:16:18.710 --> 00:16:18.720 align:start position:0%
presentation but suffice to say that
 

00:16:18.720 --> 00:16:21.829 align:start position:0%
presentation but suffice to say that
it's<00:16:19.000> solving<00:16:19.560> problems<00:16:19.920> locally<00:16:20.480> versus<00:16:21.399> uh

00:16:21.829 --> 00:16:21.839 align:start position:0%
it's solving problems locally versus uh
 

00:16:21.839 --> 00:16:23.990 align:start position:0%
it's solving problems locally versus uh
you<00:16:21.959> know<00:16:22.319> delivering<00:16:22.839> energy<00:16:23.240> locally

00:16:23.990 --> 00:16:24.000 align:start position:0%
you know delivering energy locally
 

00:16:24.000 --> 00:16:26.269 align:start position:0%
you know delivering energy locally
versus<00:16:24.360> transmitting<00:16:24.920> power<00:16:25.160> over<00:16:25.319> a<00:16:25.440> long

00:16:26.269 --> 00:16:26.279 align:start position:0%
versus transmitting power over a long
 

00:16:26.279 --> 00:16:29.309 align:start position:0%
versus transmitting power over a long
distance<00:16:27.279> to<00:16:27.600> all<00:16:27.880> the<00:16:27.959> optimization<00:16:29.000> looks

00:16:29.309 --> 00:16:29.319 align:start position:0%
distance to all the optimization looks
 

00:16:29.319 --> 00:16:33.550 align:start position:0%
distance to all the optimization looks
at<00:16:30.279> um<00:16:30.680> the<00:16:31.000> the<00:16:31.160> grid<00:16:31.480> and<00:16:32.199> looks<00:16:32.440> for<00:16:33.199> areas

00:16:33.550 --> 00:16:33.560 align:start position:0%
at um the the grid and looks for areas
 

00:16:33.560 --> 00:16:36.069 align:start position:0%
at um the the grid and looks for areas
where<00:16:33.759> you<00:16:33.880> can<00:16:34.079> reconfigure<00:16:34.720> it<00:16:35.560> um<00:16:35.880> that

00:16:36.069 --> 00:16:36.079 align:start position:0%
where you can reconfigure it um that
 

00:16:36.079 --> 00:16:38.110 align:start position:0%
where you can reconfigure it um that
will<00:16:36.519> solve<00:16:36.839> contingencies<00:16:37.440> or<00:16:37.600> solve<00:16:37.880> issues

00:16:38.110 --> 00:16:38.120 align:start position:0%
will solve contingencies or solve issues
 

00:16:38.120 --> 00:16:39.629 align:start position:0%
will solve contingencies or solve issues
on<00:16:38.240> the<00:16:38.360> grid<00:16:38.600> so<00:16:38.759> for<00:16:38.880> instance<00:16:39.199> opening<00:16:39.480> a

00:16:39.629 --> 00:16:39.639 align:start position:0%
on the grid so for instance opening a
 

00:16:39.639 --> 00:16:42.389 align:start position:0%
on the grid so for instance opening a
tiebreaker<00:16:40.160> at<00:16:40.240> a<00:16:40.360> substation<00:16:41.279> while<00:16:41.480> you<00:16:41.680> may

00:16:42.389 --> 00:16:42.399 align:start position:0%
tiebreaker at a substation while you may
 

00:16:42.399 --> 00:16:44.990 align:start position:0%
tiebreaker at a substation while you may
be<00:16:43.399> uh<00:16:43.720> intuitive<00:16:44.240> that<00:16:44.360> you<00:16:44.519> should<00:16:44.680> always

00:16:44.990 --> 00:16:45.000 align:start position:0%
be uh intuitive that you should always
 

00:16:45.000 --> 00:16:47.670 align:start position:0%
be uh intuitive that you should always
have<00:16:45.319> all<00:16:45.480> the<00:16:45.600> breakers<00:16:45.959> closed<00:16:46.759> that<00:16:47.399> can

00:16:47.670 --> 00:16:47.680 align:start position:0%
have all the breakers closed that can
 

00:16:47.680 --> 00:16:50.749 align:start position:0%
have all the breakers closed that can
allow<00:16:48.000> power<00:16:48.199> to<00:16:48.319> flow<00:16:49.160> suboptimally<00:16:50.160> um<00:16:50.560> and

00:16:50.749 --> 00:16:50.759 align:start position:0%
allow power to flow suboptimally um and
 

00:16:50.759 --> 00:16:53.949 align:start position:0%
allow power to flow suboptimally um and
so<00:16:51.759> there's<00:16:52.519> there's<00:16:52.759> been<00:16:53.000> some<00:16:53.399> examples<00:16:53.800> of

00:16:53.949 --> 00:16:53.959 align:start position:0%
so there's there's been some examples of
 

00:16:53.959 --> 00:16:57.230 align:start position:0%
so there's there's been some examples of
the<00:16:54.120> market<00:16:54.519> of<00:16:55.440> U<00:16:55.839> you<00:16:56.000> know<00:16:56.680> switching<00:16:57.079> out

00:16:57.230 --> 00:16:57.240 align:start position:0%
the market of U you know switching out
 

00:16:57.240 --> 00:17:00.309 align:start position:0%
the market of U you know switching out
switches<00:16:57.560> or<00:16:57.720> Breakers<00:16:58.800> uh<00:16:58.920> in<00:16:59.000> order<00:16:59.199> to<00:16:59.319> re

00:17:00.309 --> 00:17:00.319 align:start position:0%
switches or Breakers uh in order to re
 

00:17:00.319 --> 00:17:02.710 align:start position:0%
switches or Breakers uh in order to re
power<00:17:01.319> Dynamic<00:17:01.720> F<00:17:01.959> ring<00:17:02.199> again<00:17:02.360> we'll<00:17:02.519> touch

00:17:02.710 --> 00:17:02.720 align:start position:0%
power Dynamic F ring again we'll touch
 

00:17:02.720 --> 00:17:04.829 align:start position:0%
power Dynamic F ring again we'll touch
on<00:17:02.920> further<00:17:03.279> but<00:17:03.440> it's<00:17:03.839> it's<00:17:04.120> monitoring

00:17:04.829 --> 00:17:04.839 align:start position:0%
on further but it's it's monitoring
 

00:17:04.839 --> 00:17:07.669 align:start position:0%
on further but it's it's monitoring
ambient<00:17:05.400> conditions<00:17:05.799> and<00:17:06.520> in<00:17:06.640> the<00:17:06.760> field<00:17:07.559> in

00:17:07.669 --> 00:17:07.679 align:start position:0%
ambient conditions and in the field in
 

00:17:07.679 --> 00:17:09.470 align:start position:0%
ambient conditions and in the field in
order<00:17:07.919> to<00:17:08.720> get<00:17:08.839> the<00:17:09.000> most<00:17:09.240> out<00:17:09.360> of

00:17:09.470 --> 00:17:09.480 align:start position:0%
order to get the most out of
 

00:17:09.480 --> 00:17:11.549 align:start position:0%
order to get the most out of
transmission<00:17:09.919> line<00:17:10.400> capacity<00:17:11.319> and<00:17:11.400> then

00:17:11.549 --> 00:17:11.559 align:start position:0%
transmission line capacity and then
 

00:17:11.559 --> 00:17:13.710 align:start position:0%
transmission line capacity and then
finally<00:17:11.880> virtual<00:17:12.280> power<00:17:12.559> plant<00:17:13.120> that's<00:17:13.640> I

00:17:13.710 --> 00:17:13.720 align:start position:0%
finally virtual power plant that's I
 

00:17:13.720 --> 00:17:15.189 align:start position:0%
finally virtual power plant that's I
would<00:17:13.880> say<00:17:14.079> you<00:17:14.160> know<00:17:14.360> primary<00:17:14.720> like<00:17:14.839> demand

00:17:15.189 --> 00:17:15.199 align:start position:0%
would say you know primary like demand
 

00:17:15.199 --> 00:17:17.470 align:start position:0%
would say you know primary like demand
response<00:17:15.600> programs<00:17:16.079> right<00:17:16.280> so<00:17:17.120> I<00:17:17.240> have<00:17:17.360> an

00:17:17.470 --> 00:17:17.480 align:start position:0%
response programs right so I have an
 

00:17:17.480 --> 00:17:19.110 align:start position:0%
response programs right so I have an
electric<00:17:17.919> vehicle<00:17:18.360> icon<00:17:18.640> on<00:17:18.760> there<00:17:18.959> but<00:17:19.039> it

00:17:19.110 --> 00:17:19.120 align:start position:0%
electric vehicle icon on there but it
 

00:17:19.120 --> 00:17:22.829 align:start position:0%
electric vehicle icon on there but it
could<00:17:19.280> be<00:17:19.880> EVS<00:17:20.880> bed<00:17:21.199> air<00:17:21.480> condition<00:17:21.720> units<00:17:22.240> Etc

00:17:22.829 --> 00:17:22.839 align:start position:0%
could be EVS bed air condition units Etc
 

00:17:22.839 --> 00:17:25.029 align:start position:0%
could be EVS bed air condition units Etc
then<00:17:23.600> again<00:17:23.839> solve<00:17:24.160> the<00:17:24.319> problem<00:17:24.600> locally<00:17:24.959> so

00:17:25.029 --> 00:17:25.039 align:start position:0%
then again solve the problem locally so
 

00:17:25.039 --> 00:17:27.350 align:start position:0%
then again solve the problem locally so
you<00:17:25.120> don't<00:17:25.280> have<00:17:25.400> to<00:17:25.520> transmit<00:17:26.000> as<00:17:26.120> much<00:17:26.360> power

00:17:27.350 --> 00:17:27.360 align:start position:0%
you don't have to transmit as much power
 

00:17:27.360 --> 00:17:29.669 align:start position:0%
you don't have to transmit as much power
all<00:17:27.520> of<00:17:27.799> these<00:17:28.160> are<00:17:28.600> solutions<00:17:29.360> that<00:17:29.480> should

00:17:29.669 --> 00:17:29.679 align:start position:0%
all of these are solutions that should
 

00:17:29.679 --> 00:17:31.470 align:start position:0%
all of these are solutions that should
be

00:17:31.470 --> 00:17:31.480 align:start position:0%
be
 

00:17:31.480 --> 00:17:35.029 align:start position:0%
be
evaluated<00:17:32.480> alongside<00:17:33.240> traditional<00:17:34.039> upgrades

00:17:35.029 --> 00:17:35.039 align:start position:0%
evaluated alongside traditional upgrades
 

00:17:35.039 --> 00:17:37.270 align:start position:0%
evaluated alongside traditional upgrades
and<00:17:35.320> and<00:17:35.679> how<00:17:35.919> do<00:17:36.120> they<00:17:36.280> provide<00:17:36.720> value<00:17:37.039> so

00:17:37.270 --> 00:17:37.280 align:start position:0%
and and how do they provide value so
 

00:17:37.280 --> 00:17:39.390 align:start position:0%
and and how do they provide value so
before<00:17:37.600> it's<00:17:38.039> before<00:17:38.280> transmission<00:17:38.760> is<00:17:38.919> built

00:17:39.390 --> 00:17:39.400 align:start position:0%
before it's before transmission is built
 

00:17:39.400 --> 00:17:42.669 align:start position:0%
before it's before transmission is built
right<00:17:39.600> they<00:17:39.679> can<00:17:39.960> offset<00:17:40.600> or<00:17:41.360> um<00:17:41.520> defer<00:17:42.480> a

00:17:42.669 --> 00:17:42.679 align:start position:0%
right they can offset or um defer a
 

00:17:42.679 --> 00:17:45.710 align:start position:0%
right they can offset or um defer a
traditional<00:17:44.080> investment<00:17:45.080> and<00:17:45.240> solve<00:17:45.600> those

00:17:45.710 --> 00:17:45.720 align:start position:0%
traditional investment and solve those
 

00:17:45.720 --> 00:17:47.110 align:start position:0%
traditional investment and solve those
Network<00:17:46.080> upgrades<00:17:46.559> that<00:17:46.640> we<00:17:46.720> were<00:17:46.880> talking

00:17:47.110 --> 00:17:47.120 align:start position:0%
Network upgrades that we were talking
 

00:17:47.120 --> 00:17:51.710 align:start position:0%
Network upgrades that we were talking
about<00:17:47.559> previously<00:17:48.559> uh<00:17:48.840> for<00:17:49.360> less<00:17:49.679> expensive

00:17:51.710 --> 00:17:51.720 align:start position:0%
about previously uh for less expensive
 

00:17:51.720 --> 00:17:54.350 align:start position:0%
about previously uh for less expensive
costs<00:17:52.720> and<00:17:52.919> then<00:17:53.200> you<00:17:53.320> know<00:17:53.520> during

00:17:54.350 --> 00:17:54.360 align:start position:0%
costs and then you know during
 

00:17:54.360 --> 00:17:56.310 align:start position:0%
costs and then you know during
construction<00:17:55.360> all<00:17:55.520> of<00:17:55.679> the<00:17:55.799> infrastructure

00:17:56.310 --> 00:17:56.320 align:start position:0%
construction all of the infrastructure
 

00:17:56.320 --> 00:17:57.470 align:start position:0%
construction all of the infrastructure
that<00:17:56.400> we<00:17:56.520> have<00:17:56.640> to<00:17:56.760> build<00:17:57.200> all<00:17:57.360> the

00:17:57.470 --> 00:17:57.480 align:start position:0%
that we have to build all the
 

00:17:57.480 --> 00:17:59.270 align:start position:0%
that we have to build all the
transmission<00:17:57.919> we<00:17:58.000> have<00:17:58.080> to<00:17:58.159> build<00:17:58.760> uh<00:17:58.880> in<00:17:59.000> the

00:17:59.270 --> 00:17:59.280 align:start position:0%
transmission we have to build uh in the
 

00:17:59.280 --> 00:18:02.470 align:start position:0%
transmission we have to build uh in the
next<00:17:59.720> decade<00:18:00.039> or<00:18:00.159> so<00:18:00.640> to<00:18:01.640> integrate<00:18:02.080> this

00:18:02.470 --> 00:18:02.480 align:start position:0%
next decade or so to integrate this
 

00:18:02.480 --> 00:18:03.950 align:start position:0%
next decade or so to integrate this
these<00:18:02.600> Renewables<00:18:02.960> are<00:18:03.120> going<00:18:03.200> to<00:18:03.320> involve

00:18:03.950 --> 00:18:03.960 align:start position:0%
these Renewables are going to involve
 

00:18:03.960 --> 00:18:06.549 align:start position:0%
these Renewables are going to involve
outages<00:18:04.960> and<00:18:05.480> things<00:18:05.679> like<00:18:05.840> drr<00:18:06.360> where<00:18:06.480> you

00:18:06.549 --> 00:18:06.559 align:start position:0%
outages and things like drr where you
 

00:18:06.559 --> 00:18:08.350 align:start position:0%
outages and things like drr where you
have<00:18:06.640> a<00:18:06.760> sensor<00:18:07.080> that<00:18:07.200> you<00:18:07.280> can<00:18:07.440> mount<00:18:07.960> below

00:18:08.350 --> 00:18:08.360 align:start position:0%
have a sensor that you can mount below
 

00:18:08.360 --> 00:18:11.830 align:start position:0%
have a sensor that you can mount below
transmission<00:18:08.960> line<00:18:09.960> um<00:18:10.679> and<00:18:11.320> and<00:18:11.440> get<00:18:11.600> up<00:18:11.720> and

00:18:11.830 --> 00:18:11.840 align:start position:0%
transmission line um and and get up and
 

00:18:11.840 --> 00:18:13.510 align:start position:0%
transmission line um and and get up and
running<00:18:12.120> in<00:18:12.280> three<00:18:12.480> months<00:18:13.039> you<00:18:13.159> could<00:18:13.320> do

00:18:13.510 --> 00:18:13.520 align:start position:0%
running in three months you could do
 

00:18:13.520 --> 00:18:14.590 align:start position:0%
running in three months you could do
that<00:18:13.720> prior<00:18:13.960> to

00:18:14.590 --> 00:18:14.600 align:start position:0%
that prior to
 

00:18:14.600 --> 00:18:16.909 align:start position:0%
that prior to
construction<00:18:15.600> mitigate<00:18:16.039> that<00:18:16.200> outage<00:18:16.600> so<00:18:16.760> you

00:18:16.909 --> 00:18:16.919 align:start position:0%
construction mitigate that outage so you
 

00:18:16.919 --> 00:18:18.390 align:start position:0%
construction mitigate that outage so you
have<00:18:17.039> more<00:18:17.200> capacity<00:18:17.559> on<00:18:17.640> that<00:18:17.799> line<00:18:18.120> and<00:18:18.320> as

00:18:18.390 --> 00:18:18.400 align:start position:0%
have more capacity on that line and as
 

00:18:18.400 --> 00:18:20.110 align:start position:0%
have more capacity on that line and as
soon<00:18:18.520> as<00:18:18.640> transmission<00:18:19.039> is<00:18:19.159> built<00:18:19.760> pull<00:18:20.000> Those

00:18:20.110 --> 00:18:20.120 align:start position:0%
soon as transmission is built pull Those
 

00:18:20.120 --> 00:18:22.070 align:start position:0%
soon as transmission is built pull Those
sensors<00:18:20.640> down<00:18:21.200> and<00:18:21.360> move<00:18:21.520> them<00:18:21.640> on<00:18:21.799> to<00:18:21.960> the

00:18:22.070 --> 00:18:22.080 align:start position:0%
sensors down and move them on to the
 

00:18:22.080 --> 00:18:24.510 align:start position:0%
sensors down and move them on to the
next<00:18:22.600> project<00:18:23.600> um<00:18:23.799> because<00:18:24.000> they're<00:18:24.120> at<00:18:24.280> a

00:18:24.510 --> 00:18:24.520 align:start position:0%
next project um because they're at a
 

00:18:24.520 --> 00:18:27.549 align:start position:0%
next project um because they're at a
cost<00:18:25.480> and<00:18:26.080> uh<00:18:26.320> you<00:18:26.400> know<00:18:26.640> installation<00:18:27.240> time

00:18:27.549 --> 00:18:27.559 align:start position:0%
cost and uh you know installation time
 

00:18:27.559 --> 00:18:29.190 align:start position:0%
cost and uh you know installation time
that<00:18:27.760> allows<00:18:28.080> you<00:18:28.400> to<00:18:28.520> do<00:18:28.679> that<00:18:28.840> I<00:18:28.919> mean<00:18:29.039> these

00:18:29.190 --> 00:18:29.200 align:start position:0%
that allows you to do that I mean these
 

00:18:29.200 --> 00:18:30.630 align:start position:0%
that allows you to do that I mean these
transmission<00:18:29.679> construction<00:18:30.159> projects<00:18:30.480> could

00:18:30.630 --> 00:18:30.640 align:start position:0%
transmission construction projects could
 

00:18:30.640 --> 00:18:33.710 align:start position:0%
transmission construction projects could
be<00:18:30.799> years<00:18:31.159> long<00:18:31.960> so<00:18:32.280> you<00:18:32.400> can<00:18:32.600> do<00:18:33.080> three<00:18:33.480> six

00:18:33.710 --> 00:18:33.720 align:start position:0%
be years long so you can do three six
 

00:18:33.720 --> 00:18:36.029 align:start position:0%
be years long so you can do three six
months<00:18:34.039> Preparatory<00:18:34.559> work<00:18:34.799> for<00:18:35.080> that<00:18:35.919> and

00:18:36.029 --> 00:18:36.039 align:start position:0%
months Preparatory work for that and
 

00:18:36.039 --> 00:18:37.470 align:start position:0%
months Preparatory work for that and
then<00:18:36.159> finally<00:18:36.520> just<00:18:36.679> after<00:18:36.919> transmission<00:18:37.360> is

00:18:37.470 --> 00:18:37.480 align:start position:0%
then finally just after transmission is
 

00:18:37.480 --> 00:18:39.230 align:start position:0%
then finally just after transmission is
built<00:18:37.799> right<00:18:37.960> you<00:18:38.240> consider<00:18:38.760> them<00:18:39.000> if<00:18:39.120> you're

00:18:39.230 --> 00:18:39.240 align:start position:0%
built right you consider them if you're
 

00:18:39.240 --> 00:18:41.710 align:start position:0%
built right you consider them if you're
building<00:18:39.559> a<00:18:39.720> new<00:18:39.880> line<00:18:40.480> consider<00:18:40.960> putting

00:18:41.710 --> 00:18:41.720 align:start position:0%
building a new line consider putting
 

00:18:41.720 --> 00:18:43.710 align:start position:0%
building a new line consider putting
some<00:18:41.880> of<00:18:42.000> these<00:18:42.280> Technologies<00:18:42.880> in<00:18:43.120> place<00:18:43.520> such

00:18:43.710 --> 00:18:43.720 align:start position:0%
some of these Technologies in place such
 

00:18:43.720 --> 00:18:46.590 align:start position:0%
some of these Technologies in place such
as<00:18:44.360> flexible<00:18:44.840> Alterna<00:18:45.840> alter<00:18:46.280> correct

00:18:46.590 --> 00:18:46.600 align:start position:0%
as flexible Alterna alter correct
 

00:18:46.600 --> 00:18:47.950 align:start position:0%
as flexible Alterna alter correct
transmission<00:18:47.159> systems<00:18:47.480> you're<00:18:47.600> building<00:18:47.840> a

00:18:47.950 --> 00:18:47.960 align:start position:0%
transmission systems you're building a
 

00:18:47.960 --> 00:18:51.029 align:start position:0%
transmission systems you're building a
long<00:18:48.159> transmiss<00:18:48.720> transmission<00:18:49.159> line<00:18:50.080> um<00:18:50.919> you

00:18:51.029 --> 00:18:51.039 align:start position:0%
long transmiss transmission line um you
 

00:18:51.039 --> 00:18:52.750 align:start position:0%
long transmiss transmission line um you
know<00:18:51.320> consider<00:18:51.960> these<00:18:52.440> different

00:18:52.750 --> 00:18:52.760 align:start position:0%
know consider these different
 

00:18:52.760 --> 00:18:54.830 align:start position:0%
know consider these different
technologies<00:18:53.720> that<00:18:53.880> can<00:18:54.039> make<00:18:54.360> their<00:18:54.600> cost

00:18:54.830 --> 00:18:54.840 align:start position:0%
technologies that can make their cost
 

00:18:54.840 --> 00:18:57.310 align:start position:0%
technologies that can make their cost
benefit<00:18:55.400> ratio<00:18:56.400> even

00:18:57.310 --> 00:18:57.320 align:start position:0%
benefit ratio even
 

00:18:57.320 --> 00:18:59.870 align:start position:0%
benefit ratio even
higher<00:18:58.360> any<00:18:58.559> questions<00:18:58.880> on<00:18:59.360> this<00:18:59.520> slide<00:18:59.799> I

00:18:59.870 --> 00:18:59.880 align:start position:0%
higher any questions on this slide I
 

00:18:59.880 --> 00:19:02.590 align:start position:0%
higher any questions on this slide I
know<00:19:00.000> there's<00:19:00.200> kind<00:19:00.320> of<00:19:00.440> a<00:19:00.919> lot<00:19:01.919> a<00:19:02.159> longer

00:19:02.590 --> 00:19:02.600 align:start position:0%
know there's kind of a lot a longer
 

00:19:02.600 --> 00:19:06.390 align:start position:0%
know there's kind of a lot a longer
review<00:19:02.960> before<00:19:03.240> we'll<00:19:03.440> jump<00:19:03.760> into<00:19:04.720> um<00:19:05.200> DLR<00:19:05.880> and

00:19:06.390 --> 00:19:06.400 align:start position:0%
review before we'll jump into um DLR and
 

00:19:06.400 --> 00:19:09.350 align:start position:0%
review before we'll jump into um DLR and
storage<00:19:06.919> after<00:19:07.280> this<00:19:07.640> will<00:19:07.799> you<00:19:07.960> be<00:19:08.400> talking

00:19:09.350 --> 00:19:09.360 align:start position:0%
storage after this will you be talking
 

00:19:09.360 --> 00:19:11.830 align:start position:0%
storage after this will you be talking
at<00:19:09.520> all<00:19:09.799> so<00:19:10.080> this<00:19:10.200> is<00:19:10.559> the<00:19:10.799> technology

00:19:11.830 --> 00:19:11.840 align:start position:0%
at all so this is the technology
 

00:19:11.840 --> 00:19:14.909 align:start position:0%
at all so this is the technology
solutioning<00:19:12.840> component<00:19:13.480> of<00:19:13.760> this<00:19:14.320> there<00:19:14.480> is<00:19:14.640> a

00:19:14.909 --> 00:19:14.919 align:start position:0%
solutioning component of this there is a
 

00:19:14.919 --> 00:19:17.710 align:start position:0%
solutioning component of this there is a
significant<00:19:15.679> regulatory<00:19:16.559> both<00:19:16.720> at<00:19:16.799> the<00:19:17.320> level

00:19:17.710 --> 00:19:17.720 align:start position:0%
significant regulatory both at the level
 

00:19:17.720 --> 00:19:19.549 align:start position:0%
significant regulatory both at the level
as<00:19:17.880> well<00:19:18.039> as<00:19:18.240> at<00:19:18.360> the<00:19:18.600> state<00:19:18.919> Corporation

00:19:19.549 --> 00:19:19.559 align:start position:0%
as well as at the state Corporation
 

00:19:19.559 --> 00:19:21.669 align:start position:0%
as well as at the state Corporation
level<00:19:20.400> that<00:19:20.559> has<00:19:20.720> to<00:19:20.880> be<00:19:21.080> addressed<00:19:21.440> in

00:19:21.669 --> 00:19:21.679 align:start position:0%
level that has to be addressed in
 

00:19:21.679 --> 00:19:23.630 align:start position:0%
level that has to be addressed in
parallel<00:19:22.080> to<00:19:22.280> this<00:19:22.559> in<00:19:22.760> order<00:19:23.000> to<00:19:23.159> do<00:19:23.400> this

00:19:23.630 --> 00:19:23.640 align:start position:0%
parallel to this in order to do this
 

00:19:23.640 --> 00:19:25.870 align:start position:0%
parallel to this in order to do this
because<00:19:23.960> right<00:19:24.080> now<00:19:24.240> there's<00:19:24.400> a<00:19:24.600> number<00:19:24.960> of

00:19:25.870 --> 00:19:25.880 align:start position:0%
because right now there's a number of
 

00:19:25.880 --> 00:19:28.789 align:start position:0%
because right now there's a number of
challenges<00:19:26.880> that<00:19:27.240> would<00:19:28.280> includ<00:19:28.559> will<00:19:28.679> some

00:19:28.789 --> 00:19:28.799 align:start position:0%
challenges that would includ will some
 

00:19:28.799 --> 00:19:32.510 align:start position:0%
challenges that would includ will some
of<00:19:28.960> this<00:19:29.080> work<00:19:29.320> being<00:19:29.600> paid<00:19:29.880> for<00:19:30.720> etc<00:19:31.159> etc<00:19:32.039> I

00:19:32.510 --> 00:19:32.520 align:start position:0%
of this work being paid for etc etc I
 

00:19:32.520 --> 00:19:35.470 align:start position:0%
of this work being paid for etc etc I
completly<00:19:33.120> agree<00:19:33.960> and<00:19:34.240> we<00:19:34.440> see<00:19:35.240> the

00:19:35.470 --> 00:19:35.480 align:start position:0%
completly agree and we see the
 

00:19:35.480 --> 00:19:38.789 align:start position:0%
completly agree and we see the
regulatory<00:19:36.120> push<00:19:36.400> in<00:19:36.720> parallel<00:19:37.320> to<00:19:38.320> one

00:19:38.789 --> 00:19:38.799 align:start position:0%
regulatory push in parallel to one
 

00:19:38.799 --> 00:19:41.070 align:start position:0%
regulatory push in parallel to one
investing<00:19:39.320> into<00:19:39.559> Technologies<00:19:40.440> and<00:19:40.679> and<00:19:40.919> at

00:19:41.070 --> 00:19:41.080 align:start position:0%
investing into Technologies and and at
 

00:19:41.080 --> 00:19:42.990 align:start position:0%
investing into Technologies and and at
the<00:19:41.280> same

00:19:42.990 --> 00:19:43.000 align:start position:0%
the same
 

00:19:43.000 --> 00:19:46.470 align:start position:0%
the same
time<00:19:44.000> going<00:19:44.320> to<00:19:44.600> State<00:19:45.559> uh<00:19:45.960> Corporation

00:19:46.470 --> 00:19:46.480 align:start position:0%
time going to State uh Corporation
 

00:19:46.480 --> 00:19:50.990 align:start position:0%
time going to State uh Corporation
commissions<00:19:47.000> and<00:19:47.200> going<00:19:47.480> to<00:19:48.440> um<00:19:48.559> the<00:19:48.840> RTO<00:19:50.000> pjm

00:19:50.990 --> 00:19:51.000 align:start position:0%
commissions and going to um the RTO pjm
 

00:19:51.000 --> 00:19:54.470 align:start position:0%
commissions and going to um the RTO pjm
um<00:19:51.520> and<00:19:52.039> pushing<00:19:52.440> for<00:19:53.360> moving<00:19:53.720> from<00:19:53.919> Pilots<00:19:54.280> to

00:19:54.470 --> 00:19:54.480 align:start position:0%
um and pushing for moving from Pilots to
 

00:19:54.480 --> 00:19:57.149 align:start position:0%
um and pushing for moving from Pilots to
demonstrations<00:19:55.200> of<00:19:55.400> these<00:19:55.919> Technologies<00:19:56.919> um

00:19:57.149 --> 00:19:57.159 align:start position:0%
demonstrations of these Technologies um
 

00:19:57.159 --> 00:19:58.830 align:start position:0%
demonstrations of these Technologies um
I<00:19:57.280> get<00:19:57.400> to<00:19:57.559> that<00:19:57.640> a<00:19:57.720> little<00:19:57.880> bit<00:19:58.360> the

00:19:58.830 --> 00:19:58.840 align:start position:0%
I get to that a little bit the
 

00:19:58.840 --> 00:20:00.950 align:start position:0%
I get to that a little bit the
recommendations<00:19:59.840> but<00:20:00.080> happy<00:20:00.320> to<00:20:00.679> yeah<00:20:00.880> I

00:20:00.950 --> 00:20:00.960 align:start position:0%
recommendations but happy to yeah I
 

00:20:00.960 --> 00:20:02.549 align:start position:0%
recommendations but happy to yeah I
think<00:20:01.320> that's<00:20:01.600> really<00:20:01.880> where<00:20:02.039> a<00:20:02.159> lot<00:20:02.320> of<00:20:02.400> the

00:20:02.549 --> 00:20:02.559 align:start position:0%
think that's really where a lot of the
 

00:20:02.559 --> 00:20:05.230 align:start position:0%
think that's really where a lot of the
discussion<00:20:03.039> is<00:20:03.679> because<00:20:04.679> uh<00:20:04.799> you<00:20:04.919> know<00:20:05.080> a

00:20:05.230 --> 00:20:05.240 align:start position:0%
discussion is because uh you know a
 

00:20:05.240 --> 00:20:07.870 align:start position:0%
discussion is because uh you know a
regulated<00:20:05.840> utility<00:20:06.559> is<00:20:06.840> incentivized<00:20:07.600> it's<00:20:07.720> a

00:20:07.870 --> 00:20:07.880 align:start position:0%
regulated utility is incentivized it's a
 

00:20:07.880 --> 00:20:11.710 align:start position:0%
regulated utility is incentivized it's a
Cost<00:20:08.200> Plus<00:20:09.120> benefit<00:20:09.520> model<00:20:09.919> right<00:20:10.080> so<00:20:10.400> it's<00:20:11.400> as

00:20:11.710 --> 00:20:11.720 align:start position:0%
Cost Plus benefit model right so it's as
 

00:20:11.720 --> 00:20:14.669 align:start position:0%
Cost Plus benefit model right so it's as
has<00:20:11.880> regula<00:20:12.280> utility<00:20:12.640> so<00:20:12.919> I<00:20:13.799> understand<00:20:14.000> that

00:20:14.669 --> 00:20:14.679 align:start position:0%
has regula utility so I understand that
 

00:20:14.679 --> 00:20:18.110 align:start position:0%
has regula utility so I understand that
U<00:20:14.919> speaking<00:20:15.760> uh<00:20:15.919> carefully<00:20:16.320> here<00:20:16.640> but<00:20:17.640> we<00:20:17.840> are

00:20:18.110 --> 00:20:18.120 align:start position:0%
U speaking uh carefully here but we are
 

00:20:18.120 --> 00:20:21.630 align:start position:0%
U speaking uh carefully here but we are
also<00:20:18.520> looking<00:20:19.000> at<00:20:19.960> um<00:20:20.799> what<00:20:20.919> is<00:20:21.120> the<00:20:21.320> right<00:20:21.480> way

00:20:21.630 --> 00:20:21.640 align:start position:0%
also looking at um what is the right way
 

00:20:21.640 --> 00:20:22.510 align:start position:0%
also looking at um what is the right way
to

00:20:22.510 --> 00:20:22.520 align:start position:0%
to
 

00:20:22.520 --> 00:20:25.510 align:start position:0%
to
incentivize<00:20:23.520> uh<00:20:23.919> you<00:20:24.039> know<00:20:24.440> using<00:20:24.760> a<00:20:24.919> cheaper

00:20:25.510 --> 00:20:25.520 align:start position:0%
incentivize uh you know using a cheaper
 

00:20:25.520 --> 00:20:27.430 align:start position:0%
incentivize uh you know using a cheaper
faster<00:20:25.960> technology<00:20:26.640> than<00:20:26.799> a<00:20:27.159> than<00:20:27.280> a

00:20:27.430 --> 00:20:27.440 align:start position:0%
faster technology than a than a
 

00:20:27.440 --> 00:20:28.909 align:start position:0%
faster technology than a than a
traditional<00:20:28.159> investment<00:20:28.559> that<00:20:28.679> you<00:20:28.760> would

00:20:28.909 --> 00:20:28.919 align:start position:0%
traditional investment that you would
 

00:20:28.919 --> 00:20:31.549 align:start position:0%
traditional investment that you would
earn<00:20:29.159> a<00:20:29.400> higher<00:20:29.960> you<00:20:30.080> know<00:20:30.240> rated<00:20:30.760> return<00:20:31.120> reg

00:20:31.549 --> 00:20:31.559 align:start position:0%
earn a higher you know rated return reg
 

00:20:31.559 --> 00:20:33.390 align:start position:0%
earn a higher you know rated return reg
rated

00:20:33.390 --> 00:20:33.400 align:start position:0%
rated
 

00:20:33.400 --> 00:20:36.230 align:start position:0%
rated
return<00:20:34.400> so<00:20:34.960> yeah<00:20:35.159> we<00:20:35.520> I<00:20:35.600> think<00:20:35.760> we'll<00:20:36.039> maybe

00:20:36.230 --> 00:20:36.240 align:start position:0%
return so yeah we I think we'll maybe
 

00:20:36.240 --> 00:20:38.590 align:start position:0%
return so yeah we I think we'll maybe
have<00:20:36.360> some<00:20:36.440> more<00:20:36.600> discussion<00:20:37.120> on<00:20:38.120> few<00:20:38.320> slides

00:20:38.590 --> 00:20:38.600 align:start position:0%
have some more discussion on few slides
 

00:20:38.600 --> 00:20:41.149 align:start position:0%
have some more discussion on few slides
from<00:20:38.760> now<00:20:39.159> good<00:20:39.440> so<00:20:40.360> any<00:20:40.520> other<00:20:40.760> questions<00:20:41.000> on

00:20:41.149 --> 00:20:41.159 align:start position:0%
from now good so any other questions on
 

00:20:41.159 --> 00:20:42.590 align:start position:0%
from now good so any other questions on
the

00:20:42.590 --> 00:20:42.600 align:start position:0%
the
 

00:20:42.600 --> 00:20:44.909 align:start position:0%
the
Technologies<00:20:43.600> it's<00:20:43.720> a<00:20:43.880> real<00:20:44.159> broad<00:20:44.360> overview

00:20:44.909 --> 00:20:44.919 align:start position:0%
Technologies it's a real broad overview
 

00:20:44.919 --> 00:20:46.230 align:start position:0%
Technologies it's a real broad overview
again<00:20:45.080> I'm<00:20:45.159> not<00:20:45.280> going<00:20:45.400> to<00:20:45.520> get<00:20:45.640> into<00:20:45.840> all<00:20:46.039> six

00:20:46.230 --> 00:20:46.240 align:start position:0%
again I'm not going to get into all six
 

00:20:46.240 --> 00:20:49.830 align:start position:0%
again I'm not going to get into all six
of<00:20:46.520> these<00:20:47.159> uh<00:20:47.320> today

00:20:49.830 --> 00:20:49.840 align:start position:0%
of these uh today
 

00:20:49.840 --> 00:20:51.909 align:start position:0%
of these uh today
but

00:20:51.909 --> 00:20:51.919 align:start position:0%
but
 

00:20:51.919 --> 00:20:55.149 align:start position:0%
but
okay<00:20:52.919> so

00:20:55.149 --> 00:20:55.159 align:start position:0%
okay so
 

00:20:55.159 --> 00:20:59.430 align:start position:0%
okay so
drr<00:20:56.159> so<00:20:56.760> the<00:20:57.000> industry<00:20:57.440> is<00:20:57.799> and<00:20:58.320> most<00:20:58.600> the<00:20:59.120> most

00:20:59.430 --> 00:20:59.440 align:start position:0%
drr so the industry is and most the most
 

00:20:59.440 --> 00:21:01.149 align:start position:0%
drr so the industry is and most the most
widespread<00:21:00.159> practice<00:21:00.520> across<00:21:00.760> the<00:21:00.840> industry

00:21:01.149 --> 00:21:01.159 align:start position:0%
widespread practice across the industry
 

00:21:01.159 --> 00:21:02.950 align:start position:0%
widespread practice across the industry
is<00:21:01.240> using<00:21:01.559> static<00:21:01.919> line<00:21:02.159> ratings<00:21:02.720> which<00:21:02.840> is

00:21:02.950 --> 00:21:02.960 align:start position:0%
is using static line ratings which is
 

00:21:02.960 --> 00:21:04.750 align:start position:0%
is using static line ratings which is
just<00:21:03.080> a<00:21:03.280> conservative<00:21:03.880> approach<00:21:04.200> assuming

00:21:04.750 --> 00:21:04.760 align:start position:0%
just a conservative approach assuming
 

00:21:04.760 --> 00:21:06.830 align:start position:0%
just a conservative approach assuming
kind<00:21:04.880> of<00:21:05.200> worst<00:21:05.720> case<00:21:06.200> conditions<00:21:06.520> either

00:21:06.830 --> 00:21:06.840 align:start position:0%
kind of worst case conditions either
 

00:21:06.840 --> 00:21:09.190 align:start position:0%
kind of worst case conditions either
summer<00:21:07.640> or<00:21:07.919> winter<00:21:08.280> or<00:21:08.600> sometimes<00:21:08.840> it's<00:21:09.080> it's

00:21:09.190 --> 00:21:09.200 align:start position:0%
summer or winter or sometimes it's it's
 

00:21:09.200 --> 00:21:12.669 align:start position:0%
summer or winter or sometimes it's it's
a<00:21:09.360> standard<00:21:09.720> rating<00:21:10.520> all<00:21:10.840> year<00:21:11.760> um<00:21:11.960> for<00:21:12.320> what<00:21:12.480> a

00:21:12.669 --> 00:21:12.679 align:start position:0%
a standard rating all year um for what a
 

00:21:12.679 --> 00:21:16.310 align:start position:0%
a standard rating all year um for what a
conductor<00:21:13.679> uh<00:21:14.200> the<00:21:14.360> power<00:21:14.799> conductor<00:21:15.200> can

00:21:16.310 --> 00:21:16.320 align:start position:0%
conductor uh the power conductor can
 

00:21:16.320 --> 00:21:18.909 align:start position:0%
conductor uh the power conductor can
transmit<00:21:17.320> which<00:21:17.440> you<00:21:17.559> can<00:21:17.720> see<00:21:18.240> on<00:21:18.400> the<00:21:18.640> right

00:21:18.909 --> 00:21:18.919 align:start position:0%
transmit which you can see on the right
 

00:21:18.919 --> 00:21:21.789 align:start position:0%
transmit which you can see on the right
hand<00:21:19.480> top<00:21:19.880> right<00:21:20.720> uh<00:21:20.880> you<00:21:20.960> know<00:21:21.120> there's<00:21:21.520> a<00:21:21.640> lot

00:21:21.789 --> 00:21:21.799 align:start position:0%
hand top right uh you know there's a lot
 

00:21:21.799 --> 00:21:23.590 align:start position:0%
hand top right uh you know there's a lot
of<00:21:22.159> there's<00:21:22.400> different<00:21:22.679> factors<00:21:23.000> that<00:21:23.279> affect

00:21:23.590 --> 00:21:23.600 align:start position:0%
of there's different factors that affect
 

00:21:23.600 --> 00:21:27.630 align:start position:0%
of there's different factors that affect
a<00:21:23.880> conductor's<00:21:25.039> heating<00:21:26.039> um<00:21:26.360> and<00:21:26.840> again<00:21:27.440> why

00:21:27.630 --> 00:21:27.640 align:start position:0%
a conductor's heating um and again why
 

00:21:27.640 --> 00:21:29.070 align:start position:0%
a conductor's heating um and again why
why<00:21:27.720> do<00:21:27.799> we<00:21:28.200> about<00:21:28.320> conductor<00:21:28.720> heating

00:21:29.070 --> 00:21:29.080 align:start position:0%
why do we about conductor heating
 

00:21:29.080 --> 00:21:31.510 align:start position:0%
why do we about conductor heating
because<00:21:29.799> as<00:21:29.960> transmission<00:21:30.600> lines<00:21:30.919> heat<00:21:31.120> up

00:21:31.510 --> 00:21:31.520 align:start position:0%
because as transmission lines heat up
 

00:21:31.520 --> 00:21:33.750 align:start position:0%
because as transmission lines heat up
they<00:21:31.679> sag<00:21:32.279> into<00:21:32.520> an<00:21:32.679> unsafe<00:21:33.080> area<00:21:33.320> so<00:21:33.520> there's

00:21:33.750 --> 00:21:33.760 align:start position:0%
they sag into an unsafe area so there's
 

00:21:33.760 --> 00:21:35.470 align:start position:0%
they sag into an unsafe area so there's
there's<00:21:34.039> limits<00:21:34.320> to<00:21:34.559> how<00:21:34.640> much<00:21:34.840> they<00:21:34.919> can<00:21:35.120> sag

00:21:35.470 --> 00:21:35.480 align:start position:0%
there's limits to how much they can sag
 

00:21:35.480 --> 00:21:37.789 align:start position:0%
there's limits to how much they can sag
as<00:21:35.600> well<00:21:35.840> as<00:21:36.760> um<00:21:36.960> you<00:21:37.080> know<00:21:37.360> really<00:21:37.640> high

00:21:37.789 --> 00:21:37.799 align:start position:0%
as well as um you know really high
 

00:21:37.799 --> 00:21:39.430 align:start position:0%
as well as um you know really high
temperatures<00:21:38.320> they<00:21:38.440> can<00:21:38.600> cause<00:21:38.799> a<00:21:38.919> kneeling

00:21:39.430 --> 00:21:39.440 align:start position:0%
temperatures they can cause a kneeling
 

00:21:39.440 --> 00:21:41.870 align:start position:0%
temperatures they can cause a kneeling
on<00:21:39.559> the<00:21:39.720> conductor<00:21:40.120> and<00:21:40.320> damage<00:21:40.760> the

00:21:41.870 --> 00:21:41.880 align:start position:0%
on the conductor and damage the
 

00:21:41.880 --> 00:21:43.830 align:start position:0%
on the conductor and damage the
conductor<00:21:42.880> and<00:21:43.000> so<00:21:43.320> you<00:21:43.400> know<00:21:43.559> there's

00:21:43.830 --> 00:21:43.840 align:start position:0%
conductor and so you know there's
 

00:21:43.840 --> 00:21:45.789 align:start position:0%
conductor and so you know there's
there's<00:21:44.120> three<00:21:44.400> Factor<00:21:44.919> well<00:21:45.120> really<00:21:45.320> four

00:21:45.789 --> 00:21:45.799 align:start position:0%
there's three Factor well really four
 

00:21:45.799 --> 00:21:47.029 align:start position:0%
there's three Factor well really four
one<00:21:46.039> is<00:21:46.159> how<00:21:46.240> much<00:21:46.400> current<00:21:46.640> you're<00:21:46.760> putting

00:21:47.029 --> 00:21:47.039 align:start position:0%
one is how much current you're putting
 

00:21:47.039 --> 00:21:48.590 align:start position:0%
one is how much current you're putting
through<00:21:47.440> but<00:21:47.600> other<00:21:47.799> than<00:21:48.080> the<00:21:48.240> power<00:21:48.440> you're

00:21:48.590 --> 00:21:48.600 align:start position:0%
through but other than the power you're
 

00:21:48.600 --> 00:21:51.029 align:start position:0%
through but other than the power you're
transmitting<00:21:49.520> it's<00:21:49.919> radi<00:21:50.240> of<00:21:50.400> cooling<00:21:50.760> so

00:21:51.029 --> 00:21:51.039 align:start position:0%
transmitting it's radi of cooling so
 

00:21:51.039 --> 00:21:53.110 align:start position:0%
transmitting it's radi of cooling so
what's<00:21:51.200> the<00:21:51.360> ambient<00:21:51.679> temperature<00:21:52.120> outside

00:21:53.110 --> 00:21:53.120 align:start position:0%
what's the ambient temperature outside
 

00:21:53.120 --> 00:21:54.950 align:start position:0%
what's the ambient temperature outside
how<00:21:53.279> much<00:21:53.440> is<00:21:53.799> how<00:21:53.919> much<00:21:54.080> sunlight<00:21:54.520> is<00:21:54.640> inting

00:21:54.950 --> 00:21:54.960 align:start position:0%
how much is how much sunlight is inting
 

00:21:54.960 --> 00:21:58.230 align:start position:0%
how much is how much sunlight is inting
the<00:21:55.080> conductor<00:21:55.520> or<00:21:55.720> solar<00:21:56.360> Radiance<00:21:57.360> and<00:21:57.559> then

00:21:58.230 --> 00:21:58.240 align:start position:0%
the conductor or solar Radiance and then
 

00:21:58.240 --> 00:22:00.029 align:start position:0%
the conductor or solar Radiance and then
uh<00:21:58.400> convective<00:21:58.840> pulling<00:21:59.159> or<00:21:59.320> wind<00:21:59.720> and<00:21:59.880> that

00:22:00.029 --> 00:22:00.039 align:start position:0%
uh convective pulling or wind and that
 

00:22:00.039 --> 00:22:02.669 align:start position:0%
uh convective pulling or wind and that
is<00:22:00.240> the<00:22:00.520> most<00:22:01.039> in<00:22:01.200> the<00:22:01.320> heat<00:22:01.559> equation<00:22:02.039> that<00:22:02.159> is

00:22:02.669 --> 00:22:02.679 align:start position:0%
is the most in the heat equation that is
 

00:22:02.679 --> 00:22:04.909 align:start position:0%
is the most in the heat equation that is
the<00:22:02.960> most<00:22:03.279> important<00:22:03.720> factor<00:22:04.000> is<00:22:04.120> the<00:22:04.320> wind

00:22:04.909 --> 00:22:04.919 align:start position:0%
the most important factor is the wind
 

00:22:04.919 --> 00:22:07.470 align:start position:0%
the most important factor is the wind
and<00:22:05.080> what<00:22:05.279> angle<00:22:05.600> it's<00:22:05.760> bling<00:22:06.320> against<00:22:06.559> the

00:22:07.470 --> 00:22:07.480 align:start position:0%
and what angle it's bling against the
 

00:22:07.480 --> 00:22:10.310 align:start position:0%
and what angle it's bling against the
conductor<00:22:08.480> so<00:22:08.640> FK<00:22:09.000> is<00:22:09.080> already<00:22:09.400> active<00:22:09.840> here

00:22:10.310 --> 00:22:10.320 align:start position:0%
conductor so FK is already active here
 

00:22:10.320 --> 00:22:11.350 align:start position:0%
conductor so FK is already active here
and

00:22:11.350 --> 00:22:11.360 align:start position:0%
and
 

00:22:11.360 --> 00:22:16.070 align:start position:0%
and
881<00:22:12.360> requires<00:22:13.480> utilities<00:22:14.480> by<00:22:14.720> 2025<00:22:15.640> to<00:22:15.799> use

00:22:16.070 --> 00:22:16.080 align:start position:0%
881 requires utilities by 2025 to use
 

00:22:16.080 --> 00:22:18.310 align:start position:0%
881 requires utilities by 2025 to use
ambient<00:22:16.480> adjusted<00:22:16.880> ratings<00:22:17.480> so<00:22:17.720> take<00:22:18.039> into

00:22:18.310 --> 00:22:18.320 align:start position:0%
ambient adjusted ratings so take into
 

00:22:18.320 --> 00:22:20.950 align:start position:0%
ambient adjusted ratings so take into
account<00:22:18.600> that<00:22:18.760> radi<00:22:19.240> of<00:22:19.440> cooling<00:22:20.320> on<00:22:20.480> the

00:22:20.950 --> 00:22:20.960 align:start position:0%
account that radi of cooling on the
 

00:22:20.960 --> 00:22:24.510 align:start position:0%
account that radi of cooling on the
conductor<00:22:21.960> however<00:22:22.200> that<00:22:22.440> still<00:22:23.400> uh<00:22:24.120> makes<00:22:24.360> a

00:22:24.510 --> 00:22:24.520 align:start position:0%
conductor however that still uh makes a
 

00:22:24.520 --> 00:22:26.190 align:start position:0%
conductor however that still uh makes a
lot<00:22:24.640> of<00:22:24.760> assumptions<00:22:25.320> you<00:22:25.400> know<00:22:25.559> you're<00:22:25.720> using

00:22:26.190 --> 00:22:26.200 align:start position:0%
lot of assumptions you know you're using
 

00:22:26.200 --> 00:22:29.510 align:start position:0%
lot of assumptions you know you're using
local<00:22:26.760> you're<00:22:26.919> not<00:22:27.120> using<00:22:28.200> um<00:22:28.520> local

00:22:29.510 --> 00:22:29.520 align:start position:0%
local you're not using um local
 

00:22:29.520 --> 00:22:31.710 align:start position:0%
local you're not using um local
localized<00:22:30.039> data<00:22:30.320> on<00:22:30.559> the<00:22:30.880> transmission<00:22:31.400> line

00:22:31.710 --> 00:22:31.720 align:start position:0%
localized data on the transmission line
 

00:22:31.720 --> 00:22:33.350 align:start position:0%
localized data on the transmission line
you're<00:22:32.080> you're<00:22:32.679> you<00:22:32.760> know<00:22:32.919> looking<00:22:33.159> at<00:22:33.240> a

00:22:33.350 --> 00:22:33.360 align:start position:0%
you're you're you know looking at a
 

00:22:33.360 --> 00:22:35.470 align:start position:0%
you're you're you know looking at a
broad<00:22:33.679> weather<00:22:34.039> area<00:22:34.440> and<00:22:34.640> still<00:22:35.080> having<00:22:35.320> to

00:22:35.470 --> 00:22:35.480 align:start position:0%
broad weather area and still having to
 

00:22:35.480 --> 00:22:37.510 align:start position:0%
broad weather area and still having to
use<00:22:35.799> some<00:22:36.120> conservative<00:22:36.960> assumption<00:22:37.320> so

00:22:37.510 --> 00:22:37.520 align:start position:0%
use some conservative assumption so
 

00:22:37.520 --> 00:22:41.390 align:start position:0%
use some conservative assumption so
maybe<00:22:37.760> that<00:22:37.880> gets<00:22:38.120> you<00:22:39.000> again<00:22:39.880> uh<00:22:40.039> maybe<00:22:40.919> 10<00:22:41.200> to

00:22:41.390 --> 00:22:41.400 align:start position:0%
maybe that gets you again uh maybe 10 to
 

00:22:41.400 --> 00:22:45.669 align:start position:0%
maybe that gets you again uh maybe 10 to
15%<00:22:42.000> additional<00:22:42.520> capacity<00:22:43.520> on<00:22:43.720> the<00:22:43.960> line<00:22:44.960> but

00:22:45.669 --> 00:22:45.679 align:start position:0%
15% additional capacity on the line but
 

00:22:45.679 --> 00:22:48.430 align:start position:0%
15% additional capacity on the line but
really<00:22:46.000> what<00:22:46.320> the<00:22:47.159> technology<00:22:47.720> can<00:22:47.919> enable<00:22:48.279> is

00:22:48.430 --> 00:22:48.440 align:start position:0%
really what the technology can enable is
 

00:22:48.440 --> 00:22:51.110 align:start position:0%
really what the technology can enable is
dynamic<00:22:48.799> line<00:22:49.039> range<00:22:49.360> so<00:22:49.600> putting<00:22:50.440> sensors<00:22:51.000> in

00:22:51.110 --> 00:22:51.120 align:start position:0%
dynamic line range so putting sensors in
 

00:22:51.120 --> 00:22:54.269 align:start position:0%
dynamic line range so putting sensors in
the<00:22:51.279> field<00:22:51.760> to<00:22:52.440> monitor<00:22:53.440> uh<00:22:53.600> the<00:22:53.799> assets

00:22:54.269 --> 00:22:54.279 align:start position:0%
the field to monitor uh the assets
 

00:22:54.279 --> 00:22:56.149 align:start position:0%
the field to monitor uh the assets
directly<00:22:54.960> and<00:22:55.120> take<00:22:55.320> into<00:22:55.640> account<00:22:55.960> that

00:22:56.149 --> 00:22:56.159 align:start position:0%
directly and take into account that
 

00:22:56.159 --> 00:22:58.669 align:start position:0%
directly and take into account that
solar<00:22:56.760> heating<00:22:57.200> and<00:22:57.600> most<00:22:58.039> importantly<00:22:58.520> the

00:22:58.669 --> 00:22:58.679 align:start position:0%
solar heating and most importantly the
 

00:22:58.679 --> 00:23:01.830 align:start position:0%
solar heating and most importantly the
wind<00:22:59.120> speed<00:23:00.120> u<00:23:00.279> in<00:23:01.000> conditions<00:23:01.240> on<00:23:01.400> the

00:23:01.830 --> 00:23:01.840 align:start position:0%
wind speed u in conditions on the
 

00:23:01.840 --> 00:23:04.430 align:start position:0%
wind speed u in conditions on the
conductor<00:23:02.840> and<00:23:02.960> so<00:23:03.240> you<00:23:03.360> see<00:23:03.559> it<00:23:04.159> what<00:23:04.240> does

00:23:04.430 --> 00:23:04.440 align:start position:0%
conductor and so you see it what does
 

00:23:04.440 --> 00:23:06.870 align:start position:0%
conductor and so you see it what does
that<00:23:04.559> do<00:23:04.799> on<00:23:04.960> the<00:23:05.120> graph<00:23:05.400> at<00:23:05.520> the<00:23:05.679> bottom<00:23:06.200> right

00:23:06.870 --> 00:23:06.880 align:start position:0%
that do on the graph at the bottom right
 

00:23:06.880 --> 00:23:08.870 align:start position:0%
that do on the graph at the bottom right
you<00:23:07.000> know<00:23:07.159> on<00:23:07.279> a<00:23:07.400> cool<00:23:07.720> cloudy<00:23:08.039> and<00:23:08.159> windy<00:23:08.520> day

00:23:08.870 --> 00:23:08.880 align:start position:0%
you know on a cool cloudy and windy day
 

00:23:08.880 --> 00:23:10.149 align:start position:0%
you know on a cool cloudy and windy day
when<00:23:09.000> you<00:23:09.120> take<00:23:09.279> all<00:23:09.400> those<00:23:09.559> factors<00:23:09.919> into

00:23:10.149 --> 00:23:10.159 align:start position:0%
when you take all those factors into
 

00:23:10.159 --> 00:23:11.789 align:start position:0%
when you take all those factors into
account<00:23:10.400> you<00:23:10.480> can<00:23:10.600> see<00:23:11.120> the<00:23:11.279> amount<00:23:11.600> of

00:23:11.789 --> 00:23:11.799 align:start position:0%
account you can see the amount of
 

00:23:11.799 --> 00:23:13.510 align:start position:0%
account you can see the amount of
additional<00:23:12.320> capacity<00:23:12.760> or<00:23:12.919> megawatts<00:23:13.440> that

00:23:13.510 --> 00:23:13.520 align:start position:0%
additional capacity or megawatts that
 

00:23:13.520 --> 00:23:16.590 align:start position:0%
additional capacity or megawatts that
You'<00:23:13.679> been<00:23:13.919> transmit<00:23:14.360> on<00:23:14.480> a<00:23:15.000> on<00:23:15.159> a<00:23:15.360> line<00:23:16.360> um

00:23:16.590 --> 00:23:16.600 align:start position:0%
You' been transmit on a on a line um
 

00:23:16.600 --> 00:23:19.110 align:start position:0%
You' been transmit on a on a line um
versus<00:23:17.559> you<00:23:17.679> know<00:23:17.960> even<00:23:18.200> on<00:23:18.320> a<00:23:18.480> hot<00:23:18.679> sunny<00:23:19.000> and

00:23:19.110 --> 00:23:19.120 align:start position:0%
versus you know even on a hot sunny and
 

00:23:19.120 --> 00:23:23.909 align:start position:0%
versus you know even on a hot sunny and
calm<00:23:19.440> day<00:23:19.880> it's<00:23:20.159> likely<00:23:21.320> drr<00:23:22.559> is<00:23:23.559> going<00:23:23.760> to

00:23:23.909 --> 00:23:23.919 align:start position:0%
calm day it's likely drr is going to
 

00:23:23.919 --> 00:23:25.870 align:start position:0%
calm day it's likely drr is going to
divide<00:23:24.240> Radiance<00:23:24.720> above<00:23:25.000> and<00:23:25.200> beyond<00:23:25.720> what

00:23:25.870 --> 00:23:25.880 align:start position:0%
divide Radiance above and beyond what
 

00:23:25.880 --> 00:23:30.029 align:start position:0%
divide Radiance above and beyond what
static<00:23:26.279> radi<00:23:26.679> do<00:23:27.559> and<00:23:27.919> of<00:23:28.039> course<00:23:28.640> drr<00:23:29.159> can<00:23:29.360> sit

00:23:30.029 --> 00:23:30.039 align:start position:0%
static radi do and of course drr can sit
 

00:23:30.039 --> 00:23:31.430 align:start position:0%
static radi do and of course drr can sit
prevent<00:23:30.360> you<00:23:30.480> from<00:23:30.640> hurting<00:23:30.919> your<00:23:31.039> conductor

00:23:31.430 --> 00:23:31.440 align:start position:0%
prevent you from hurting your conductor
 

00:23:31.440 --> 00:23:33.510 align:start position:0%
prevent you from hurting your conductor
you<00:23:31.520> can<00:23:31.640> see<00:23:32.000> the<00:23:32.120> line<00:23:32.360> starts<00:23:32.640> to<00:23:32.919> dip<00:23:33.400> a

00:23:33.510 --> 00:23:33.520 align:start position:0%
you can see the line starts to dip a
 

00:23:33.520 --> 00:23:35.990 align:start position:0%
you can see the line starts to dip a
little<00:23:33.799> bit<00:23:34.039> below<00:23:34.480> at<00:23:34.640> the<00:23:34.799> end<00:23:35.120> the<00:23:35.279> red<00:23:35.480> line

00:23:35.990 --> 00:23:36.000 align:start position:0%
little bit below at the end the red line
 

00:23:36.000 --> 00:23:38.230 align:start position:0%
little bit below at the end the red line
This<00:23:36.240> below<00:23:36.480> the<00:23:36.640> blue<00:23:37.039> which<00:23:37.159> is<00:23:37.720> blue<00:23:38.000> is

00:23:38.230 --> 00:23:38.240 align:start position:0%
This below the blue which is blue is
 

00:23:38.240 --> 00:23:41.630 align:start position:0%
This below the blue which is blue is
static<00:23:38.919> rating<00:23:39.919> um<00:23:40.840> there's<00:23:41.000> a<00:23:41.200> there's<00:23:41.440> times

00:23:41.630 --> 00:23:41.640 align:start position:0%
static rating um there's a there's times
 

00:23:41.640 --> 00:23:43.470 align:start position:0%
static rating um there's a there's times
when<00:23:41.760> it's<00:23:41.960> actually<00:23:42.480> not<00:23:42.679> safe<00:23:42.960> to<00:23:43.080> transmit

00:23:43.470 --> 00:23:43.480 align:start position:0%
when it's actually not safe to transmit
 

00:23:43.480 --> 00:23:46.149 align:start position:0%
when it's actually not safe to transmit
as<00:23:43.559> much<00:23:43.760> power<00:23:44.320> as<00:23:44.679> the<00:23:44.799> line<00:23:45.039> is<00:23:45.159> rated<00:23:45.520> for

00:23:46.149 --> 00:23:46.159 align:start position:0%
as much power as the line is rated for
 

00:23:46.159 --> 00:23:50.070 align:start position:0%
as much power as the line is rated for
and<00:23:46.320> the<00:23:46.600> drr<00:23:46.960> can<00:23:47.120> help<00:23:47.279> with<00:23:47.440> that<00:23:47.640> as

00:23:50.070 --> 00:23:50.080 align:start position:0%
 
 

00:23:50.080 --> 00:23:55.549 align:start position:0%
 
well<00:23:51.080> so<00:23:51.360> how<00:23:51.520> can<00:23:51.679> DLR<00:23:52.120> be<00:23:52.720> applied<00:23:53.760> so<00:23:54.760> uh<00:23:55.279> and

00:23:55.549 --> 00:23:55.559 align:start position:0%
well so how can DLR be applied so uh and
 

00:23:55.559 --> 00:23:58.029 align:start position:0%
well so how can DLR be applied so uh and
as<00:23:55.960> is<00:23:56.200> actually<00:23:57.000> partnering<00:23:57.559> with<00:23:57.880> the

00:23:58.029 --> 00:23:58.039 align:start position:0%
as is actually partnering with the
 

00:23:58.039 --> 00:23:59.590 align:start position:0%
as is actually partnering with the
company<00:23:58.440> showing<00:23:58.760> the<00:23:58.880> picture<00:23:59.120> there<00:23:59.360> line

00:23:59.590 --> 00:23:59.600 align:start position:0%
company showing the picture there line
 

00:23:59.600 --> 00:24:02.630 align:start position:0%
company showing the picture there line
Vision<00:24:00.000> our<00:24:00.279> utilities<00:24:00.760> in<00:24:00.919> Ohio<00:24:01.279> and<00:24:01.640> Indiana

00:24:02.630 --> 00:24:02.640 align:start position:0%
Vision our utilities in Ohio and Indiana
 

00:24:02.640 --> 00:24:04.789 align:start position:0%
Vision our utilities in Ohio and Indiana
but<00:24:02.880> you<00:24:03.000> know<00:24:03.240> it<00:24:03.360> can<00:24:03.559> take<00:24:04.240> less<00:24:04.440> than<00:24:04.600> two

00:24:04.789 --> 00:24:04.799 align:start position:0%
but you know it can take less than two
 

00:24:04.799 --> 00:24:07.950 align:start position:0%
but you know it can take less than two
months<00:24:05.039> to<00:24:05.240> deploy<00:24:06.159> uh<00:24:06.440> these<00:24:06.799> again<00:24:07.720> there's

00:24:07.950 --> 00:24:07.960 align:start position:0%
months to deploy uh these again there's
 

00:24:07.960 --> 00:24:09.430 align:start position:0%
months to deploy uh these again there's
different<00:24:08.279> technology<00:24:08.799> some<00:24:09.080> involve

00:24:09.430 --> 00:24:09.440 align:start position:0%
different technology some involve
 

00:24:09.440 --> 00:24:12.350 align:start position:0%
different technology some involve
sensors<00:24:09.840> on<00:24:10.080> the<00:24:10.279> line<00:24:10.799> some<00:24:11.080> involve<00:24:12.039> um<00:24:12.200> just

00:24:12.350 --> 00:24:12.360 align:start position:0%
sensors on the line some involve um just
 

00:24:12.360 --> 00:24:14.590 align:start position:0%
sensors on the line some involve um just
local<00:24:12.679> wind<00:24:13.000> State<00:24:13.640> uh

00:24:14.590 --> 00:24:14.600 align:start position:0%
local wind State uh
 

00:24:14.600 --> 00:24:18.269 align:start position:0%
local wind State uh
we<00:24:15.600> stations<00:24:16.159> or<00:24:16.559> or<00:24:17.240> anemometers<00:24:17.919> and<00:24:18.080> things

00:24:18.269 --> 00:24:18.279 align:start position:0%
we stations or or anemometers and things
 

00:24:18.279 --> 00:24:19.110 align:start position:0%
we stations or or anemometers and things
like

00:24:19.110 --> 00:24:19.120 align:start position:0%
like
 

00:24:19.120 --> 00:24:22.110 align:start position:0%
like
that<00:24:20.120> but<00:24:20.360> it<00:24:20.480> can<00:24:20.679> take<00:24:21.360> weeks<00:24:21.679> really<00:24:21.960> to

00:24:22.110 --> 00:24:22.120 align:start position:0%
that but it can take weeks really to
 

00:24:22.120 --> 00:24:24.870 align:start position:0%
that but it can take weeks really to
deploy<00:24:22.480> on<00:24:22.559> a<00:24:22.720> transmission<00:24:23.400> line<00:24:24.400> and<00:24:24.600> then

00:24:24.870 --> 00:24:24.880 align:start position:0%
deploy on a transmission line and then
 

00:24:24.880 --> 00:24:26.470 align:start position:0%
deploy on a transmission line and then
you<00:24:24.960> know<00:24:25.120> another<00:24:25.440> three<00:24:25.679> months<00:24:25.880> or<00:24:26.039> so<00:24:26.320> can

00:24:26.470 --> 00:24:26.480 align:start position:0%
you know another three months or so can
 

00:24:26.480 --> 00:24:29.870 align:start position:0%
you know another three months or so can
train<00:24:26.919> the<00:24:27.120> the<00:24:27.279> data<00:24:27.880> in<00:24:28.000> order<00:24:28.399> to<00:24:29.399> um<00:24:29.760> you

00:24:29.870 --> 00:24:29.880 align:start position:0%
train the the data in order to um you
 

00:24:29.880 --> 00:24:31.549 align:start position:0%
train the the data in order to um you
know<00:24:30.039> get<00:24:30.159> the<00:24:30.320> computational<00:24:30.799> flu<00:24:31.159> Dynamics

00:24:31.549 --> 00:24:31.559 align:start position:0%
know get the computational flu Dynamics
 

00:24:31.559 --> 00:24:34.269 align:start position:0%
know get the computational flu Dynamics
models<00:24:31.960> and<00:24:32.159> the<00:24:32.440> the<00:24:32.600> the<00:24:32.760> algorithms<00:24:33.760> to<00:24:34.159> get

00:24:34.269 --> 00:24:34.279 align:start position:0%
models and the the the algorithms to get
 

00:24:34.279 --> 00:24:37.789 align:start position:0%
models and the the the algorithms to get
to<00:24:34.440> the<00:24:34.640> point<00:24:34.960> where<00:24:35.679> um<00:24:36.080> they<00:24:36.240> can<00:24:36.799> provide

00:24:37.789 --> 00:24:37.799 align:start position:0%
to the point where um they can provide
 

00:24:37.799 --> 00:24:41.110 align:start position:0%
to the point where um they can provide
uh<00:24:37.960> Dynamic<00:24:38.440> line<00:24:39.080> readings<00:24:40.080> and<00:24:40.200> so<00:24:40.640> you<00:24:40.760> know

00:24:41.110 --> 00:24:41.120 align:start position:0%
uh Dynamic line readings and so you know
 

00:24:41.120 --> 00:24:44.630 align:start position:0%
uh Dynamic line readings and so you know
just<00:24:42.120> some<00:24:42.360> examples<00:24:42.720> in<00:24:42.840> the<00:24:42.919> industry<00:24:43.640> but

00:24:44.630 --> 00:24:44.640 align:start position:0%
just some examples in the industry but
 

00:24:44.640 --> 00:24:47.750 align:start position:0%
just some examples in the industry but
you<00:24:44.720> know<00:24:44.840> a<00:24:45.000> 500<00:24:45.360> or<00:24:45.559> half<00:24:45.720> a<00:24:45.799> million<00:24:46.120> dollar

00:24:47.750 --> 00:24:47.760 align:start position:0%
you know a 500 or half a million dollar
 

00:24:47.760 --> 00:24:51.350 align:start position:0%
you know a 500 or half a million dollar
$500,000<00:24:48.760> uh<00:24:48.880> DLR<00:24:49.399> installation<00:24:50.279> can<00:24:50.520> Offset

00:24:51.350 --> 00:24:51.360 align:start position:0%
$500,000 uh DLR installation can Offset
 

00:24:51.360 --> 00:24:53.110 align:start position:0%
$500,000 uh DLR installation can Offset
you<00:24:51.480> know<00:24:51.799> a<00:24:51.840> $10<00:24:52.159> million<00:24:52.640> transmission

00:24:53.110 --> 00:24:53.120 align:start position:0%
you know a $10 million transmission
 

00:24:53.120 --> 00:24:57.230 align:start position:0%
you know a $10 million transmission
rebuild<00:24:54.080> and<00:24:54.279> again<00:24:54.679> this<00:24:54.799> is<00:24:55.080> not<00:24:56.080> uh<00:24:57.080> not

00:24:57.230 --> 00:24:57.240 align:start position:0%
rebuild and again this is not uh not
 

00:24:57.240 --> 00:24:58.549 align:start position:0%
rebuild and again this is not uh not
saying<00:24:57.480> that<00:24:57.600> we're

00:24:58.549 --> 00:24:58.559 align:start position:0%
saying that we're
 

00:24:58.559 --> 00:25:00.350 align:start position:0%
saying that we're
never<00:24:58.840> going<00:24:58.919> to<00:24:59.039> build<00:24:59.240> transmission<00:25:00.200> of

00:25:00.350 --> 00:25:00.360 align:start position:0%
never going to build transmission of
 

00:25:00.360 --> 00:25:02.870 align:start position:0%
never going to build transmission of
course<00:25:00.679> transmission<00:25:01.159> is<00:25:01.320> a<00:25:01.640> solution<00:25:02.200> it's<00:25:02.320> a

00:25:02.870 --> 00:25:02.880 align:start position:0%
course transmission is a solution it's a
 

00:25:02.880 --> 00:25:04.830 align:start position:0%
course transmission is a solution it's a
yes<00:25:03.159> and<00:25:03.559> we're<00:25:03.720> going<00:25:03.840> to<00:25:03.919> build

00:25:04.830 --> 00:25:04.840 align:start position:0%
yes and we're going to build
 

00:25:04.840 --> 00:25:08.470 align:start position:0%
yes and we're going to build
transmission<00:25:05.840> but<00:25:06.480> drr<00:25:07.440> can<00:25:07.720> in<00:25:07.840> a<00:25:08.000> targeted

00:25:08.470 --> 00:25:08.480 align:start position:0%
transmission but drr can in a targeted
 

00:25:08.480 --> 00:25:10.310 align:start position:0%
transmission but drr can in a targeted
sense<00:25:08.840> if<00:25:08.919> you're<00:25:09.120> building<00:25:09.720> a<00:25:10.120> new

00:25:10.310 --> 00:25:10.320 align:start position:0%
sense if you're building a new
 

00:25:10.320 --> 00:25:14.070 align:start position:0%
sense if you're building a new
transition<00:25:10.880> line<00:25:11.080> to<00:25:11.200> solve<00:25:11.520> a<00:25:12.240> 10%

00:25:14.070 --> 00:25:14.080 align:start position:0%
transition line to solve a 10%
 

00:25:14.080 --> 00:25:18.110 align:start position:0%
transition line to solve a 10%
overload<00:25:15.080> that's<00:25:15.240> a<00:25:15.440> great<00:25:15.640> DLR<00:25:16.600> solution<00:25:17.600> um

00:25:18.110 --> 00:25:18.120 align:start position:0%
overload that's a great DLR solution um
 

00:25:18.120 --> 00:25:20.070 align:start position:0%
overload that's a great DLR solution um
now<00:25:18.279> if<00:25:18.399> you're<00:25:18.799> if<00:25:18.960> you<00:25:19.200> if<00:25:19.320> you<00:25:19.399> have<00:25:19.679> 100%

00:25:20.070 --> 00:25:20.080 align:start position:0%
now if you're if you if you have 100%
 

00:25:20.080 --> 00:25:22.950 align:start position:0%
now if you're if you if you have 100%
overload<00:25:20.760> DLR<00:25:21.720> is<00:25:21.919> not<00:25:22.520> uh<00:25:22.640> you're<00:25:22.760> going<00:25:22.840> to

00:25:22.950 --> 00:25:22.960 align:start position:0%
overload DLR is not uh you're going to
 

00:25:22.960 --> 00:25:26.470 align:start position:0%
overload DLR is not uh you're going to
need<00:25:23.159> more<00:25:23.360> transmission<00:25:24.200> right<00:25:25.159> uh<00:25:25.600> but

00:25:26.470 --> 00:25:26.480 align:start position:0%
need more transmission right uh but
 

00:25:26.480 --> 00:25:28.510 align:start position:0%
need more transmission right uh but
we've<00:25:26.720> seen<00:25:27.159> instances<00:25:27.799> is<00:25:28.200> in<00:25:28.320> our

00:25:28.510 --> 00:25:28.520 align:start position:0%
we've seen instances is in our
 

00:25:28.520 --> 00:25:30.389 align:start position:0%
we've seen instances is in our
experience<00:25:29.039> where<00:25:29.399> we<00:25:29.600> can<00:25:29.919> we've<00:25:30.080> been<00:25:30.240> able

00:25:30.389 --> 00:25:30.399 align:start position:0%
experience where we can we've been able
 

00:25:30.399 --> 00:25:32.950 align:start position:0%
experience where we can we've been able
to<00:25:30.600> offset<00:25:31.440> potentially<00:25:31.840> offset<00:25:32.200> major

00:25:32.950 --> 00:25:32.960 align:start position:0%
to offset potentially offset major
 

00:25:32.960 --> 00:25:35.710 align:start position:0%
to offset potentially offset major
transmission<00:25:33.720> builds<00:25:34.720> and<00:25:34.840> this<00:25:34.960> is<00:25:35.120> proven

00:25:35.710 --> 00:25:35.720 align:start position:0%
transmission builds and this is proven
 

00:25:35.720 --> 00:25:38.710 align:start position:0%
transmission builds and this is proven
with<00:25:35.880> B<00:25:36.360> so<00:25:36.960> actually<00:25:37.240> in<00:25:37.399> pjm<00:25:38.159> right<00:25:38.320> now

00:25:38.710 --> 00:25:38.720 align:start position:0%
with B so actually in pjm right now
 

00:25:38.720 --> 00:25:41.070 align:start position:0%
with B so actually in pjm right now
they're<00:25:38.960> using<00:25:39.360> DLR<00:25:40.200> in<00:25:40.360> their<00:25:40.559> transmission

00:25:41.070 --> 00:25:41.080 align:start position:0%
they're using DLR in their transmission
 

00:25:41.080 --> 00:25:44.909 align:start position:0%
they're using DLR in their transmission
operations<00:25:41.919> control<00:25:42.520> center<00:25:43.520> um<00:25:43.960> PPL<00:25:44.559> won<00:25:44.760> an

00:25:44.909 --> 00:25:44.919 align:start position:0%
operations control center um PPL won an
 

00:25:44.919 --> 00:25:46.909 align:start position:0%
operations control center um PPL won an
Edison<00:25:45.320> award<00:25:45.600> for<00:25:45.880> this<00:25:46.200> which<00:25:46.320> is<00:25:46.440> a

00:25:46.909 --> 00:25:46.919 align:start position:0%
Edison award for this which is a
 

00:25:46.919 --> 00:25:48.710 align:start position:0%
Edison award for this which is a
industry<00:25:47.320> Innovation<00:25:47.960> so<00:25:48.120> they're<00:25:48.279> using<00:25:48.520> it

00:25:48.710 --> 00:25:48.720 align:start position:0%
industry Innovation so they're using it
 

00:25:48.720 --> 00:25:50.630 align:start position:0%
industry Innovation so they're using it
now<00:25:48.880> but<00:25:49.000> are<00:25:49.200> they<00:25:49.440> are<00:25:49.600> they<00:25:50.080> using<00:25:50.320> it<00:25:50.440> to

00:25:50.630 --> 00:25:50.640 align:start position:0%
now but are they are they using it to
 

00:25:50.640 --> 00:25:53.549 align:start position:0%
now but are they are they using it to
evaluate<00:25:51.440> projects<00:25:52.360> entering<00:25:52.720> a

00:25:53.549 --> 00:25:53.559 align:start position:0%
evaluate projects entering a
 

00:25:53.559 --> 00:25:56.470 align:start position:0%
evaluate projects entering a
que<00:25:54.559> they're<00:25:54.799> using<00:25:55.399> great<00:25:55.760> question<00:25:56.279> they're

00:25:56.470 --> 00:25:56.480 align:start position:0%
que they're using great question they're
 

00:25:56.480 --> 00:26:00.190 align:start position:0%
que they're using great question they're
using<00:25:56.760> an<00:25:57.000> operation<00:25:57.799> right<00:25:58.080> right<00:25:58.279> now<00:25:59.200> not

00:26:00.190 --> 00:26:00.200 align:start position:0%
using an operation right right now not
 

00:26:00.200 --> 00:26:01.950 align:start position:0%
using an operation right right now not
and<00:26:00.399> that<00:26:00.880> I'm<00:26:01.120> glad<00:26:01.360> you<00:26:01.520> brought<00:26:01.720> that<00:26:01.799> up

00:26:01.950 --> 00:26:01.960 align:start position:0%
and that I'm glad you brought that up
 

00:26:01.960 --> 00:26:04.630 align:start position:0%
and that I'm glad you brought that up
because<00:26:02.159> that<00:26:02.240> is<00:26:02.480> the<00:26:03.080> the<00:26:03.360> biggest<00:26:04.039> push<00:26:04.480> and

00:26:04.630 --> 00:26:04.640 align:start position:0%
because that is the the biggest push and
 

00:26:04.640 --> 00:26:07.830 align:start position:0%
because that is the the biggest push and
that<00:26:04.799> goes<00:26:05.039> back<00:26:05.159> to<00:26:05.320> Paul's<00:26:05.679> question<00:26:05.960> on<00:26:06.279> on

00:26:07.830 --> 00:26:07.840 align:start position:0%
that goes back to Paul's question on on
 

00:26:07.840 --> 00:26:10.710 align:start position:0%
that goes back to Paul's question on on
regulatory<00:26:08.840> it<00:26:09.000> needs<00:26:09.320> to<00:26:09.520> be<00:26:09.840> a<00:26:10.039> planning

00:26:10.710 --> 00:26:10.720 align:start position:0%
regulatory it needs to be a planning
 

00:26:10.720 --> 00:26:14.070 align:start position:0%
regulatory it needs to be a planning
solution<00:26:11.720> not<00:26:12.080> just<00:26:12.720> an<00:26:12.919> operational

00:26:14.070 --> 00:26:14.080 align:start position:0%
solution not just an operational
 

00:26:14.080 --> 00:26:17.029 align:start position:0%
solution not just an operational
solution<00:26:15.080> and<00:26:15.320> those<00:26:15.679> those<00:26:15.880> Horizons<00:26:16.559> are<00:26:16.919> in

00:26:17.029 --> 00:26:17.039 align:start position:0%
solution and those those Horizons are in
 

00:26:17.039 --> 00:26:19.909 align:start position:0%
solution and those those Horizons are in
the<00:26:17.120> industry<00:26:17.600> are<00:26:18.600> uh<00:26:18.760> melting<00:26:19.399> together

00:26:19.909 --> 00:26:19.919 align:start position:0%
the industry are uh melting together
 

00:26:19.919 --> 00:26:22.110 align:start position:0%
the industry are uh melting together
more<00:26:20.279> as<00:26:20.679> software<00:26:21.120> tools<00:26:21.440> and<00:26:21.640> forecasting

00:26:22.110 --> 00:26:22.120 align:start position:0%
more as software tools and forecasting
 

00:26:22.120 --> 00:26:25.590 align:start position:0%
more as software tools and forecasting
gets<00:26:22.399> better<00:26:23.399> um<00:26:24.080> but<00:26:24.240> it's<00:26:24.520> it's<00:26:24.760> it's<00:26:24.880> a<00:26:25.360> push

00:26:25.590 --> 00:26:25.600 align:start position:0%
gets better um but it's it's it's a push
 

00:26:25.600 --> 00:26:28.310 align:start position:0%
gets better um but it's it's it's a push
we<00:26:25.720> need<00:26:25.840> to<00:26:25.960> make<00:26:26.120> in<00:26:26.279> the<00:26:26.399> industry<00:26:27.399> uh

00:26:28.310 --> 00:26:28.320 align:start position:0%
we need to make in the industry uh
 

00:26:28.320 --> 00:26:32.710 align:start position:0%
we need to make in the industry uh
to<00:26:28.760> actually<00:26:29.039> make<00:26:29.159> a<00:26:29.240> no<00:26:29.399> planning

00:26:32.710 --> 00:26:32.720 align:start position:0%
 
 

00:26:32.720 --> 00:26:35.149 align:start position:0%
 
solution<00:26:33.720> okay<00:26:34.200> was<00:26:34.360> just

00:26:35.149 --> 00:26:35.159 align:start position:0%
solution okay was just
 

00:26:35.159 --> 00:26:40.070 align:start position:0%
solution okay was just
PPL<00:26:36.159> yes<00:26:36.919> now<00:26:37.760> others<00:26:38.760> um<00:26:39.240> including<00:26:39.919> I<00:26:39.960> think

00:26:40.070 --> 00:26:40.080 align:start position:0%
PPL yes now others um including I think
 

00:26:40.080 --> 00:26:41.909 align:start position:0%
PPL yes now others um including I think
some<00:26:40.240> Utilities<00:26:40.600> in<00:26:40.720> Virginia<00:26:41.159> do<00:26:41.559> have

00:26:41.909 --> 00:26:41.919 align:start position:0%
some Utilities in Virginia do have
 

00:26:41.919 --> 00:26:45.669 align:start position:0%
some Utilities in Virginia do have
active<00:26:42.760> Pilots<00:26:43.760> of<00:26:44.000> drr<00:26:44.760> technology<00:26:45.399> I<00:26:45.520> think

00:26:45.669 --> 00:26:45.679 align:start position:0%
active Pilots of drr technology I think
 

00:26:45.679 --> 00:26:48.389 align:start position:0%
active Pilots of drr technology I think
Dominion<00:26:46.240> for<00:26:46.399> instance<00:26:46.840> has<00:26:47.440> uh<00:26:47.679> some<00:26:48.000> pil

00:26:48.389 --> 00:26:48.399 align:start position:0%
Dominion for instance has uh some pil
 

00:26:48.399 --> 00:26:50.830 align:start position:0%
Dominion for instance has uh some pil
with<00:26:48.520> line<00:26:48.919> V<00:26:49.240> Vision<00:26:49.559> or<00:26:50.080> I'm<00:26:50.200> not<00:26:50.320> sure

00:26:50.830 --> 00:26:50.840 align:start position:0%
with line V Vision or I'm not sure
 

00:26:50.840 --> 00:26:53.950 align:start position:0%
with line V Vision or I'm not sure
exactly<00:26:51.240> the<00:26:51.520> vendors<00:26:52.520> but<00:26:53.039> um<00:26:53.399> just<00:26:53.559> on<00:26:53.760> some

00:26:53.950 --> 00:26:53.960 align:start position:0%
exactly the vendors but um just on some
 

00:26:53.960 --> 00:26:57.310 align:start position:0%
exactly the vendors but um just on some
brief<00:26:54.279> research<00:26:55.159> yes<00:26:56.159> than<00:26:56.679> so<00:26:57.080> I'm<00:26:57.200> just

00:26:57.310 --> 00:26:57.320 align:start position:0%
brief research yes than so I'm just
 

00:26:57.320 --> 00:26:59.950 align:start position:0%
brief research yes than so I'm just
curious<00:26:58.000> yeah<00:26:58.320> so<00:26:58.520> this<00:26:58.640> is<00:26:58.880> monitoring<00:26:59.640> the

00:26:59.950 --> 00:26:59.960 align:start position:0%
curious yeah so this is monitoring the
 

00:26:59.960 --> 00:27:02.750 align:start position:0%
curious yeah so this is monitoring the
conditions<00:27:00.399> on<00:27:00.559> the<00:27:00.720> line<00:27:01.679> what<00:27:01.840> is<00:27:02.000> it<00:27:02.240> doing

00:27:02.750 --> 00:27:02.760 align:start position:0%
conditions on the line what is it doing
 

00:27:02.760 --> 00:27:07.149 align:start position:0%
conditions on the line what is it doing
to<00:27:03.080> actually<00:27:04.039> control<00:27:04.760> the<00:27:05.679> the<00:27:06.159> conditions

00:27:07.149 --> 00:27:07.159 align:start position:0%
to actually control the the conditions
 

00:27:07.159 --> 00:27:10.549 align:start position:0%
to actually control the the conditions
yeah<00:27:07.320> so<00:27:07.559> it's<00:27:07.760> it's<00:27:08.200> monitoring<00:27:09.200> when<00:27:09.840> um

00:27:10.549 --> 00:27:10.559 align:start position:0%
yeah so it's it's monitoring when um
 

00:27:10.559 --> 00:27:12.110 align:start position:0%
yeah so it's it's monitoring when um
again<00:27:11.080> there's<00:27:11.320> different<00:27:11.600> Technologies

00:27:12.110 --> 00:27:12.120 align:start position:0%
again there's different Technologies
 

00:27:12.120 --> 00:27:14.190 align:start position:0%
again there's different Technologies
line<00:27:12.360> Vision<00:27:12.640> uses<00:27:12.880> a<00:27:13.000> lar<00:27:13.360> sensor<00:27:13.760> you<00:27:13.919> can

00:27:14.190 --> 00:27:14.200 align:start position:0%
line Vision uses a lar sensor you can
 

00:27:14.200 --> 00:27:16.110 align:start position:0%
line Vision uses a lar sensor you can
see<00:27:14.360> at<00:27:14.480> the<00:27:14.679> top<00:27:14.919> there<00:27:15.120> that<00:27:15.320> actually<00:27:15.960> is

00:27:16.110 --> 00:27:16.120 align:start position:0%
see at the top there that actually is
 

00:27:16.120 --> 00:27:18.269 align:start position:0%
see at the top there that actually is
going<00:27:16.360> to<00:27:17.080> tell<00:27:17.360> you<00:27:17.720> how<00:27:17.880> much<00:27:18.080> your

00:27:18.269 --> 00:27:18.279 align:start position:0%
going to tell you how much your
 

00:27:18.279 --> 00:27:19.669 align:start position:0%
going to tell you how much your
transmission<00:27:18.679> line<00:27:18.919> is

00:27:19.669 --> 00:27:19.679 align:start position:0%
transmission line is
 

00:27:19.679 --> 00:27:22.149 align:start position:0%
transmission line is
sagging<00:27:20.679> um<00:27:21.159> but<00:27:21.320> there's<00:27:21.559> others<00:27:21.799> that<00:27:22.000> just

00:27:22.149 --> 00:27:22.159 align:start position:0%
sagging um but there's others that just
 

00:27:22.159 --> 00:27:26.230 align:start position:0%
sagging um but there's others that just
use<00:27:22.679> localized<00:27:23.279> wind<00:27:23.559> speed<00:27:24.279> and<00:27:24.559> and<00:27:25.320> and<00:27:25.840> um

00:27:26.230 --> 00:27:26.240 align:start position:0%
use localized wind speed and and and um
 

00:27:26.240 --> 00:27:28.310 align:start position:0%
use localized wind speed and and and um
all<00:27:26.399> of<00:27:26.559> them<00:27:26.960> use<00:27:27.600> some<00:27:27.799> kind<00:27:27.960> of<00:27:28.080> weather

00:27:28.310 --> 00:27:28.320 align:start position:0%
all of them use some kind of weather
 

00:27:28.320 --> 00:27:30.190 align:start position:0%
all of them use some kind of weather
data<00:27:28.919> right<00:27:29.279> right<00:27:29.440> but<00:27:29.559> it's<00:27:29.679> not<00:27:29.919> actually

00:27:30.190 --> 00:27:30.200 align:start position:0%
data right right but it's not actually
 

00:27:30.200 --> 00:27:31.750 align:start position:0%
data right right but it's not actually
controlling<00:27:30.679> the<00:27:30.799> power<00:27:31.039> flow<00:27:31.279> it's<00:27:31.520> just

00:27:31.750 --> 00:27:31.760 align:start position:0%
controlling the power flow it's just
 

00:27:31.760 --> 00:27:33.750 align:start position:0%
controlling the power flow it's just
informing<00:27:32.440> the<00:27:32.559> operation<00:27:33.000> cing<00:27:33.600> the

00:27:33.750 --> 00:27:33.760 align:start position:0%
informing the operation cing the
 

00:27:33.760 --> 00:27:37.149 align:start position:0%
informing the operation cing the
Operation<00:27:34.360> Center<00:27:35.360> um<00:27:35.720> hey<00:27:36.200> you<00:27:36.360> are<00:27:36.559> able<00:27:36.799> to

00:27:37.149 --> 00:27:37.159 align:start position:0%
Operation Center um hey you are able to
 

00:27:37.159 --> 00:27:40.029 align:start position:0%
Operation Center um hey you are able to
transmit<00:27:38.159> 1,600<00:27:38.919> amps<00:27:39.200> on<00:27:39.320> this

00:27:40.029 --> 00:27:40.039 align:start position:0%
transmit 1,600 amps on this
 

00:27:40.039 --> 00:27:43.070 align:start position:0%
transmit 1,600 amps on this
line<00:27:41.039> at<00:27:41.240> this<00:27:41.440> time<00:27:41.799> and<00:27:41.919> it's<00:27:42.159> forecasting

00:27:43.070 --> 00:27:43.080 align:start position:0%
line at this time and it's forecasting
 

00:27:43.080 --> 00:27:44.630 align:start position:0%
line at this time and it's forecasting
that<00:27:43.360> right<00:27:43.480> because<00:27:43.640> it's<00:27:43.760> not<00:27:44.000> valuable

00:27:44.630 --> 00:27:44.640 align:start position:0%
that right because it's not valuable
 

00:27:44.640 --> 00:27:46.990 align:start position:0%
that right because it's not valuable
they<00:27:44.799> can't<00:27:45.200> if<00:27:45.360> you<00:27:45.519> can't<00:27:45.880> forecast<00:27:46.399> out

00:27:46.990 --> 00:27:47.000 align:start position:0%
they can't if you can't forecast out
 

00:27:47.000 --> 00:27:49.389 align:start position:0%
they can't if you can't forecast out
because<00:27:47.240> a<00:27:47.360> lot<00:27:47.559> of<00:27:48.360> um<00:27:48.559> you<00:27:48.640> know<00:27:48.840> planning

00:27:49.389 --> 00:27:49.399 align:start position:0%
because a lot of um you know planning
 

00:27:49.399 --> 00:27:51.070 align:start position:0%
because a lot of um you know planning
and<00:27:49.679> and<00:27:49.880> transmission<00:27:50.360> operations<00:27:50.760> happens

00:27:51.070 --> 00:27:51.080 align:start position:0%
and and transmission operations happens
 

00:27:51.080 --> 00:27:53.269 align:start position:0%
and and transmission operations happens
in<00:27:51.240> like<00:27:51.360> you<00:27:51.440> know<00:27:51.919> day<00:27:52.159> ahead<00:27:53.120> uh

00:27:53.269 --> 00:27:53.279 align:start position:0%
in like you know day ahead uh
 

00:27:53.279 --> 00:27:55.590 align:start position:0%
in like you know day ahead uh
reliability<00:27:54.000> studies<00:27:54.399> and<00:27:54.559> day<00:27:54.720> Ahad<00:27:55.000> markets

00:27:55.590 --> 00:27:55.600 align:start position:0%
reliability studies and day Ahad markets
 

00:27:55.600 --> 00:27:58.110 align:start position:0%
reliability studies and day Ahad markets
that<00:27:55.720> are<00:27:55.880> Bid<00:27:56.159> into<00:27:56.480> for<00:27:56.720> generators

00:27:58.110 --> 00:27:58.120 align:start position:0%
that are Bid into for generators
 

00:27:58.120 --> 00:28:00.509 align:start position:0%
that are Bid into for generators
um<00:27:58.399> so<00:27:58.679> yeah<00:27:59.039> typically<00:27:59.440> they<00:27:59.559> can<00:27:59.720> forecast

00:28:00.509 --> 00:28:00.519 align:start position:0%
um so yeah typically they can forecast
 

00:28:00.519 --> 00:28:01.990 align:start position:0%
um so yeah typically they can forecast
two<00:28:00.760> weeks<00:28:00.960> out<00:28:01.200> but<00:28:01.320> you<00:28:01.519> know<00:28:01.720> weather

00:28:01.990 --> 00:28:02.000 align:start position:0%
two weeks out but you know weather
 

00:28:02.000 --> 00:28:04.070 align:start position:0%
two weeks out but you know weather
forecast<00:28:02.440> two<00:28:02.559> weeks<00:28:02.720> out<00:28:02.880> are<00:28:03.320> not<00:28:03.600> the<00:28:03.799> most

00:28:04.070 --> 00:28:04.080 align:start position:0%
forecast two weeks out are not the most
 

00:28:04.080 --> 00:28:05.789 align:start position:0%
forecast two weeks out are not the most
accurate<00:28:04.360> in<00:28:04.480> the<00:28:04.600> world<00:28:05.080> so<00:28:05.279> they're<00:28:05.519> more

00:28:05.789 --> 00:28:05.799 align:start position:0%
accurate in the world so they're more
 

00:28:05.799 --> 00:28:08.630 align:start position:0%
accurate in the world so they're more
accurate<00:28:06.120> of<00:28:06.320> course<00:28:07.039> uh<00:28:07.200> coming

00:28:08.630 --> 00:28:08.640 align:start position:0%
accurate of course uh coming
 

00:28:08.640 --> 00:28:11.190 align:start position:0%
accurate of course uh coming
into<00:28:09.640> Horizon<00:28:10.240> I'm<00:28:10.399> sorry<00:28:10.600> another<00:28:10.880> question

00:28:11.190 --> 00:28:11.200 align:start position:0%
into Horizon I'm sorry another question
 

00:28:11.200 --> 00:28:13.710 align:start position:0%
into Horizon I'm sorry another question
so<00:28:12.200> based<00:28:12.440> on<00:28:12.679> that<00:28:12.799> it<00:28:12.880> seems<00:28:13.120> to<00:28:13.240> me<00:28:13.399> that

00:28:13.710 --> 00:28:13.720 align:start position:0%
so based on that it seems to me that
 

00:28:13.720 --> 00:28:16.830 align:start position:0%
so based on that it seems to me that
your<00:28:14.080> your<00:28:14.279> best<00:28:14.600> capacity<00:28:15.440> would<00:28:15.679> be<00:28:16.159> during

00:28:16.830 --> 00:28:16.840 align:start position:0%
your your best capacity would be during
 

00:28:16.840 --> 00:28:20.149 align:start position:0%
your your best capacity would be during
the<00:28:17.159> winter<00:28:18.159> is<00:28:18.360> that<00:28:18.679> correct<00:28:19.600> it's<00:28:19.760> actually

00:28:20.149 --> 00:28:20.159 align:start position:0%
the winter is that correct it's actually
 

00:28:20.159 --> 00:28:23.350 align:start position:0%
the winter is that correct it's actually
the<00:28:20.279> shoulder<00:28:20.760> Seasons<00:28:21.440> okay<00:28:22.120> usually<00:28:23.120> yeah

00:28:23.350 --> 00:28:23.360 align:start position:0%
the shoulder Seasons okay usually yeah
 

00:28:23.360 --> 00:28:26.830 align:start position:0%
the shoulder Seasons okay usually yeah
but<00:28:23.519> not<00:28:23.799> when<00:28:24.720> the<00:28:25.279> demand<00:28:26.279> Capac<00:28:26.679> is<00:28:26.720> going

00:28:26.830 --> 00:28:26.840 align:start position:0%
but not when the demand Capac is going
 

00:28:26.840 --> 00:28:29.509 align:start position:0%
but not when the demand Capac is going
to<00:28:26.919> be<00:28:27.039> the<00:28:27.159> highest

00:28:29.509 --> 00:28:29.519 align:start position:0%
 
 

00:28:29.519 --> 00:28:33.830 align:start position:0%
 
um<00:28:30.200> yes<00:28:30.519> so<00:28:31.000> I<00:28:31.279> I<00:28:31.880> going<00:28:32.159> back<00:28:32.440> to<00:28:33.440> one<00:28:33.600> more

00:28:33.830 --> 00:28:33.840 align:start position:0%
um yes so I I going back to one more
 

00:28:33.840 --> 00:28:35.789 align:start position:0%
um yes so I I going back to one more
slide<00:28:34.159> like<00:28:34.279> you<00:28:34.440> see<00:28:34.679> hot<00:28:34.880> sunny<00:28:35.279> calm<00:28:35.600> so

00:28:35.789 --> 00:28:35.799 align:start position:0%
slide like you see hot sunny calm so
 

00:28:35.799 --> 00:28:38.149 align:start position:0%
slide like you see hot sunny calm so
like<00:28:35.919> so<00:28:36.080> a<00:28:36.200> day<00:28:36.399> like<00:28:36.559> today<00:28:36.960> it's<00:28:37.120> 90<00:28:37.480> degrees

00:28:38.149 --> 00:28:38.159 align:start position:0%
like so a day like today it's 90 degrees
 

00:28:38.159 --> 00:28:41.389 align:start position:0%
like so a day like today it's 90 degrees
maybe<00:28:38.360> there's<00:28:38.559> not<00:28:38.640> a<00:28:38.760> lot<00:28:38.880> of<00:28:39.240> wind<00:28:40.240> um<00:28:41.120> yeah

00:28:41.389 --> 00:28:41.399 align:start position:0%
maybe there's not a lot of wind um yeah
 

00:28:41.399 --> 00:28:43.149 align:start position:0%
maybe there's not a lot of wind um yeah
you're<00:28:41.640> not<00:28:42.000> going<00:28:42.279> you<00:28:42.519> might<00:28:42.679> not<00:28:42.840> get<00:28:43.000> as

00:28:43.149 --> 00:28:43.159 align:start position:0%
you're not going you might not get as
 

00:28:43.159 --> 00:28:46.029 align:start position:0%
you're not going you might not get as
much<00:28:43.519> capacity<00:28:44.480> out<00:28:44.600> of<00:28:44.679> the<00:28:44.799> line<00:28:45.039> so<00:28:45.320> that

00:28:46.029 --> 00:28:46.039 align:start position:0%
much capacity out of the line so that
 

00:28:46.039 --> 00:28:48.110 align:start position:0%
much capacity out of the line so that
that<00:28:46.200> has<00:28:46.320> to<00:28:46.440> be<00:28:46.679> factored<00:28:47.159> in<00:28:47.679> to<00:28:47.960> your

00:28:48.110 --> 00:28:48.120 align:start position:0%
that has to be factored in to your
 

00:28:48.120 --> 00:28:50.710 align:start position:0%
that has to be factored in to your
solution<00:28:48.559> now<00:28:48.720> you<00:28:48.880> might<00:28:49.159> get<00:28:49.480> still<00:28:50.120> an

00:28:50.710 --> 00:28:50.720 align:start position:0%
solution now you might get still an
 

00:28:50.720 --> 00:28:53.350 align:start position:0%
solution now you might get still an
additional<00:28:51.720> 10%<00:28:52.440> and<00:28:52.559> that<00:28:52.679> might<00:28:52.840> be<00:28:52.960> all<00:28:53.159> you

00:28:53.350 --> 00:28:53.360 align:start position:0%
additional 10% and that might be all you
 

00:28:53.360 --> 00:28:57.669 align:start position:0%
additional 10% and that might be all you
need<00:28:54.240> right<00:28:55.399> and<00:28:56.399> and<00:28:56.600> there's<00:28:56.919> you<00:28:57.000> know<00:28:57.159> two

00:28:57.669 --> 00:28:57.679 align:start position:0%
need right and and there's you know two
 

00:28:57.679 --> 00:29:01.350 align:start position:0%
need right and and there's you know two
2%<00:28:58.200> of<00:28:58.320> the<00:28:58.519> year<00:28:59.000> that<00:28:59.159> you<00:28:59.600> might<00:29:00.600> uh<00:29:00.840> you<00:29:01.080> not

00:29:01.350 --> 00:29:01.360 align:start position:0%
2% of the year that you might uh you not
 

00:29:01.360 --> 00:29:04.630 align:start position:0%
2% of the year that you might uh you not
have<00:29:01.559> more<00:29:01.799> capacity<00:29:02.279> than<00:29:02.519> static<00:29:02.840> line<00:29:03.640> read

00:29:04.630 --> 00:29:04.640 align:start position:0%
have more capacity than static line read
 

00:29:04.640 --> 00:29:06.990 align:start position:0%
have more capacity than static line read
can<00:29:04.799> I<00:29:05.279> yeah<00:29:05.519> SP<00:29:05.799> a<00:29:05.880> little<00:29:06.039> on<00:29:06.200> that<00:29:06.399> because<00:29:06.799> I

00:29:06.990 --> 00:29:07.000 align:start position:0%
can I yeah SP a little on that because I
 

00:29:07.000 --> 00:29:09.909 align:start position:0%
can I yeah SP a little on that because I
I<00:29:07.080> think<00:29:07.279> what<00:29:07.600> John<00:29:08.600> where<00:29:08.760> you<00:29:08.880> were<00:29:09.120> going

00:29:09.909 --> 00:29:09.919 align:start position:0%
I think what John where you were going
 

00:29:09.919 --> 00:29:11.830 align:start position:0%
I think what John where you were going
was<00:29:10.279> that<00:29:10.600> because<00:29:10.840> it's<00:29:11.080> colder<00:29:11.679> because

00:29:11.830 --> 00:29:11.840 align:start position:0%
was that because it's colder because
 

00:29:11.840 --> 00:29:15.830 align:start position:0%
was that because it's colder because
you're<00:29:12.120> left<00:29:12.600> there<00:29:13.200> yeah<00:29:13.399> you<00:29:13.559> get<00:29:14.360> more<00:29:15.360> head

00:29:15.830 --> 00:29:15.840 align:start position:0%
you're left there yeah you get more head
 

00:29:15.840 --> 00:29:18.750 align:start position:0%
you're left there yeah you get more head
but<00:29:16.080> because<00:29:16.640> many<00:29:17.039> utilities<00:29:18.039> have<00:29:18.360> winter

00:29:18.750 --> 00:29:18.760 align:start position:0%
but because many utilities have winter
 

00:29:18.760 --> 00:29:21.110 align:start position:0%
but because many utilities have winter
peaking

00:29:21.110 --> 00:29:21.120 align:start position:0%
peaking
 

00:29:21.120 --> 00:29:23.389 align:start position:0%
peaking
load<00:29:22.120> available

00:29:23.389 --> 00:29:23.399 align:start position:0%
load available
 

00:29:23.399 --> 00:29:25.470 align:start position:0%
load available
capacity<00:29:24.399> even<00:29:24.600> though<00:29:24.720> you<00:29:24.840> do<00:29:25.039> get<00:29:25.200> more

00:29:25.470 --> 00:29:25.480 align:start position:0%
capacity even though you do get more
 

00:29:25.480 --> 00:29:27.710 align:start position:0%
capacity even though you do get more
margin<00:29:26.039> as<00:29:26.120> you<00:29:26.240> can<00:29:26.320> see<00:29:27.000> look<00:29:27.360> wor<00:29:27.600> case

00:29:27.710 --> 00:29:27.720 align:start position:0%
margin as you can see look wor case
 

00:29:27.720 --> 00:29:29.549 align:start position:0%
margin as you can see look wor case
scenario<00:29:28.279> exactly<00:29:28.799> so<00:29:28.960> in<00:29:29.039> the<00:29:29.159> shoulder

00:29:29.549 --> 00:29:29.559 align:start position:0%
scenario exactly so in the shoulder
 

00:29:29.559 --> 00:29:31.310 align:start position:0%
scenario exactly so in the shoulder
months<00:29:29.880> we<00:29:30.000> have<00:29:30.159> a<00:29:30.399> reduction<00:29:30.799> in<00:29:30.960> cooling

00:29:31.310 --> 00:29:31.320 align:start position:0%
months we have a reduction in cooling
 

00:29:31.320 --> 00:29:33.350 align:start position:0%
months we have a reduction in cooling
load<00:29:31.799> as<00:29:31.919> well<00:29:32.039> as<00:29:32.200> heating<00:29:32.519> load<00:29:32.840> so<00:29:33.000> in<00:29:33.120> terms

00:29:33.350 --> 00:29:33.360 align:start position:0%
load as well as heating load so in terms
 

00:29:33.360 --> 00:29:36.350 align:start position:0%
load as well as heating load so in terms
of<00:29:33.559> available<00:29:34.480> capacity<00:29:35.480> shoulder<00:29:35.880> periods

00:29:36.350 --> 00:29:36.360 align:start position:0%
of available capacity shoulder periods
 

00:29:36.360 --> 00:29:38.549 align:start position:0%
of available capacity shoulder periods
probably<00:29:36.679> have<00:29:36.799> the<00:29:36.919> lowest<00:29:37.480> demand<00:29:38.360> which

00:29:38.549 --> 00:29:38.559 align:start position:0%
probably have the lowest demand which
 

00:29:38.559 --> 00:29:40.549 align:start position:0%
probably have the lowest demand which
then<00:29:38.799> increases<00:29:39.200> our<00:29:39.399> heads<00:29:39.960> in<00:29:40.120> hosting

00:29:40.549 --> 00:29:40.559 align:start position:0%
then increases our heads in hosting
 

00:29:40.559 --> 00:29:42.990 align:start position:0%
then increases our heads in hosting
toate<00:29:41.440> yeah<00:29:41.760> and<00:29:41.880> that's<00:29:42.000> a<00:29:42.159> good<00:29:42.360> point<00:29:42.720> and

00:29:42.990 --> 00:29:43.000 align:start position:0%
toate yeah and that's a good point and
 

00:29:43.000 --> 00:29:45.430 align:start position:0%
toate yeah and that's a good point and
also<00:29:43.720> a<00:29:43.840> lot<00:29:43.960> of<00:29:44.200> Chili's<00:29:44.559> have<00:29:44.760> winter<00:29:45.120> static

00:29:45.430 --> 00:29:45.440 align:start position:0%
also a lot of Chili's have winter static
 

00:29:45.440 --> 00:29:48.350 align:start position:0%
also a lot of Chili's have winter static
ratings<00:29:45.880> already<00:29:46.880> and<00:29:47.080> so<00:29:47.720> if<00:29:47.840> you<00:29:47.960> look<00:29:48.120> at

00:29:48.350 --> 00:29:48.360 align:start position:0%
ratings already and so if you look at
 

00:29:48.360 --> 00:29:50.149 align:start position:0%
ratings already and so if you look at
actual<00:29:48.679> Improvement<00:29:49.279> this<00:29:49.440> would<00:29:49.679> build<00:29:50.039> you

00:29:50.149 --> 00:29:50.159 align:start position:0%
actual Improvement this would build you
 

00:29:50.159 --> 00:29:52.389 align:start position:0%
actual Improvement this would build you
know<00:29:50.640> that<00:29:50.880> blue<00:29:51.279> line<00:29:51.600> in<00:29:51.720> the<00:29:51.840> winter<00:29:52.240> might

00:29:52.389 --> 00:29:52.399 align:start position:0%
know that blue line in the winter might
 

00:29:52.399 --> 00:29:56.070 align:start position:0%
know that blue line in the winter might
be<00:29:52.600> actually<00:29:52.960> higher<00:29:53.760> for<00:29:54.000> instance<00:29:55.080> U

00:29:56.070 --> 00:29:56.080 align:start position:0%
be actually higher for instance U
 

00:29:56.080 --> 00:30:01.789 align:start position:0%
be actually higher for instance U
seasonality<00:29:56.799> yeah<00:29:56.919> if<00:29:57.039> they<00:29:57.399> spr

00:30:01.789 --> 00:30:01.799 align:start position:0%
 
 

00:30:01.799 --> 00:30:05.269 align:start position:0%
 
that<00:30:02.799> few<00:30:03.080> questions

00:30:05.269 --> 00:30:05.279 align:start position:0%
that few questions
 

00:30:05.279 --> 00:30:09.830 align:start position:0%
that few questions
thanks<00:30:06.279> okay<00:30:06.679> so<00:30:07.279> storage<00:30:08.279> so<00:30:08.679> I<00:30:09.320> example

00:30:09.830 --> 00:30:09.840 align:start position:0%
thanks okay so storage so I example
 

00:30:09.840 --> 00:30:11.509 align:start position:0%
thanks okay so storage so I example
there's<00:30:10.000> an<00:30:10.159> example<00:30:10.480> here<00:30:10.679> from<00:30:11.000> from

00:30:11.509 --> 00:30:11.519 align:start position:0%
there's an example here from from
 

00:30:11.519 --> 00:30:13.830 align:start position:0%
there's an example here from from
Germany<00:30:12.519> uh<00:30:12.760> but<00:30:12.960> there<00:30:13.080> are<00:30:13.279> some<00:30:13.480> instances

00:30:13.830 --> 00:30:13.840 align:start position:0%
Germany uh but there are some instances
 

00:30:13.840 --> 00:30:15.350 align:start position:0%
Germany uh but there are some instances
in<00:30:13.919> the<00:30:14.000> US<00:30:14.200> we<00:30:14.320> can<00:30:14.480> talk<00:30:14.679> about<00:30:15.000> but

00:30:15.350 --> 00:30:15.360 align:start position:0%
in the US we can talk about but
 

00:30:15.360 --> 00:30:18.830 align:start position:0%
in the US we can talk about but
essentially<00:30:16.360> what<00:30:16.519> storage<00:30:17.000> can<00:30:17.200> do<00:30:18.120> is<00:30:18.679> it

00:30:18.830 --> 00:30:18.840 align:start position:0%
essentially what storage can do is it
 

00:30:18.840 --> 00:30:22.149 align:start position:0%
essentially what storage can do is it
can<00:30:19.360> allow<00:30:20.240> transmission<00:30:20.799> lines<00:30:21.399> that<00:30:21.519> are

00:30:22.149 --> 00:30:22.159 align:start position:0%
can allow transmission lines that are
 

00:30:22.159 --> 00:30:24.909 align:start position:0%
can allow transmission lines that are
typically<00:30:22.840> radial<00:30:23.360> connected<00:30:23.960> so<00:30:24.360> think<00:30:24.559> of

00:30:24.909 --> 00:30:24.919 align:start position:0%
typically radial connected so think of
 

00:30:24.919 --> 00:30:27.669 align:start position:0%
typically radial connected so think of
like<00:30:25.519> this<00:30:25.720> example<00:30:26.240> in<00:30:27.279> they<00:30:27.399> have<00:30:27.480> all<00:30:27.600> the

00:30:27.669 --> 00:30:27.679 align:start position:0%
like this example in they have all the
 

00:30:27.679 --> 00:30:29.430 align:start position:0%
like this example in they have all the
wind<00:30:27.880> generation<00:30:28.279> in<00:30:28.399> the<00:30:28.559> north<00:30:29.240> and<00:30:29.360> they

00:30:29.430 --> 00:30:29.440 align:start position:0%
wind generation in the north and they
 

00:30:29.440 --> 00:30:32.549 align:start position:0%
wind generation in the north and they
have<00:30:29.519> the<00:30:29.600> low<00:30:29.799> centers<00:30:30.120> in<00:30:30.240> the<00:30:30.799> South<00:30:31.799> and<00:30:32.000> so

00:30:32.549 --> 00:30:32.559 align:start position:0%
have the low centers in the South and so
 

00:30:32.559 --> 00:30:33.990 align:start position:0%
have the low centers in the South and so
you<00:30:32.679> have<00:30:32.799> a<00:30:32.960> limited<00:30:33.320> number<00:30:33.519> of<00:30:33.640> long

00:30:33.990 --> 00:30:34.000 align:start position:0%
you have a limited number of long
 

00:30:34.000 --> 00:30:36.310 align:start position:0%
you have a limited number of long
transmission<00:30:34.480> lines<00:30:35.039> that<00:30:35.360> can<00:30:35.600> carry<00:30:36.000> that

00:30:36.310 --> 00:30:36.320 align:start position:0%
transmission lines that can carry that
 

00:30:36.320 --> 00:30:40.350 align:start position:0%
transmission lines that can carry that
power<00:30:37.320> and<00:30:37.480> so<00:30:37.840> if<00:30:38.360> one<00:30:39.000> one<00:30:39.159> of<00:30:39.840> those<00:30:40.039> lines

00:30:40.350 --> 00:30:40.360 align:start position:0%
power and so if one one of those lines
 

00:30:40.360 --> 00:30:44.470 align:start position:0%
power and so if one one of those lines
goes<00:30:40.720> out<00:30:41.720> um<00:30:42.480> then<00:30:43.480> there's<00:30:43.840> you<00:30:43.960> know<00:30:44.240> a<00:30:44.360> lot

00:30:44.470 --> 00:30:44.480 align:start position:0%
goes out um then there's you know a lot
 

00:30:44.480 --> 00:30:46.870 align:start position:0%
goes out um then there's you know a lot
of<00:30:44.640> curtailment<00:30:45.399> right<00:30:45.559> that<00:30:45.720> happens<00:30:46.480> and<00:30:46.600> so

00:30:46.870 --> 00:30:46.880 align:start position:0%
of curtailment right that happens and so
 

00:30:46.880 --> 00:30:49.509 align:start position:0%
of curtailment right that happens and so
what<00:30:47.240> storage<00:30:47.720> can<00:30:47.919> do<00:30:48.159> is<00:30:48.519> when<00:30:48.799> located<00:30:49.320> at

00:30:49.509 --> 00:30:49.519 align:start position:0%
what storage can do is when located at
 

00:30:49.519 --> 00:30:52.070 align:start position:0%
what storage can do is when located at
each<00:30:49.679> end<00:30:50.000> it<00:30:50.120> can<00:30:50.320> provide<00:30:50.760> that<00:30:51.000> back<00:30:51.640> in<00:30:51.799> a

00:30:52.070 --> 00:30:52.080 align:start position:0%
each end it can provide that back in a
 

00:30:52.080 --> 00:30:56.430 align:start position:0%
each end it can provide that back in a
contingency<00:30:53.080> it<00:30:53.240> can<00:30:53.760> solve<00:30:54.760> uh<00:30:55.760> it<00:30:55.880> can<00:30:56.320> you

00:30:56.430 --> 00:30:56.440 align:start position:0%
contingency it can solve uh it can you
 

00:30:56.440 --> 00:30:57.950 align:start position:0%
contingency it can solve uh it can you
know<00:30:56.919> provide<00:30:57.440> the<00:30:57.519> power<00:30:57.720> of<00:30:57.799> the

00:30:57.950 --> 00:30:57.960 align:start position:0%
know provide the power of the
 

00:30:57.960 --> 00:30:59.830 align:start position:0%
know provide the power of the
contingency<00:30:58.519> and<00:30:58.760> allow<00:30:59.279> you<00:30:59.360> know<00:30:59.600> both

00:30:59.830 --> 00:30:59.840 align:start position:0%
contingency and allow you know both
 

00:30:59.840 --> 00:31:02.590 align:start position:0%
contingency and allow you know both
lines<00:31:00.159> in<00:31:00.320> the<00:31:00.679> middle<00:31:01.240> pain<00:31:01.639> here<00:31:02.440> to

00:31:02.590 --> 00:31:02.600 align:start position:0%
lines in the middle pain here to
 

00:31:02.600 --> 00:31:05.549 align:start position:0%
lines in the middle pain here to
transmit<00:31:03.159> more<00:31:03.600> power<00:31:04.600> there's<00:31:04.760> a<00:31:04.919> similar

00:31:05.549 --> 00:31:05.559 align:start position:0%
transmit more power there's a similar
 

00:31:05.559 --> 00:31:10.029 align:start position:0%
transmit more power there's a similar
example<00:31:07.039> in<00:31:08.039> N<00:31:08.399> Tucket

00:31:10.029 --> 00:31:10.039 align:start position:0%
example in N Tucket
 

00:31:10.039 --> 00:31:13.509 align:start position:0%
example in N Tucket
uh<00:31:11.039> n<00:31:11.639> National<00:31:12.039> Grid<00:31:12.760> has<00:31:13.039> you<00:31:13.200> know<00:31:13.320> there's

00:31:13.509 --> 00:31:13.519 align:start position:0%
uh n National Grid has you know there's
 

00:31:13.519 --> 00:31:15.669 align:start position:0%
uh n National Grid has you know there's
subseed<00:31:14.039> cables<00:31:14.360> that<00:31:14.720> feat<00:31:15.039> and<00:31:15.240> Tucket<00:31:15.600> and

00:31:15.669 --> 00:31:15.679 align:start position:0%
subseed cables that feat and Tucket and
 

00:31:15.679 --> 00:31:17.070 align:start position:0%
subseed cables that feat and Tucket and
they<00:31:15.760> were<00:31:15.880> looking<00:31:16.080> at<00:31:16.200> putting<00:31:16.480> in<00:31:16.639> a<00:31:16.799> third

00:31:17.070 --> 00:31:17.080 align:start position:0%
they were looking at putting in a third
 

00:31:17.080 --> 00:31:19.950 align:start position:0%
they were looking at putting in a third
subseed<00:31:17.600> cable<00:31:18.000> at<00:31:18.039> $200<00:31:18.799> million<00:31:19.799> they

00:31:19.950 --> 00:31:19.960 align:start position:0%
subseed cable at $200 million they
 

00:31:19.960 --> 00:31:23.909 align:start position:0%
subseed cable at $200 million they
decided<00:31:20.279> to<00:31:20.399> do<00:31:20.799> a<00:31:21.200> six<00:31:22.159> uh<00:31:22.679> think<00:31:22.880> it's<00:31:23.000> a<00:31:23.200> six

00:31:23.909 --> 00:31:23.919 align:start position:0%
decided to do a six uh think it's a six
 

00:31:23.919 --> 00:31:27.230 align:start position:0%
decided to do a six uh think it's a six
megawatt<00:31:24.440> 8<00:31:24.720> Hour<00:31:25.279> battery<00:31:26.279> um<00:31:26.559> to<00:31:26.799> provide

00:31:27.230 --> 00:31:27.240 align:start position:0%
megawatt 8 Hour battery um to provide
 

00:31:27.240 --> 00:31:29.149 align:start position:0%
megawatt 8 Hour battery um to provide
power<00:31:27.559> at<00:31:27.720> you<00:31:27.840> know<00:31:28.080> maybe<00:31:28.320> a<00:31:28.440> cost<00:31:28.679> of<00:31:28.880> 50

00:31:29.149 --> 00:31:29.159 align:start position:0%
power at you know maybe a cost of 50
 

00:31:29.159 --> 00:31:32.629 align:start position:0%
power at you know maybe a cost of 50
million<00:31:29.840> the<00:31:30.039> actual<00:31:31.039> project<00:31:31.519> cost<00:31:32.159> but<00:31:32.440> much

00:31:32.629 --> 00:31:32.639 align:start position:0%
million the actual project cost but much
 

00:31:32.639 --> 00:31:36.389 align:start position:0%
million the actual project cost but much
cheaper<00:31:33.039> solution<00:31:34.000> so<00:31:34.760> storage<00:31:35.679> based<00:31:35.919> on<00:31:36.120> the

00:31:36.389 --> 00:31:36.399 align:start position:0%
cheaper solution so storage based on the
 

00:31:36.399 --> 00:31:38.830 align:start position:0%
cheaper solution so storage based on the
C<00:31:36.799> based<00:31:37.000> on<00:31:37.200> cost<00:31:37.559> right<00:31:37.720> now<00:31:38.200> really<00:31:38.600> need

00:31:38.830 --> 00:31:38.840 align:start position:0%
C based on cost right now really need
 

00:31:38.840 --> 00:31:40.950 align:start position:0%
C based on cost right now really need
needs<00:31:39.080> to<00:31:39.200> be<00:31:39.360> applied<00:31:39.720> in<00:31:39.919> areas<00:31:40.360> where<00:31:40.760> you

00:31:40.950 --> 00:31:40.960 align:start position:0%
needs to be applied in areas where you
 

00:31:40.960 --> 00:31:43.509 align:start position:0%
needs to be applied in areas where you
have<00:31:41.320> very<00:31:41.679> high<00:31:41.960> cost<00:31:42.279> for<00:31:42.519> transmission

00:31:43.509 --> 00:31:43.519 align:start position:0%
have very high cost for transmission
 

00:31:43.519 --> 00:31:46.990 align:start position:0%
have very high cost for transmission
upgrade<00:31:44.519> or<00:31:44.880> high<00:31:45.159> cost<00:31:45.440> to<00:31:46.240> uh<00:31:46.480> in

00:31:46.990 --> 00:31:47.000 align:start position:0%
upgrade or high cost to uh in
 

00:31:47.000 --> 00:31:48.950 align:start position:0%
upgrade or high cost to uh in
availability<00:31:47.559> to<00:31:47.679> find<00:31:47.919> rideway<00:31:48.559> for

00:31:48.950 --> 00:31:48.960 align:start position:0%
availability to find rideway for
 

00:31:48.960 --> 00:31:51.750 align:start position:0%
availability to find rideway for
transmission<00:31:49.760> you<00:31:50.000> can<00:31:51.000> site<00:31:51.320> storage

00:31:51.750 --> 00:31:51.760 align:start position:0%
transmission you can site storage
 

00:31:51.760 --> 00:31:55.190 align:start position:0%
transmission you can site storage
locally<00:31:52.519> right<00:31:52.840> without<00:31:53.840> um<00:31:54.399> major<00:31:54.840> right

00:31:55.190 --> 00:31:55.200 align:start position:0%
locally right without um major right
 

00:31:55.200 --> 00:31:57.870 align:start position:0%
locally right without um major right
away<00:31:56.200> but<00:31:56.399> I<00:31:56.480> would<00:31:56.679> say<00:31:57.279> the<00:31:57.440> storage<00:31:57.760> of

00:31:57.870 --> 00:31:57.880 align:start position:0%
away but I would say the storage of
 

00:31:57.880 --> 00:32:01.190 align:start position:0%
away but I would say the storage of
transmission<00:31:58.360> in<00:31:58.440> the<00:31:58.600> US<00:31:59.120> is<00:31:59.320> not<00:31:59.840> as<00:32:00.840> far

00:32:01.190 --> 00:32:01.200 align:start position:0%
transmission in the US is not as far
 

00:32:01.200 --> 00:32:02.470 align:start position:0%
transmission in the US is not as far
along<00:32:01.600> in<00:32:01.760> the

00:32:02.470 --> 00:32:02.480 align:start position:0%
along in the
 

00:32:02.480 --> 00:32:04.590 align:start position:0%
along in the
commercialization<00:32:03.480> as<00:32:03.880> Dynamic<00:32:04.279> blind

00:32:04.590 --> 00:32:04.600 align:start position:0%
commercialization as Dynamic blind
 

00:32:04.600 --> 00:32:06.990 align:start position:0%
commercialization as Dynamic blind
ratings<00:32:05.360> but<00:32:05.480> it's<00:32:05.679> coming

00:32:06.990 --> 00:32:07.000 align:start position:0%
ratings but it's coming
 

00:32:07.000 --> 00:32:10.789 align:start position:0%
ratings but it's coming
soon<00:32:08.000> in<00:32:08.159> terms<00:32:08.480> of<00:32:08.919> storages<00:32:09.679> applicable<00:32:10.320> to

00:32:10.789 --> 00:32:10.799 align:start position:0%
soon in terms of storages applicable to
 

00:32:10.799 --> 00:32:12.870 align:start position:0%
soon in terms of storages applicable to
transmission<00:32:11.399> to<00:32:11.720> yes<00:32:12.080> storages

00:32:12.870 --> 00:32:12.880 align:start position:0%
transmission to yes storages
 

00:32:12.880 --> 00:32:14.830 align:start position:0%
transmission to yes storages
transmission<00:32:13.880> sometimes<00:32:14.080> it's<00:32:14.240> prer<00:32:14.600> to

00:32:14.830 --> 00:32:14.840 align:start position:0%
transmission sometimes it's prer to
 

00:32:14.840 --> 00:32:17.789 align:start position:0%
transmission sometimes it's prer to
storage<00:32:15.200> as<00:32:15.320> a<00:32:15.840> transmission<00:32:16.360> only<00:32:16.799> adet<00:32:17.440> or

00:32:17.789 --> 00:32:17.799 align:start position:0%
storage as a transmission only adet or
 

00:32:17.799 --> 00:32:20.310 align:start position:0%
storage as a transmission only adet or
as<00:32:18.360> transmission<00:32:19.360> uh<00:32:19.600> obviously<00:32:19.919> storage

00:32:20.310 --> 00:32:20.320 align:start position:0%
as transmission uh obviously storage
 

00:32:20.320 --> 00:32:23.870 align:start position:0%
as transmission uh obviously storage
sided<00:32:20.840> with<00:32:21.639> um<00:32:21.840> Renewables<00:32:22.519> and<00:32:22.679> and<00:32:22.840> for<00:32:23.320> uh

00:32:23.870 --> 00:32:23.880 align:start position:0%
sided with um Renewables and and for uh
 

00:32:23.880 --> 00:32:26.230 align:start position:0%
sided with um Renewables and and for uh
uh<00:32:24.039> you<00:32:24.159> know<00:32:25.159> gas<00:32:25.360> keeper<00:32:25.679> Replacements

00:32:26.230 --> 00:32:26.240 align:start position:0%
uh you know gas keeper Replacements
 

00:32:26.240 --> 00:32:28.789 align:start position:0%
uh you know gas keeper Replacements
those<00:32:26.399> things<00:32:27.480> as<00:32:27.679> far<00:32:27.919> along<00:32:28.200> we<00:32:28.320> saw<00:32:28.639> that

00:32:28.789 --> 00:32:28.799 align:start position:0%
those things as far along we saw that
 

00:32:28.799 --> 00:32:32.470 align:start position:0%
those things as far along we saw that
back<00:32:28.960> in<00:32:29.080> the<00:32:29.760> queue<00:32:30.760> but<00:32:31.360> specifically<00:32:31.960> for

00:32:32.470 --> 00:32:32.480 align:start position:0%
back in the queue but specifically for
 

00:32:32.480 --> 00:32:35.190 align:start position:0%
back in the queue but specifically for
transmission<00:32:33.480> which<00:32:33.639> is

00:32:35.190 --> 00:32:35.200 align:start position:0%
transmission which is
 

00:32:35.200 --> 00:32:39.110 align:start position:0%
transmission which is
how<00:32:36.200> uh<00:32:36.559> right<00:32:36.799> now<00:32:37.440> even<00:32:37.720> in<00:32:37.960> in<00:32:38.159> the<00:32:38.320> German

00:32:39.110 --> 00:32:39.120 align:start position:0%
how uh right now even in in the German
 

00:32:39.120 --> 00:32:41.909 align:start position:0%
how uh right now even in in the German
example<00:32:40.120> it's<00:32:40.799> the<00:32:41.000> full<00:32:41.320> capacity<00:32:41.679> of<00:32:41.799> that

00:32:41.909 --> 00:32:41.919 align:start position:0%
example it's the full capacity of that
 

00:32:41.919 --> 00:32:43.190 align:start position:0%
example it's the full capacity of that
storage<00:32:42.320> is<00:32:42.480> reserved<00:32:42.840> for<00:32:43.000> that

00:32:43.190 --> 00:32:43.200 align:start position:0%
storage is reserved for that
 

00:32:43.200 --> 00:32:45.549 align:start position:0%
storage is reserved for that
transmission<00:32:43.840> contingency<00:32:44.840> so<00:32:45.120> that<00:32:45.279> there

00:32:45.549 --> 00:32:45.559 align:start position:0%
transmission contingency so that there
 

00:32:45.559 --> 00:32:47.710 align:start position:0%
transmission contingency so that there
can't<00:32:45.799> you<00:32:45.960> can't<00:32:46.159> be<00:32:46.360> also<00:32:46.559> using<00:32:46.840> it<00:32:47.039> as<00:32:47.200> a<00:32:47.480> an

00:32:47.710 --> 00:32:47.720 align:start position:0%
can't you can't be also using it as a an
 

00:32:47.720 --> 00:32:50.029 align:start position:0%
can't you can't be also using it as a an
asset<00:32:48.480> fit<00:32:48.679> into<00:32:48.880> the<00:32:49.039> commercial<00:32:49.600> energy

00:32:50.029 --> 00:32:50.039 align:start position:0%
asset fit into the commercial energy
 

00:32:50.039 --> 00:32:52.310 align:start position:0%
asset fit into the commercial energy
market<00:32:50.480> so<00:32:50.679> it's<00:32:50.960> for<00:32:51.200> resource<00:32:51.559> adoc

00:32:52.310 --> 00:32:52.320 align:start position:0%
market so it's for resource adoc
 

00:32:52.320 --> 00:32:54.389 align:start position:0%
market so it's for resource adoc
capacity<00:32:52.919> right<00:32:53.120> you<00:32:53.279> can't<00:32:53.559> do<00:32:53.760> that<00:32:54.159> that's

00:32:54.389 --> 00:32:54.399 align:start position:0%
capacity right you can't do that that's
 

00:32:54.399 --> 00:32:57.110 align:start position:0%
capacity right you can't do that that's
right<00:32:55.320> that's<00:32:55.559> right<00:32:55.799> so<00:32:56.000> can<00:32:56.120> you<00:32:56.279> opine<00:32:56.760> on

00:32:57.110 --> 00:32:57.120 align:start position:0%
right that's right so can you opine on
 

00:32:57.120 --> 00:32:59.029 align:start position:0%
right that's right so can you opine on
why<00:32:57.279> in<00:32:57.399> the<00:32:57.519> US<00:32:57.840> were<00:32:58.039> behind<00:32:58.720> what<00:32:58.880> they're

00:32:59.029 --> 00:32:59.039 align:start position:0%
why in the US were behind what they're
 

00:32:59.039 --> 00:33:00.509 align:start position:0%
why in the US were behind what they're
doing<00:32:59.240> in<00:32:59.360> Germany<00:32:59.720> where<00:32:59.880> we<00:33:00.000> have<00:33:00.159> the<00:33:00.279> same

00:33:00.509 --> 00:33:00.519 align:start position:0%
doing in Germany where we have the same
 

00:33:00.519 --> 00:33:01.710 align:start position:0%
doing in Germany where we have the same
capacity

00:33:01.710 --> 00:33:01.720 align:start position:0%
capacity
 

00:33:01.720 --> 00:33:03.470 align:start position:0%
capacity
strings

00:33:03.470 --> 00:33:03.480 align:start position:0%
strings
 

00:33:03.480 --> 00:33:07.269 align:start position:0%
strings
um<00:33:04.480> I<00:33:04.679> don't<00:33:05.480> I<00:33:05.600> don't<00:33:06.000> really<00:33:06.320> have<00:33:06.600> a<00:33:06.919> a<00:33:07.080> good

00:33:07.269 --> 00:33:07.279 align:start position:0%
um I don't I don't really have a a good
 

00:33:07.279 --> 00:33:09.430 align:start position:0%
um I don't I don't really have a a good
answer<00:33:07.679> there<00:33:08.120> I<00:33:08.519> the<00:33:08.639> example<00:33:09.039> here<00:33:09.200> is<00:33:09.279> from

00:33:09.430 --> 00:33:09.440 align:start position:0%
answer there I the example here is from
 

00:33:09.440 --> 00:33:12.269 align:start position:0%
answer there I the example here is from
flu<00:33:09.919> which<00:33:10.000> is<00:33:10.120> an<00:33:10.279> as<00:33:10.639> sister<00:33:11.240> me<00:33:11.399> I<00:33:11.519> know

00:33:12.269 --> 00:33:12.279 align:start position:0%
flu which is an as sister me I know
 

00:33:12.279 --> 00:33:17.430 align:start position:0%
flu which is an as sister me I know
col's<00:33:12.720> former<00:33:13.720> all<00:33:14.080> mo<00:33:14.760> here<00:33:15.120> so<00:33:15.919> um<00:33:16.919> call<00:33:17.279> you

00:33:17.430 --> 00:33:17.440 align:start position:0%
col's former all mo here so um call you
 

00:33:17.440 --> 00:33:20.070 align:start position:0%
col's former all mo here so um call you
have<00:33:17.639> any<00:33:18.120> comments<00:33:18.960> it's<00:33:19.080> a<00:33:19.279> good<00:33:19.559> question

00:33:20.070 --> 00:33:20.080 align:start position:0%
have any comments it's a good question
 

00:33:20.080 --> 00:33:22.149 align:start position:0%
have any comments it's a good question
I'm<00:33:20.360> I'm<00:33:20.480> wondering<00:33:20.840> if<00:33:21.039> there<00:33:21.320> regulatory<00:33:21.880> or

00:33:22.149 --> 00:33:22.159 align:start position:0%
I'm I'm wondering if there regulatory or
 

00:33:22.159 --> 00:33:26.310 align:start position:0%
I'm I'm wondering if there regulatory or
policy<00:33:22.639> reasons<00:33:23.360> why<00:33:23.919> it<00:33:24.120> becomes<00:33:25.039> a<00:33:26.039> more

00:33:26.310 --> 00:33:26.320 align:start position:0%
policy reasons why it becomes a more
 

00:33:26.320 --> 00:33:30.149 align:start position:0%
policy reasons why it becomes a more
accepted<00:33:26.679> solution<00:33:27.200> in<00:33:27.360> Europe<00:33:28.159> first<00:33:29.159> um<00:33:30.080> I

00:33:30.149 --> 00:33:30.159 align:start position:0%
accepted solution in Europe first um I
 

00:33:30.159 --> 00:33:31.870 align:start position:0%
accepted solution in Europe first um I
think<00:33:30.639> probably<00:33:30.919> a<00:33:31.039> lot<00:33:31.159> of<00:33:31.279> it<00:33:31.399> is<00:33:31.559> finding

00:33:31.870 --> 00:33:31.880 align:start position:0%
think probably a lot of it is finding
 

00:33:31.880 --> 00:33:34.470 align:start position:0%
think probably a lot of it is finding
the<00:33:32.000> right<00:33:32.720> applications<00:33:33.720> Germany<00:33:34.159> very

00:33:34.470 --> 00:33:34.480 align:start position:0%
the right applications Germany very
 

00:33:34.480 --> 00:33:37.230 align:start position:0%
the right applications Germany very
specifically<00:33:35.120> there's<00:33:35.519> that<00:33:36.320> you<00:33:36.480> know

00:33:37.230 --> 00:33:37.240 align:start position:0%
specifically there's that you know
 

00:33:37.240 --> 00:33:39.389 align:start position:0%
specifically there's that you know
Renewables<00:33:37.799> in<00:33:37.960> the<00:33:38.080> north<00:33:38.519> and<00:33:38.840> and<00:33:39.000> load<00:33:39.279> in

00:33:39.389 --> 00:33:39.399 align:start position:0%
Renewables in the north and and load in
 

00:33:39.399 --> 00:33:44.950 align:start position:0%
Renewables in the north and and load in
the<00:33:39.880> South<00:33:40.880> um<00:33:41.760> it's<00:33:41.960> also<00:33:42.360> a<00:33:42.559> newer<00:33:43.720> um<00:33:44.720> uh

00:33:44.950 --> 00:33:44.960 align:start position:0%
the South um it's also a newer um uh
 

00:33:44.960 --> 00:33:46.830 align:start position:0%
the South um it's also a newer um uh
technology<00:33:45.600> in<00:33:45.720> terms<00:33:45.960> of<00:33:46.120> the<00:33:46.279> inverter

00:33:46.830 --> 00:33:46.840 align:start position:0%
technology in terms of the inverter
 

00:33:46.840 --> 00:33:50.149 align:start position:0%
technology in terms of the inverter
technology<00:33:47.600> so<00:33:48.440> grid<00:33:48.840> forming<00:33:49.440> inverters

00:33:50.149 --> 00:33:50.159 align:start position:0%
technology so grid forming inverters
 

00:33:50.159 --> 00:33:52.230 align:start position:0%
technology so grid forming inverters
rather<00:33:50.399> than<00:33:50.600> grid<00:33:51.000> following<00:33:51.519> inverters

00:33:52.230 --> 00:33:52.240 align:start position:0%
rather than grid following inverters
 

00:33:52.240 --> 00:33:54.269 align:start position:0%
rather than grid following inverters
which<00:33:52.360> are<00:33:52.519> the<00:33:52.880> typical<00:33:53.440> technology<00:33:54.039> that

00:33:54.269 --> 00:33:54.279 align:start position:0%
which are the typical technology that
 

00:33:54.279 --> 00:33:57.029 align:start position:0%
which are the typical technology that
energy<00:33:54.600> storage<00:33:55.039> uses<00:33:55.799> and<00:33:56.000> that<00:33:56.240> enables<00:33:56.720> it

00:33:57.029 --> 00:33:57.039 align:start position:0%
energy storage uses and that enables it
 

00:33:57.039 --> 00:33:59.110 align:start position:0%
energy storage uses and that enables it
to<00:33:57.399> respond<00:33:58.200> you<00:33:58.360> know<00:33:58.600> essentially

00:33:59.110 --> 00:33:59.120 align:start position:0%
to respond you know essentially
 

00:33:59.120 --> 00:34:01.389 align:start position:0%
to respond you know essentially
instantaneously<00:34:00.000> the<00:34:00.159> way<00:34:00.399> that<00:34:00.679> a<00:34:00.880> spinning

00:34:01.389 --> 00:34:01.399 align:start position:0%
instantaneously the way that a spinning
 

00:34:01.399 --> 00:34:05.149 align:start position:0%
instantaneously the way that a spinning
generator<00:34:02.159> would<00:34:03.159> and<00:34:03.399> that<00:34:03.880> that<00:34:04.200> technology

00:34:05.149 --> 00:34:05.159 align:start position:0%
generator would and that that technology
 

00:34:05.159 --> 00:34:07.029 align:start position:0%
generator would and that that technology
is<00:34:05.480> becoming<00:34:05.960> more<00:34:06.200> widespread<00:34:06.679> and<00:34:06.799> it's<00:34:06.880> a

00:34:07.029 --> 00:34:07.039 align:start position:0%
is becoming more widespread and it's a
 

00:34:07.039 --> 00:34:12.030 align:start position:0%
is becoming more widespread and it's a
more<00:34:07.320> sophisticated<00:34:08.119> application<00:34:08.560> of<00:34:08.720> energy

00:34:12.030 --> 00:34:12.040 align:start position:0%
 
 

00:34:12.040 --> 00:34:14.990 align:start position:0%
 
storage<00:34:13.040> and<00:34:13.240> as<00:34:13.639> is<00:34:13.800> also<00:34:14.119> looking<00:34:14.440> at<00:34:14.760> some

00:34:14.990 --> 00:34:15.000 align:start position:0%
storage and as is also looking at some
 

00:34:15.000 --> 00:34:17.270 align:start position:0%
storage and as is also looking at some
opportunities<00:34:15.679> within<00:34:15.919> our

00:34:17.270 --> 00:34:17.280 align:start position:0%
opportunities within our
 

00:34:17.280 --> 00:34:18.869 align:start position:0%
opportunities within our
utilities

00:34:18.869 --> 00:34:18.879 align:start position:0%
utilities
 

00:34:18.879 --> 00:34:20.869 align:start position:0%
utilities
been

00:34:20.869 --> 00:34:20.879 align:start position:0%
been
 

00:34:20.879 --> 00:34:23.510 align:start position:0%
been
offsetting<00:34:21.879> a<00:34:22.320> new<00:34:22.520> distribution<00:34:22.960> substation

00:34:23.510 --> 00:34:23.520 align:start position:0%
offsetting a new distribution substation
 

00:34:23.520 --> 00:34:25.790 align:start position:0%
offsetting a new distribution substation
in<00:34:23.639> a<00:34:23.800> local<00:34:24.159> area<00:34:24.599> by<00:34:24.760> using<00:34:25.079> storage<00:34:25.480> as<00:34:25.599> an

00:34:25.790 --> 00:34:25.800 align:start position:0%
in a local area by using storage as an
 

00:34:25.800 --> 00:34:29.030 align:start position:0%
in a local area by using storage as an
example<00:34:26.560> so<00:34:27.359> there's<00:34:28.320> like<00:34:28.440> I<00:34:28.520> said<00:34:28.800> I<00:34:28.879> think

00:34:29.030 --> 00:34:29.040 align:start position:0%
example so there's like I said I think
 

00:34:29.040 --> 00:34:33.750 align:start position:0%
example so there's like I said I think
is<00:34:29.599> coming<00:34:29.919> in<00:34:30.079> the<00:34:30.240> next<00:34:30.520> couple

00:34:33.750 --> 00:34:33.760 align:start position:0%
 
 

00:34:33.760 --> 00:34:37.030 align:start position:0%
 
years<00:34:34.760> all<00:34:34.879> right<00:34:35.079> so<00:34:35.280> this<00:34:35.399> is<00:34:35.639> my<00:34:36.599> final

00:34:37.030 --> 00:34:37.040 align:start position:0%
years all right so this is my final
 

00:34:37.040 --> 00:34:40.430 align:start position:0%
years all right so this is my final
slide<00:34:37.520> on<00:34:37.839> recommendations<00:34:39.200> so<00:34:40.200> and<00:34:40.320> this

00:34:40.430 --> 00:34:40.440 align:start position:0%
slide on recommendations so and this
 

00:34:40.440 --> 00:34:41.750 align:start position:0%
slide on recommendations so and this
will<00:34:40.720> get<00:34:40.919> back<00:34:41.040> to<00:34:41.159> some<00:34:41.280> of<00:34:41.440> things<00:34:41.599> were

00:34:41.750 --> 00:34:41.760 align:start position:0%
will get back to some of things were
 

00:34:41.760 --> 00:34:43.629 align:start position:0%
will get back to some of things were
talking<00:34:41.960> about<00:34:42.159> Paul<00:34:42.440> so<00:34:42.720> what<00:34:43.280> what<00:34:43.399> are<00:34:43.520> the

00:34:43.629 --> 00:34:43.639 align:start position:0%
talking about Paul so what what are the
 

00:34:43.639 --> 00:34:46.069 align:start position:0%
talking about Paul so what what are the
things<00:34:43.800> we<00:34:43.919> can<00:34:44.119> do<00:34:44.960> um<00:34:45.119> here<00:34:45.240> in<00:34:45.359> Virginia<00:34:45.800> so

00:34:46.069 --> 00:34:46.079 align:start position:0%
things we can do um here in Virginia so
 

00:34:46.079 --> 00:34:48.030 align:start position:0%
things we can do um here in Virginia so
we<00:34:46.280> should<00:34:46.599> encourage<00:34:47.560> continued

00:34:48.030 --> 00:34:48.040 align:start position:0%
we should encourage continued
 

00:34:48.040 --> 00:34:49.909 align:start position:0%
we should encourage continued
demonstration<00:34:48.639> or<00:34:49.159> demonstration<00:34:49.599> of<00:34:49.679> a<00:34:49.760> new

00:34:49.909 --> 00:34:49.919 align:start position:0%
demonstration or demonstration of a new
 

00:34:49.919 --> 00:34:53.710 align:start position:0%
demonstration or demonstration of a new
flexible<00:34:50.399> grid<00:34:50.960> abling<00:34:51.839> Technologies<00:34:52.839> so

00:34:53.710 --> 00:34:53.720 align:start position:0%
flexible grid abling Technologies so
 

00:34:53.720 --> 00:34:55.310 align:start position:0%
flexible grid abling Technologies so
there<00:34:53.879> is<00:34:54.079> increased<00:34:54.480> Federal<00:34:54.800> funding<00:34:55.079> for

00:34:55.310 --> 00:34:55.320 align:start position:0%
there is increased Federal funding for
 

00:34:55.320 --> 00:34:57.550 align:start position:0%
there is increased Federal funding for
this<00:34:55.520> right<00:34:55.679> now<00:34:56.040> the<00:34:56.240> DOE

00:34:57.550 --> 00:34:57.560 align:start position:0%
this right now the DOE
 

00:34:57.560 --> 00:35:00.670 align:start position:0%
this right now the DOE
um<00:34:58.440> grent<00:34:58.880> program<00:34:59.480> as<00:34:59.640> well<00:34:59.800> as<00:35:00.040> others

00:35:00.670 --> 00:35:00.680 align:start position:0%
um grent program as well as others
 

00:35:00.680 --> 00:35:05.510 align:start position:0%
um grent program as well as others
offers<00:35:01.520> uh<00:35:02.079> you<00:35:02.200> know<00:35:03.079> cost<00:35:03.359> shares<00:35:04.160> to<00:35:05.160> either

00:35:05.510 --> 00:35:05.520 align:start position:0%
offers uh you know cost shares to either
 

00:35:05.520 --> 00:35:08.349 align:start position:0%
offers uh you know cost shares to either
utilities<00:35:06.079> or<00:35:06.280> even<00:35:06.760> um<00:35:07.000> universities<00:35:08.000> and

00:35:08.349 --> 00:35:08.359 align:start position:0%
utilities or even um universities and
 

00:35:08.359 --> 00:35:09.510 align:start position:0%
utilities or even um universities and
other<00:35:08.560> research

00:35:09.510 --> 00:35:09.520 align:start position:0%
other research
 

00:35:09.520 --> 00:35:14.069 align:start position:0%
other research
organizations<00:35:10.520> um<00:35:10.800> for<00:35:11.520> demonstrating<00:35:12.079> new

00:35:14.069 --> 00:35:14.079 align:start position:0%
organizations um for demonstrating new
 

00:35:14.079 --> 00:35:16.710 align:start position:0%
organizations um for demonstrating new
technologies<00:35:15.079> and<00:35:15.200> then<00:35:15.400> this<00:35:15.560> gets<00:35:15.800> to<00:35:16.160> the

00:35:16.710 --> 00:35:16.720 align:start position:0%
technologies and then this gets to the
 

00:35:16.720 --> 00:35:18.790 align:start position:0%
technologies and then this gets to the
the<00:35:17.720> question<00:35:18.040> here<00:35:18.160> about<00:35:18.359> planning

00:35:18.790 --> 00:35:18.800 align:start position:0%
the question here about planning
 

00:35:18.800 --> 00:35:20.990 align:start position:0%
the question here about planning
processes<00:35:19.760> know<00:35:20.040> we<00:35:20.160> need<00:35:20.320> to<00:35:20.520> require

00:35:20.990 --> 00:35:21.000 align:start position:0%
processes know we need to require
 

00:35:21.000 --> 00:35:23.109 align:start position:0%
processes know we need to require
utilities<00:35:21.440> to<00:35:21.599> consider<00:35:22.119> gets<00:35:22.440> in<00:35:22.599> the

00:35:23.109 --> 00:35:23.119 align:start position:0%
utilities to consider gets in the
 

00:35:23.119 --> 00:35:26.109 align:start position:0%
utilities to consider gets in the
transmission<00:35:24.119> and<00:35:24.480> IRP<00:35:25.480> uh<00:35:25.599> planning

00:35:26.109 --> 00:35:26.119 align:start position:0%
transmission and IRP uh planning
 

00:35:26.119 --> 00:35:27.630 align:start position:0%
transmission and IRP uh planning
processes

00:35:27.630 --> 00:35:27.640 align:start position:0%
processes
 

00:35:27.640 --> 00:35:29.109 align:start position:0%
processes
and<00:35:27.880> provide<00:35:28.240> justification<00:35:28.800> that<00:35:28.960> they're

00:35:29.109 --> 00:35:29.119 align:start position:0%
and provide justification that they're
 

00:35:29.119 --> 00:35:31.870 align:start position:0%
and provide justification that they're
not<00:35:29.359> used<00:35:29.839> you<00:35:29.920> know<00:35:30.079> the<00:35:30.240> next<00:35:30.480> IRP<00:35:31.040> cycle<00:35:31.760> or

00:35:31.870 --> 00:35:31.880 align:start position:0%
not used you know the next IRP cycle or
 

00:35:31.880 --> 00:35:34.230 align:start position:0%
not used you know the next IRP cycle or
the<00:35:32.000> next<00:35:32.160> transmission<00:35:32.640> planning

00:35:34.230 --> 00:35:34.240 align:start position:0%
the next transmission planning
 

00:35:34.240 --> 00:35:37.270 align:start position:0%
the next transmission planning
cycle<00:35:35.240> that<00:35:35.480> utility<00:35:35.920> should<00:35:36.119> be<00:35:36.240> able<00:35:37.200> you

00:35:37.270 --> 00:35:37.280 align:start position:0%
cycle that utility should be able you
 

00:35:37.280 --> 00:35:39.470 align:start position:0%
cycle that utility should be able you
should<00:35:37.480> ask<00:35:37.640> the<00:35:37.800> question<00:35:38.200> why<00:35:38.359> are<00:35:38.480> you<00:35:38.680> not

00:35:39.470 --> 00:35:39.480 align:start position:0%
should ask the question why are you not
 

00:35:39.480 --> 00:35:42.069 align:start position:0%
should ask the question why are you not
considering<00:35:39.960> great<00:35:40.200> enhancing<00:35:41.079> Technologies

00:35:42.069 --> 00:35:42.079 align:start position:0%
considering great enhancing Technologies
 

00:35:42.079 --> 00:35:44.710 align:start position:0%
considering great enhancing Technologies
this<00:35:42.520> this<00:35:42.680> is<00:35:42.839> a<00:35:43.040> way<00:35:43.240> to<00:35:44.040> uh<00:35:44.160> you<00:35:44.280> know

00:35:44.710 --> 00:35:44.720 align:start position:0%
this this is a way to uh you know
 

00:35:44.720 --> 00:35:47.270 align:start position:0%
this this is a way to uh you know
deliver<00:35:45.200> capacity<00:35:45.880> for<00:35:46.240> the<00:35:46.400> these<00:35:46.960> coming

00:35:47.270 --> 00:35:47.280 align:start position:0%
deliver capacity for the these coming
 

00:35:47.280 --> 00:35:48.990 align:start position:0%
deliver capacity for the these coming
loads<00:35:47.760> like<00:35:47.920> for<00:35:48.040> instance<00:35:48.480> data<00:35:48.720> center

00:35:48.990 --> 00:35:49.000 align:start position:0%
loads like for instance data center
 

00:35:49.000 --> 00:35:51.150 align:start position:0%
loads like for instance data center
alley<00:35:49.880> these<00:35:50.040> customers<00:35:50.440> want<00:35:50.560> to<00:35:50.640> be<00:35:50.760> up<00:35:50.960> in

00:35:51.150 --> 00:35:51.160 align:start position:0%
alley these customers want to be up in
 

00:35:51.160 --> 00:35:53.390 align:start position:0%
alley these customers want to be up in
operational<00:35:51.640> in<00:35:51.800> 24<00:35:52.240> months<00:35:53.040> and<00:35:53.119> you<00:35:53.240> can't

00:35:53.390 --> 00:35:53.400 align:start position:0%
operational in 24 months and you can't
 

00:35:53.400 --> 00:35:56.190 align:start position:0%
operational in 24 months and you can't
build<00:35:53.640> transmission<00:35:54.200> that<00:35:54.480> fast<00:35:55.280> so<00:35:55.680> so<00:35:55.880> as<00:35:56.000> a

00:35:56.190 --> 00:35:56.200 align:start position:0%
build transmission that fast so so as a
 

00:35:56.200 --> 00:35:57.510 align:start position:0%
build transmission that fast so so as a
carent<00:35:56.520> for

00:35:57.510 --> 00:35:57.520 align:start position:0%
carent for
 

00:35:57.520 --> 00:36:00.270 align:start position:0%
carent for
you<00:35:57.640> know<00:35:58.160> utilities<00:35:59.160> you<00:35:59.359> want<00:35:59.640> this<00:35:59.800> load<00:36:00.079> on

00:36:00.270 --> 00:36:00.280 align:start position:0%
you know utilities you want this load on
 

00:36:00.280 --> 00:36:02.990 align:start position:0%
you know utilities you want this load on
your<00:36:00.960> system<00:36:01.960> these<00:36:02.240> Technologies<00:36:02.800> can

00:36:02.990 --> 00:36:03.000 align:start position:0%
your system these Technologies can
 

00:36:03.000 --> 00:36:05.670 align:start position:0%
your system these Technologies can
actually<00:36:03.640> get<00:36:03.880> that<00:36:04.000> load<00:36:04.280> onto<00:36:04.520> your<00:36:04.680> system

00:36:05.670 --> 00:36:05.680 align:start position:0%
actually get that load onto your system
 

00:36:05.680 --> 00:36:08.910 align:start position:0%
actually get that load onto your system
faster<00:36:06.680> um<00:36:07.440> and<00:36:07.599> then<00:36:07.880> we<00:36:08.000> can<00:36:08.200> interconnect

00:36:08.910 --> 00:36:08.920 align:start position:0%
faster um and then we can interconnect
 

00:36:08.920 --> 00:36:10.950 align:start position:0%
faster um and then we can interconnect
generate<00:36:09.480> the<00:36:09.640> you<00:36:09.760> know<00:36:10.240> solve<00:36:10.720> that

00:36:10.950 --> 00:36:10.960 align:start position:0%
generate the you know solve that
 

00:36:10.960 --> 00:36:13.069 align:start position:0%
generate the you know solve that
interconnection<00:36:11.720> queue<00:36:12.480> with<00:36:12.760> some<00:36:12.839> of<00:36:12.960> these

00:36:13.069 --> 00:36:13.079 align:start position:0%
interconnection queue with some of these
 

00:36:13.079 --> 00:36:14.990 align:start position:0%
interconnection queue with some of these
flexible<00:36:13.480> Technologies<00:36:14.119> and<00:36:14.400> prevent<00:36:14.880> you

00:36:14.990 --> 00:36:15.000 align:start position:0%
flexible Technologies and prevent you
 

00:36:15.000 --> 00:36:18.950 align:start position:0%
flexible Technologies and prevent you
know<00:36:15.280> only<00:36:15.680> 15%<00:36:16.760> of<00:36:17.760> uh<00:36:18.079> those<00:36:18.319> projects<00:36:18.720> or

00:36:18.950 --> 00:36:18.960 align:start position:0%
know only 15% of uh those projects or
 

00:36:18.960 --> 00:36:20.750 align:start position:0%
know only 15% of uh those projects or
only<00:36:19.200> 5%<00:36:19.720> let's<00:36:19.880> say<00:36:20.040> in<00:36:20.160> those<00:36:20.359> projects<00:36:20.640> in

00:36:20.750 --> 00:36:20.760 align:start position:0%
only 5% let's say in those projects in
 

00:36:20.760 --> 00:36:25.470 align:start position:0%
only 5% let's say in those projects in
the<00:36:20.880> PGM<00:36:21.599> Q<00:36:22.599> from<00:36:23.599> or<00:36:23.880> the<00:36:24.040> ne<00:36:24.520> are<00:36:24.720> allowed<00:36:25.000> to

00:36:25.470 --> 00:36:25.480 align:start position:0%
the PGM Q from or the ne are allowed to
 

00:36:25.480 --> 00:36:27.270 align:start position:0%
the PGM Q from or the ne are allowed to
complete<00:36:26.480> and<00:36:26.599> then

00:36:27.270 --> 00:36:27.280 align:start position:0%
complete and then
 

00:36:27.280 --> 00:36:29.550 align:start position:0%
complete and then
ultimately<00:36:28.280> load<00:36:28.680> pays<00:36:28.920> for<00:36:29.079> all<00:36:29.240> of<00:36:29.359> this

00:36:29.550 --> 00:36:29.560 align:start position:0%
ultimately load pays for all of this
 

00:36:29.560 --> 00:36:31.630 align:start position:0%
ultimately load pays for all of this
whether<00:36:29.720> it's<00:36:30.319> if<00:36:30.480> generation<00:36:31.280> is<00:36:31.480> more

00:36:31.630 --> 00:36:31.640 align:start position:0%
whether it's if generation is more
 

00:36:31.640 --> 00:36:34.510 align:start position:0%
whether it's if generation is more
expensive<00:36:32.000> to<00:36:32.160> connect<00:36:33.119> or<00:36:33.800> um<00:36:34.119> we<00:36:34.240> need<00:36:34.400> to

00:36:34.510 --> 00:36:34.520 align:start position:0%
expensive to connect or um we need to
 

00:36:34.520 --> 00:36:37.349 align:start position:0%
expensive to connect or um we need to
build<00:36:34.760> more<00:36:34.920> transmission<00:36:35.359> to<00:36:35.520> connect<00:36:36.040> data

00:36:37.349 --> 00:36:37.359 align:start position:0%
build more transmission to connect data
 

00:36:37.359 --> 00:36:39.870 align:start position:0%
build more transmission to connect data
centers<00:36:38.359> customers<00:36:38.839> pay<00:36:39.040> for<00:36:39.280> this<00:36:39.560> and<00:36:39.720> their

00:36:39.870 --> 00:36:39.880 align:start position:0%
centers customers pay for this and their
 

00:36:39.880 --> 00:36:42.430 align:start position:0%
centers customers pay for this and their
in<00:36:40.000> their<00:36:40.160> bills<00:36:40.760> and

00:36:42.430 --> 00:36:42.440 align:start position:0%
in their bills and
 

00:36:42.440 --> 00:36:45.670 align:start position:0%
in their bills and
um<00:36:43.440> we<00:36:43.680> should<00:36:43.920> be<00:36:44.119> looking<00:36:44.400> at<00:36:44.599> the<00:36:44.839> best<00:36:45.480> uh

00:36:45.670 --> 00:36:45.680 align:start position:0%
um we should be looking at the best uh
 

00:36:45.680 --> 00:36:47.950 align:start position:0%
um we should be looking at the best uh
Solutions<00:36:46.200> the<00:36:46.319> best<00:36:46.480> available<00:36:46.960> technology

00:36:47.950 --> 00:36:47.960 align:start position:0%
Solutions the best available technology
 

00:36:47.960 --> 00:36:49.950 align:start position:0%
Solutions the best available technology
in<00:36:48.079> order<00:36:48.359> to<00:36:49.000> uh<00:36:49.240> make<00:36:49.359> sure<00:36:49.599> that<00:36:49.760> this

00:36:49.950 --> 00:36:49.960 align:start position:0%
in order to uh make sure that this
 

00:36:49.960 --> 00:36:52.470 align:start position:0%
in order to uh make sure that this
energy<00:36:50.359> transition<00:36:51.160> is

00:36:52.470 --> 00:36:52.480 align:start position:0%
energy transition is
 

00:36:52.480 --> 00:36:54.510 align:start position:0%
energy transition is
Affordable<00:36:53.480> and<00:36:53.640> then<00:36:53.880> finally<00:36:54.200> on<00:36:54.359> the

00:36:54.510 --> 00:36:54.520 align:start position:0%
Affordable and then finally on the
 

00:36:54.520 --> 00:36:57.069 align:start position:0%
Affordable and then finally on the
incentives<00:36:55.160> piece<00:36:55.520> you<00:36:55.680> know<00:36:56.720> recommend

00:36:57.069 --> 00:36:57.079 align:start position:0%
incentives piece you know recommend
 

00:36:57.079 --> 00:36:59.990 align:start position:0%
incentives piece you know recommend
advising<00:36:57.839> the<00:36:57.920> SEC<00:36:58.800> to<00:36:59.000> support<00:36:59.440> regulatory

00:36:59.990 --> 00:37:00.000 align:start position:0%
advising the SEC to support regulatory
 

00:37:00.000 --> 00:37:02.430 align:start position:0%
advising the SEC to support regulatory
incentives<00:37:00.480> so<00:37:01.240> greatness<00:37:01.680> and<00:37:01.839> Technologies

00:37:02.430 --> 00:37:02.440 align:start position:0%
incentives so greatness and Technologies
 

00:37:02.440 --> 00:37:04.550 align:start position:0%
incentives so greatness and Technologies
can<00:37:02.680> compete<00:37:03.000> on<00:37:03.160> equal<00:37:03.440> footing<00:37:04.280> and<00:37:04.400> that

00:37:04.550 --> 00:37:04.560 align:start position:0%
can compete on equal footing and that
 

00:37:04.560 --> 00:37:07.910 align:start position:0%
can compete on equal footing and that
can<00:37:04.800> look<00:37:05.160> like<00:37:05.920> some<00:37:06.440> performance<00:37:06.960> incentive

00:37:07.910 --> 00:37:07.920 align:start position:0%
can look like some performance incentive
 

00:37:07.920 --> 00:37:11.550 align:start position:0%
can look like some performance incentive
that<00:37:08.079> can<00:37:08.280> look<00:37:08.560> like<00:37:09.319> um<00:37:09.520> incentives<00:37:10.400> for<00:37:11.400> U

00:37:11.550 --> 00:37:11.560 align:start position:0%
that can look like um incentives for U
 

00:37:11.560 --> 00:37:15.470 align:start position:0%
that can look like um incentives for U
you<00:37:11.920> know<00:37:12.920> a<00:37:13.160> cost<00:37:13.480> savings<00:37:14.119> share<00:37:14.839> where<00:37:15.160> the

00:37:15.470 --> 00:37:15.480 align:start position:0%
you know a cost savings share where the
 

00:37:15.480 --> 00:37:18.190 align:start position:0%
you know a cost savings share where the
the<00:37:16.000> what's<00:37:16.640> what's<00:37:16.920> Sav<00:37:17.160> and<00:37:17.400> rate<00:37:17.560> base<00:37:18.079> in

00:37:18.190 --> 00:37:18.200 align:start position:0%
the what's what's Sav and rate base in
 

00:37:18.200 --> 00:37:20.349 align:start position:0%
the what's what's Sav and rate base in
the<00:37:18.319> utility<00:37:18.760> can<00:37:18.880> share<00:37:19.440> some<00:37:19.640> of<00:37:19.839> that<00:37:20.119> cost

00:37:20.349 --> 00:37:20.359 align:start position:0%
the utility can share some of that cost
 

00:37:20.359 --> 00:37:22.270 align:start position:0%
the utility can share some of that cost
savings<00:37:20.880> there's<00:37:21.200> some<00:37:21.480> models<00:37:21.800> being<00:37:22.000> talked

00:37:22.270 --> 00:37:22.280 align:start position:0%
savings there's some models being talked
 

00:37:22.280 --> 00:37:25.190 align:start position:0%
savings there's some models being talked
about<00:37:22.440> in<00:37:22.599> different<00:37:23.319> jurisdictions<00:37:24.319> and<00:37:24.640> you

00:37:25.190 --> 00:37:25.200 align:start position:0%
about in different jurisdictions and you
 

00:37:25.200 --> 00:37:28.750 align:start position:0%
about in different jurisdictions and you
know<00:37:26.200> B<00:37:26.760> put<00:37:27.240> because<00:37:27.400> I<00:37:27.720> put<00:37:27.880> a<00:37:28.160> tweet<00:37:28.560> in

00:37:28.750 --> 00:37:28.760 align:start position:0%
know B put because I put a tweet in
 

00:37:28.760 --> 00:37:30.510 align:start position:0%
know B put because I put a tweet in
there<00:37:29.000> maybe<00:37:29.200> it's<00:37:29.359> called<00:37:29.560> an<00:37:29.760> X<00:37:30.119> now<00:37:30.359> or

00:37:30.510 --> 00:37:30.520 align:start position:0%
there maybe it's called an X now or
 

00:37:30.520 --> 00:37:34.710 align:start position:0%
there maybe it's called an X now or
something<00:37:31.319> elon's<00:37:32.240> changes<00:37:33.160> but<00:37:33.560> um<00:37:34.200> you<00:37:34.319> know

00:37:34.710 --> 00:37:34.720 align:start position:0%
something elon's changes but um you know
 

00:37:34.720 --> 00:37:36.870 align:start position:0%
something elon's changes but um you know
Burke<00:37:35.040> is<00:37:35.200> coming<00:37:35.480> out<00:37:35.880> with<00:37:36.680> an

00:37:36.870 --> 00:37:36.880 align:start position:0%
Burke is coming out with an
 

00:37:36.880 --> 00:37:39.710 align:start position:0%
Burke is coming out with an
interconnection<00:37:37.560> noer<00:37:38.560> uh<00:37:38.800> or<00:37:38.960> a<00:37:39.079> ruling<00:37:39.440> on

00:37:39.710 --> 00:37:39.720 align:start position:0%
interconnection noer uh or a ruling on
 

00:37:39.720 --> 00:37:41.470 align:start position:0%
interconnection noer uh or a ruling on
the<00:37:40.040> interconnection<00:37:40.520> noer<00:37:40.880> that<00:37:41.000> was<00:37:41.319> put

00:37:41.470 --> 00:37:41.480 align:start position:0%
the interconnection noer that was put
 

00:37:41.480 --> 00:37:45.630 align:start position:0%
the interconnection noer that was put
out<00:37:41.800> last<00:37:42.040> year<00:37:42.839> could<00:37:43.000> be<00:37:43.200> even<00:37:43.560> this<00:37:44.000> week<00:37:45.000> um

00:37:45.630 --> 00:37:45.640 align:start position:0%
out last year could be even this week um
 

00:37:45.640 --> 00:37:47.470 align:start position:0%
out last year could be even this week um
and<00:37:45.760> it's<00:37:46.160> going<00:37:46.400> to<00:37:46.599> have<00:37:46.839> language<00:37:47.359> that

00:37:47.470 --> 00:37:47.480 align:start position:0%
and it's going to have language that
 

00:37:47.480 --> 00:37:50.829 align:start position:0%
and it's going to have language that
says<00:37:48.079> utilities<00:37:49.079> should<00:37:49.560> use<00:37:50.079> great<00:37:50.359> advaning

00:37:50.829 --> 00:37:50.839 align:start position:0%
says utilities should use great advaning
 

00:37:50.839 --> 00:37:53.270 align:start position:0%
says utilities should use great advaning
Technologies<00:37:51.599> as<00:37:51.720> a<00:37:52.000> part<00:37:52.560> of<00:37:53.000> the

00:37:53.270 --> 00:37:53.280 align:start position:0%
Technologies as a part of the
 

00:37:53.280 --> 00:37:55.630 align:start position:0%
Technologies as a part of the
interconnection<00:37:54.319> processes<00:37:55.319> at<00:37:55.440> least

00:37:55.630 --> 00:37:55.640 align:start position:0%
interconnection processes at least
 

00:37:55.640 --> 00:37:57.750 align:start position:0%
interconnection processes at least
that's<00:37:55.760> what<00:37:55.920> the<00:37:56.040> industry<00:37:56.920> I<00:37:57.480> I<00:37:57.520> don't<00:37:57.680> have

00:37:57.750 --> 00:37:57.760 align:start position:0%
that's what the industry I I don't have
 

00:37:57.760 --> 00:38:01.550 align:start position:0%
that's what the industry I I don't have
a<00:37:57.880> crystal<00:37:58.359> ball<00:37:59.319> um<00:37:59.839> but<00:38:00.680> fer<00:38:01.000> has<00:38:01.119> been<00:38:01.280> very

00:38:01.550 --> 00:38:01.560 align:start position:0%
a crystal ball um but fer has been very
 

00:38:01.560 --> 00:38:04.470 align:start position:0%
a crystal ball um but fer has been very
active<00:38:02.119> and<00:38:02.319> looking<00:38:02.640> at<00:38:03.040> how<00:38:03.200> do<00:38:03.400> we<00:38:04.319> that

00:38:04.470 --> 00:38:04.480 align:start position:0%
active and looking at how do we that
 

00:38:04.480 --> 00:38:05.829 align:start position:0%
active and looking at how do we that
they<00:38:04.680> recognize<00:38:05.079> the<00:38:05.200> same<00:38:05.440> problem<00:38:05.680> with

00:38:05.829 --> 00:38:05.839 align:start position:0%
they recognize the same problem with
 

00:38:05.839 --> 00:38:08.069 align:start position:0%
they recognize the same problem with
limited<00:38:06.119> transmission<00:38:06.720> capacity<00:38:07.720> and<00:38:07.920> they

00:38:08.069 --> 00:38:08.079 align:start position:0%
limited transmission capacity and they
 

00:38:08.079 --> 00:38:09.829 align:start position:0%
limited transmission capacity and they
recognize<00:38:08.480> the<00:38:08.640> problem<00:38:08.960> that<00:38:09.440> it's<00:38:09.599> going<00:38:09.720> to

00:38:09.829 --> 00:38:09.839 align:start position:0%
recognize the problem that it's going to
 

00:38:09.839 --> 00:38:11.790 align:start position:0%
recognize the problem that it's going to
be<00:38:10.079> very<00:38:10.359> expensive<00:38:10.800> to<00:38:10.960> build<00:38:11.240> that<00:38:11.400> capacity

00:38:11.790 --> 00:38:11.800 align:start position:0%
be very expensive to build that capacity
 

00:38:11.800 --> 00:38:13.589 align:start position:0%
be very expensive to build that capacity
if<00:38:11.920> we<00:38:12.040> don't<00:38:12.640> use<00:38:12.880> all<00:38:13.000> the<00:38:13.079> tools<00:38:13.319> in<00:38:13.440> our

00:38:13.589 --> 00:38:13.599 align:start position:0%
if we don't use all the tools in our
 

00:38:13.599 --> 00:38:15.950 align:start position:0%
if we don't use all the tools in our
tool

00:38:15.950 --> 00:38:15.960 align:start position:0%
 
 

00:38:15.960 --> 00:38:18.589 align:start position:0%
 
boxs<00:38:16.960> and<00:38:17.160> that's<00:38:17.560> I<00:38:17.680> think<00:38:17.960> that's<00:38:18.440> yeah

00:38:18.589 --> 00:38:18.599 align:start position:0%
boxs and that's I think that's yeah
 

00:38:18.599 --> 00:38:21.230 align:start position:0%
boxs and that's I think that's yeah
that's<00:38:18.720> the<00:38:18.920> last<00:38:19.119> slide<00:38:19.480> so<00:38:19.920> um<00:38:20.599> can<00:38:21.040> any

00:38:21.230 --> 00:38:21.240 align:start position:0%
that's the last slide so um can any
 

00:38:21.240 --> 00:38:23.349 align:start position:0%
that's the last slide so um can any
question<00:38:21.599> ask<00:38:21.760> a<00:38:21.960> question<00:38:22.920> this<00:38:23.040> is<00:38:23.160> going<00:38:23.280> to

00:38:23.349 --> 00:38:23.359 align:start position:0%
question ask a question this is going to
 

00:38:23.359 --> 00:38:24.630 align:start position:0%
question ask a question this is going to
be<00:38:23.440> a<00:38:23.560> dumb<00:38:23.800> question<00:38:24.000> for<00:38:24.160> everybody<00:38:24.400> else<00:38:24.560> in

00:38:24.630 --> 00:38:24.640 align:start position:0%
be a dumb question for everybody else in
 

00:38:24.640 --> 00:38:27.710 align:start position:0%
be a dumb question for everybody else in
the<00:38:24.720> room<00:38:24.880> so<00:38:25.040> I<00:38:25.200> apologize<00:38:26.200> um<00:38:26.720> how<00:38:26.920> much<00:38:27.520> if

00:38:27.710 --> 00:38:27.720 align:start position:0%
the room so I apologize um how much if
 

00:38:27.720 --> 00:38:31.829 align:start position:0%
the room so I apologize um how much if
any<00:38:28.640> of<00:38:28.800> our<00:38:29.040> need<00:38:29.359> to<00:38:29.760> enhance<00:38:30.839> transmission

00:38:31.829 --> 00:38:31.839 align:start position:0%
any of our need to enhance transmission
 

00:38:31.839 --> 00:38:35.510 align:start position:0%
any of our need to enhance transmission
is<00:38:32.319> due<00:38:33.079> just<00:38:33.520> to<00:38:34.520> the<00:38:34.680> demand<00:38:35.119> side<00:38:35.400> The

00:38:35.510 --> 00:38:35.520 align:start position:0%
is due just to the demand side The
 

00:38:35.520 --> 00:38:38.390 align:start position:0%
is due just to the demand side The
increased<00:38:36.000> demand<00:38:36.319> for<00:38:36.720> electricity<00:38:37.720> versus

00:38:38.390 --> 00:38:38.400 align:start position:0%
increased demand for electricity versus
 

00:38:38.400 --> 00:38:39.950 align:start position:0%
increased demand for electricity versus
the<00:38:38.520> shift<00:38:38.800> to<00:38:38.960> Renewables<00:38:39.680> on<00:38:39.839> the

00:38:39.950 --> 00:38:39.960 align:start position:0%
the shift to Renewables on the
 

00:38:39.960 --> 00:38:42.910 align:start position:0%
the shift to Renewables on the
generation<00:38:40.520> side<00:38:41.480> I<00:38:41.599> think<00:38:41.720> it<00:38:41.880> has<00:38:42.040> to<00:38:42.160> be<00:38:42.800> I

00:38:42.910 --> 00:38:42.920 align:start position:0%
generation side I think it has to be I
 

00:38:42.920 --> 00:38:44.190 align:start position:0%
generation side I think it has to be I
think<00:38:43.040> it<00:38:43.119> has<00:38:43.240> to<00:38:43.319> be<00:38:43.480> both<00:38:43.680> you<00:38:43.760> know

00:38:44.190 --> 00:38:44.200 align:start position:0%
think it has to be both you know
 

00:38:44.200 --> 00:38:46.910 align:start position:0%
think it has to be both you know
developers<00:38:44.599> aren't<00:38:44.880> building<00:38:45.800> um<00:38:46.079> projects

00:38:46.910 --> 00:38:46.920 align:start position:0%
developers aren't building um projects
 

00:38:46.920 --> 00:38:50.870 align:start position:0%
developers aren't building um projects
with<00:38:47.119> no<00:38:47.640> off-taker<00:38:48.640> right<00:38:49.119> and<00:38:49.359> so<00:38:50.280> um<00:38:50.599> yes

00:38:50.870 --> 00:38:50.880 align:start position:0%
with no off-taker right and so um yes
 

00:38:50.880 --> 00:38:53.589 align:start position:0%
with no off-taker right and so um yes
the<00:38:51.280> que<00:38:52.280> I<00:38:52.319> mean<00:38:52.560> you<00:38:52.680> looked<00:38:52.880> at<00:38:53.119> go<00:38:53.280> back<00:38:53.400> to

00:38:53.589 --> 00:38:53.599 align:start position:0%
the que I mean you looked at go back to
 

00:38:53.599 --> 00:38:59.589 align:start position:0%
the que I mean you looked at go back to
that<00:38:53.760> pjm<00:38:54.400> Q<00:38:55.400> um<00:38:56.200> didn't<00:38:56.560> 297<00:38:57.560> gaw<00:38:58.200> is<00:38:58.520> is<00:38:58.760> more

00:38:59.589 --> 00:38:59.599 align:start position:0%
that pjm Q um didn't 297 gaw is is more
 

00:38:59.599 --> 00:39:02.630 align:start position:0%
that pjm Q um didn't 297 gaw is is more
more<00:38:59.920> than<00:39:00.319> pjm's<00:39:00.880> peak<00:39:01.119> of<00:39:01.240> like<00:39:02.079> 160<00:39:02.520> or

00:39:02.630 --> 00:39:02.640 align:start position:0%
more than pjm's peak of like 160 or
 

00:39:02.640 --> 00:39:05.390 align:start position:0%
more than pjm's peak of like 160 or
something<00:39:02.960> like<00:39:03.119> that<00:39:03.280> some<00:39:03.640> Peak<00:39:04.040> so<00:39:04.640> yes<00:39:05.119> not

00:39:05.390 --> 00:39:05.400 align:start position:0%
something like that some Peak so yes not
 

00:39:05.400 --> 00:39:06.950 align:start position:0%
something like that some Peak so yes not
all<00:39:05.560> of<00:39:05.680> this<00:39:05.839> is<00:39:06.040> going<00:39:06.240> to<00:39:06.359> be<00:39:06.480> built<00:39:06.839> that's

00:39:06.950 --> 00:39:06.960 align:start position:0%
all of this is going to be built that's
 

00:39:06.960 --> 00:39:09.349 align:start position:0%
all of this is going to be built that's
a<00:39:07.079> very<00:39:07.240> inflated<00:39:08.119> 2007<00:39:08.680> is<00:39:08.839> probably<00:39:09.040> like

00:39:09.349 --> 00:39:09.359 align:start position:0%
a very inflated 2007 is probably like
 

00:39:09.359 --> 00:39:11.790 align:start position:0%
a very inflated 2007 is probably like
160<00:39:09.680> or<00:39:09.800> something<00:39:10.160> yes<00:39:11.079> agree<00:39:11.440> agree<00:39:11.680> with

00:39:11.790 --> 00:39:11.800 align:start position:0%
160 or something yes agree agree with
 

00:39:11.800 --> 00:39:13.670 align:start position:0%
160 or something yes agree agree with
you<00:39:12.040> and<00:39:12.319> got<00:39:12.560> think<00:39:12.720> that<00:39:12.839> Renewables<00:39:13.359> don't

00:39:13.670 --> 00:39:13.680 align:start position:0%
you and got think that Renewables don't
 

00:39:13.680 --> 00:39:15.430 align:start position:0%
you and got think that Renewables don't
have<00:39:14.079> you<00:39:14.160> know<00:39:14.319> the<00:39:14.560> effective<00:39:14.880> lcer

00:39:15.430 --> 00:39:15.440 align:start position:0%
have you know the effective lcer
 

00:39:15.440 --> 00:39:17.470 align:start position:0%
have you know the effective lcer
capacity<00:39:15.839> is<00:39:16.040> not<00:39:16.800> their<00:39:16.960> name<00:39:17.240> plate

00:39:17.470 --> 00:39:17.480 align:start position:0%
capacity is not their name plate
 

00:39:17.480 --> 00:39:19.150 align:start position:0%
capacity is not their name plate
capacity<00:39:17.960> right<00:39:18.200> so<00:39:18.319> we're<00:39:18.480> going<00:39:18.680> to<00:39:18.800> build

00:39:19.150 --> 00:39:19.160 align:start position:0%
capacity right so we're going to build
 

00:39:19.160 --> 00:39:21.190 align:start position:0%
capacity right so we're going to build
more<00:39:19.599> name<00:39:19.920> plate<00:39:20.240> capacity<00:39:20.800> then<00:39:20.920> we<00:39:21.040> have

00:39:21.190 --> 00:39:21.200 align:start position:0%
more name plate capacity then we have
 

00:39:21.200 --> 00:39:25.390 align:start position:0%
more name plate capacity then we have
Peak<00:39:21.839> but<00:39:22.280> yeah<00:39:22.440> to<00:39:22.599> your<00:39:22.960> question<00:39:24.119> uh<00:39:25.119> I<00:39:25.280> I

00:39:25.390 --> 00:39:25.400 align:start position:0%
Peak but yeah to your question uh I I
 

00:39:25.400 --> 00:39:27.470 align:start position:0%
Peak but yeah to your question uh I I
think<00:39:25.560> it's<00:39:25.760> both<00:39:26.040> you<00:39:26.160> know<00:39:26.680> at<00:39:26.800> least<00:39:27.319> from

00:39:27.470 --> 00:39:27.480 align:start position:0%
think it's both you know at least from
 

00:39:27.480 --> 00:39:29.870 align:start position:0%
think it's both you know at least from
speaking<00:39:27.760> from<00:39:28.000> as's<00:39:28.680> standpoint<00:39:29.240> like<00:39:29.680> we

00:39:29.870 --> 00:39:29.880 align:start position:0%
speaking from as's standpoint like we
 

00:39:29.880 --> 00:39:31.790 align:start position:0%
speaking from as's standpoint like we
are<00:39:30.119> not<00:39:30.440> building<00:39:30.960> Pro<00:39:31.240> we're<00:39:31.359> not<00:39:31.560> looking

00:39:31.790 --> 00:39:31.800 align:start position:0%
are not building Pro we're not looking
 

00:39:31.800 --> 00:39:33.390 align:start position:0%
are not building Pro we're not looking
at<00:39:32.000> developing<00:39:32.480> projects<00:39:32.880> where<00:39:33.040> we<00:39:33.160> don't

00:39:33.390 --> 00:39:33.400 align:start position:0%
at developing projects where we don't
 

00:39:33.400 --> 00:39:36.109 align:start position:0%
at developing projects where we don't
have<00:39:33.520> an<00:39:33.640> off-taker<00:39:34.440> so<00:39:34.599> we're<00:39:34.720> seeing<00:39:35.440> both

00:39:36.109 --> 00:39:36.119 align:start position:0%
have an off-taker so we're seeing both
 

00:39:36.119 --> 00:39:38.550 align:start position:0%
have an off-taker so we're seeing both
yes<00:39:36.280> there's<00:39:36.760> incredible<00:39:37.359> with<00:39:37.599> the<00:39:38.079> demand

00:39:38.550 --> 00:39:38.560 align:start position:0%
yes there's incredible with the demand
 

00:39:38.560 --> 00:39:43.829 align:start position:0%
yes there's incredible with the demand
for<00:39:39.400> building<00:39:39.839> Renewables<00:39:40.480> with<00:39:40.640> the<00:39:41.200> IRA<00:39:42.200> um

00:39:43.829 --> 00:39:43.839 align:start position:0%
for building Renewables with the IRA um
 

00:39:43.839 --> 00:39:47.670 align:start position:0%
for building Renewables with the IRA um
but<00:39:44.839> we're<00:39:45.079> also<00:39:45.359> seeing<00:39:46.040> offers<00:39:47.000> you<00:39:47.079> know

00:39:47.670 --> 00:39:47.680 align:start position:0%
but we're also seeing offers you know
 

00:39:47.680 --> 00:39:51.430 align:start position:0%
but we're also seeing offers you know
and<00:39:48.359> uh<00:39:49.359> you<00:39:49.480> know<00:39:49.800> load<00:39:50.079> serving<00:39:50.440> entities

00:39:51.430 --> 00:39:51.440 align:start position:0%
and uh you know load serving entities
 

00:39:51.440 --> 00:39:53.030 align:start position:0%
and uh you know load serving entities
consistently<00:39:52.280> to<00:39:52.560> you<00:39:52.640> know<00:39:52.760> demand

00:39:53.030 --> 00:39:53.040 align:start position:0%
consistently to you know demand
 

00:39:53.040 --> 00:39:55.150 align:start position:0%
consistently to you know demand
renewable<00:39:53.640> but<00:39:53.800> but<00:39:53.920> it's<00:39:54.119> nothing<00:39:54.560> special

00:39:55.150 --> 00:39:55.160 align:start position:0%
renewable but but it's nothing special
 

00:39:55.160 --> 00:39:58.550 align:start position:0%
renewable but but it's nothing special
about<00:39:56.040> Ren<00:39:56.400> reble<00:39:56.760> generation<00:39:57.640> it's<00:39:57.880> just<00:39:58.119> the

00:39:58.550 --> 00:39:58.560 align:start position:0%
about Ren reble generation it's just the
 

00:39:58.560 --> 00:40:01.630 align:start position:0%
about Ren reble generation it's just the
increased<00:39:59.319> demand<00:40:00.319> that's<00:40:00.480> going<00:40:00.599> to<00:40:00.720> require

00:40:01.630 --> 00:40:01.640 align:start position:0%
increased demand that's going to require
 

00:40:01.640 --> 00:40:03.790 align:start position:0%
increased demand that's going to require
I<00:40:01.720> think<00:40:01.920> that<00:40:02.839> I<00:40:02.920> think

00:40:03.790 --> 00:40:03.800 align:start position:0%
I think that I think
 

00:40:03.800 --> 00:40:06.470 align:start position:0%
I think that I think
it's<00:40:04.800> yeah<00:40:04.920> it's<00:40:05.160> both<00:40:05.599> and<00:40:05.960> you<00:40:06.119> got<00:40:06.200> to<00:40:06.319> think

00:40:06.470 --> 00:40:06.480 align:start position:0%
it's yeah it's both and you got to think
 

00:40:06.480 --> 00:40:09.829 align:start position:0%
it's yeah it's both and you got to think
too<00:40:07.200> that<00:40:07.359> with<00:40:07.480> the<00:40:07.599> transition<00:40:08.440> these<00:40:08.839> solar

00:40:09.829 --> 00:40:09.839 align:start position:0%
too that with the transition these solar
 

00:40:09.839 --> 00:40:13.109 align:start position:0%
too that with the transition these solar
uh<00:40:09.960> farms<00:40:10.520> and<00:40:10.680> and<00:40:10.800> then<00:40:11.000> also<00:40:11.880> um<00:40:12.880> you<00:40:13.000> know

00:40:13.109 --> 00:40:13.119 align:start position:0%
uh farms and and then also um you know
 

00:40:13.119 --> 00:40:16.630 align:start position:0%
uh farms and and then also um you know
wind<00:40:13.400> generation<00:40:14.119> is<00:40:14.319> located<00:40:15.280> away<00:40:15.880> from<00:40:16.480> the

00:40:16.630 --> 00:40:16.640 align:start position:0%
wind generation is located away from the
 

00:40:16.640 --> 00:40:19.870 align:start position:0%
wind generation is located away from the
load<00:40:16.880> centers<00:40:17.440> typically<00:40:18.440> right<00:40:19.119> more<00:40:19.560> maybe

00:40:19.870 --> 00:40:19.880 align:start position:0%
load centers typically right more maybe
 

00:40:19.880 --> 00:40:24.030 align:start position:0%
load centers typically right more maybe
so<00:40:20.640> than<00:40:20.880> a<00:40:21.079> gas<00:40:21.319> or<00:40:21.520> a<00:40:21.640> coal<00:40:22.040> or<00:40:22.520> nuclear<00:40:23.079> plant

00:40:24.030 --> 00:40:24.040 align:start position:0%
so than a gas or a coal or nuclear plant
 

00:40:24.040 --> 00:40:26.670 align:start position:0%
so than a gas or a coal or nuclear plant
um<00:40:24.560> and<00:40:24.640> so<00:40:24.960> that<00:40:25.480> hence<00:40:25.800> requires<00:40:26.200> more<00:40:26.359> War

00:40:26.670 --> 00:40:26.680 align:start position:0%
um and so that hence requires more War
 

00:40:26.680 --> 00:40:28.430 align:start position:0%
um and so that hence requires more War
transmission<00:40:27.200> the<00:40:27.319> generation<00:40:27.839> profiles

00:40:28.430 --> 00:40:28.440 align:start position:0%
transmission the generation profiles
 

00:40:28.440 --> 00:40:29.829 align:start position:0%
transmission the generation profiles
highly<00:40:28.800> different<00:40:29.119> that<00:40:29.240> you<00:40:29.359> would<00:40:29.520> expect

00:40:29.829 --> 00:40:29.839 align:start position:0%
highly different that you would expect
 

00:40:29.839 --> 00:40:31.150 align:start position:0%
highly different that you would expect
from

00:40:31.150 --> 00:40:31.160 align:start position:0%
from
 

00:40:31.160 --> 00:40:34.790 align:start position:0%
from
like<00:40:32.240> plan<00:40:33.240> gas<00:40:33.720> yeah<00:40:33.920> because<00:40:34.160> of<00:40:34.520> because

00:40:34.790 --> 00:40:34.800 align:start position:0%
like plan gas yeah because of because
 

00:40:34.800 --> 00:40:37.510 align:start position:0%
like plan gas yeah because of because
they're<00:40:35.079> not<00:40:35.800> uh<00:40:36.359> you<00:40:36.480> know

00:40:37.510 --> 00:40:37.520 align:start position:0%
they're not uh you know
 

00:40:37.520 --> 00:40:41.030 align:start position:0%
they're not uh you know
98%<00:40:38.520> uh<00:40:38.760> online<00:40:39.520> all<00:40:39.640> the<00:40:39.800> time<00:40:40.160> you<00:40:40.440> need<00:40:40.800> more

00:40:41.030 --> 00:40:41.040 align:start position:0%
98% uh online all the time you need more
 

00:40:41.040 --> 00:40:44.069 align:start position:0%
98% uh online all the time you need more
transmission<00:40:41.640> to<00:40:42.040> to<00:40:42.359> share<00:40:42.880> when<00:40:43.000> the<00:40:43.119> sun<00:40:43.359> is

00:40:44.069 --> 00:40:44.079 align:start position:0%
transmission to to share when the sun is
 

00:40:44.079 --> 00:40:46.349 align:start position:0%
transmission to to share when the sun is
you<00:40:44.160> know<00:40:44.319> wind<00:40:44.480> is<00:40:44.599> blowing<00:40:44.880> one<00:40:45.040> place<00:40:45.560> so<00:40:46.040> so

00:40:46.349 --> 00:40:46.359 align:start position:0%
you know wind is blowing one place so so
 

00:40:46.359 --> 00:40:48.109 align:start position:0%
you know wind is blowing one place so so
Skyler<00:40:46.760> and<00:40:46.880> I<00:40:47.040> and<00:40:47.119> others<00:40:47.359> deal<00:40:47.560> with<00:40:47.760> policy

00:40:48.109 --> 00:40:48.119 align:start position:0%
Skyler and I and others deal with policy
 

00:40:48.119 --> 00:40:51.150 align:start position:0%
Skyler and I and others deal with policy
makers<00:40:48.680> a<00:40:48.839> lot<00:40:49.280> some<00:40:49.480> of<00:40:49.680> whom<00:40:50.520> aren't<00:40:50.839> super

00:40:51.150 --> 00:40:51.160 align:start position:0%
makers a lot some of whom aren't super
 

00:40:51.160 --> 00:40:54.109 align:start position:0%
makers a lot some of whom aren't super
supportive<00:40:51.680> of<00:40:52.200> our<00:40:52.400> transition<00:40:53.119> Renewables

00:40:54.109 --> 00:40:54.119 align:start position:0%
supportive of our transition Renewables
 

00:40:54.119 --> 00:40:55.829 align:start position:0%
supportive of our transition Renewables
and<00:40:54.319> so<00:40:55.000> these<00:40:55.119> are<00:40:55.280> the<00:40:55.400> types<00:40:55.599> of<00:40:55.680> things

00:40:55.829 --> 00:40:55.839 align:start position:0%
and so these are the types of things
 

00:40:55.839 --> 00:40:57.910 align:start position:0%
and so these are the types of things
that<00:40:56.000> they<00:40:56.119> point<00:40:56.319> going<00:40:56.520> to<00:40:56.760> and<00:40:56.920> say<00:40:57.520> see

00:40:57.910 --> 00:40:57.920 align:start position:0%
that they point going to and say see
 

00:40:57.920 --> 00:41:00.510 align:start position:0%
that they point going to and say see
these<00:40:58.200> costs<00:40:58.520> you're<00:40:58.760> piling<00:40:59.119> on<00:41:00.079> because<00:41:00.319> of

00:41:00.510 --> 00:41:00.520 align:start position:0%
these costs you're piling on because of
 

00:41:00.520 --> 00:41:02.510 align:start position:0%
these costs you're piling on because of
the<00:41:01.000> transition<00:41:01.680> so<00:41:01.839> so<00:41:02.040> what<00:41:02.160> I<00:41:02.240> would

00:41:02.510 --> 00:41:02.520 align:start position:0%
the transition so so what I would
 

00:41:02.520 --> 00:41:06.309 align:start position:0%
the transition so so what I would
actually<00:41:03.000> add<00:41:03.440> to<00:41:03.760> that<00:41:04.119> is<00:41:04.599> that<00:41:05.599> this<00:41:05.800> year

00:41:06.309 --> 00:41:06.319 align:start position:0%
actually add to that is that this year
 

00:41:06.319 --> 00:41:07.349 align:start position:0%
actually add to that is that this year
so<00:41:06.560> for

00:41:07.349 --> 00:41:07.359 align:start position:0%
so for
 

00:41:07.359 --> 00:41:11.030 align:start position:0%
so for
2022<00:41:08.359> there<00:41:08.480> were<00:41:08.839> 20<00:41:09.480> billion<00:41:10.160> dollar<00:41:10.800> of

00:41:11.030 --> 00:41:11.040 align:start position:0%
2022 there were 20 billion dollar of
 

00:41:11.040 --> 00:41:12.950 align:start position:0%
2022 there were 20 billion dollar of
transmission<00:41:11.720> congestion<00:41:12.359> costs<00:41:12.680> for

00:41:12.950 --> 00:41:12.960 align:start position:0%
transmission congestion costs for
 

00:41:12.960 --> 00:41:15.710 align:start position:0%
transmission congestion costs for
consumers<00:41:13.599> in<00:41:13.720> the<00:41:13.880> US<00:41:14.560> the<00:41:14.680> year<00:41:15.000> before<00:41:15.480> that

00:41:15.710 --> 00:41:15.720 align:start position:0%
consumers in the US the year before that
 

00:41:15.720 --> 00:41:18.670 align:start position:0%
consumers in the US the year before that
it<00:41:15.839> was<00:41:16.160> 13<00:41:16.839> billion<00:41:17.760> the<00:41:17.880> year<00:41:18.119> before<00:41:18.480> that

00:41:18.670 --> 00:41:18.680 align:start position:0%
it was 13 billion the year before that
 

00:41:18.680 --> 00:41:22.510 align:start position:0%
it was 13 billion the year before that
it<00:41:18.800> was<00:41:19.079> half<00:41:19.560> that<00:41:20.440> so<00:41:21.160> it's<00:41:21.400> not<00:41:21.880> that<00:41:22.240> we're

00:41:22.510 --> 00:41:22.520 align:start position:0%
it was half that so it's not that we're
 

00:41:22.520 --> 00:41:25.630 align:start position:0%
it was half that so it's not that we're
trying<00:41:22.800> to<00:41:23.000> make<00:41:23.319> room<00:41:23.960> for<00:41:24.800> New<00:41:25.119> Generation

00:41:25.630 --> 00:41:25.640 align:start position:0%
trying to make room for New Generation
 

00:41:25.640 --> 00:41:28.309 align:start position:0%
trying to make room for New Generation
and<00:41:25.760> new<00:41:25.920> load<00:41:26.400> it's<00:41:26.640> that<00:41:27.200> there<00:41:27.440> isn't<00:41:27.839> room

00:41:28.309 --> 00:41:28.319 align:start position:0%
and new load it's that there isn't room
 

00:41:28.319 --> 00:41:30.150 align:start position:0%
and new load it's that there isn't room
for<00:41:28.599> the<00:41:28.760> new<00:41:28.960> generation<00:41:29.480> and<00:41:29.640> the<00:41:29.720> new<00:41:29.880> load

00:41:30.150 --> 00:41:30.160 align:start position:0%
for the new generation and the new load
 

00:41:30.160 --> 00:41:33.910 align:start position:0%
for the new generation and the new load
that<00:41:30.280> is<00:41:30.920> already<00:41:31.920> there<00:41:32.839> so<00:41:33.160> it's<00:41:33.359> like<00:41:33.720> these

00:41:33.910 --> 00:41:33.920 align:start position:0%
that is already there so it's like these
 

00:41:33.920 --> 00:41:35.550 align:start position:0%
that is already there so it's like these
are<00:41:34.160> costs<00:41:34.520> that<00:41:34.640> can<00:41:34.760> be

00:41:35.550 --> 00:41:35.560 align:start position:0%
are costs that can be
 

00:41:35.560 --> 00:41:40.230 align:start position:0%
are costs that can be
alleviated<00:41:36.640> by<00:41:37.640> using<00:41:38.119> gets<00:41:38.960> by<00:41:39.760> you<00:41:39.920> know

00:41:40.230 --> 00:41:40.240 align:start position:0%
alleviated by using gets by you know
 

00:41:40.240 --> 00:41:42.589 align:start position:0%
alleviated by using gets by you know
using<00:41:40.599> storage<00:41:40.960> is<00:41:41.160> transmission<00:41:41.960> and

00:41:42.589 --> 00:41:42.599 align:start position:0%
using storage is transmission and
 

00:41:42.599 --> 00:41:45.309 align:start position:0%
using storage is transmission and
integrating<00:41:43.440> Renewables<00:41:44.119> that<00:41:44.280> way<00:41:44.720> so<00:41:45.200> the

00:41:45.309 --> 00:41:45.319 align:start position:0%
integrating Renewables that way so the
 

00:41:45.319 --> 00:41:47.109 align:start position:0%
integrating Renewables that way so the
congestion<00:41:46.200> I<00:41:46.280> want<00:41:46.400> to<00:41:46.520> make<00:41:46.640> sure<00:41:46.800> I<00:41:46.920> get

00:41:47.109 --> 00:41:47.119 align:start position:0%
congestion I want to make sure I get
 

00:41:47.119 --> 00:41:50.069 align:start position:0%
congestion I want to make sure I get
that's<00:41:47.599> right<00:41:48.000> so<00:41:48.440> the<00:41:48.640> congestion<00:41:49.200> charges

00:41:50.069 --> 00:41:50.079 align:start position:0%
that's right so the congestion charges
 

00:41:50.079 --> 00:41:53.510 align:start position:0%
that's right so the congestion charges
your<00:41:50.400> statement<00:41:51.319> suggests<00:41:52.319> that<00:41:52.520> instead<00:41:53.160> of

00:41:53.510 --> 00:41:53.520 align:start position:0%
your statement suggests that instead of
 

00:41:53.520 --> 00:41:55.270 align:start position:0%
your statement suggests that instead of
like<00:41:53.680> the<00:41:53.839> day<00:41:54.040> ahead<00:41:54.359> demand<00:41:54.760> and<00:41:54.880> the<00:41:55.000> same

00:41:55.270 --> 00:41:55.280 align:start position:0%
like the day ahead demand and the same
 

00:41:55.280 --> 00:41:58.550 align:start position:0%
like the day ahead demand and the same
day<00:41:55.560> demand<00:41:56.040> which<00:41:56.240> which<00:41:56.720> is<00:41:57.720> you<00:41:57.839> know

00:41:58.550 --> 00:41:58.560 align:start position:0%
day demand which which is you know
 

00:41:58.560 --> 00:42:00.270 align:start position:0%
day demand which which is you know
pushing<00:41:58.880> us<00:41:59.079> towards<00:41:59.359> those<00:41:59.599> congestion

00:42:00.270 --> 00:42:00.280 align:start position:0%
pushing us towards those congestion
 

00:42:00.280 --> 00:42:04.510 align:start position:0%
pushing us towards those congestion
charges<00:42:01.280> by<00:42:01.599> introduction<00:42:02.599> of<00:42:03.440> this<00:42:03.800> into<00:42:04.280> the

00:42:04.510 --> 00:42:04.520 align:start position:0%
charges by introduction of this into the
 

00:42:04.520 --> 00:42:06.190 align:start position:0%
charges by introduction of this into the
planning<00:42:05.119> process<00:42:05.599> as<00:42:05.760> well<00:42:05.880> as<00:42:06.000> the

00:42:06.190 --> 00:42:06.200 align:start position:0%
planning process as well as the
 

00:42:06.200 --> 00:42:08.750 align:start position:0%
planning process as well as the
operation<00:42:06.880> process<00:42:07.359> that<00:42:07.560> 20<00:42:07.920> billion<00:42:08.240> or<00:42:08.400> 40

00:42:08.750 --> 00:42:08.760 align:start position:0%
operation process that 20 billion or 40
 

00:42:08.760 --> 00:42:10.190 align:start position:0%
operation process that 20 billion or 40
billion<00:42:09.040> in<00:42:09.200> projection<00:42:09.839> whatever<00:42:10.119> the

00:42:10.190 --> 00:42:10.200 align:start position:0%
billion in projection whatever the
 

00:42:10.200 --> 00:42:12.510 align:start position:0%
billion in projection whatever the
number<00:42:10.440> is<00:42:10.560> going<00:42:10.680> to<00:42:10.760> be<00:42:10.880> for<00:42:11.079> next<00:42:11.319> year<00:42:12.240> we

00:42:12.510 --> 00:42:12.520 align:start position:0%
number is going to be for next year we
 

00:42:12.520 --> 00:42:14.109 align:start position:0%
number is going to be for next year we
shifting<00:42:13.280> and

00:42:14.109 --> 00:42:14.119 align:start position:0%
shifting and
 

00:42:14.119 --> 00:42:17.230 align:start position:0%
shifting and
reducing<00:42:15.119> by<00:42:15.680> getting<00:42:16.200> active<00:42:16.640> now<00:42:16.880> so<00:42:17.040> an

00:42:17.230 --> 00:42:17.240 align:start position:0%
reducing by getting active now so an
 

00:42:17.240 --> 00:42:20.670 align:start position:0%
reducing by getting active now so an
investment<00:42:18.119> now<00:42:19.119> could<00:42:19.520> potentially<00:42:20.200> reduce

00:42:20.670 --> 00:42:20.680 align:start position:0%
investment now could potentially reduce
 

00:42:20.680 --> 00:42:22.190 align:start position:0%
investment now could potentially reduce
congestion<00:42:21.119> charges<00:42:21.559> which<00:42:21.680> are<00:42:21.880> being

00:42:22.190 --> 00:42:22.200 align:start position:0%
congestion charges which are being
 

00:42:22.200 --> 00:42:24.870 align:start position:0%
congestion charges which are being
passed<00:42:22.559> on<00:42:23.559> they're<00:42:23.800> either<00:42:24.079> absorbed<00:42:24.520> by<00:42:24.680> the

00:42:24.870 --> 00:42:24.880 align:start position:0%
passed on they're either absorbed by the
 

00:42:24.880 --> 00:42:26.670 align:start position:0%
passed on they're either absorbed by the
utility<00:42:25.720> and<00:42:25.880> then

00:42:26.670 --> 00:42:26.680 align:start position:0%
utility and then
 

00:42:26.680 --> 00:42:29.790 align:start position:0%
utility and then
manest<00:42:27.400> themselves<00:42:27.839> as<00:42:27.960> a<00:42:28.119> GRC<00:42:29.079> approval

00:42:29.790 --> 00:42:29.800 align:start position:0%
manest themselves as a GRC approval
 

00:42:29.800 --> 00:42:32.390 align:start position:0%
manest themselves as a GRC approval
right<00:42:29.920> a<00:42:30.079> general<00:42:30.359> rate<00:42:30.599> case<00:42:31.040> approval<00:42:32.040> or

00:42:32.390 --> 00:42:32.400 align:start position:0%
right a general rate case approval or
 

00:42:32.400 --> 00:42:36.150 align:start position:0%
right a general rate case approval or
they<00:42:32.559> get<00:42:32.800> passed<00:42:33.160> on<00:42:33.520> depending<00:42:34.160> on<00:42:35.160> the<00:42:35.319> cni

00:42:36.150 --> 00:42:36.160 align:start position:0%
they get passed on depending on the cni
 

00:42:36.160 --> 00:42:37.950 align:start position:0%
they get passed on depending on the cni
they<00:42:36.440> to<00:42:36.599> deal<00:42:36.839> with<00:42:36.960> in<00:42:37.040> terms<00:42:37.280> of<00:42:37.480> capacity

00:42:37.950 --> 00:42:37.960 align:start position:0%
they to deal with in terms of capacity
 

00:42:37.960 --> 00:42:40.190 align:start position:0%
they to deal with in terms of capacity
charges<00:42:38.440> and<00:42:38.599> Ratchet<00:42:39.000> charges<00:42:39.880> things<00:42:40.040> of

00:42:40.190 --> 00:42:40.200 align:start position:0%
charges and Ratchet charges things of
 

00:42:40.200 --> 00:42:42.630 align:start position:0%
charges and Ratchet charges things of
that<00:42:40.400> nature<00:42:41.040> exactly<00:42:41.599> and<00:42:41.839> to<00:42:42.040> take<00:42:42.280> it<00:42:42.400> to

00:42:42.630 --> 00:42:42.640 align:start position:0%
that nature exactly and to take it to
 

00:42:42.640 --> 00:42:46.030 align:start position:0%
that nature exactly and to take it to
like<00:42:42.800> a<00:42:43.079> really<00:42:43.800> you<00:42:43.960> know<00:42:44.839> simple<00:42:45.440> example<00:42:45.920> if

00:42:46.030 --> 00:42:46.040 align:start position:0%
like a really you know simple example if
 

00:42:46.040 --> 00:42:49.589 align:start position:0%
like a really you know simple example if
you<00:42:46.280> have<00:42:46.440> a<00:42:46.599> line<00:42:47.000> that's<00:42:47.440> congested<00:42:48.599> today

00:42:49.589 --> 00:42:49.599 align:start position:0%
you have a line that's congested today
 

00:42:49.599 --> 00:42:52.069 align:start position:0%
you have a line that's congested today
because<00:42:49.880> it<00:42:50.079> has<00:42:50.280> a<00:42:50.559> static<00:42:51.079> rating<00:42:51.800> and<00:42:51.960> you

00:42:52.069 --> 00:42:52.079 align:start position:0%
because it has a static rating and you
 

00:42:52.079 --> 00:42:54.790 align:start position:0%
because it has a static rating and you
could<00:42:52.319> apply<00:42:52.680> DLR<00:42:53.440> and<00:42:53.599> you<00:42:53.720> could<00:42:54.240> increase

00:42:54.790 --> 00:42:54.800 align:start position:0%
could apply DLR and you could increase
 

00:42:54.800 --> 00:42:57.950 align:start position:0%
could apply DLR and you could increase
that<00:42:54.960> rating<00:42:55.319> by<00:42:55.440> an<00:42:55.559> average<00:42:55.839> of<00:42:56.280> 40%<00:42:57.280> or<00:42:57.720> by

00:42:57.950 --> 00:42:57.960 align:start position:0%
that rating by an average of 40% or by
 

00:42:57.960 --> 00:42:58.829 align:start position:0%
that rating by an average of 40% or by
up<00:42:58.119> to

00:42:58.829 --> 00:42:58.839 align:start position:0%
up to
 

00:42:58.839 --> 00:43:03.230 align:start position:0%
up to
40%<00:42:59.839> then<00:43:00.599> the<00:43:00.760> congestion<00:43:01.240> charges<00:43:02.040> due<00:43:02.359> to

00:43:03.230 --> 00:43:03.240 align:start position:0%
40% then the congestion charges due to
 

00:43:03.240 --> 00:43:05.670 align:start position:0%
40% then the congestion charges due to
congestion<00:43:03.680> on<00:43:03.839> that<00:43:04.119> line<00:43:04.720> would<00:43:04.920> go<00:43:05.160> down

00:43:05.670 --> 00:43:05.680 align:start position:0%
congestion on that line would go down
 

00:43:05.680 --> 00:43:08.710 align:start position:0%
congestion on that line would go down
that's<00:43:05.880> just<00:43:06.280> kind<00:43:06.400> of<00:43:06.559> like<00:43:06.880> the<00:43:07.720> that's<00:43:08.079> the

00:43:08.710 --> 00:43:08.720 align:start position:0%
that's just kind of like the that's the
 

00:43:08.720 --> 00:43:10.750 align:start position:0%
that's just kind of like the that's the
the<00:43:08.920> core<00:43:09.599> action<00:43:10.079> that<00:43:10.200> would<00:43:10.440> help

00:43:10.750 --> 00:43:10.760 align:start position:0%
the core action that would help
 

00:43:10.760 --> 00:43:15.950 align:start position:0%
the core action that would help
alleviate<00:43:11.520> congestion<00:43:12.520> across<00:43:13.079> the

00:43:15.950 --> 00:43:15.960 align:start position:0%
 
 

00:43:15.960 --> 00:43:19.349 align:start position:0%
 
US<00:43:16.960> what<00:43:17.079> are<00:43:17.280> the<00:43:17.800> besides<00:43:18.559> the<00:43:18.839> cost<00:43:19.160> of

00:43:19.349 --> 00:43:19.359 align:start position:0%
US what are the besides the cost of
 

00:43:19.359 --> 00:43:21.510 align:start position:0%
US what are the besides the cost of
investment<00:43:20.000> what<00:43:20.160> are<00:43:20.319> the<00:43:20.520> counterarguments

00:43:21.510 --> 00:43:21.520 align:start position:0%
investment what are the counterarguments
 

00:43:21.520 --> 00:43:25.069 align:start position:0%
investment what are the counterarguments
to<00:43:22.240> this<00:43:23.240> are<00:43:23.359> there<00:43:23.520> any<00:43:23.760> besides

00:43:25.069 --> 00:43:25.079 align:start position:0%
to this are there any besides
 

00:43:25.079 --> 00:43:28.030 align:start position:0%
to this are there any besides
cost<00:43:26.280> in<00:43:26.440> Virginia<00:43:27.400> Dominion<00:43:27.760> is<00:43:27.880> not

00:43:28.030 --> 00:43:28.040 align:start position:0%
cost in Virginia Dominion is not
 

00:43:28.040 --> 00:43:31.309 align:start position:0%
cost in Virginia Dominion is not
incentivized<00:43:28.800> to

00:43:31.309 --> 00:43:31.319 align:start position:0%
 
 

00:43:31.319 --> 00:43:35.150 align:start position:0%
 
implement<00:43:32.319> Catherine<00:43:33.200> B<00:43:34.200> she's<00:43:34.359> not<00:43:34.880> on<00:43:35.000> the

00:43:35.150 --> 00:43:35.160 align:start position:0%
implement Catherine B she's not on the
 

00:43:35.160 --> 00:43:37.510 align:start position:0%
implement Catherine B she's not on the
call<00:43:35.480> she<00:43:35.599> on<00:43:35.680> the<00:43:35.800> call<00:43:36.160> no<00:43:36.319> I<00:43:36.400> don't<00:43:36.599> think<00:43:36.720> so

00:43:37.510 --> 00:43:37.520 align:start position:0%
call she on the call no I don't think so
 

00:43:37.520 --> 00:43:38.470 align:start position:0%
call she on the call no I don't think so
back

00:43:38.470 --> 00:43:38.480 align:start position:0%
back
 

00:43:38.480 --> 00:43:43.750 align:start position:0%
back
minutes<00:43:39.480> we<00:43:39.640> can't<00:43:40.040> we<00:43:40.160> can't<00:43:40.319> take

00:43:43.750 --> 00:43:43.760 align:start position:0%
 
 

00:43:43.760 --> 00:43:46.349 align:start position:0%
 
minutes<00:43:44.760> um<00:43:44.960> I<00:43:45.160> is<00:43:45.280> this<00:43:45.559> stuff<00:43:45.800> not<00:43:46.040> covered

00:43:46.349 --> 00:43:46.359 align:start position:0%
minutes um I is this stuff not covered
 

00:43:46.359 --> 00:43:47.589 align:start position:0%
minutes um I is this stuff not covered
by<00:43:46.520> grid

00:43:47.589 --> 00:43:47.599 align:start position:0%
by grid
 

00:43:47.599 --> 00:43:52.190 align:start position:0%
by grid
mod<00:43:48.599> uh<00:43:49.079> the<00:43:49.280> doe<00:43:49.839> program<00:43:50.960> or<00:43:51.960> these

00:43:52.190 --> 00:43:52.200 align:start position:0%
mod uh the doe program or these
 

00:43:52.200 --> 00:43:53.790 align:start position:0%
mod uh the doe program or these
Investments<00:43:52.640> I<00:43:52.680> mean<00:43:52.839> obviously<00:43:53.280> dominions

00:43:53.790 --> 00:43:53.800 align:start position:0%
Investments I mean obviously dominions
 

00:43:53.800 --> 00:43:55.309 align:start position:0%
Investments I mean obviously dominions
incentivized<00:43:54.280> to<00:43:54.359> build<00:43:54.559> more<00:43:54.720> transmission

00:43:55.309 --> 00:43:55.319 align:start position:0%
incentivized to build more transmission
 

00:43:55.319 --> 00:43:59.710 align:start position:0%
incentivized to build more transmission
and<00:43:55.839> F<00:43:56.440> C<00:43:57.440> they<00:43:57.559> are<00:43:57.920> so<00:43:58.200> they<00:43:58.440> they<00:43:58.599> can<00:43:59.000> be

00:43:59.710 --> 00:43:59.720 align:start position:0%
and F C they are so they they can be
 

00:43:59.720 --> 00:44:02.030 align:start position:0%
and F C they are so they they can be
capitalized<00:44:00.440> by<00:44:00.640> utilities<00:44:01.319> that's<00:44:01.559> right

00:44:02.030 --> 00:44:02.040 align:start position:0%
capitalized by utilities that's right
 

00:44:02.040 --> 00:44:04.390 align:start position:0%
capitalized by utilities that's right
they're<00:44:02.240> at<00:44:02.400> lower<00:44:02.760> cost<00:44:03.040> than<00:44:03.400> transmission

00:44:04.390 --> 00:44:04.400 align:start position:0%
they're at lower cost than transmission
 

00:44:04.400 --> 00:44:06.390 align:start position:0%
they're at lower cost than transmission
so<00:44:04.720> that's<00:44:05.240> that's<00:44:05.400> a<00:44:05.559> hindrance<00:44:06.079> rather

00:44:06.390 --> 00:44:06.400 align:start position:0%
so that's that's a hindrance rather
 

00:44:06.400 --> 00:44:07.589 align:start position:0%
so that's that's a hindrance rather
build<00:44:06.599> the<00:44:06.680> transmission<00:44:07.200> but<00:44:07.319> that's<00:44:07.440> a

00:44:07.589 --> 00:44:07.599 align:start position:0%
build the transmission but that's a
 

00:44:07.599 --> 00:44:09.910 align:start position:0%
build the transmission but that's a
hindrance<00:44:08.000> to<00:44:08.160> the<00:44:08.319> regulatory<00:44:09.040> construct

00:44:09.910 --> 00:44:09.920 align:start position:0%
hindrance to the regulatory construct
 

00:44:09.920 --> 00:44:12.630 align:start position:0%
hindrance to the regulatory construct
that<00:44:10.119> utilities<00:44:10.599> are<00:44:10.800> using<00:44:11.559> not<00:44:12.119> an<00:44:12.319> actual

00:44:12.630 --> 00:44:12.640 align:start position:0%
that utilities are using not an actual
 

00:44:12.640 --> 00:44:15.069 align:start position:0%
that utilities are using not an actual
hindrance<00:44:13.119> to<00:44:13.559> the<00:44:14.200> you<00:44:14.319> know<00:44:14.559> benefits<00:44:14.920> of

00:44:15.069 --> 00:44:15.079 align:start position:0%
hindrance to the you know benefits of
 

00:44:15.079 --> 00:44:18.150 align:start position:0%
hindrance to the you know benefits of
the<00:44:15.599> grid<00:44:16.599> other<00:44:16.760> than<00:44:17.040> incentive<00:44:17.640> which<00:44:17.880> I<00:44:18.079> I

00:44:18.150 --> 00:44:18.160 align:start position:0%
the grid other than incentive which I I
 

00:44:18.160 --> 00:44:20.589 align:start position:0%
the grid other than incentive which I I
agree<00:44:18.440> is<00:44:18.559> the<00:44:18.720> biggest<00:44:19.119> one<00:44:19.680> I<00:44:19.800> think<00:44:20.319> there's

00:44:20.589 --> 00:44:20.599 align:start position:0%
agree is the biggest one I think there's
 

00:44:20.599 --> 00:44:23.230 align:start position:0%
agree is the biggest one I think there's
there's<00:44:20.760> the<00:44:21.319> trust<00:44:21.720> issue<00:44:22.119> too<00:44:22.839> right<00:44:23.000> so

00:44:23.230 --> 00:44:23.240 align:start position:0%
there's the trust issue too right so
 

00:44:23.240 --> 00:44:26.069 align:start position:0%
there's the trust issue too right so
this<00:44:23.319> is<00:44:23.440> a<00:44:23.720> technology<00:44:24.480> this<00:44:24.599> is<00:44:24.839> not<00:44:25.240> Steel

00:44:26.069 --> 00:44:26.079 align:start position:0%
this is a technology this is not Steel
 

00:44:26.079 --> 00:44:28.630 align:start position:0%
this is a technology this is not Steel
wires<00:44:26.400> in<00:44:26.559> the<00:44:26.720> ground<00:44:27.079> so<00:44:27.359> you<00:44:27.680> have<00:44:27.800> to<00:44:28.119> build

00:44:28.630 --> 00:44:28.640 align:start position:0%
wires in the ground so you have to build
 

00:44:28.640 --> 00:44:30.710 align:start position:0%
wires in the ground so you have to build
enough<00:44:29.160> trust<00:44:29.480> in<00:44:29.640> the<00:44:29.760> industry<00:44:30.200> to<00:44:30.440> move

00:44:30.710 --> 00:44:30.720 align:start position:0%
enough trust in the industry to move
 

00:44:30.720 --> 00:44:32.790 align:start position:0%
enough trust in the industry to move
into<00:44:31.079> that<00:44:31.359> planning<00:44:31.960> Horizon<00:44:32.440> you<00:44:32.559> have<00:44:32.680> to

00:44:32.790 --> 00:44:32.800 align:start position:0%
into that planning Horizon you have to
 

00:44:32.800 --> 00:44:36.710 align:start position:0%
into that planning Horizon you have to
convince<00:44:33.559> you<00:44:33.680> know<00:44:34.000> pjm<00:44:35.000> and<00:44:35.160> the<00:44:35.720> utilities

00:44:36.710 --> 00:44:36.720 align:start position:0%
convince you know pjm and the utilities
 

00:44:36.720 --> 00:44:37.589 align:start position:0%
convince you know pjm and the utilities
and

00:44:37.589 --> 00:44:37.599 align:start position:0%
and
 

00:44:37.599 --> 00:44:41.109 align:start position:0%
and
say<00:44:38.599> yes<00:44:39.240> we<00:44:39.400> can<00:44:39.800> prove<00:44:40.240> we<00:44:40.359> have<00:44:40.520> enough<00:44:40.800> data

00:44:41.109 --> 00:44:41.119 align:start position:0%
say yes we can prove we have enough data
 

00:44:41.119 --> 00:44:43.309 align:start position:0%
say yes we can prove we have enough data
we<00:44:41.240> can<00:44:41.440> prove<00:44:41.760> that<00:44:42.040> you're<00:44:42.240> going<00:44:42.359> to<00:44:42.599> get<00:44:43.040> at

00:44:43.309 --> 00:44:43.319 align:start position:0%
we can prove that you're going to get at
 

00:44:43.319 --> 00:44:46.430 align:start position:0%
we can prove that you're going to get at
least<00:44:44.319> 5%<00:44:45.319> additional<00:44:45.760> capacity<00:44:46.200> of<00:44:46.319> this

00:44:46.430 --> 00:44:46.440 align:start position:0%
least 5% additional capacity of this
 

00:44:46.440 --> 00:44:48.270 align:start position:0%
least 5% additional capacity of this
line<00:44:46.680> all<00:44:46.880> year<00:44:47.160> because<00:44:47.359> some<00:44:47.640> some<00:44:47.920> major

00:44:48.270 --> 00:44:48.280 align:start position:0%
line all year because some some major
 

00:44:48.280 --> 00:44:50.990 align:start position:0%
line all year because some some major
transmission<00:44:48.720> lines<00:44:49.079> will<00:44:49.240> be<00:44:50.040> rebuilt<00:44:50.640> at

00:44:50.990 --> 00:44:51.000 align:start position:0%
transmission lines will be rebuilt at
 

00:44:51.000 --> 00:44:53.270 align:start position:0%
transmission lines will be rebuilt at
tens<00:44:51.240> of<00:44:51.400> million<00:44:51.640> dollars<00:44:51.880> a<00:44:52.040> cost<00:44:52.280> for<00:44:52.480> a<00:44:52.680> 5%

00:44:53.270 --> 00:44:53.280 align:start position:0%
tens of million dollars a cost for a 5%
 

00:44:53.280 --> 00:44:56.750 align:start position:0%
tens of million dollars a cost for a 5%
overload<00:44:54.280> of<00:44:54.440> a<00:44:54.680> contingency<00:44:55.559> so<00:44:56.119> not<00:44:56.319> in<00:44:56.480> real

00:44:56.750 --> 00:44:56.760 align:start position:0%
overload of a contingency so not in real
 

00:44:56.760 --> 00:44:59.829 align:start position:0%
overload of a contingency so not in real
time<00:44:57.079> but<00:44:57.839> if<00:44:58.040> this<00:44:58.160> other<00:44:58.400> line<00:44:58.599> is<00:44:58.760> out<00:44:59.680> this

00:44:59.829 --> 00:44:59.839 align:start position:0%
time but if this other line is out this
 

00:44:59.839 --> 00:45:02.549 align:start position:0%
time but if this other line is out this
line<00:45:00.040> is<00:45:00.400> going<00:45:00.520> to<00:45:00.599> be<00:45:00.720> overload<00:45:01.119> by<00:45:01.400> 5%<00:45:02.400> which

00:45:02.549 --> 00:45:02.559 align:start position:0%
line is going to be overload by 5% which
 

00:45:02.559 --> 00:45:03.829 align:start position:0%
line is going to be overload by 5% which
might<00:45:02.760> only

00:45:03.829 --> 00:45:03.839 align:start position:0%
might only
 

00:45:03.839 --> 00:45:09.030 align:start position:0%
might only
happen<00:45:04.839> and<00:45:05.599> maybe<00:45:05.960> 5%<00:45:06.480> of<00:45:06.559> the<00:45:06.800> year<00:45:07.800> and<00:45:08.040> so

00:45:09.030 --> 00:45:09.040 align:start position:0%
happen and maybe 5% of the year and so
 

00:45:09.040 --> 00:45:10.750 align:start position:0%
happen and maybe 5% of the year and so
or<00:45:09.359> less<00:45:09.599> four<00:45:09.760> or<00:45:09.960> less<00:45:10.280> it<00:45:10.359> could<00:45:10.520> happen

00:45:10.750 --> 00:45:10.760 align:start position:0%
or less four or less it could happen
 

00:45:10.760 --> 00:45:12.549 align:start position:0%
or less four or less it could happen
once<00:45:11.000> it<00:45:11.079> could<00:45:11.200> happen<00:45:11.400> once<00:45:11.559> every<00:45:11.720> 10<00:45:11.960> year

00:45:12.549 --> 00:45:12.559 align:start position:0%
once it could happen once every 10 year
 

00:45:12.559 --> 00:45:13.950 align:start position:0%
once it could happen once every 10 year
and<00:45:12.720> some<00:45:13.040> that's<00:45:13.160> how<00:45:13.319> some<00:45:13.400> of<00:45:13.520> the<00:45:13.599> planning

00:45:13.950 --> 00:45:13.960 align:start position:0%
and some that's how some of the planning
 

00:45:13.960 --> 00:45:16.910 align:start position:0%
and some that's how some of the planning
processes<00:45:14.359> are<00:45:14.839> so<00:45:15.839> we<00:45:16.040> have<00:45:16.200> the<00:45:16.359> technology

00:45:16.910 --> 00:45:16.920 align:start position:0%
processes are so we have the technology
 

00:45:16.920 --> 00:45:20.230 align:start position:0%
processes are so we have the technology
to<00:45:17.400> move<00:45:18.400> to<00:45:19.079> move<00:45:19.400> away<00:45:19.680> from<00:45:19.920> some<00:45:20.040> of<00:45:20.119> the

00:45:20.230 --> 00:45:20.240 align:start position:0%
to move to move away from some of the
 

00:45:20.240 --> 00:45:21.750 align:start position:0%
to move to move away from some of the
conservative<00:45:20.800> approaches<00:45:21.240> that<00:45:21.359> we've<00:45:21.559> had

00:45:21.750 --> 00:45:21.760 align:start position:0%
conservative approaches that we've had
 

00:45:21.760 --> 00:45:24.710 align:start position:0%
conservative approaches that we've had
in<00:45:21.839> the<00:45:22.079> past<00:45:22.880> and<00:45:23.000> we<00:45:23.160> have<00:45:23.280> to<00:45:23.480> move<00:45:24.359> more

00:45:24.710 --> 00:45:24.720 align:start position:0%
in the past and we have to move more
 

00:45:24.720 --> 00:45:27.549 align:start position:0%
in the past and we have to move more
toward<00:45:25.280> a<00:45:25.440> problem<00:45:26.079> istic<00:45:26.359> planning<00:45:27.000> versus

00:45:27.549 --> 00:45:27.559 align:start position:0%
toward a problem istic planning versus
 

00:45:27.559 --> 00:45:30.349 align:start position:0%
toward a problem istic planning versus
determinist<00:45:28.559> that<00:45:28.720> we<00:45:29.000> use<00:45:29.599> another<00:45:29.960> barrier

00:45:30.349 --> 00:45:30.359 align:start position:0%
determinist that we use another barrier
 

00:45:30.359 --> 00:45:33.470 align:start position:0%
determinist that we use another barrier
is<00:45:30.559> the<00:45:30.760> fact<00:45:30.960> that<00:45:31.160> pjm's<00:45:31.760> not<00:45:32.000> using<00:45:32.559> VR<00:45:33.319> in

00:45:33.470 --> 00:45:33.480 align:start position:0%
is the fact that pjm's not using VR in
 

00:45:33.480 --> 00:45:36.870 align:start position:0%
is the fact that pjm's not using VR in
their<00:45:33.920> valuation<00:45:34.920> studies<00:45:35.920> as<00:45:36.040> a<00:45:36.200> developer

00:45:36.870 --> 00:45:36.880 align:start position:0%
their valuation studies as a developer
 

00:45:36.880 --> 00:45:39.190 align:start position:0%
their valuation studies as a developer
I'm<00:45:36.960> not<00:45:37.160> going<00:45:37.280> to<00:45:38.240> assume<00:45:38.599> they<00:45:38.720> will<00:45:38.920> be

00:45:39.190 --> 00:45:39.200 align:start position:0%
I'm not going to assume they will be
 

00:45:39.200 --> 00:45:41.270 align:start position:0%
I'm not going to assume they will be
sometime<00:45:39.480> in<00:45:39.599> the<00:45:39.720> future<00:45:40.000> when<00:45:40.160> I<00:45:40.680> develop<00:45:41.040> a

00:45:41.270 --> 00:45:41.280 align:start position:0%
sometime in the future when I develop a
 

00:45:41.280 --> 00:45:42.910 align:start position:0%
sometime in the future when I develop a
project<00:45:41.800> I'm<00:45:41.960> just<00:45:42.040> going<00:45:42.160> to<00:45:42.280> go<00:45:42.520> with<00:45:42.800> what

00:45:42.910 --> 00:45:42.920 align:start position:0%
project I'm just going to go with what
 

00:45:42.920 --> 00:45:45.270 align:start position:0%
project I'm just going to go with what
they're<00:45:43.040> doing<00:45:43.359> right<00:45:43.520> now<00:45:44.000> right<00:45:44.720> so<00:45:45.079> that's

00:45:45.270 --> 00:45:45.280 align:start position:0%
they're doing right now right so that's
 

00:45:45.280 --> 00:45:47.710 align:start position:0%
they're doing right now right so that's
going<00:45:45.400> to<00:45:45.720> keep<00:45:46.280> a<00:45:46.480> developer<00:45:47.040> from<00:45:47.359> assuming

00:45:47.710 --> 00:45:47.720 align:start position:0%
going to keep a developer from assuming
 

00:45:47.720 --> 00:45:50.069 align:start position:0%
going to keep a developer from assuming
that<00:45:47.839> he's<00:45:48.000> not<00:45:48.319> to<00:45:48.440> pay<00:45:48.559> for<00:45:48.720> an<00:45:48.920> upgrade<00:45:49.920> on

00:45:50.069 --> 00:45:50.079 align:start position:0%
that he's not to pay for an upgrade on
 

00:45:50.079 --> 00:45:51.150 align:start position:0%
that he's not to pay for an upgrade on
transmission

00:45:51.150 --> 00:45:51.160 align:start position:0%
transmission
 

00:45:51.160 --> 00:45:53.030 align:start position:0%
transmission
line<00:45:52.160> he's<00:45:52.319> going<00:45:52.400> to<00:45:52.520> assume<00:45:52.760> he's<00:45:52.880> going<00:45:52.960> to

00:45:53.030 --> 00:45:53.040 align:start position:0%
line he's going to assume he's going to
 

00:45:53.040 --> 00:45:55.870 align:start position:0%
line he's going to assume he's going to
have<00:45:53.119> to<00:45:53.359> pay<00:45:54.359> yeah<00:45:54.920> but<00:45:55.119> putting<00:45:55.359> aside<00:45:55.599> the

00:45:55.870 --> 00:45:55.880 align:start position:0%
have to pay yeah but putting aside the
 

00:45:55.880 --> 00:45:58.790 align:start position:0%
have to pay yeah but putting aside the
incentives<00:45:56.359> and<00:45:57.200> uh<00:45:57.359> and<00:45:57.680> I<00:45:57.839> get<00:45:58.119> all<00:45:58.280> of<00:45:58.480> that

00:45:58.790 --> 00:45:58.800 align:start position:0%
incentives and uh and I get all of that
 

00:45:58.800 --> 00:46:01.270 align:start position:0%
incentives and uh and I get all of that
if<00:45:59.160> to<00:45:59.359> me<00:45:59.520> it<00:45:59.599> was<00:45:59.760> just<00:46:00.240> altruistic<00:46:00.880> suddenly

00:46:01.270 --> 00:46:01.280 align:start position:0%
if to me it was just altruistic suddenly
 

00:46:01.280 --> 00:46:02.950 align:start position:0%
if to me it was just altruistic suddenly
tomorrow<00:46:01.880> are<00:46:02.040> there<00:46:02.240> barriers<00:46:02.640> to<00:46:02.839> them

00:46:02.950 --> 00:46:02.960 align:start position:0%
tomorrow are there barriers to them
 

00:46:02.960 --> 00:46:04.670 align:start position:0%
tomorrow are there barriers to them
doing<00:46:03.240> these<00:46:03.400> types<00:46:03.599> of<00:46:04.040> making<00:46:04.359> these<00:46:04.520> types

00:46:04.670 --> 00:46:04.680 align:start position:0%
doing these types of making these types
 

00:46:04.680 --> 00:46:05.510 align:start position:0%
doing these types of making these types
of

00:46:05.510 --> 00:46:05.520 align:start position:0%
of
 

00:46:05.520 --> 00:46:09.109 align:start position:0%
of
Investments<00:46:06.520> um<00:46:06.920> legal

00:46:09.109 --> 00:46:09.119 align:start position:0%
Investments um legal
 

00:46:09.119 --> 00:46:12.150 align:start position:0%
Investments um legal
barriers<00:46:10.119> um<00:46:10.440> I<00:46:10.680> I<00:46:11.160> you<00:46:11.280> know<00:46:11.559> as<00:46:11.680> far<00:46:11.839> as<00:46:12.079> you

00:46:12.150 --> 00:46:12.160 align:start position:0%
barriers um I I you know as far as you
 

00:46:12.160 --> 00:46:14.309 align:start position:0%
barriers um I I you know as far as you
know<00:46:12.280> the<00:46:12.440> technology<00:46:12.960> uses<00:46:13.680> like<00:46:14.000> a<00:46:14.079> lot<00:46:14.200> of

00:46:14.309 --> 00:46:14.319 align:start position:0%
know the technology uses like a lot of
 

00:46:14.319 --> 00:46:16.750 align:start position:0%
know the technology uses like a lot of
them<00:46:14.480> use<00:46:14.680> cellular<00:46:15.240> networks<00:46:15.599> and<00:46:15.760> things

00:46:16.750 --> 00:46:16.760 align:start position:0%
them use cellular networks and things
 

00:46:16.760 --> 00:46:18.309 align:start position:0%
them use cellular networks and things
and<00:46:16.880> there's<00:46:17.040> a<00:46:17.200> lot<00:46:17.359> of<00:46:17.640> you<00:46:17.760> know<00:46:17.880> course

00:46:18.309 --> 00:46:18.319 align:start position:0%
and there's a lot of you know course
 

00:46:18.319 --> 00:46:21.630 align:start position:0%
and there's a lot of you know course
data<00:46:19.079> um<00:46:19.480> privacy<00:46:20.000> in<00:46:20.359> cyber<00:46:20.720> security<00:46:21.480> that

00:46:21.630 --> 00:46:21.640 align:start position:0%
data um privacy in cyber security that
 

00:46:21.640 --> 00:46:24.190 align:start position:0%
data um privacy in cyber security that
has<00:46:22.040> you<00:46:22.319> you're<00:46:22.599> putting<00:46:23.000> more<00:46:23.359> sensors<00:46:23.960> out

00:46:24.190 --> 00:46:24.200 align:start position:0%
has you you're putting more sensors out
 

00:46:24.200 --> 00:46:26.109 align:start position:0%
has you you're putting more sensors out
there<00:46:24.480> but<00:46:24.880> that's<00:46:25.160> no<00:46:25.359> nothing<00:46:25.559> new<00:46:26.040> the

00:46:26.109 --> 00:46:26.119 align:start position:0%
there but that's no nothing new the
 

00:46:26.119 --> 00:46:28.190 align:start position:0%
there but that's no nothing new the
smart<00:46:26.319> greater<00:46:26.599> grade<00:46:26.839> mod<00:46:27.280> programs<00:46:28.000> that

00:46:28.190 --> 00:46:28.200 align:start position:0%
smart greater grade mod programs that
 

00:46:28.200 --> 00:46:31.069 align:start position:0%
smart greater grade mod programs that
probably<00:46:28.480> Dominion<00:46:28.920> is<00:46:29.040> already<00:46:29.800> working<00:46:30.200> on

00:46:31.069 --> 00:46:31.079 align:start position:0%
probably Dominion is already working on
 

00:46:31.079 --> 00:46:33.069 align:start position:0%
probably Dominion is already working on
um<00:46:31.200> so<00:46:31.599> I<00:46:31.680> don't<00:46:31.839> really<00:46:32.040> see<00:46:32.480> a<00:46:32.599> material

00:46:33.069 --> 00:46:33.079 align:start position:0%
um so I don't really see a material
 

00:46:33.079 --> 00:46:36.430 align:start position:0%
um so I don't really see a material
barrier<00:46:33.400> from<00:46:33.599> a<00:46:33.839> a<00:46:33.960> legal<00:46:35.000> standpoint<00:46:36.000> um<00:46:36.400> I

00:46:36.430 --> 00:46:36.440 align:start position:0%
barrier from a a legal standpoint um I
 

00:46:36.440 --> 00:46:37.349 align:start position:0%
barrier from a a legal standpoint um I
mean<00:46:36.640> these

00:46:37.349 --> 00:46:37.359 align:start position:0%
mean these
 

00:46:37.359 --> 00:46:39.870 align:start position:0%
mean these
industry<00:46:38.359> the<00:46:38.440> industry<00:46:38.839> from<00:46:39.119> like<00:46:39.359> from<00:46:39.480> a

00:46:39.870 --> 00:46:39.880 align:start position:0%
industry the industry from like from a
 

00:46:39.880 --> 00:46:42.190 align:start position:0%
industry the industry from like from a
DLR<00:46:40.880> honestly<00:46:41.400> almost<00:46:41.599> everything<00:46:41.960> on<00:46:42.040> this

00:46:42.190 --> 00:46:42.200 align:start position:0%
DLR honestly almost everything on this
 

00:46:42.200 --> 00:46:44.870 align:start position:0%
DLR honestly almost everything on this
page<00:46:42.480> maybe<00:46:42.760> except<00:46:43.000> for<00:46:44.000> um<00:46:44.480> you<00:46:44.599> know<00:46:44.760> the

00:46:44.870 --> 00:46:44.880 align:start position:0%
page maybe except for um you know the
 

00:46:44.880 --> 00:46:47.950 align:start position:0%
page maybe except for um you know the
VPP<00:46:45.400> which<00:46:45.520> is<00:46:46.040> domain<00:46:46.359> response<00:46:46.680> is<00:46:46.839> well<00:46:47.640> uh

00:46:47.950 --> 00:46:47.960 align:start position:0%
VPP which is domain response is well uh
 

00:46:47.960 --> 00:46:50.470 align:start position:0%
VPP which is domain response is well uh
know<00:46:48.240> and<00:46:48.400> then<00:46:48.599> the<00:46:49.079> facts<00:46:49.559> on<00:46:49.760> the<00:46:49.960> top<00:46:50.240> left

00:46:50.470 --> 00:46:50.480 align:start position:0%
know and then the facts on the top left
 

00:46:50.480 --> 00:46:53.870 align:start position:0%
know and then the facts on the top left
is<00:46:50.640> pretty<00:46:50.920> well<00:46:51.119> known<00:46:51.720> um<00:46:52.640> you<00:46:52.800> know<00:46:53.359> they're

00:46:53.870 --> 00:46:53.880 align:start position:0%
is pretty well known um you know they're
 

00:46:53.880 --> 00:46:55.870 align:start position:0%
is pretty well known um you know they're
they<00:46:54.000> are<00:46:54.200> somewhat<00:46:54.559> new<00:46:55.280> there's<00:46:55.440> a<00:46:55.559> lot<00:46:55.680> of

00:46:55.870 --> 00:46:55.880 align:start position:0%
they are somewhat new there's a lot of
 

00:46:55.880 --> 00:46:58.710 align:start position:0%
they are somewhat new there's a lot of
of<00:46:56.480> uh<00:46:57.440> you<00:46:57.559> know<00:46:57.680> companies<00:46:58.000> doing<00:46:58.280> pilots

00:46:58.710 --> 00:46:58.720 align:start position:0%
of uh you know companies doing pilots
 

00:46:58.720 --> 00:47:01.270 align:start position:0%
of uh you know companies doing pilots
and<00:46:58.920> few<00:46:59.280> have<00:46:59.640> operationalized<00:47:00.520> it<00:47:00.920> as<00:47:01.040> I

00:47:01.270 --> 00:47:01.280 align:start position:0%
and few have operationalized it as I
 

00:47:01.280 --> 00:47:03.030 align:start position:0%
and few have operationalized it as I
mentioned<00:47:01.599> I<00:47:01.680> didn't<00:47:01.880> have<00:47:02.000> a<00:47:02.200> really<00:47:02.400> good<00:47:02.640> us

00:47:03.030 --> 00:47:03.040 align:start position:0%
mentioned I didn't have a really good us
 

00:47:03.040 --> 00:47:04.990 align:start position:0%
mentioned I didn't have a really good us
example<00:47:03.480> of<00:47:03.640> stores<00:47:04.160> transmission<00:47:04.800> other

00:47:04.990 --> 00:47:05.000 align:start position:0%
example of stores transmission other
 

00:47:05.000 --> 00:47:08.470 align:start position:0%
example of stores transmission other
than<00:47:05.880> in<00:47:06.079> Tucket<00:47:06.359> so<00:47:06.480> there's<00:47:06.680> not<00:47:07.520> a<00:47:07.760> a<00:47:08.000> lot<00:47:08.200> of

00:47:08.470 --> 00:47:08.480 align:start position:0%
than in Tucket so there's not a a lot of
 

00:47:08.480 --> 00:47:10.470 align:start position:0%
than in Tucket so there's not a a lot of
Market<00:47:09.079> traction<00:47:09.480> but<00:47:09.599> it's<00:47:09.800> coming<00:47:10.240> that's

00:47:10.470 --> 00:47:10.480 align:start position:0%
Market traction but it's coming that's
 

00:47:10.480 --> 00:47:13.150 align:start position:0%
Market traction but it's coming that's
why<00:47:11.079> you<00:47:11.240> know<00:47:12.000> uh<00:47:12.240> Colleen<00:47:12.599> and<00:47:12.720> I<00:47:12.839> are<00:47:13.000> both

00:47:13.150 --> 00:47:13.160 align:start position:0%
why you know uh Colleen and I are both
 

00:47:13.160 --> 00:47:16.270 align:start position:0%
why you know uh Colleen and I are both
in<00:47:13.280> our<00:47:13.720> new<00:47:13.920> AJ<00:47:14.359> Technologies<00:47:14.920> Group<00:47:15.240> at<00:47:15.400> as

00:47:16.270 --> 00:47:16.280 align:start position:0%
in our new AJ Technologies Group at as
 

00:47:16.280 --> 00:47:18.990 align:start position:0%
in our new AJ Technologies Group at as
and<00:47:16.440> so<00:47:17.000> you<00:47:17.119> know<00:47:17.800> as<00:47:18.240> as<00:47:18.359> well<00:47:18.480> as<00:47:18.559> a<00:47:18.680> lot<00:47:18.839> of

00:47:18.990 --> 00:47:19.000 align:start position:0%
and so you know as as well as a lot of
 

00:47:19.000 --> 00:47:20.990 align:start position:0%
and so you know as as well as a lot of
other<00:47:19.319> companies<00:47:19.920> I<00:47:20.000> think<00:47:20.319> including<00:47:20.880> like<00:47:20.920> I

00:47:20.990 --> 00:47:21.000 align:start position:0%
other companies I think including like I
 

00:47:21.000 --> 00:47:23.750 align:start position:0%
other companies I think including like I
said<00:47:21.119> including<00:47:21.480> Dom<00:47:21.640> men<00:47:22.280> I<00:47:22.440> believe<00:47:23.440> um<00:47:23.559> are

00:47:23.750 --> 00:47:23.760 align:start position:0%
said including Dom men I believe um are
 

00:47:23.760 --> 00:47:27.549 align:start position:0%
said including Dom men I believe um are
looking<00:47:24.079> into<00:47:24.400> some<00:47:24.520> of<00:47:24.680> these<00:47:24.880> Technologies

00:47:27.549 --> 00:47:27.559 align:start position:0%
looking into some of these Technologies
 

00:47:27.559 --> 00:47:31.109 align:start position:0%
looking into some of these Technologies
sorry<00:47:28.400> goad<00:47:29.400> so<00:47:29.680> From<00:47:29.920> aes's<00:47:30.559> perspective<00:47:31.000> and

00:47:31.109 --> 00:47:31.119 align:start position:0%
sorry goad so From aes's perspective and
 

00:47:31.119 --> 00:47:33.150 align:start position:0%
sorry goad so From aes's perspective and
I<00:47:31.200> know<00:47:31.599> obviously<00:47:32.040> you're<00:47:32.480> you're

00:47:33.150 --> 00:47:33.160 align:start position:0%
I know obviously you're you're
 

00:47:33.160 --> 00:47:35.309 align:start position:0%
I know obviously you're you're
representing<00:47:34.000> your<00:47:34.440> your<00:47:34.800> company's

00:47:35.309 --> 00:47:35.319 align:start position:0%
representing your your company's
 

00:47:35.319 --> 00:47:38.270 align:start position:0%
representing your your company's
position<00:47:35.839> here<00:47:36.800> you<00:47:37.000> had<00:47:37.400> a<00:47:37.599> comment<00:47:38.000> there

00:47:38.270 --> 00:47:38.280 align:start position:0%
position here you had a comment there
 

00:47:38.280 --> 00:47:41.510 align:start position:0%
position here you had a comment there
about<00:47:38.599> getting<00:47:38.920> sec<00:47:39.440> to<00:47:39.640> support<00:47:40.000> regulator

00:47:41.510 --> 00:47:41.520 align:start position:0%
about getting sec to support regulator
 

00:47:41.520 --> 00:47:43.950 align:start position:0%
about getting sec to support regulator
incentives<00:47:42.520> so<00:47:42.720> that<00:47:42.880> gets<00:47:43.200> can<00:47:43.520> compete<00:47:43.800> on

00:47:43.950 --> 00:47:43.960 align:start position:0%
incentives so that gets can compete on
 

00:47:43.960 --> 00:47:45.910 align:start position:0%
incentives so that gets can compete on
equal<00:47:44.200> footing<00:47:44.480> with<00:47:44.640> traditional<00:47:45.000> upgrades

00:47:45.910 --> 00:47:45.920 align:start position:0%
equal footing with traditional upgrades
 

00:47:45.920 --> 00:47:47.829 align:start position:0%
equal footing with traditional upgrades
that's<00:47:46.040> an<00:47:46.200> alternativ<00:47:46.880> analysis<00:47:47.559> that<00:47:47.720> has

00:47:47.829 --> 00:47:47.839 align:start position:0%
that's an alternativ analysis that has
 

00:47:47.839 --> 00:47:50.430 align:start position:0%
that's an alternativ analysis that has
to<00:47:47.960> be<00:47:48.319> introduced<00:47:49.319> at<00:47:49.480> the<00:47:49.760> fundamental

00:47:50.430 --> 00:47:50.440 align:start position:0%
to be introduced at the fundamental
 

00:47:50.440 --> 00:47:52.589 align:start position:0%
to be introduced at the fundamental
component<00:47:50.880> because<00:47:51.079> the<00:47:51.200> SEC<00:47:52.200> and<00:47:52.319> we<00:47:52.440> know

00:47:52.589 --> 00:47:52.599 align:start position:0%
component because the SEC and we know
 

00:47:52.599 --> 00:47:54.190 align:start position:0%
component because the SEC and we know
the<00:47:52.680> engineering<00:47:53.119> gr<00:47:53.359> at<00:47:53.480> the<00:47:53.559> SEC<00:47:53.920> they<00:47:54.000> don't

00:47:54.190 --> 00:47:54.200 align:start position:0%
the engineering gr at the SEC they don't
 

00:47:54.200 --> 00:47:56.910 align:start position:0%
the engineering gr at the SEC they don't
have<00:47:54.319> the<00:47:54.599> resource<00:47:55.280> EX<00:47:55.760> to<00:47:55.960> do<00:47:56.240> this<00:47:56.680> let

00:47:56.910 --> 00:47:56.920 align:start position:0%
have the resource EX to do this let
 

00:47:56.920 --> 00:48:00.230 align:start position:0%
have the resource EX to do this let
alone<00:47:57.480> advise<00:47:58.480> the<00:47:58.839> non-engineering<00:47:59.839> side<00:48:00.079> of

00:48:00.230 --> 00:48:00.240 align:start position:0%
alone advise the non-engineering side of
 

00:48:00.240 --> 00:48:03.470 align:start position:0%
alone advise the non-engineering side of
the<00:48:00.359> SEC<00:48:01.119> on<00:48:01.319> how<00:48:01.480> to<00:48:01.720> best<00:48:02.200> proceed<00:48:03.200> so<00:48:03.359> in

00:48:03.470 --> 00:48:03.480 align:start position:0%
the SEC on how to best proceed so in
 

00:48:03.480 --> 00:48:06.990 align:start position:0%
the SEC on how to best proceed so in
your<00:48:03.760> perfect<00:48:04.160> world<00:48:04.839> where<00:48:05.119> do<00:48:05.480> you<00:48:05.920> see

00:48:06.990 --> 00:48:07.000 align:start position:0%
your perfect world where do you see
 

00:48:07.000 --> 00:48:10.829 align:start position:0%
your perfect world where do you see
Virginia<00:48:08.000> the<00:48:08.200> SEC<00:48:09.200> and<00:48:09.440> and<00:48:09.599> by<00:48:09.760> the<00:48:09.920> way<00:48:10.680> the

00:48:10.829 --> 00:48:10.839 align:start position:0%
Virginia the SEC and and by the way the
 

00:48:10.839 --> 00:48:13.710 align:start position:0%
Virginia the SEC and and by the way the
SEC<00:48:11.280> doesn't<00:48:11.559> direct<00:48:12.079> pjm<00:48:13.079> yes<00:48:13.240> they<00:48:13.400> direct

00:48:13.710 --> 00:48:13.720 align:start position:0%
SEC doesn't direct pjm yes they direct
 

00:48:13.720 --> 00:48:15.990 align:start position:0%
SEC doesn't direct pjm yes they direct
the<00:48:14.040> state<00:48:14.599> of<00:48:14.760> Virginia<00:48:15.280> the<00:48:15.440> Commonwealth

00:48:15.990 --> 00:48:16.000 align:start position:0%
the state of Virginia the Commonwealth
 

00:48:16.000 --> 00:48:20.870 align:start position:0%
the state of Virginia the Commonwealth
of<00:48:16.119> Virginia<00:48:17.200> and<00:48:18.200> bur<00:48:18.800> and<00:48:19.520> pjm<00:48:20.520> have<00:48:20.720> the

00:48:20.870 --> 00:48:20.880 align:start position:0%
of Virginia and bur and pjm have the
 

00:48:20.880 --> 00:48:22.670 align:start position:0%
of Virginia and bur and pjm have the
overall<00:48:21.280> umbrella<00:48:21.720> on<00:48:21.920> transmission

00:48:22.670 --> 00:48:22.680 align:start position:0%
overall umbrella on transmission
 

00:48:22.680 --> 00:48:25.790 align:start position:0%
overall umbrella on transmission
jurisdiction<00:48:23.680> and<00:48:23.880> and<00:48:24.079> what<00:48:24.319> happens<00:48:25.200> so<00:48:25.520> now

00:48:25.790 --> 00:48:25.800 align:start position:0%
jurisdiction and and what happens so now
 

00:48:25.800 --> 00:48:29.710 align:start position:0%
jurisdiction and and what happens so now
you<00:48:26.000> set<00:48:26.240> up<00:48:26.760> a<00:48:27.760> a<00:48:28.319> contest<00:48:28.880> between<00:48:29.240> these<00:48:29.440> two

00:48:29.710 --> 00:48:29.720 align:start position:0%
you set up a a contest between these two
 

00:48:29.720 --> 00:48:31.309 align:start position:0%
you set up a a contest between these two
entities<00:48:30.200> where<00:48:30.359> they're<00:48:30.520> not<00:48:30.880> necessarily

00:48:31.309 --> 00:48:31.319 align:start position:0%
entities where they're not necessarily
 

00:48:31.319 --> 00:48:34.670 align:start position:0%
entities where they're not necessarily
aligned<00:48:31.640> in<00:48:31.880> objectives<00:48:32.680> or<00:48:33.079> their<00:48:33.680> processes

00:48:34.670 --> 00:48:34.680 align:start position:0%
aligned in objectives or their processes
 

00:48:34.680 --> 00:48:37.069 align:start position:0%
aligned in objectives or their processes
how<00:48:34.800> do<00:48:34.960> we<00:48:35.119> address<00:48:35.559> that<00:48:35.839> and<00:48:36.079> and<00:48:36.359> what's

00:48:37.069 --> 00:48:37.079 align:start position:0%
how do we address that and and what's
 

00:48:37.079 --> 00:48:39.670 align:start position:0%
how do we address that and and what's
what's<00:48:37.240> our<00:48:37.480> role<00:48:37.880> here<00:48:38.400> to<00:48:38.720> influence<00:48:39.319> that

00:48:39.670 --> 00:48:39.680 align:start position:0%
what's our role here to influence that
 

00:48:39.680 --> 00:48:42.230 align:start position:0%
what's our role here to influence that
and<00:48:39.960> and<00:48:40.359> bring<00:48:40.680> those<00:48:40.880> worlds<00:48:41.359> together<00:48:42.119> I

00:48:42.230 --> 00:48:42.240 align:start position:0%
and and bring those worlds together I
 

00:48:42.240 --> 00:48:44.030 align:start position:0%
and and bring those worlds together I
mean<00:48:42.599> so<00:48:42.920> going<00:48:43.480> to<00:48:43.640> the<00:48:43.760> first

00:48:44.030 --> 00:48:44.040 align:start position:0%
mean so going to the first
 

00:48:44.040 --> 00:48:46.470 align:start position:0%
mean so going to the first
recommendation<00:48:45.040> one<00:48:45.520> we<00:48:45.640> need<00:48:45.800> to<00:48:46.000> De<00:48:46.200> we<00:48:46.319> need

00:48:46.470 --> 00:48:46.480 align:start position:0%
recommendation one we need to De we need
 

00:48:46.480 --> 00:48:48.829 align:start position:0%
recommendation one we need to De we need
more<00:48:46.640> Market<00:48:46.960> traction<00:48:47.319> so<00:48:47.440> we<00:48:47.559> need<00:48:47.680> to<00:48:47.920> do

00:48:48.829 --> 00:48:48.839 align:start position:0%
more Market traction so we need to do
 

00:48:48.839 --> 00:48:52.950 align:start position:0%
more Market traction so we need to do
more<00:48:49.280> pilots<00:48:50.000> and<00:48:50.839> then<00:48:51.040> further<00:48:51.839> operational

00:48:52.950 --> 00:48:52.960 align:start position:0%
more pilots and then further operational
 

00:48:52.960 --> 00:48:55.710 align:start position:0%
more pilots and then further operational
operationalizations<00:48:53.960> so<00:48:54.240> like<00:48:54.720> uh<00:48:54.839> PPL<00:48:55.319> did

00:48:55.710 --> 00:48:55.720 align:start position:0%
operationalizations so like uh PPL did
 

00:48:55.720 --> 00:48:59.349 align:start position:0%
operationalizations so like uh PPL did
right<00:48:55.839> so<00:48:56.400> you<00:48:57.079> if<00:48:57.280> you<00:48:57.599> prove<00:48:57.920> the<00:48:58.359> technology

00:48:59.349 --> 00:48:59.359 align:start position:0%
right so you if you prove the technology
 

00:48:59.359 --> 00:49:02.270 align:start position:0%
right so you if you prove the technology
it's<00:48:59.640> hard<00:48:59.960> for<00:49:00.280> Regulators<00:49:01.280> to<00:49:01.559> say<00:49:02.119> well

00:49:02.270 --> 00:49:02.280 align:start position:0%
it's hard for Regulators to say well
 

00:49:02.280 --> 00:49:03.510 align:start position:0%
it's hard for Regulators to say well
this<00:49:02.359> is

00:49:03.510 --> 00:49:03.520 align:start position:0%
this is
 

00:49:03.520 --> 00:49:06.150 align:start position:0%
this is
unprovable<00:49:04.520> this<00:49:04.640> is<00:49:04.839> not<00:49:05.160> what<00:49:05.280> we<00:49:05.359> should<00:49:05.559> do

00:49:06.150 --> 00:49:06.160 align:start position:0%
unprovable this is not what we should do
 

00:49:06.160 --> 00:49:10.549 align:start position:0%
unprovable this is not what we should do
um<00:49:06.760> as<00:49:07.520> so<00:49:07.920> we<00:49:08.040> are<00:49:08.240> also<00:49:08.480> in<00:49:08.680> my<00:49:09.559> because<00:49:10.160> we

00:49:10.549 --> 00:49:10.559 align:start position:0%
um as so we are also in my because we
 

00:49:10.559 --> 00:49:13.190 align:start position:0%
um as so we are also in my because we
have<00:49:10.720> a<00:49:11.280> utility<00:49:11.799> indana<00:49:12.280> so<00:49:12.400> we<00:49:12.839> recently

00:49:13.190 --> 00:49:13.200 align:start position:0%
have a utility indana so we recently
 

00:49:13.200 --> 00:49:16.270 align:start position:0%
have a utility indana so we recently
presented<00:49:13.559> at<00:49:13.720> their<00:49:13.960> planning<00:49:14.960> uh<00:49:15.760> uh<00:49:16.079> it's

00:49:16.270 --> 00:49:16.280 align:start position:0%
presented at their planning uh uh it's
 

00:49:16.280 --> 00:49:19.030 align:start position:0%
presented at their planning uh uh it's
called<00:49:16.440> a<00:49:16.920> planning<00:49:17.480> activity<00:49:17.920> committee<00:49:18.880> uh

00:49:19.030 --> 00:49:19.040 align:start position:0%
called a planning activity committee uh
 

00:49:19.040 --> 00:49:22.069 align:start position:0%
called a planning activity committee uh
where<00:49:19.599> they<00:49:20.599> they<00:49:20.799> govern<00:49:21.200> that<00:49:21.599> how<00:49:21.760> do<00:49:21.920> we

00:49:22.069 --> 00:49:22.079 align:start position:0%
where they they govern that how do we
 

00:49:22.079 --> 00:49:24.710 align:start position:0%
where they they govern that how do we
plan<00:49:22.319> our<00:49:22.880> transmission<00:49:23.880> and<00:49:24.040> so<00:49:24.480> we

00:49:24.710 --> 00:49:24.720 align:start position:0%
plan our transmission and so we
 

00:49:24.720 --> 00:49:26.430 align:start position:0%
plan our transmission and so we
presented<00:49:25.079> a<00:49:25.160> similar<00:49:25.640> presentation<00:49:26.240> there

00:49:26.430 --> 00:49:26.440 align:start position:0%
presented a similar presentation there
 

00:49:26.440 --> 00:49:29.190 align:start position:0%
presented a similar presentation there
so<00:49:26.920> I<00:49:27.000> think<00:49:27.200> working<00:49:27.559> at<00:49:28.079> ases<00:49:28.480> is<00:49:28.640> working<00:49:29.040> at

00:49:29.190 --> 00:49:29.200 align:start position:0%
so I think working at ases is working at
 

00:49:29.200 --> 00:49:32.230 align:start position:0%
so I think working at ases is working at
all<00:49:29.440> levels<00:49:29.960> so<00:49:30.640> we're<00:49:30.799> looking<00:49:31.040> with<00:49:31.240> ber<00:49:32.000> we

00:49:32.230 --> 00:49:32.240 align:start position:0%
all levels so we're looking with ber we
 

00:49:32.240 --> 00:49:34.390 align:start position:0%
all levels so we're looking with ber we
submitting<00:49:32.720> comments<00:49:33.079> to<00:49:33.280> you<00:49:33.400> know<00:49:33.599> B<00:49:33.960> doe

00:49:34.390 --> 00:49:34.400 align:start position:0%
submitting comments to you know B doe
 

00:49:34.400 --> 00:49:37.150 align:start position:0%
submitting comments to you know B doe
doe<00:49:34.839> I<00:49:34.920> would<00:49:35.040> say<00:49:35.160> is<00:49:35.359> very<00:49:35.880> like<00:49:36.040> FK<00:49:36.359> is<00:49:36.520> very

00:49:37.150 --> 00:49:37.160 align:start position:0%
doe I would say is very like FK is very
 

00:49:37.160 --> 00:49:39.950 align:start position:0%
doe I would say is very like FK is very
active<00:49:38.160> um<00:49:38.640> you<00:49:38.720> know<00:49:38.880> we<00:49:39.000> are<00:49:39.200> working<00:49:39.640> at<00:49:39.799> the

00:49:39.950 --> 00:49:39.960 align:start position:0%
active um you know we are working at the
 

00:49:39.960 --> 00:49:41.910 align:start position:0%
active um you know we are working at the
Congressional<00:49:40.440> level<00:49:40.720> as<00:49:40.880> well<00:49:41.319> on<00:49:41.599> some<00:49:41.720> of

00:49:41.910 --> 00:49:41.920 align:start position:0%
Congressional level as well on some of
 

00:49:41.920 --> 00:49:44.349 align:start position:0%
Congressional level as well on some of
these<00:49:42.480> uh<00:49:42.680> initiatives<00:49:43.200> but<00:49:43.359> of<00:49:43.520> course<00:49:44.160> um

00:49:44.349 --> 00:49:44.359 align:start position:0%
these uh initiatives but of course um
 

00:49:44.359 --> 00:49:46.349 align:start position:0%
these uh initiatives but of course um
you<00:49:44.480> know<00:49:44.760> Congress<00:49:45.079> mov<00:49:45.359> that<00:49:45.799> okay<00:49:46.000> so<00:49:46.160> we

00:49:46.349 --> 00:49:46.359 align:start position:0%
you know Congress mov that okay so we
 

00:49:46.359 --> 00:49:49.829 align:start position:0%
you know Congress mov that okay so we
recognize<00:49:47.040> that<00:49:47.559> um<00:49:48.400> and<00:49:48.559> then<00:49:48.839> so<00:49:49.160> again<00:49:49.599> so

00:49:49.829 --> 00:49:49.839 align:start position:0%
recognize that um and then so again so
 

00:49:49.839 --> 00:49:52.309 align:start position:0%
recognize that um and then so again so
yeah<00:49:50.119> working<00:49:50.480> pjm<00:49:50.839> and<00:49:50.960> miso<00:49:51.559> and<00:49:51.720> then<00:49:52.079> with

00:49:52.309 --> 00:49:52.319 align:start position:0%
yeah working pjm and miso and then with
 

00:49:52.319 --> 00:49:54.990 align:start position:0%
yeah working pjm and miso and then with
our<00:49:53.000> utilities<00:49:54.000> we're<00:49:54.240> actually<00:49:54.520> looking<00:49:54.839> not

00:49:54.990 --> 00:49:55.000 align:start position:0%
our utilities we're actually looking not
 

00:49:55.000 --> 00:49:56.549 align:start position:0%
our utilities we're actually looking not
just<00:49:55.119> in<00:49:55.240> our<00:49:55.359> own<00:49:55.720> but<00:49:55.839> we're<00:49:56.040> looking<00:49:56.280> at

00:49:56.549 --> 00:49:56.559 align:start position:0%
just in our own but we're looking at
 

00:49:56.559 --> 00:49:58.870 align:start position:0%
just in our own but we're looking at
other<00:49:56.880> Utilities<00:49:57.520> in<00:49:57.799> our<00:49:58.000> Serv<00:49:58.319> territory

00:49:58.870 --> 00:49:58.880 align:start position:0%
other Utilities in our Serv territory
 

00:49:58.880 --> 00:50:02.030 align:start position:0%
other Utilities in our Serv territory
where<00:49:59.319> as<00:49:59.839> might<00:50:00.119> have<00:50:00.559> projects<00:50:01.559> and<00:50:01.720> and<00:50:01.880> go

00:50:02.030 --> 00:50:02.040 align:start position:0%
where as might have projects and and go
 

00:50:02.040 --> 00:50:03.950 align:start position:0%
where as might have projects and and go
into<00:50:02.200> that<00:50:02.319> utility<00:50:02.640> and<00:50:02.720> saying<00:50:03.079> hey<00:50:03.799> we

00:50:03.950 --> 00:50:03.960 align:start position:0%
into that utility and saying hey we
 

00:50:03.960 --> 00:50:06.430 align:start position:0%
into that utility and saying hey we
think<00:50:04.200> we<00:50:04.319> could<00:50:04.480> do<00:50:04.680> DLR<00:50:05.359> here<00:50:05.799> to<00:50:06.040> mitigate

00:50:06.430 --> 00:50:06.440 align:start position:0%
think we could do DLR here to mitigate
 

00:50:06.440 --> 00:50:09.630 align:start position:0%
think we could do DLR here to mitigate
this<00:50:06.559> network<00:50:06.920> upgrade<00:50:07.640> and<00:50:08.160> having<00:50:08.520> them<00:50:08.720> say

00:50:09.630 --> 00:50:09.640 align:start position:0%
this network upgrade and having them say
 

00:50:09.640 --> 00:50:11.670 align:start position:0%
this network upgrade and having them say
you<00:50:09.760> know<00:50:09.920> they<00:50:10.040> can<00:50:10.200> say<00:50:10.400> yes<00:50:10.520> or<00:50:10.720> no<00:50:11.520> but

00:50:11.670 --> 00:50:11.680 align:start position:0%
you know they can say yes or no but
 

00:50:11.680 --> 00:50:13.950 align:start position:0%
you know they can say yes or no but
we're<00:50:11.839> going<00:50:12.000> to<00:50:12.160> bring<00:50:12.359> that<00:50:12.520> issue<00:50:12.839> up<00:50:13.040> to

00:50:13.950 --> 00:50:13.960 align:start position:0%
we're going to bring that issue up to
 

00:50:13.960 --> 00:50:15.950 align:start position:0%
we're going to bring that issue up to
the<00:50:14.839> um<00:50:15.000> Regional<00:50:15.480> transmission

00:50:15.950 --> 00:50:15.960 align:start position:0%
the um Regional transmission
 

00:50:15.960 --> 00:50:20.470 align:start position:0%
the um Regional transmission
organization<00:50:16.440> or<00:50:16.760> RTO<00:50:17.760> um<00:50:18.839> and<00:50:19.839> keep<00:50:20.119> pushing

00:50:20.470 --> 00:50:20.480 align:start position:0%
organization or RTO um and keep pushing
 

00:50:20.480 --> 00:50:23.309 align:start position:0%
organization or RTO um and keep pushing
that<00:50:20.640> off<00:50:21.079> lad<00:50:21.760> so<00:50:22.000> I<00:50:22.200> think<00:50:22.559> you<00:50:22.799> have<00:50:22.920> to<00:50:23.200> kind

00:50:23.309 --> 00:50:23.319 align:start position:0%
that off lad so I think you have to kind
 

00:50:23.319 --> 00:50:25.549 align:start position:0%
that off lad so I think you have to kind
of<00:50:23.480> work<00:50:23.799> that<00:50:23.920> at<00:50:24.079> all<00:50:24.280> levels<00:50:24.720> and<00:50:24.920> I<00:50:25.119> I<00:50:25.280> we

00:50:25.549 --> 00:50:25.559 align:start position:0%
of work that at all levels and I I we
 

00:50:25.559 --> 00:50:28.829 align:start position:0%
of work that at all levels and I I we
have<00:50:25.680> seen<00:50:25.839> that<00:50:26.359> again<00:50:26.520> do<00:50:27.160> per<00:50:27.520> from<00:50:27.839> the<00:50:28.280> top

00:50:28.829 --> 00:50:28.839 align:start position:0%
have seen that again do per from the top
 

00:50:28.839 --> 00:50:30.589 align:start position:0%
have seen that again do per from the top
side<00:50:29.000> of<00:50:29.200> that<00:50:29.599> say<00:50:30.000> which<00:50:30.119> they<00:50:30.240> were<00:50:30.359> talking

00:50:30.589 --> 00:50:30.599 align:start position:0%
side of that say which they were talking
 

00:50:30.599 --> 00:50:32.030 align:start position:0%
side of that say which they were talking
about<00:50:30.839> I<00:50:30.920> think<00:50:31.079> is<00:50:31.400> they<00:50:31.520> are<00:50:31.760> pushing

00:50:32.030 --> 00:50:32.040 align:start position:0%
about I think is they are pushing
 

00:50:32.040 --> 00:50:34.150 align:start position:0%
about I think is they are pushing
through<00:50:32.440> this<00:50:33.079> we've<00:50:33.240> seen<00:50:33.520> a<00:50:33.640> lot<00:50:33.799> of

00:50:34.150 --> 00:50:34.160 align:start position:0%
through this we've seen a lot of
 

00:50:34.160 --> 00:50:37.549 align:start position:0%
through this we've seen a lot of
traction<00:50:34.960> on<00:50:35.240> that<00:50:36.240> and<00:50:36.559> I<00:50:36.640> would<00:50:36.839> just<00:50:37.079> add<00:50:37.319> to

00:50:37.549 --> 00:50:37.559 align:start position:0%
traction on that and I would just add to
 

00:50:37.559 --> 00:50:40.750 align:start position:0%
traction on that and I would just add to
that<00:50:38.079> you<00:50:38.200> know<00:50:39.000> I<00:50:39.119> think<00:50:39.400> that<00:50:39.799> uh<00:50:40.200> of<00:50:40.359> course

00:50:40.750 --> 00:50:40.760 align:start position:0%
that you know I think that uh of course
 

00:50:40.760 --> 00:50:43.349 align:start position:0%
that you know I think that uh of course
SEC<00:50:41.760> you<00:50:41.880> know<00:50:42.240> they<00:50:42.880> they<00:50:43.000> don't<00:50:43.200> have

00:50:43.349 --> 00:50:43.359 align:start position:0%
SEC you know they they don't have
 

00:50:43.359 --> 00:50:48.109 align:start position:0%
SEC you know they they don't have
jurisdiction<00:50:44.280> over<00:50:44.760> pjm<00:50:45.640> for<00:50:46.480> but

00:50:48.109 --> 00:50:48.119 align:start position:0%
jurisdiction over pjm for but
 

00:50:48.119 --> 00:50:52.549 align:start position:0%
jurisdiction over pjm for but
um<00:50:49.119> we<00:50:49.520> we<00:50:49.680> do<00:50:49.920> need<00:50:50.200> to<00:50:50.440> implement<00:50:50.839> FK<00:50:51.280> 881<00:50:52.280> in

00:50:52.549 --> 00:50:52.559 align:start position:0%
um we we do need to implement FK 881 in
 

00:50:52.559 --> 00:50:55.950 align:start position:0%
um we we do need to implement FK 881 in
in<00:50:52.640> a<00:50:52.799> way<00:50:52.960> in<00:50:53.160> Virginia<00:50:53.880> and<00:50:54.640> if<00:50:55.119> in<00:50:55.480> Virginia

00:50:55.950 --> 00:50:55.960 align:start position:0%
in a way in Virginia and if in Virginia
 

00:50:55.960 --> 00:50:58.349 align:start position:0%
in a way in Virginia and if in Virginia
we<00:50:56.079> say<00:50:56.319> hey<00:50:56.480> we're<00:50:56.640> implementing<00:50:57.119> 881<00:50:58.040> with<00:50:58.200> a

00:50:58.349 --> 00:50:58.359 align:start position:0%
we say hey we're implementing 881 with a
 

00:50:58.359 --> 00:50:59.910 align:start position:0%
we say hey we're implementing 881 with a
preference<00:50:58.720> of<00:50:58.880> using

00:50:59.910 --> 00:50:59.920 align:start position:0%
preference of using
 

00:50:59.920 --> 00:51:04.309 align:start position:0%
preference of using
DLR<00:51:00.920> uh<00:51:01.400> that<00:51:01.680> is<00:51:02.400> a<00:51:02.799> good<00:51:03.079> message<00:51:03.599> to<00:51:03.760> send<00:51:04.079> to

00:51:04.309 --> 00:51:04.319 align:start position:0%
DLR uh that is a good message to send to
 

00:51:04.319 --> 00:51:06.549 align:start position:0%
DLR uh that is a good message to send to
F<00:51:04.720> to<00:51:04.839> say<00:51:05.079> this<00:51:05.200> is<00:51:05.440> how<00:51:05.640> we've<00:51:05.920> implemented

00:51:06.549 --> 00:51:06.559 align:start position:0%
F to say this is how we've implemented
 

00:51:06.559 --> 00:51:09.069 align:start position:0%
F to say this is how we've implemented
ambient<00:51:06.960> adjusted<00:51:07.359> ratings<00:51:08.000> we<00:51:08.280> have<00:51:08.760> done

00:51:09.069 --> 00:51:09.079 align:start position:0%
ambient adjusted ratings we have done
 

00:51:09.079 --> 00:51:10.990 align:start position:0%
ambient adjusted ratings we have done
something<00:51:09.520> that<00:51:09.839> qualifies<00:51:10.359> for<00:51:10.599> ambient

00:51:10.990 --> 00:51:11.000 align:start position:0%
something that qualifies for ambient
 

00:51:11.000 --> 00:51:14.230 align:start position:0%
something that qualifies for ambient
adjusted<00:51:11.960> and<00:51:12.240> goes<00:51:12.559> beyond<00:51:12.960> that<00:51:13.720> um<00:51:14.040> we've

00:51:14.230 --> 00:51:14.240 align:start position:0%
adjusted and goes beyond that um we've
 

00:51:14.240 --> 00:51:16.589 align:start position:0%
adjusted and goes beyond that um we've
used<00:51:14.520> the<00:51:14.640> best<00:51:14.839> available<00:51:15.319> technology<00:51:16.200> that

00:51:16.589 --> 00:51:16.599 align:start position:0%
used the best available technology that
 

00:51:16.599 --> 00:51:20.390 align:start position:0%
used the best available technology that
that<00:51:16.760> we<00:51:16.880> can<00:51:17.079> use<00:51:17.440> to<00:51:18.000> to<00:51:18.200> do<00:51:18.480> that<00:51:19.200> and<00:51:19.400> then

00:51:20.390 --> 00:51:20.400 align:start position:0%
that we can use to to do that and then
 

00:51:20.400 --> 00:51:22.870 align:start position:0%
that we can use to to do that and then
on<00:51:20.799> on<00:51:21.000> pjm<00:51:21.559> side<00:51:21.799> what's<00:51:22.079> great<00:51:22.400> about

00:51:22.870 --> 00:51:22.880 align:start position:0%
on on pjm side what's great about
 

00:51:22.880 --> 00:51:25.910 align:start position:0%
on on pjm side what's great about
already<00:51:23.359> having<00:51:23.599> a<00:51:23.880> pilot<00:51:24.480> example<00:51:24.839> in<00:51:25.000> pjm

00:51:25.910 --> 00:51:25.920 align:start position:0%
already having a pilot example in pjm
 

00:51:25.920 --> 00:51:29.430 align:start position:0%
already having a pilot example in pjm
you<00:51:26.040> can<00:51:26.240> go<00:51:26.400> to<00:51:26.680> pjm's<00:51:27.319> website<00:51:28.240> and<00:51:28.480> under

00:51:29.430 --> 00:51:29.440 align:start position:0%
you can go to pjm's website and under
 

00:51:29.440 --> 00:51:31.549 align:start position:0%
you can go to pjm's website and under
the<00:51:29.599> transmission<00:51:30.079> operations<00:51:30.559> line<00:51:30.799> ratings

00:51:31.549 --> 00:51:31.559 align:start position:0%
the transmission operations line ratings
 

00:51:31.559 --> 00:51:35.750 align:start position:0%
the transmission operations line ratings
you<00:51:31.680> can<00:51:32.119> download<00:51:33.119> the<00:51:34.160> everyday's<00:51:35.160> um<00:51:35.319> DLR

00:51:35.750 --> 00:51:35.760 align:start position:0%
you can download the everyday's um DLR
 

00:51:35.760 --> 00:51:37.670 align:start position:0%
you can download the everyday's um DLR
ratings<00:51:36.119> on<00:51:36.240> the<00:51:36.359> lines<00:51:36.640> that<00:51:36.799> it's<00:51:37.000> being

00:51:37.670 --> 00:51:37.680 align:start position:0%
ratings on the lines that it's being
 

00:51:37.680 --> 00:51:41.069 align:start position:0%
ratings on the lines that it's being
used<00:51:38.040> on<00:51:38.799> and<00:51:38.960> so<00:51:39.319> that's<00:51:40.079> that<00:51:40.559> process<00:51:40.920> is

00:51:41.069 --> 00:51:41.079 align:start position:0%
used on and so that's that process is
 

00:51:41.079 --> 00:51:43.829 align:start position:0%
used on and so that's that process is
already<00:51:41.440> in<00:51:41.680> place<00:51:42.240> to<00:51:42.559> operationalize<00:51:43.440> DLR

00:51:43.829 --> 00:51:43.839 align:start position:0%
already in place to operationalize DLR
 

00:51:43.839 --> 00:51:47.470 align:start position:0%
already in place to operationalize DLR
and<00:51:44.440> pjm<00:51:45.440> and<00:51:45.880> and<00:51:46.000> so<00:51:46.280> that's<00:51:46.799> you<00:51:46.920> know<00:51:47.160> where

00:51:47.470 --> 00:51:47.480 align:start position:0%
and pjm and and so that's you know where
 

00:51:47.480 --> 00:51:50.510 align:start position:0%
and pjm and and so that's you know where
Dominion<00:51:47.960> can<00:51:48.240> so<00:51:48.440> what<00:51:48.680> is<00:51:49.160> there<00:51:49.559> is<00:51:49.799> just

00:51:50.510 --> 00:51:50.520 align:start position:0%
Dominion can so what is there is just
 

00:51:50.520 --> 00:51:54.109 align:start position:0%
Dominion can so what is there is just
contined<00:51:51.400> awareness

00:51:54.109 --> 00:51:54.119 align:start position:0%
contined awareness
 

00:51:54.119 --> 00:51:56.230 align:start position:0%
contined awareness
education<00:51:55.119> yeah<00:51:55.480> effectively<00:51:55.839> laying<00:51:56.119> out

00:51:56.230 --> 00:51:56.240 align:start position:0%
education yeah effectively laying out
 

00:51:56.240 --> 00:52:00.109 align:start position:0%
education yeah effectively laying out
the<00:51:56.400> road<00:51:56.680> map<00:51:57.079> for<00:51:58.079> how<00:51:58.280> SEC<00:51:58.880> is<00:51:59.040> going<00:51:59.160> to<00:51:59.400> do

00:52:00.109 --> 00:52:00.119 align:start position:0%
the road map for how SEC is going to do
 

00:52:00.119 --> 00:52:04.589 align:start position:0%
the road map for how SEC is going to do
this<00:52:01.119> how<00:52:01.319> pjm<00:52:01.839> and<00:52:02.559> SEC<00:52:03.160> could<00:52:03.400> work

00:52:04.589 --> 00:52:04.599 align:start position:0%
this how pjm and SEC could work
 

00:52:04.599 --> 00:52:07.829 align:start position:0%
this how pjm and SEC could work
together<00:52:05.599> yeah<00:52:05.839> sounds<00:52:06.079> like<00:52:06.240> we<00:52:06.359> need

00:52:07.829 --> 00:52:07.839 align:start position:0%
together yeah sounds like we need
 

00:52:07.839 --> 00:52:10.670 align:start position:0%
together yeah sounds like we need
legislation<00:52:08.839> yeah<00:52:09.359> so<00:52:09.839> my<00:52:10.040> question<00:52:10.440> Greg

00:52:10.670 --> 00:52:10.680 align:start position:0%
legislation yeah so my question Greg
 

00:52:10.680 --> 00:52:13.390 align:start position:0%
legislation yeah so my question Greg
might<00:52:10.839> be<00:52:10.920> able<00:52:11.079> to<00:52:11.200> answer<00:52:11.599> this<00:52:11.960> but<00:52:12.680> order

00:52:13.390 --> 00:52:13.400 align:start position:0%
might be able to answer this but order
 

00:52:13.400 --> 00:52:15.870 align:start position:0%
might be able to answer this but order
for<00:52:14.400> these<00:52:14.760> recommendations<00:52:15.359> that<00:52:15.480> you<00:52:15.640> make

00:52:15.870 --> 00:52:15.880 align:start position:0%
for these recommendations that you make
 

00:52:15.880 --> 00:52:18.549 align:start position:0%
for these recommendations that you make
AJ<00:52:16.319> to<00:52:16.640> to<00:52:16.799> take<00:52:17.079> effect<00:52:17.559> requiring<00:52:18.079> utilities

00:52:18.549 --> 00:52:18.559 align:start position:0%
AJ to to take effect requiring utilities
 

00:52:18.559 --> 00:52:21.309 align:start position:0%
AJ to to take effect requiring utilities
to<00:52:19.119> consider

00:52:21.309 --> 00:52:21.319 align:start position:0%
to consider
 

00:52:21.319 --> 00:52:23.630 align:start position:0%
to consider
advis<00:52:22.319> which<00:52:22.680> both<00:52:22.799> of<00:52:23.000> those<00:52:23.240> require

00:52:23.630 --> 00:52:23.640 align:start position:0%
advis which both of those require
 

00:52:23.640 --> 00:52:26.150 align:start position:0%
advis which both of those require
legislation<00:52:24.480> with<00:52:24.640> the<00:52:24.839> advice

00:52:26.150 --> 00:52:26.160 align:start position:0%
legislation with the advice
 

00:52:26.160 --> 00:52:27.710 align:start position:0%
legislation with the advice
SEC

00:52:27.710 --> 00:52:27.720 align:start position:0%
SEC
 

00:52:27.720 --> 00:52:31.030 align:start position:0%
SEC
ba<00:52:28.720> something<00:52:29.160> the<00:52:29.280> government<00:52:29.599> could<00:52:29.760> do

00:52:31.030 --> 00:52:31.040 align:start position:0%
ba something the government could do
 

00:52:31.040 --> 00:52:34.190 align:start position:0%
ba something the government could do
unilaterally<00:52:32.040> yeah<00:52:32.200> I'm<00:52:32.359> not<00:52:32.599> exactly

00:52:34.190 --> 00:52:34.200 align:start position:0%
unilaterally yeah I'm not exactly
 

00:52:34.200 --> 00:52:36.150 align:start position:0%
unilaterally yeah I'm not exactly
sure<00:52:35.200> well<00:52:35.359> yeah<00:52:35.480> that's<00:52:35.599> why<00:52:35.720> I<00:52:35.799> was<00:52:35.920> asking

00:52:36.150 --> 00:52:36.160 align:start position:0%
sure well yeah that's why I was asking
 

00:52:36.160 --> 00:52:37.510 align:start position:0%
sure well yeah that's why I was asking
if<00:52:36.280> this<00:52:36.400> stuff's<00:52:36.640> covered<00:52:36.880> by<00:52:37.000> the<00:52:37.079> grid<00:52:37.359> mod

00:52:37.510 --> 00:52:37.520 align:start position:0%
if this stuff's covered by the grid mod
 

00:52:37.520 --> 00:52:38.829 align:start position:0%
if this stuff's covered by the grid mod
bill<00:52:37.920> and<00:52:38.040> when<00:52:38.160> you<00:52:38.280> go<00:52:38.440> back<00:52:38.599> to<00:52:38.680> the

00:52:38.829 --> 00:52:38.839 align:start position:0%
bill and when you go back to the
 

00:52:38.839 --> 00:52:40.589 align:start position:0%
bill and when you go back to the
legislation<00:52:39.359> that's<00:52:39.559> been<00:52:39.839> passed<00:52:40.200> like<00:52:40.400> to

00:52:40.589 --> 00:52:40.599 align:start position:0%
legislation that's been passed like to
 

00:52:40.599 --> 00:52:42.430 align:start position:0%
legislation that's been passed like to
get

00:52:42.430 --> 00:52:42.440 align:start position:0%
get
 

00:52:42.440 --> 00:52:46.470 align:start position:0%
get
the<00:52:43.440> the<00:52:43.520> solar<00:52:44.000> legislation<00:52:44.640> to<00:52:44.960> scale<00:52:45.480> solar

00:52:46.470 --> 00:52:46.480 align:start position:0%
the the solar legislation to scale solar
 

00:52:46.480 --> 00:52:48.030 align:start position:0%
the the solar legislation to scale solar
I<00:52:46.559> think<00:52:46.680> it'<00:52:46.839> be<00:52:46.920> the<00:52:47.000> same<00:52:47.160> sort<00:52:47.359> of<00:52:47.520> thing

00:52:48.030 --> 00:52:48.040 align:start position:0%
I think it' be the same sort of thing
 

00:52:48.040 --> 00:52:50.430 align:start position:0%
I think it' be the same sort of thing
yeah<00:52:48.240> I<00:52:48.319> mean<00:52:48.920> to<00:52:49.200> to<00:52:49.359> direct<00:52:49.640> the<00:52:49.760> SEC<00:52:50.240> to

00:52:50.430 --> 00:52:50.440 align:start position:0%
yeah I mean to to direct the SEC to
 

00:52:50.440 --> 00:52:53.870 align:start position:0%
yeah I mean to to direct the SEC to
interpret<00:52:50.960> the<00:52:51.079> rules<00:52:51.440> liberally<00:52:52.119> to<00:52:53.119> to<00:52:53.480> let

00:52:53.870 --> 00:52:53.880 align:start position:0%
interpret the rules liberally to to let
 

00:52:53.880 --> 00:52:56.630 align:start position:0%
interpret the rules liberally to to let
those<00:52:54.359> sort<00:52:54.559> of<00:52:54.760> projects<00:52:55.240> they<00:52:55.640> through

00:52:56.630 --> 00:52:56.640 align:start position:0%
those sort of projects they through
 

00:52:56.640 --> 00:52:58.190 align:start position:0%
those sort of projects they through
easier<00:52:57.040> than<00:52:57.200> other<00:52:57.440> projects<00:52:57.799> yeah<00:52:57.920> I<00:52:57.960> mean

00:52:58.190 --> 00:52:58.200 align:start position:0%
easier than other projects yeah I mean
 

00:52:58.200 --> 00:53:00.950 align:start position:0%
easier than other projects yeah I mean
there's<00:52:58.599> the<00:52:58.760> SEC<00:52:59.240> has<00:52:59.359> some<00:52:59.760> general<00:53:00.760> like

00:53:00.950 --> 00:53:00.960 align:start position:0%
there's the SEC has some general like
 

00:53:00.960 --> 00:53:03.390 align:start position:0%
there's the SEC has some general like
rate<00:53:01.280> payer<00:53:01.640> protection<00:53:02.040> language<00:53:02.920> that<00:53:03.200> they

00:53:03.390 --> 00:53:03.400 align:start position:0%
rate payer protection language that they
 

00:53:03.400 --> 00:53:04.829 align:start position:0%
rate payer protection language that they
can<00:53:03.920> if<00:53:04.040> they<00:53:04.200> were<00:53:04.359> a<00:53:04.440> little<00:53:04.599> more

00:53:04.829 --> 00:53:04.839 align:start position:0%
can if they were a little more
 

00:53:04.839 --> 00:53:07.309 align:start position:0%
can if they were a little more
aggressive<00:53:05.280> of<00:53:05.960> of<00:53:06.079> a<00:53:06.240> utility<00:53:06.720> regulatory

00:53:07.309 --> 00:53:07.319 align:start position:0%
aggressive of of a utility regulatory
 

00:53:07.319 --> 00:53:09.870 align:start position:0%
aggressive of of a utility regulatory
body<00:53:08.240> could<00:53:08.559> extend<00:53:09.079> to<00:53:09.240> saying<00:53:09.599> we<00:53:09.720> can

00:53:09.870 --> 00:53:09.880 align:start position:0%
body could extend to saying we can
 

00:53:09.880 --> 00:53:11.750 align:start position:0%
body could extend to saying we can
direct<00:53:10.200> some<00:53:10.319> of<00:53:10.480> these<00:53:10.680> things<00:53:11.079> but<00:53:11.319> they

00:53:11.750 --> 00:53:11.760 align:start position:0%
direct some of these things but they
 

00:53:11.760 --> 00:53:12.950 align:start position:0%
direct some of these things but they
that<00:53:12.079> that's<00:53:12.280> totally<00:53:12.599> different<00:53:12.839> than

00:53:12.950 --> 00:53:12.960 align:start position:0%
that that's totally different than
 

00:53:12.960 --> 00:53:15.190 align:start position:0%
that that's totally different than
Virginia<00:53:13.319> has<00:53:13.440> ever<00:53:13.640> done<00:53:14.559> so<00:53:14.799> certainly<00:53:15.160> if

00:53:15.190 --> 00:53:15.200 align:start position:0%
Virginia has ever done so certainly if
 

00:53:15.200 --> 00:53:16.950 align:start position:0%
Virginia has ever done so certainly if
you're<00:53:15.319> going<00:53:15.440> to<00:53:15.520> try<00:53:15.680> to<00:53:15.880> direct<00:53:16.319> SEC<00:53:16.720> is<00:53:16.839> not

00:53:16.950 --> 00:53:16.960 align:start position:0%
you're going to try to direct SEC is not
 

00:53:16.960 --> 00:53:20.750 align:start position:0%
you're going to try to direct SEC is not
going<00:53:17.079> to<00:53:17.160> have<00:53:17.280> the<00:53:17.359> power<00:53:17.520> to<00:53:17.760> direct<00:53:18.640> it<00:53:18.880> be

00:53:20.750 --> 00:53:20.760 align:start position:0%
going to have the power to direct it be
 

00:53:20.760 --> 00:53:23.549 align:start position:0%
going to have the power to direct it be
done<00:53:21.760> right<00:53:22.000> all<00:53:22.200> they<00:53:22.359> all<00:53:22.520> we<00:53:22.680> can<00:53:22.960> all

00:53:23.549 --> 00:53:23.559 align:start position:0%
done right all they all we can all
 

00:53:23.559 --> 00:53:26.030 align:start position:0%
done right all they all we can all
legislation<00:53:24.160> can<00:53:24.319> do<00:53:24.520> I<00:53:24.640> think<00:53:24.760> is<00:53:25.280> is<00:53:25.760> tell

00:53:26.030 --> 00:53:26.040 align:start position:0%
legislation can do I think is is tell
 

00:53:26.040 --> 00:53:28.670 align:start position:0%
legislation can do I think is is tell
them<00:53:26.280> they<00:53:26.359> can<00:53:26.839> interpret<00:53:27.839> existing<00:53:28.240> rules

00:53:28.670 --> 00:53:28.680 align:start position:0%
them they can interpret existing rules
 

00:53:28.680 --> 00:53:31.549 align:start position:0%
them they can interpret existing rules
liberally<00:53:29.680> to<00:53:29.920> give<00:53:30.160> those<00:53:30.559> projects<00:53:31.000> prer

00:53:31.549 --> 00:53:31.559 align:start position:0%
liberally to give those projects prer
 

00:53:31.559 --> 00:53:33.950 align:start position:0%
liberally to give those projects prer
and<00:53:32.040> I<00:53:32.079> mean<00:53:32.240> you<00:53:32.400> could<00:53:32.680> pass<00:53:32.880> a<00:53:33.000> bill<00:53:33.559> that

00:53:33.950 --> 00:53:33.960 align:start position:0%
and I mean you could pass a bill that
 

00:53:33.960 --> 00:53:36.430 align:start position:0%
and I mean you could pass a bill that
says<00:53:34.960> SEC<00:53:35.440> can<00:53:35.559> only

00:53:36.430 --> 00:53:36.440 align:start position:0%
says SEC can only
 

00:53:36.440 --> 00:53:39.069 align:start position:0%
says SEC can only
approve<00:53:37.440> costs<00:53:37.960> submitted<00:53:38.359> by<00:53:38.480> the<00:53:38.640> opinion

00:53:39.069 --> 00:53:39.079 align:start position:0%
approve costs submitted by the opinion
 

00:53:39.079 --> 00:53:41.910 align:start position:0%
approve costs submitted by the opinion
where<00:53:39.760> you<00:53:39.880> know<00:53:40.480> these<00:53:40.799> Technologies<00:53:41.319> are

00:53:41.910 --> 00:53:41.920 align:start position:0%
where you know these Technologies are
 

00:53:41.920 --> 00:53:44.069 align:start position:0%
where you know these Technologies are
you<00:53:42.040> can<00:53:42.200> do

00:53:44.069 --> 00:53:44.079 align:start position:0%
you can do
 

00:53:44.079 --> 00:53:47.230 align:start position:0%
you can do
that<00:53:45.079> right<00:53:45.680> literally<00:53:46.520> that's<00:53:46.760> literally

00:53:47.230 --> 00:53:47.240 align:start position:0%
that right literally that's literally
 

00:53:47.240 --> 00:53:48.549 align:start position:0%
that right literally that's literally
you<00:53:47.359> could<00:53:47.599> pass<00:53:47.760> a<00:53:47.839> bill<00:53:48.040> to<00:53:48.119> did<00:53:48.280> that<00:53:48.400> if<00:53:48.440> you

00:53:48.549 --> 00:53:48.559 align:start position:0%
you could pass a bill to did that if you
 

00:53:48.559 --> 00:53:49.829 align:start position:0%
you could pass a bill to did that if you
had<00:53:48.680> the

00:53:49.829 --> 00:53:49.839 align:start position:0%
had the
 

00:53:49.839 --> 00:53:52.270 align:start position:0%
had the
votes<00:53:50.839> could<00:53:51.040> you<00:53:51.160> say<00:53:51.440> a<00:53:51.640> certain<00:53:51.920> amount<00:53:52.119> of

00:53:52.270 --> 00:53:52.280 align:start position:0%
votes could you say a certain amount of
 

00:53:52.280 --> 00:53:55.470 align:start position:0%
votes could you say a certain amount of
investment<00:53:52.720> in<00:53:53.040> Gs<00:53:54.040> or<00:53:54.280> a<00:53:54.440> certain<00:53:55.200> amount<00:53:55.359> of

00:53:55.470 --> 00:53:55.480 align:start position:0%
investment in Gs or a certain amount of
 

00:53:55.480 --> 00:53:57.030 align:start position:0%
investment in Gs or a certain amount of
investment<00:53:55.839> in<00:53:56.040> pilot<00:53:56.359> projects<00:53:56.720> be<00:53:56.880> in

00:53:57.030 --> 00:53:57.040 align:start position:0%
investment in pilot projects be in
 

00:53:57.040 --> 00:53:58.950 align:start position:0%
investment in pilot projects be in
public<00:53:57.280> interest<00:53:57.680> yeah<00:53:58.200> yeah<00:53:58.559> although

00:53:58.950 --> 00:53:58.960 align:start position:0%
public interest yeah yeah although
 

00:53:58.960 --> 00:54:00.470 align:start position:0%
public interest yeah yeah although
everybody's<00:53:59.440> hating<00:53:59.760> the<00:53:59.960> public<00:54:00.200> interest

00:54:00.470 --> 00:54:00.480 align:start position:0%
everybody's hating the public interest
 

00:54:00.480 --> 00:54:02.549 align:start position:0%
everybody's hating the public interest
language<00:54:00.880> more<00:54:01.040> and<00:54:01.160> more<00:54:01.640> yeah

00:54:02.549 --> 00:54:02.559 align:start position:0%
language more and more yeah
 

00:54:02.559 --> 00:54:03.670 align:start position:0%
language more and more yeah
Administration<00:54:03.119> last<00:54:03.280> week<00:54:03.400> and<00:54:03.480> they<00:54:03.559> said

00:54:03.670 --> 00:54:03.680 align:start position:0%
Administration last week and they said
 

00:54:03.680 --> 00:54:04.710 align:start position:0%
Administration last week and they said
they're<00:54:03.799> trying<00:54:03.920> to<00:54:04.040> get<00:54:04.119> rid<00:54:04.280> of<00:54:04.359> as<00:54:04.480> much<00:54:04.599> of

00:54:04.710 --> 00:54:04.720 align:start position:0%
they're trying to get rid of as much of
 

00:54:04.720 --> 00:54:07.750 align:start position:0%
they're trying to get rid of as much of
that<00:54:04.839> as<00:54:04.960> they<00:54:05.160> can<00:54:05.960> no<00:54:06.200> you<00:54:06.440> could<00:54:07.440> you<00:54:07.559> could

00:54:07.750 --> 00:54:07.760 align:start position:0%
that as they can no you could you could
 

00:54:07.760 --> 00:54:09.030 align:start position:0%
that as they can no you could you could
make<00:54:07.960> it<00:54:08.160> clear<00:54:08.520> what<00:54:08.640> they<00:54:08.760> can<00:54:08.880> be

00:54:09.030 --> 00:54:09.040 align:start position:0%
make it clear what they can be
 

00:54:09.040 --> 00:54:11.750 align:start position:0%
make it clear what they can be
reimbursed<00:54:09.559> on<00:54:09.880> you<00:54:10.000> could<00:54:10.200> say<00:54:10.720> they<00:54:11.240> shall

00:54:11.750 --> 00:54:11.760 align:start position:0%
reimbursed on you could say they shall
 

00:54:11.760 --> 00:54:13.430 align:start position:0%
reimbursed on you could say they shall
consider<00:54:12.240> these<00:54:12.520> as<00:54:12.640> a<00:54:12.720> lower<00:54:13.119> cost

00:54:13.430 --> 00:54:13.440 align:start position:0%
consider these as a lower cost
 

00:54:13.440 --> 00:54:15.190 align:start position:0%
consider these as a lower cost
alternative<00:54:14.440> there's<00:54:14.680> lots<00:54:14.839> of<00:54:14.960> ways<00:54:15.119> you

00:54:15.190 --> 00:54:15.200 align:start position:0%
alternative there's lots of ways you
 

00:54:15.200 --> 00:54:17.870 align:start position:0%
alternative there's lots of ways you
could<00:54:15.440> put<00:54:15.559> it<00:54:15.799> in<00:54:16.119> there<00:54:17.119> um<00:54:17.440> and<00:54:17.559> there<00:54:17.680> are

00:54:17.870 --> 00:54:17.880 align:start position:0%
could put it in there um and there are
 

00:54:17.880 --> 00:54:20.510 align:start position:0%
could put it in there um and there are
already<00:54:18.280> times<00:54:19.079> where<00:54:20.079> you<00:54:20.160> know<00:54:20.359> the

00:54:20.510 --> 00:54:20.520 align:start position:0%
already times where you know the
 

00:54:20.520 --> 00:54:23.390 align:start position:0%
already times where you know the
opposite<00:54:20.839> of<00:54:21.040> this<00:54:21.160> is<00:54:21.400> like<00:54:21.599> the<00:54:21.760> de<00:54:22.440> SEC<00:54:22.880> said

00:54:23.390 --> 00:54:23.400 align:start position:0%
opposite of this is like the de SEC said
 

00:54:23.400 --> 00:54:25.549 align:start position:0%
opposite of this is like the de SEC said
hey<00:54:23.960> the<00:54:24.119> wind<00:54:24.440> project<00:54:25.160> that's<00:54:25.319> super

00:54:25.549 --> 00:54:25.559 align:start position:0%
hey the wind project that's super
 

00:54:25.559 --> 00:54:26.950 align:start position:0%
hey the wind project that's super
expensive<00:54:26.119> but<00:54:26.240> we're<00:54:26.400> not<00:54:26.520> allowed<00:54:26.720> to<00:54:26.839> say

00:54:26.950 --> 00:54:26.960 align:start position:0%
expensive but we're not allowed to say
 

00:54:26.960 --> 00:54:28.470 align:start position:0%
expensive but we're not allowed to say
you<00:54:27.040> can't<00:54:27.240> do<00:54:27.359> it<00:54:27.559> therefore<00:54:28.000> we're<00:54:28.240> going<00:54:28.359> to

00:54:28.470 --> 00:54:28.480 align:start position:0%
you can't do it therefore we're going to
 

00:54:28.480 --> 00:54:31.030 align:start position:0%
you can't do it therefore we're going to
let<00:54:28.640> you<00:54:28.760> do<00:54:28.960> it<00:54:29.440> but<00:54:29.640> had<00:54:29.760> you<00:54:29.920> not<00:54:30.119> said<00:54:30.400> we

00:54:31.030 --> 00:54:31.040 align:start position:0%
let you do it but had you not said we
 

00:54:31.040 --> 00:54:32.470 align:start position:0%
let you do it but had you not said we
can't<00:54:31.319> say<00:54:31.599> that<00:54:31.839> we<00:54:31.960> would<00:54:32.119> have<00:54:32.200> told<00:54:32.359> you

00:54:32.470 --> 00:54:32.480 align:start position:0%
can't say that we would have told you
 

00:54:32.480 --> 00:54:33.990 align:start position:0%
can't say that we would have told you
can't<00:54:32.599> do<00:54:32.720> that<00:54:32.880> project<00:54:33.480> when<00:54:33.559> it<00:54:33.680> comes<00:54:33.839> to

00:54:33.990 --> 00:54:34.000 align:start position:0%
can't do that project when it comes to
 

00:54:34.000 --> 00:54:36.750 align:start position:0%
can't do that project when it comes to
Dominion<00:54:34.440> really<00:54:34.599> comes<00:54:34.880> down<00:54:35.280> to<00:54:36.280> what's

00:54:36.750 --> 00:54:36.760 align:start position:0%
Dominion really comes down to what's
 

00:54:36.760 --> 00:54:40.589 align:start position:0%
Dominion really comes down to what's
best<00:54:37.119> for<00:54:37.359> them<00:54:38.240> um<00:54:38.839> and<00:54:38.960> if<00:54:39.119> it's<00:54:40.119> the<00:54:40.280> bottom

00:54:40.589 --> 00:54:40.599 align:start position:0%
best for them um and if it's the bottom
 

00:54:40.599 --> 00:54:41.950 align:start position:0%
best for them um and if it's the bottom
line<00:54:40.880> it's<00:54:41.119> better<00:54:41.280> for<00:54:41.400> them<00:54:41.520> to<00:54:41.640> build<00:54:41.839> a

00:54:41.950 --> 00:54:41.960 align:start position:0%
line it's better for them to build a
 

00:54:41.960 --> 00:54:42.990 align:start position:0%
line it's better for them to build a
transmission<00:54:42.559> that's<00:54:42.680> what<00:54:42.799> they're<00:54:42.920> going

00:54:42.990 --> 00:54:43.000 align:start position:0%
transmission that's what they're going
 

00:54:43.000 --> 00:54:44.789 align:start position:0%
transmission that's what they're going
to<00:54:43.160> do<00:54:43.799> well<00:54:43.920> they<00:54:44.000> have<00:54:44.079> a<00:54:44.160> fici

00:54:44.789 --> 00:54:44.799 align:start position:0%
to do well they have a fici
 

00:54:44.799 --> 00:54:46.190 align:start position:0%
to do well they have a fici
responsibility<00:54:45.400> they're<00:54:45.520> share<00:54:45.839> holders

00:54:46.190 --> 00:54:46.200 align:start position:0%
responsibility they're share holders
 

00:54:46.200 --> 00:54:49.349 align:start position:0%
responsibility they're share holders
just<00:54:46.319> like<00:54:46.440> the<00:54:46.960> ads<00:54:47.960> right<00:54:48.160> I<00:54:48.240> mean<00:54:49.000> that's<00:54:49.160> a

00:54:49.349 --> 00:54:49.359 align:start position:0%
just like the ads right I mean that's a
 

00:54:49.359 --> 00:54:52.150 align:start position:0%
just like the ads right I mean that's a
corporation<00:54:49.960> that's<00:54:50.079> a<00:54:50.960> corporation<00:54:51.720> unless

00:54:52.150 --> 00:54:52.160 align:start position:0%
corporation that's a corporation unless
 

00:54:52.160 --> 00:54:55.829 align:start position:0%
corporation that's a corporation unless
you<00:54:52.760> um<00:54:53.720> as<00:54:53.839> we<00:54:53.960> did<00:54:54.160> with<00:54:54.319> solar<00:54:55.079> say<00:54:55.720> a

00:54:55.829 --> 00:54:55.839 align:start position:0%
you um as we did with solar say a
 

00:54:55.839 --> 00:54:58.950 align:start position:0%
you um as we did with solar say a
certain<00:54:56.119> amount<00:54:56.319> of<00:54:57.079> this<00:54:58.079> is<00:54:58.359> in<00:54:58.480> the<00:54:58.640> public

00:54:58.950 --> 00:54:58.960 align:start position:0%
certain amount of this is in the public
 

00:54:58.960 --> 00:55:00.870 align:start position:0%
certain amount of this is in the public
interest<00:54:59.599> so<00:54:59.799> then<00:54:59.960> the<00:55:00.040> way<00:55:00.280> used<00:55:00.520> do

00:55:00.870 --> 00:55:00.880 align:start position:0%
interest so then the way used do
 

00:55:00.880 --> 00:55:05.069 align:start position:0%
interest so then the way used do
Virginia<00:55:01.160> is<00:55:01.200> the<00:55:01.359> pilot<00:55:01.599> program<00:55:02.400> legislated

00:55:05.069 --> 00:55:05.079 align:start position:0%
Virginia is the pilot program legislated
 

00:55:05.079 --> 00:55:08.270 align:start position:0%
Virginia is the pilot program legislated
yeah<00:55:06.079> I<00:55:06.240> go<00:55:06.400> back<00:55:06.520> to<00:55:06.599> you<00:55:06.880> though<00:55:07.160> it<00:55:07.319> is<00:55:07.480> in's

00:55:08.270 --> 00:55:08.280 align:start position:0%
yeah I go back to you though it is in's
 

00:55:08.280 --> 00:55:10.390 align:start position:0%
yeah I go back to you though it is in's
interest<00:55:08.839> to<00:55:09.359> put<00:55:09.480> more

00:55:10.390 --> 00:55:10.400 align:start position:0%
interest to put more
 

00:55:10.400 --> 00:55:15.030 align:start position:0%
interest to put more
days<00:55:11.480> that<00:55:12.480> and<00:55:12.640> so<00:55:13.640> this<00:55:13.799> is<00:55:14.040> something<00:55:14.880> you

00:55:15.030 --> 00:55:15.040 align:start position:0%
days that and so this is something you
 

00:55:15.040 --> 00:55:18.150 align:start position:0%
days that and so this is something you
could<00:55:15.319> do<00:55:15.720> in<00:55:16.559> six<00:55:16.920> months<00:55:17.440> on<00:55:17.599> an<00:55:17.799> existing

00:55:18.150 --> 00:55:18.160 align:start position:0%
could do in six months on an existing
 

00:55:18.160 --> 00:55:20.109 align:start position:0%
could do in six months on an existing
transition<00:55:18.680> line<00:55:19.359> you<00:55:19.480> know<00:55:19.640> in<00:55:19.760> Northern

00:55:20.109 --> 00:55:20.119 align:start position:0%
transition line you know in Northern
 

00:55:20.119 --> 00:55:22.710 align:start position:0%
transition line you know in Northern
Virginia<00:55:20.839> that<00:55:21.079> is<00:55:21.880> where<00:55:22.240> they're<00:55:22.480> looking

00:55:22.710 --> 00:55:22.720 align:start position:0%
Virginia that is where they're looking
 

00:55:22.720 --> 00:55:25.349 align:start position:0%
Virginia that is where they're looking
at<00:55:22.960> Major<00:55:23.440> 500<00:55:23.920> KV<00:55:24.359> upgrades<00:55:25.079> things<00:55:25.240> like

00:55:25.349 --> 00:55:25.359 align:start position:0%
at Major 500 KV upgrades things like
 

00:55:25.359 --> 00:55:27.990 align:start position:0%
at Major 500 KV upgrades things like
that<00:55:25.480> that<00:55:25.559> are<00:55:25.680> going<00:55:25.760> to<00:55:25.920> take<00:55:26.319> years<00:55:27.319> so<00:55:27.760> to

00:55:27.990 --> 00:55:28.000 align:start position:0%
that that are going to take years so to
 

00:55:28.000 --> 00:55:30.950 align:start position:0%
that that are going to take years so to
me<00:55:28.520> and<00:55:29.039> we<00:55:29.520> as<00:55:29.880> is<00:55:30.000> seeing<00:55:30.280> the<00:55:30.400> same<00:55:30.640> thing<00:55:30.799> so

00:55:30.950 --> 00:55:30.960 align:start position:0%
me and we as is seeing the same thing so
 

00:55:30.960 --> 00:55:33.029 align:start position:0%
me and we as is seeing the same thing so
the<00:55:31.119> initial<00:55:31.520> use<00:55:31.839> cases<00:55:32.160> are<00:55:32.680> and<00:55:32.839> we're

00:55:33.029 --> 00:55:33.039 align:start position:0%
the initial use cases are and we're
 

00:55:33.039 --> 00:55:35.589 align:start position:0%
the initial use cases are and we're
seeing<00:55:33.240> a<00:55:33.359> lot<00:55:33.480> of<00:55:33.839> you<00:55:33.920> know<00:55:34.480> uh<00:55:34.880> like<00:55:35.079> Honda

00:55:35.589 --> 00:55:35.599 align:start position:0%
seeing a lot of you know uh like Honda
 

00:55:35.599 --> 00:55:37.910 align:start position:0%
seeing a lot of you know uh like Honda
for<00:55:35.760> instance<00:55:36.640> just<00:55:36.880> announcing<00:55:37.319> a<00:55:37.480> battery

00:55:37.910 --> 00:55:37.920 align:start position:0%
for instance just announcing a battery
 

00:55:37.920 --> 00:55:39.950 align:start position:0%
for instance just announcing a battery
Factory<00:55:38.520> in<00:55:38.799> Southern<00:55:39.200> Ohio<00:55:39.599> that's<00:55:39.720> in<00:55:39.839> our

00:55:39.950 --> 00:55:39.960 align:start position:0%
Factory in Southern Ohio that's in our
 

00:55:39.960 --> 00:55:42.549 align:start position:0%
Factory in Southern Ohio that's in our
service<00:55:40.280> territory<00:55:41.039> that<00:55:41.799> certain<00:55:42.400> the

00:55:42.549 --> 00:55:42.559 align:start position:0%
service territory that certain the
 

00:55:42.559 --> 00:55:45.510 align:start position:0%
service territory that certain the
existing<00:55:43.319> problem<00:55:44.319> of<00:55:44.559> getting<00:55:44.760> solar<00:55:45.200> on<00:55:45.359> the

00:55:45.510 --> 00:55:45.520 align:start position:0%
existing problem of getting solar on the
 

00:55:45.520 --> 00:55:47.829 align:start position:0%
existing problem of getting solar on the
grid<00:55:46.280> it's<00:55:46.400> not<00:55:46.520> going<00:55:46.640> to<00:55:46.720> be

00:55:47.829 --> 00:55:47.839 align:start position:0%
grid it's not going to be
 

00:55:47.839 --> 00:55:51.190 align:start position:0%
grid it's not going to be
evaluated<00:55:48.839> yes<00:55:49.200> it<00:55:49.640> it's<00:55:50.319> but<00:55:50.680> to<00:55:50.839> me<00:55:51.079> if

00:55:51.190 --> 00:55:51.200 align:start position:0%
evaluated yes it it's but to me if
 

00:55:51.200 --> 00:55:52.829 align:start position:0%
evaluated yes it it's but to me if
you're<00:55:51.480> if<00:55:51.599> you're<00:55:51.839> utility<00:55:52.319> doing<00:55:52.559> that<00:55:52.720> for

00:55:52.829 --> 00:55:52.839 align:start position:0%
you're if you're utility doing that for
 

00:55:52.839 --> 00:55:55.510 align:start position:0%
you're if you're utility doing that for
a<00:55:53.319> customer<00:55:54.319> how<00:55:54.480> are<00:55:54.559> you<00:55:54.720> not<00:55:55.119> doing<00:55:55.359> that

00:55:55.510 --> 00:55:55.520 align:start position:0%
a customer how are you not doing that
 

00:55:55.520 --> 00:55:59.710 align:start position:0%
a customer how are you not doing that
for<00:55:56.079> Generation<00:55:56.720> as<00:55:56.920> well<00:55:57.520> right<00:55:57.839> it's<00:55:57.920> not

00:55:59.710 --> 00:55:59.720 align:start position:0%
for Generation as well right it's not
 

00:55:59.720 --> 00:56:02.510 align:start position:0%
for Generation as well right it's not
most<00:56:00.720> but<00:56:00.799> it<00:56:00.880> is<00:56:01.000> a<00:56:01.240> wedge<00:56:01.720> it's<00:56:01.920> getting<00:56:02.280> it's

00:56:02.510 --> 00:56:02.520 align:start position:0%
most but it is a wedge it's getting it's
 

00:56:02.520 --> 00:56:04.230 align:start position:0%
most but it is a wedge it's getting it's
it's<00:56:02.680> saying<00:56:03.119> you<00:56:03.280> now<00:56:03.480> have<00:56:03.640> this<00:56:03.760> on<00:56:03.960> your

00:56:04.230 --> 00:56:04.240 align:start position:0%
it's saying you now have this on your
 

00:56:04.240 --> 00:56:05.789 align:start position:0%
it's saying you now have this on your
you're<00:56:04.440> now<00:56:04.799> evaluating<00:56:05.319> this<00:56:05.440> as<00:56:05.599> part<00:56:05.720> of

00:56:05.789 --> 00:56:05.799 align:start position:0%
you're now evaluating this as part of
 

00:56:05.799 --> 00:56:08.990 align:start position:0%
you're now evaluating this as part of
your<00:56:06.319> toolbox<00:56:07.319> uh<00:56:07.520> for<00:56:07.880> integrating<00:56:08.400> load<00:56:08.920> it

00:56:08.990 --> 00:56:09.000 align:start position:0%
your toolbox uh for integrating load it
 

00:56:09.000 --> 00:56:11.630 align:start position:0%
your toolbox uh for integrating load it
should<00:56:09.240> also<00:56:09.520> be<00:56:10.400> it<00:56:10.720> again<00:56:11.079> I<00:56:11.160> think<00:56:11.280> it<00:56:11.440> still

00:56:11.630 --> 00:56:11.640 align:start position:0%
should also be it again I think it still
 

00:56:11.640 --> 00:56:14.390 align:start position:0%
should also be it again I think it still
advances<00:56:12.160> The<00:56:12.559> Narrative<00:56:13.559> there<00:56:13.680> is<00:56:13.920> barrier

00:56:14.390 --> 00:56:14.400 align:start position:0%
advances The Narrative there is barrier
 

00:56:14.400 --> 00:56:16.950 align:start position:0%
advances The Narrative there is barrier
I<00:56:14.520> ad<00:56:14.839> it's<00:56:15.000> not<00:56:15.240> the<00:56:15.359> same<00:56:15.960> Integra

00:56:16.950 --> 00:56:16.960 align:start position:0%
I ad it's not the same Integra
 

00:56:16.960 --> 00:56:19.270 align:start position:0%
I ad it's not the same Integra
generation<00:56:17.319> is<00:56:17.440> an<00:56:17.680> exact<00:56:18.079> same<00:56:18.599> I<00:56:18.760> I<00:56:18.839> think<00:56:19.039> to

00:56:19.270 --> 00:56:19.280 align:start position:0%
generation is an exact same I I think to
 

00:56:19.280 --> 00:56:23.510 align:start position:0%
generation is an exact same I I think to
the<00:56:19.720> the<00:56:19.960> extent<00:56:20.599> that<00:56:20.760> a<00:56:21.480> corporation<00:56:22.480> has<00:56:22.680> a

00:56:23.510 --> 00:56:23.520 align:start position:0%
the the extent that a corporation has a
 

00:56:23.520 --> 00:56:25.829 align:start position:0%
the the extent that a corporation has a
a<00:56:23.920> primary<00:56:24.319> obligation<00:56:24.760> of<00:56:24.960> safety

00:56:25.829 --> 00:56:25.839 align:start position:0%
a primary obligation of safety
 

00:56:25.839 --> 00:56:29.390 align:start position:0%
a primary obligation of safety
reliability<00:56:26.839> secondary<00:56:27.359> obligations<00:56:28.000> to

00:56:29.390 --> 00:56:29.400 align:start position:0%
reliability secondary obligations to
 

00:56:29.400 --> 00:56:32.190 align:start position:0%
reliability secondary obligations to
shareholders<00:56:30.400> that's<00:56:30.720> as<00:56:30.799> a<00:56:30.960> public

00:56:32.190 --> 00:56:32.200 align:start position:0%
shareholders that's as a public
 

00:56:32.200 --> 00:56:35.349 align:start position:0%
shareholders that's as a public
corporation<00:56:33.200> we<00:56:33.400> have<00:56:33.520> to<00:56:33.799> align<00:56:34.799> the

00:56:35.349 --> 00:56:35.359 align:start position:0%
corporation we have to align the
 

00:56:35.359 --> 00:56:37.910 align:start position:0%
corporation we have to align the
Technologies<00:56:36.359> and<00:56:37.160> the<00:56:37.319> Alternatives

00:56:37.910 --> 00:56:37.920 align:start position:0%
Technologies and the Alternatives
 

00:56:37.920 --> 00:56:41.510 align:start position:0%
Technologies and the Alternatives
analysis<00:56:38.680> for<00:56:38.920> that<00:56:39.200> this<00:56:40.039> if<00:56:40.319> is<00:56:40.839> if<00:56:41.000> this<00:56:41.119> is

00:56:41.510 --> 00:56:41.520 align:start position:0%
analysis for that this if is if this is
 

00:56:41.520 --> 00:56:46.270 align:start position:0%
analysis for that this if is if this is
possible<00:56:42.520> to<00:56:43.359> meet<00:56:44.119> that<00:56:44.839> level<00:56:45.319> of<00:56:45.640> of<00:56:45.960> cost

00:56:46.270 --> 00:56:46.280 align:start position:0%
possible to meet that level of of cost
 

00:56:46.280 --> 00:56:49.549 align:start position:0%
possible to meet that level of of cost
reimbursable<00:56:47.280> or<00:56:47.640> fair<00:56:48.119> value<00:56:49.079> then<00:56:49.240> it<00:56:49.440> has

00:56:49.549 --> 00:56:49.559 align:start position:0%
reimbursable or fair value then it has
 

00:56:49.559 --> 00:56:52.270 align:start position:0%
reimbursable or fair value then it has
to<00:56:49.760> be<00:56:50.280> you<00:56:50.400> know<00:56:50.839> presented<00:56:51.400> that<00:56:51.559> way<00:56:52.039> if<00:56:52.160> you

00:56:52.270 --> 00:56:52.280 align:start position:0%
to be you know presented that way if you
 

00:56:52.280 --> 00:56:53.789 align:start position:0%
to be you know presented that way if you
don't<00:56:52.599> do<00:56:52.880> that<00:56:53.119> just<00:56:53.280> because<00:56:53.480> it's<00:56:53.599> a

00:56:53.789 --> 00:56:53.799 align:start position:0%
don't do that just because it's a
 

00:56:53.799 --> 00:56:55.430 align:start position:0%
don't do that just because it's a
technology<00:56:54.400> solution

00:56:55.430 --> 00:56:55.440 align:start position:0%
technology solution
 

00:56:55.440 --> 00:56:57.870 align:start position:0%
technology solution
it<00:56:55.599> is<00:56:55.880> not

00:56:57.870 --> 00:56:57.880 align:start position:0%
it is not
 

00:56:57.880 --> 00:57:01.630 align:start position:0%
it is not
necessarily<00:56:58.880> able<00:56:59.240> to<00:56:59.720> people<00:57:00.000> who<00:57:00.119> are<00:57:00.319> not

00:57:01.630 --> 00:57:01.640 align:start position:0%
necessarily able to people who are not
 

00:57:01.640 --> 00:57:03.829 align:start position:0%
necessarily able to people who are not
technology<00:57:02.640> folks<00:57:03.039> are<00:57:03.240> not<00:57:03.480> necessarily

00:57:03.829 --> 00:57:03.839 align:start position:0%
technology folks are not necessarily
 

00:57:03.839 --> 00:57:05.870 align:start position:0%
technology folks are not necessarily
going<00:57:03.960> to<00:57:04.000> be<00:57:04.119> able<00:57:04.280> to<00:57:04.400> make<00:57:04.599> a<00:57:04.960> financial

00:57:05.870 --> 00:57:05.880 align:start position:0%
going to be able to make a financial
 

00:57:05.880 --> 00:57:08.069 align:start position:0%
going to be able to make a financial
jump<00:57:06.280> in<00:57:06.359> the<00:57:06.480> Alternatives<00:57:07.119> analysis<00:57:07.680> to<00:57:07.839> say

00:57:08.069 --> 00:57:08.079 align:start position:0%
jump in the Alternatives analysis to say
 

00:57:08.079 --> 00:57:11.870 align:start position:0%
jump in the Alternatives analysis to say
this<00:57:08.440> the<00:57:08.720> a<00:57:09.079> better<00:57:09.680> solution<00:57:10.680> and<00:57:10.920> I<00:57:11.079> think

00:57:11.870 --> 00:57:11.880 align:start position:0%
this the a better solution and I think
 

00:57:11.880 --> 00:57:13.910 align:start position:0%
this the a better solution and I think
that's<00:57:12.240> what<00:57:12.400> the<00:57:12.640> industry<00:57:13.160> needs<00:57:13.440> to<00:57:13.640> do

00:57:13.910 --> 00:57:13.920 align:start position:0%
that's what the industry needs to do
 

00:57:13.920 --> 00:57:16.029 align:start position:0%
that's what the industry needs to do
here<00:57:14.160> in<00:57:14.280> order<00:57:14.480> to<00:57:14.599> move<00:57:14.839> this<00:57:15.039> forward

00:57:16.029 --> 00:57:16.039 align:start position:0%
here in order to move this forward
 

00:57:16.039 --> 00:57:18.670 align:start position:0%
here in order to move this forward
because<00:57:16.839> the<00:57:17.079> go<00:57:17.319> the<00:57:17.440> do<00:57:17.760> nothing<00:57:18.160> solution

00:57:18.670 --> 00:57:18.680 align:start position:0%
because the go the do nothing solution
 

00:57:18.680 --> 00:57:19.829 align:start position:0%
because the go the do nothing solution
is<00:57:18.920> a

00:57:19.829 --> 00:57:19.839 align:start position:0%
is a
 

00:57:19.839 --> 00:57:24.349 align:start position:0%
is a
powerful<00:57:21.200> momentum<00:57:22.200> you<00:57:22.359> know<00:57:22.960> solution<00:57:23.960> onto

00:57:24.349 --> 00:57:24.359 align:start position:0%
powerful momentum you know solution onto
 

00:57:24.359 --> 00:57:27.510 align:start position:0%
powerful momentum you know solution onto
how<00:57:24.520> we<00:57:25.280> upgrade<00:57:26.280> the<00:57:26.440> grid<00:57:26.799> because<00:57:27.200> safety

00:57:27.510 --> 00:57:27.520 align:start position:0%
how we upgrade the grid because safety
 

00:57:27.520 --> 00:57:30.430 align:start position:0%
how we upgrade the grid because safety
and<00:57:27.680> reliability<00:57:28.520> become<00:57:29.000> the<00:57:29.200> first<00:57:29.559> thing

00:57:30.430 --> 00:57:30.440 align:start position:0%
and reliability become the first thing
 

00:57:30.440 --> 00:57:33.789 align:start position:0%
and reliability become the first thing
so<00:57:30.640> I<00:57:30.760> think<00:57:31.079> it<00:57:31.400> the<00:57:31.559> the<00:57:31.720> honest<00:57:32.119> is<00:57:32.440> on

00:57:33.789 --> 00:57:33.799 align:start position:0%
so I think it the the honest is on
 

00:57:33.799 --> 00:57:36.670 align:start position:0%
so I think it the the honest is on
industry<00:57:34.799> to<00:57:35.200> put<00:57:35.520> this<00:57:35.720> in<00:57:35.920> a<00:57:36.160> way<00:57:36.400> and

00:57:36.670 --> 00:57:36.680 align:start position:0%
industry to put this in a way and
 

00:57:36.680 --> 00:57:38.390 align:start position:0%
industry to put this in a way and
demonstrate<00:57:37.319> to<00:57:37.520> the<00:57:37.680> regulators<00:57:38.240> and

00:57:38.390 --> 00:57:38.400 align:start position:0%
demonstrate to the regulators and
 

00:57:38.400 --> 00:57:42.150 align:start position:0%
demonstrate to the regulators and
demonstrate<00:57:39.000> to<00:57:39.480> the<00:57:39.680> our<00:57:40.160> ISO<00:57:40.960> toos<00:57:41.960> that

00:57:42.150 --> 00:57:42.160 align:start position:0%
demonstrate to the our ISO toos that
 

00:57:42.160 --> 00:57:44.150 align:start position:0%
demonstrate to the our ISO toos that
this<00:57:42.280> is<00:57:42.480> a<00:57:42.680> viable<00:57:43.119> solution<00:57:43.640> and<00:57:43.720> it<00:57:43.880> does

00:57:44.150 --> 00:57:44.160 align:start position:0%
this is a viable solution and it does
 

00:57:44.160 --> 00:57:45.510 align:start position:0%
this is a viable solution and it does
alleviate<00:57:44.680> some<00:57:44.799> of<00:57:44.880> the<00:57:45.039> capacity

00:57:45.510 --> 00:57:45.520 align:start position:0%
alleviate some of the capacity
 

00:57:45.520 --> 00:57:47.990 align:start position:0%
alleviate some of the capacity
constraints<00:57:46.119> and<00:57:46.480> can<00:57:46.720> be<00:57:46.960> used<00:57:47.559> as<00:57:47.720> part<00:57:47.880> of

00:57:47.990 --> 00:57:48.000 align:start position:0%
constraints and can be used as part of
 

00:57:48.000 --> 00:57:51.430 align:start position:0%
constraints and can be used as part of
the<00:57:48.160> planning<00:57:48.640> process<00:57:49.039> for<00:57:49.319> dynamic<00:57:50.440> ratings

00:57:51.430 --> 00:57:51.440 align:start position:0%
the planning process for dynamic ratings
 

00:57:51.440 --> 00:57:53.750 align:start position:0%
the planning process for dynamic ratings
to<00:57:51.960> to<00:57:52.200> give<00:57:52.359> you<00:57:52.520> some<00:57:52.760> breath<00:57:53.200> and<00:57:53.400> maybe

00:57:53.750 --> 00:57:53.760 align:start position:0%
to to give you some breath and maybe
 

00:57:53.760 --> 00:57:55.829 align:start position:0%
to to give you some breath and maybe
allow<00:57:54.079> some<00:57:54.200> of<00:57:54.280> these<00:57:54.400> prodcts<00:57:54.920> go<00:57:55.119> forward<00:57:55.760> I

00:57:55.829 --> 00:57:55.839 align:start position:0%
allow some of these prodcts go forward I
 

00:57:55.839 --> 00:57:57.950 align:start position:0%
allow some of these prodcts go forward I
don't<00:57:55.960> think<00:57:56.079> it's<00:57:56.240> been<00:57:56.839> demonstrated<00:57:57.839> at

00:57:57.950 --> 00:57:57.960 align:start position:0%
don't think it's been demonstrated at
 

00:57:57.960 --> 00:57:59.870 align:start position:0%
don't think it's been demonstrated at
least<00:57:58.119> not<00:57:58.240> to<00:57:58.400> the<00:57:58.559> extent<00:57:59.000> where<00:57:59.599> people

00:57:59.870 --> 00:57:59.880 align:start position:0%
least not to the extent where people
 

00:57:59.880 --> 00:58:01.950 align:start position:0%
least not to the extent where people
would<00:58:00.079> have<00:58:00.319> confidence<00:58:00.720> to<00:58:01.000> adopt<00:58:01.720> and

00:58:01.950 --> 00:58:01.960 align:start position:0%
would have confidence to adopt and
 

00:58:01.960 --> 00:58:03.630 align:start position:0%
would have confidence to adopt and
that's<00:58:02.160> the<00:58:02.319> demonstration<00:58:03.079> projects<00:58:03.359> that<00:58:03.480> I

00:58:03.630 --> 00:58:03.640 align:start position:0%
that's the demonstration projects that I
 

00:58:03.640 --> 00:58:09.109 align:start position:0%
that's the demonstration projects that I
think<00:58:04.119> we<00:58:04.640> everybody

00:58:09.109 --> 00:58:09.119 align:start position:0%
 
 

00:58:09.119 --> 00:58:12.309 align:start position:0%
 
yes<00:58:10.119> with<00:58:10.319> that<00:58:10.559> thank<00:58:10.720> you<00:58:10.839> so<00:58:11.000> much<00:58:11.240> AJ<00:58:11.880> we'll

00:58:12.309 --> 00:58:12.319 align:start position:0%
yes with that thank you so much AJ we'll
 

00:58:12.319 --> 00:58:14.150 align:start position:0%
yes with that thank you so much AJ we'll
uh<00:58:12.680> keep<00:58:12.920> you<00:58:13.039> around<00:58:13.359> in<00:58:13.520> case<00:58:13.680> there's<00:58:13.920> extra

00:58:14.150 --> 00:58:14.160 align:start position:0%
uh keep you around in case there's extra
 

00:58:14.160 --> 00:58:15.750 align:start position:0%
uh keep you around in case there's extra
time<00:58:14.280> or<00:58:14.440> additional<00:58:14.839> questions<00:58:15.160> during<00:58:15.440> open

00:58:15.750 --> 00:58:15.760 align:start position:0%
time or additional questions during open
 

00:58:15.760 --> 00:58:17.510 align:start position:0%
time or additional questions during open
discussion<00:58:16.400> but<00:58:16.720> appreciate<00:58:17.079> you<00:58:17.200> taking<00:58:17.400> the

00:58:17.510 --> 00:58:17.520 align:start position:0%
discussion but appreciate you taking the
 

00:58:17.520 --> 00:58:20.109 align:start position:0%
discussion but appreciate you taking the
time<00:58:17.640> to<00:58:17.799> be<00:58:18.039> here<00:58:18.319> and<00:58:19.000> filling<00:58:19.280> Us<00:58:19.440> in<00:58:19.640> on<00:58:19.920> an

00:58:20.109 --> 00:58:20.119 align:start position:0%
time to be here and filling Us in on an
 

00:58:20.119 --> 00:58:23.430 align:start position:0%
time to be here and filling Us in on an
exciting<00:58:20.559> topic<00:58:21.280> thank<00:58:21.440> you<00:58:22.200> copy<00:58:22.559> that<00:58:23.280> yeah

00:58:23.430 --> 00:58:23.440 align:start position:0%
exciting topic thank you copy that yeah
 

00:58:23.440 --> 00:58:25.270 align:start position:0%
exciting topic thank you copy that yeah
would<00:58:23.520> you<00:58:23.640> be<00:58:23.760> willing<00:58:23.960> to<00:58:24.000> share<00:58:24.200> one

00:58:25.270 --> 00:58:25.280 align:start position:0%
would you be willing to share one
 

00:58:25.280 --> 00:58:26.510 align:start position:0%
would you be willing to share one
y<00:58:25.520> thank

00:58:26.510 --> 00:58:26.520 align:start position:0%
y thank
 

00:58:26.520 --> 00:58:31.829 align:start position:0%
y thank
you<00:58:27.520> appreciate<00:58:28.160> that<00:58:29.160> um<00:58:29.680> moving<00:58:30.280> on<00:58:30.839> now<00:58:31.559> is

00:58:31.829 --> 00:58:31.839 align:start position:0%
you appreciate that um moving on now is
 

00:58:31.839 --> 00:58:35.029 align:start position:0%
you appreciate that um moving on now is
back<00:58:32.119> perfect<00:58:32.440> timing<00:58:32.880> Ken<00:58:33.720> um<00:58:34.200> want<00:58:34.440> to

00:58:35.029 --> 00:58:35.039 align:start position:0%
back perfect timing Ken um want to
 

00:58:35.039 --> 00:58:38.390 align:start position:0%
back perfect timing Ken um want to
briefly<00:58:35.720> discuss<00:58:36.440> the<00:58:37.000> annual<00:58:37.480> report<00:58:38.240> and

00:58:38.390 --> 00:58:38.400 align:start position:0%
briefly discuss the annual report and
 

00:58:38.400 --> 00:58:40.750 align:start position:0%
briefly discuss the annual report and
what<00:58:38.520> we<00:58:38.599> can<00:58:38.720> be<00:58:38.839> doing<00:58:39.160> to<00:58:39.480> prepare<00:58:39.960> for<00:58:40.440> this

00:58:40.750 --> 00:58:40.760 align:start position:0%
what we can be doing to prepare for this
 

00:58:40.760 --> 00:58:45.029 align:start position:0%
what we can be doing to prepare for this
fall<00:58:41.680> um<00:58:41.839> I'll<00:58:42.000> have<00:58:42.200> Kim<00:58:42.520> remind<00:58:42.920> us<00:58:43.319> of<00:58:44.160> the

00:58:45.029 --> 00:58:45.039 align:start position:0%
fall um I'll have Kim remind us of the
 

00:58:45.039 --> 00:58:48.109 align:start position:0%
fall um I'll have Kim remind us of the
instructions<00:58:46.039> that<00:58:46.599> the<00:58:46.880> Administration<00:58:47.839> has

00:58:48.109 --> 00:58:48.119 align:start position:0%
instructions that the Administration has
 

00:58:48.119 --> 00:58:52.029 align:start position:0%
instructions that the Administration has
given<00:58:48.400> us<00:58:48.760> on<00:58:49.119> a<00:58:49.280> shortened<00:58:49.799> report<00:58:50.520> and<00:58:51.480> um

00:58:52.029 --> 00:58:52.039 align:start position:0%
given us on a shortened report and um
 

00:58:52.039 --> 00:58:54.150 align:start position:0%
given us on a shortened report and um
and<00:58:52.119> a<00:58:52.280> harsh<00:58:52.680> deadline<00:58:53.280> or<00:58:53.559> a<00:58:53.680> deadline<00:58:54.039> that

00:58:54.150 --> 00:58:54.160 align:start position:0%
and a harsh deadline or a deadline that
 

00:58:54.160 --> 00:58:56.390 align:start position:0%
and a harsh deadline or a deadline that
they<00:58:54.319> expected<00:58:54.920> the<00:58:55.000> meet<00:58:55.359> this<00:58:55.559> year<00:58:56.200> but

00:58:56.390 --> 00:58:56.400 align:start position:0%
they expected the meet this year but
 

00:58:56.400 --> 00:58:59.630 align:start position:0%
they expected the meet this year but
before<00:58:56.640> we<00:58:56.799> do<00:58:56.960> so<00:58:57.160> I<00:58:57.240> shared<00:58:57.599> some<00:58:57.839> copies<00:58:58.640> of

00:58:59.630 --> 00:58:59.640 align:start position:0%
before we do so I shared some copies of
 

00:58:59.640 --> 00:59:02.670 align:start position:0%
before we do so I shared some copies of
um<00:58:59.839> essentially<00:59:00.240> the<00:59:00.480> legislation<00:59:01.480> that

00:59:02.670 --> 00:59:02.680 align:start position:0%
um essentially the legislation that
 

00:59:02.680 --> 00:59:05.950 align:start position:0%
um essentially the legislation that
renewed<00:59:03.680> the<00:59:04.079> solar<00:59:04.799> and<00:59:05.319> solar<00:59:05.640> energy

00:59:05.950 --> 00:59:05.960 align:start position:0%
renewed the solar and solar energy
 

00:59:05.960 --> 00:59:08.950 align:start position:0%
renewed the solar and solar energy
development<00:59:06.400> and<00:59:06.799> energy<00:59:07.160> storage<00:59:07.960> Authority

00:59:08.950 --> 00:59:08.960 align:start position:0%
development and energy storage Authority
 

00:59:08.960 --> 00:59:12.150 align:start position:0%
development and energy storage Authority
uh<00:59:09.079> until<00:59:09.480> 2025<00:59:10.480> I<00:59:10.680> just<00:59:10.760> want<00:59:10.839> to<00:59:11.000> call<00:59:11.319> to

00:59:12.150 --> 00:59:12.160 align:start position:0%
uh until 2025 I just want to call to
 

00:59:12.160 --> 00:59:13.670 align:start position:0%
uh until 2025 I just want to call to
everyone's<00:59:12.559> attention<00:59:12.960> a<00:59:13.079> few<00:59:13.400> different

00:59:13.670 --> 00:59:13.680 align:start position:0%
everyone's attention a few different
 

00:59:13.680 --> 00:59:16.670 align:start position:0%
everyone's attention a few different
items<00:59:14.319> um<00:59:14.440> in<00:59:14.599> terms<00:59:14.880> of<00:59:15.200> the<00:59:15.720> the<00:59:16.000> purpose

00:59:16.670 --> 00:59:16.680 align:start position:0%
items um in terms of the the purpose
 

00:59:16.680 --> 00:59:18.750 align:start position:0%
items um in terms of the the purpose
among<00:59:17.000> other<00:59:17.319> things<00:59:17.640> of<00:59:17.799> the<00:59:17.960> authorities<00:59:18.359> to

00:59:18.750 --> 00:59:18.760 align:start position:0%
among other things of the authorities to
 

00:59:18.760 --> 00:59:21.270 align:start position:0%
among other things of the authorities to
facilitate<00:59:19.760> coordinate<00:59:20.240> and<00:59:20.440> support<00:59:21.079> the

00:59:21.270 --> 00:59:21.280 align:start position:0%
facilitate coordinate and support the
 

00:59:21.280 --> 00:59:23.630 align:start position:0%
facilitate coordinate and support the
development<00:59:21.960> of<00:59:22.280> these<00:59:22.640> Technologies<00:59:23.280> in

00:59:23.630 --> 00:59:23.640 align:start position:0%
development of these Technologies in
 

00:59:23.640 --> 00:59:25.950 align:start position:0%
development of these Technologies in
Virginia<00:59:24.720> and<00:59:24.839> promote<00:59:25.160> the<00:59:25.400> Commonwealth

00:59:25.950 --> 00:59:25.960 align:start position:0%
Virginia and promote the Commonwealth
 

00:59:25.960 --> 00:59:28.870 align:start position:0%
Virginia and promote the Commonwealth
solar<00:59:26.440> and<00:59:26.680> energy<00:59:27.000> storage<00:59:27.880> Industries

00:59:28.870 --> 00:59:28.880 align:start position:0%
solar and energy storage Industries
 

00:59:28.880 --> 00:59:30.829 align:start position:0%
solar and energy storage Industries
positioning<00:59:29.400> the<00:59:29.559> Commonwealth<00:59:30.240> as<00:59:30.319> a<00:59:30.480> leader

00:59:30.829 --> 00:59:30.839 align:start position:0%
positioning the Commonwealth as a leader
 

00:59:30.839 --> 00:59:32.510 align:start position:0%
positioning the Commonwealth as a leader
in<00:59:31.000> research<00:59:31.520> development

00:59:32.510 --> 00:59:32.520 align:start position:0%
in research development
 

00:59:32.520 --> 00:59:34.470 align:start position:0%
in research development
commercialization<00:59:33.520> manufacturing<00:59:34.280> and

00:59:34.470 --> 00:59:34.480 align:start position:0%
commercialization manufacturing and
 

00:59:34.480 --> 00:59:36.349 align:start position:0%
commercialization manufacturing and
deployment<00:59:35.480> of

00:59:36.349 --> 00:59:36.359 align:start position:0%
deployment of
 

00:59:36.359 --> 00:59:40.549 align:start position:0%
deployment of
energy<00:59:37.359> energy<00:59:37.960> storage<00:59:38.599> and<00:59:38.799> solar<00:59:39.119> energy

00:59:40.549 --> 00:59:40.559 align:start position:0%
energy energy storage and solar energy
 

00:59:40.559 --> 00:59:42.950 align:start position:0%
energy energy storage and solar energy
technology<00:59:41.559> um<00:59:41.839> in<00:59:41.960> terms<00:59:42.200> of<00:59:42.319> the<00:59:42.520> powers<00:59:42.799> and

00:59:42.950 --> 00:59:42.960 align:start position:0%
technology um in terms of the powers and
 

00:59:42.960 --> 00:59:45.789 align:start position:0%
technology um in terms of the powers and
duties<00:59:43.400> of<00:59:43.559> the<00:59:44.079> authority<00:59:45.079> uh<00:59:45.400> you<00:59:45.559> have<00:59:45.680> the

00:59:45.789 --> 00:59:45.799 align:start position:0%
duties of the authority uh you have the
 

00:59:45.799 --> 00:59:47.430 align:start position:0%
duties of the authority uh you have the
entire<00:59:46.119> list<00:59:46.319> but<00:59:46.440> I'll<00:59:46.599> call<00:59:46.799> your<00:59:47.119> attention

00:59:47.430 --> 00:59:47.440 align:start position:0%
entire list but I'll call your attention
 

00:59:47.440 --> 00:59:50.150 align:start position:0%
entire list but I'll call your attention
to<00:59:47.640> number<00:59:47.880> 11<00:59:48.839> identify<00:59:49.319> and<00:59:49.480> take<00:59:49.720> steps<00:59:49.960> to

00:59:50.150 --> 00:59:50.160 align:start position:0%
to number 11 identify and take steps to
 

00:59:50.160 --> 00:59:53.230 align:start position:0%
to number 11 identify and take steps to
mitigate<00:59:50.799> existing<00:59:51.280> state<00:59:51.760> and<00:59:52.240> Regulatory

00:59:53.230 --> 00:59:53.240 align:start position:0%
mitigate existing state and Regulatory
 

00:59:53.240 --> 00:59:55.309 align:start position:0%
mitigate existing state and Regulatory
or<00:59:53.880> administrative<00:59:54.480> B<00:59:54.640> barriers<00:59:55.000> to<00:59:55.160> the

00:59:55.309 --> 00:59:55.319 align:start position:0%
or administrative B barriers to the
 

00:59:55.319 --> 00:59:57.470 align:start position:0%
or administrative B barriers to the
development<00:59:55.839> of<00:59:56.039> solar<00:59:56.599> energy<00:59:57.000> and<00:59:57.160> energy

00:59:57.470 --> 00:59:57.480 align:start position:0%
development of solar energy and energy
 

00:59:57.480 --> 00:59:59.670 align:start position:0%
development of solar energy and energy
storage<00:59:57.920> Industries<00:59:58.680> including

00:59:59.670 --> 00:59:59.680 align:start position:0%
storage Industries including
 

00:59:59.680 --> 01:00:02.190 align:start position:0%
storage Industries including
facilitating<01:00:00.319> anyting

01:00:02.190 --> 01:00:02.200 align:start position:0%
facilitating anyting
 

01:00:02.200 --> 01:00:05.069 align:start position:0%
facilitating anyting
processes<01:00:03.200> number<01:00:03.480> 13<01:00:04.280> collaborate<01:00:04.839> with

01:00:05.069 --> 01:00:05.079 align:start position:0%
processes number 13 collaborate with
 

01:00:05.079 --> 01:00:06.870 align:start position:0%
processes number 13 collaborate with
entities<01:00:05.599> including<01:00:06.079> institutions<01:00:06.680> of

01:00:06.870 --> 01:00:06.880 align:start position:0%
entities including institutions of
 

01:00:06.880 --> 01:00:08.950 align:start position:0%
entities including institutions of
higher<01:00:07.160> education<01:00:07.640> that<01:00:07.799> increase<01:00:08.520> training

01:00:08.950 --> 01:00:08.960 align:start position:0%
higher education that increase training
 

01:00:08.960 --> 01:00:11.510 align:start position:0%
higher education that increase training
development<01:00:09.760> Workforce<01:00:10.760> needed<01:00:11.160> by<01:00:11.319> the

01:00:11.510 --> 01:00:11.520 align:start position:0%
development Workforce needed by the
 

01:00:11.520 --> 01:00:13.870 align:start position:0%
development Workforce needed by the
solar<01:00:12.079> and<01:00:12.240> energy<01:00:12.599> storage

01:00:13.870 --> 01:00:13.880 align:start position:0%
solar and energy storage
 

01:00:13.880 --> 01:00:16.950 align:start position:0%
solar and energy storage
Industries<01:00:14.920> 15<01:00:15.920> promote<01:00:16.400> collaborative

01:00:16.950 --> 01:00:16.960 align:start position:0%
Industries 15 promote collaborative
 

01:00:16.960 --> 01:00:18.829 align:start position:0%
Industries 15 promote collaborative
efforts<01:00:17.520> among<01:00:17.920> the<01:00:18.039> Commonwealth<01:00:18.640> public

01:00:18.829 --> 01:00:18.839 align:start position:0%
efforts among the Commonwealth public
 

01:00:18.839 --> 01:00:20.230 align:start position:0%
efforts among the Commonwealth public
and<01:00:19.000> private

01:00:20.230 --> 01:00:20.240 align:start position:0%
and private
 

01:00:20.240 --> 01:00:22.630 align:start position:0%
and private
institutions<01:00:21.240> uh<01:00:21.559> Higher<01:00:21.880> Education<01:00:22.319> and

01:00:22.630 --> 01:00:22.640 align:start position:0%
institutions uh Higher Education and
 

01:00:22.640 --> 01:00:24.710 align:start position:0%
institutions uh Higher Education and
Research<01:00:23.640> development<01:00:24.079> and<01:00:24.240> Cur

01:00:24.710 --> 01:00:24.720 align:start position:0%
Research development and Cur
 

01:00:24.720 --> 01:00:26.829 align:start position:0%
Research development and Cur
personalization<01:00:25.720> of<01:00:26.039> efforts<01:00:26.400> related<01:00:26.680> to

01:00:26.829 --> 01:00:26.839 align:start position:0%
personalization of efforts related to
 

01:00:26.839 --> 01:00:29.109 align:start position:0%
personalization of efforts related to
energy<01:00:27.160> storage<01:00:27.599> and<01:00:27.920> 16<01:00:28.400> to<01:00:28.640> monitor

01:00:29.109 --> 01:00:29.119 align:start position:0%
energy storage and 16 to monitor
 

01:00:29.119 --> 01:00:30.549 align:start position:0%
energy storage and 16 to monitor
developments<01:00:29.640> of<01:00:29.839> energy<01:00:30.119> storage

01:00:30.549 --> 01:00:30.559 align:start position:0%
developments of energy storage
 

01:00:30.559 --> 01:00:32.750 align:start position:0%
developments of energy storage
technology<01:00:31.039> and<01:00:31.160> employment<01:00:31.720> nationally<01:00:32.599> and

01:00:32.750 --> 01:00:32.760 align:start position:0%
technology and employment nationally and
 

01:00:32.760 --> 01:00:34.349 align:start position:0%
technology and employment nationally and
disseminate<01:00:33.359> relevant

01:00:34.349 --> 01:00:34.359 align:start position:0%
disseminate relevant
 

01:00:34.359 --> 01:00:37.549 align:start position:0%
disseminate relevant
information<01:00:35.359> and<01:00:35.520> research<01:00:36.079> results<01:00:36.720> and<01:00:37.400> in

01:00:37.549 --> 01:00:37.559 align:start position:0%
information and research results and in
 

01:00:37.559 --> 01:00:40.589 align:start position:0%
information and research results and in
terms<01:00:37.799> of<01:00:38.280> the<01:00:39.280> the<01:00:39.640> the<01:00:39.799> requirement<01:00:40.280> to

01:00:40.589 --> 01:00:40.599 align:start position:0%
terms of the the the requirement to
 

01:00:40.599 --> 01:00:43.069 align:start position:0%
terms of the the the requirement to
submit<01:00:41.000> an<01:00:41.319> an<01:00:41.520> annual<01:00:41.960> report<01:00:42.400> it's<01:00:42.799> it's

01:00:43.069 --> 01:00:43.079 align:start position:0%
submit an an annual report it's it's
 

01:00:43.079 --> 01:00:44.910 align:start position:0%
submit an an annual report it's it's
rather<01:00:43.359> vague<01:00:43.640> but<01:00:43.760> it<01:00:43.880> says<01:00:44.160> two<01:00:44.400> things<01:00:44.799> we

01:00:44.910 --> 01:00:44.920 align:start position:0%
rather vague but it says two things we
 

01:00:44.920 --> 01:00:46.470 align:start position:0%
rather vague but it says two things we
need<01:00:45.079> to<01:00:45.240> include<01:00:45.559> in<01:00:45.640> the<01:00:45.799> report<01:00:46.160> our

01:00:46.470 --> 01:00:46.480 align:start position:0%
need to include in the report our
 

01:00:46.480 --> 01:00:49.349 align:start position:0%
need to include in the report our
activities<01:00:47.119> of<01:00:47.280> the<01:00:47.440> authority<01:00:48.240> as<01:00:48.359> well<01:00:48.559> as

01:00:49.349 --> 01:00:49.359 align:start position:0%
activities of the authority as well as
 

01:00:49.359 --> 01:00:52.589 align:start position:0%
activities of the authority as well as
recommendations<01:00:50.359> with<01:00:50.480> the<01:00:50.599> governor<01:00:51.520> to<01:00:52.200> the

01:00:52.589 --> 01:00:52.599 align:start position:0%
recommendations with the governor to the
 

01:00:52.599 --> 01:00:54.470 align:start position:0%
recommendations with the governor to the
leader<01:00:53.039> of<01:00:53.400> the<01:00:53.559> leaders<01:00:53.839> of<01:00:53.920> the<01:00:54.000> general

01:00:54.470 --> 01:00:54.480 align:start position:0%
leader of the leaders of the general
 

01:00:54.480 --> 01:00:55.990 align:start position:0%
leader of the leaders of the general
assmbly<01:00:54.799> including<01:00:55.160> the<01:00:55.319> relevant

01:00:55.990 --> 01:00:56.000 align:start position:0%
assmbly including the relevant
 

01:00:56.000 --> 01:00:59.069 align:start position:0%
assmbly including the relevant
committees<01:00:56.760> so<01:00:57.480> with<01:00:57.880> this<01:00:58.079> report<01:00:58.720> and<01:00:58.880> a

01:00:59.069 --> 01:00:59.079 align:start position:0%
committees so with this report and a
 

01:00:59.079 --> 01:01:04.029 align:start position:0%
committees so with this report and a
more<01:00:59.400> digestable<01:01:00.240> 10<01:01:00.480> to<01:01:00.720> 15<01:01:01.359> page<01:01:02.559> package<01:01:03.559> um

01:01:04.029 --> 01:01:04.039 align:start position:0%
more digestable 10 to 15 page package um
 

01:01:04.039 --> 01:01:05.670 align:start position:0%
more digestable 10 to 15 page package um
we<01:01:04.200> hope<01:01:04.400> to<01:01:04.720> take<01:01:04.880> the<01:01:05.039> step<01:01:05.240> forward<01:01:05.559> this

01:01:05.670 --> 01:01:05.680 align:start position:0%
we hope to take the step forward this
 

01:01:05.680 --> 01:01:07.349 align:start position:0%
we hope to take the step forward this
year<01:01:05.799> and<01:01:05.960> make<01:01:06.119> some<01:01:06.319> recommendations<01:01:07.160> and

01:01:07.349 --> 01:01:07.359 align:start position:0%
year and make some recommendations and
 

01:01:07.359 --> 01:01:10.470 align:start position:0%
year and make some recommendations and
and<01:01:07.559> follow<01:01:08.000> what<01:01:08.359> the<01:01:08.760> authority<01:01:09.760> uh<01:01:09.960> was<01:01:10.240> was

01:01:10.470 --> 01:01:10.480 align:start position:0%
and follow what the authority uh was was
 

01:01:10.480 --> 01:01:12.190 align:start position:0%
and follow what the authority uh was was
set<01:01:10.599> out<01:01:10.720> to<01:01:10.839> do<01:01:10.960> in<01:01:11.119> legislation<01:01:11.640> and<01:01:11.839> hopes

01:01:12.190 --> 01:01:12.200 align:start position:0%
set out to do in legislation and hopes
 

01:01:12.200 --> 01:01:14.270 align:start position:0%
set out to do in legislation and hopes
that<01:01:12.559> the<01:01:13.119> general<01:01:13.440> assembly<01:01:13.920> and<01:01:14.079> the

01:01:14.270 --> 01:01:14.280 align:start position:0%
that the general assembly and the
 

01:01:14.280 --> 01:01:16.390 align:start position:0%
that the general assembly and the
governor<01:01:14.720> sees<01:01:15.039> fit<01:01:15.240> to<01:01:15.440> extend<01:01:15.839> and<01:01:16.039> pass

01:01:16.390 --> 01:01:16.400 align:start position:0%
governor sees fit to extend and pass
 

01:01:16.400 --> 01:01:19.430 align:start position:0%
governor sees fit to extend and pass
2025<01:01:17.400> so<01:01:17.640> Ken<01:01:17.880> would<01:01:18.000> you<01:01:18.240> remind<01:01:18.640> us<01:01:18.920> briefly

01:01:19.430 --> 01:01:19.440 align:start position:0%
2025 so Ken would you remind us briefly
 

01:01:19.440 --> 01:01:22.510 align:start position:0%
2025 so Ken would you remind us briefly
about<01:01:20.119> the<01:01:21.119> uh<01:01:21.280> what<01:01:21.400> the<01:01:21.559> report<01:01:21.839> will<01:01:22.000> look

01:01:22.510 --> 01:01:22.520 align:start position:0%
about the uh what the report will look
 

01:01:22.520 --> 01:01:24.990 align:start position:0%
about the uh what the report will look
like<01:01:23.520> well<01:01:23.680> I<01:01:23.720> don't<01:01:23.960> have<01:01:24.240> the<01:01:24.559> guance<01:01:24.920> in

01:01:24.990 --> 01:01:25.000 align:start position:0%
like well I don't have the guance in
 

01:01:25.000 --> 01:01:26.910 align:start position:0%
like well I don't have the guance in
front<01:01:25.160> of<01:01:25.240> me<01:01:25.400> but<01:01:25.559> generally<01:01:26.039> it's<01:01:26.599> keep<01:01:26.760> it

01:01:26.910 --> 01:01:26.920 align:start position:0%
front of me but generally it's keep it
 

01:01:26.920 --> 01:01:28.829 align:start position:0%
front of me but generally it's keep it
short<01:01:27.640> keep<01:01:27.839> it<01:01:27.920> to<01:01:28.119> what<01:01:28.280> the<01:01:28.400> authority

01:01:28.829 --> 01:01:28.839 align:start position:0%
short keep it to what the authority
 

01:01:28.839 --> 01:01:32.309 align:start position:0%
short keep it to what the authority
actually<01:01:29.160> worked<01:01:29.599> on<01:01:30.520> don't<01:01:30.839> go<01:01:31.039> into<01:01:31.880> items

01:01:32.309 --> 01:01:32.319 align:start position:0%
actually worked on don't go into items
 

01:01:32.319 --> 01:01:34.430 align:start position:0%
actually worked on don't go into items
that<01:01:32.480> are<01:01:32.720> outside<01:01:33.280> of<01:01:33.760> what<01:01:33.960> the<01:01:34.079> authority

01:01:34.430 --> 01:01:34.440 align:start position:0%
that are outside of what the authority
 

01:01:34.440 --> 01:01:37.029 align:start position:0%
that are outside of what the authority
has<01:01:34.599> looked<01:01:34.799> at<01:01:34.960> over<01:01:35.160> the<01:01:35.359> past<01:01:35.720> year<01:01:36.720> uh<01:01:36.880> and

01:01:37.029 --> 01:01:37.039 align:start position:0%
has looked at over the past year uh and
 

01:01:37.039 --> 01:01:39.150 align:start position:0%
has looked at over the past year uh and
that's<01:01:37.440> basically<01:01:37.880> what<01:01:38.119> the<01:01:38.319> entire<01:01:38.799> report

01:01:39.150 --> 01:01:39.160 align:start position:0%
that's basically what the entire report
 

01:01:39.160 --> 01:01:40.829 align:start position:0%
that's basically what the entire report
in<01:01:39.280> the<01:01:39.440> past<01:01:39.640> has<01:01:39.839> been<01:01:40.200> it's<01:01:40.520> what<01:01:40.640> is

01:01:40.829 --> 01:01:40.839 align:start position:0%
in the past has been it's what is
 

01:01:40.839 --> 01:01:41.870 align:start position:0%
in the past has been it's what is
happening<01:01:41.119> in

01:01:41.870 --> 01:01:41.880 align:start position:0%
happening in
 

01:01:41.880 --> 01:01:45.270 align:start position:0%
happening in
Virginia<01:01:43.039> and<01:01:44.039> if<01:01:44.160> it<01:01:44.319> doesn't<01:01:44.559> have<01:01:44.720> anything

01:01:45.270 --> 01:01:45.280 align:start position:0%
Virginia and if it doesn't have anything
 

01:01:45.280 --> 01:01:47.309 align:start position:0%
Virginia and if it doesn't have anything
to<01:01:45.520> directly<01:01:45.920> do<01:01:46.119> with<01:01:46.240> the<01:01:46.359> authority

01:01:47.309 --> 01:01:47.319 align:start position:0%
to directly do with the authority
 

01:01:47.319 --> 01:01:51.269 align:start position:0%
to directly do with the authority
apparently<01:01:48.319> they<01:01:48.920> don't<01:01:49.119> want<01:01:49.240> to<01:01:49.319> see<01:01:49.520> it<01:01:50.279> y

01:01:51.269 --> 01:01:51.279 align:start position:0%
apparently they don't want to see it y
 

01:01:51.279 --> 01:01:52.910 align:start position:0%
apparently they don't want to see it y
well<01:01:51.359> I<01:01:51.520> hope<01:01:51.760> that<01:01:51.880> frees<01:01:52.240> up<01:01:52.400> some<01:01:52.559> brain

01:01:52.910 --> 01:01:52.920 align:start position:0%
well I hope that frees up some brain
 

01:01:52.920 --> 01:01:55.910 align:start position:0%
well I hope that frees up some brain
power<01:01:53.559> of<01:01:53.760> authority<01:01:54.079> members<01:01:54.720> and<01:01:55.160> for<01:01:55.520> staff

01:01:55.910 --> 01:01:55.920 align:start position:0%
power of authority members and for staff
 

01:01:55.920 --> 01:02:01.549 align:start position:0%
power of authority members and for staff
to<01:01:56.440> uh<01:01:57.359> get<01:01:57.960> a<01:01:58.960> a<01:01:59.119> very<01:01:59.400> solid<01:02:00.160> shorter<01:02:01.160> list<01:02:01.359> of

01:02:01.549 --> 01:02:01.559 align:start position:0%
to uh get a a very solid shorter list of
 

01:02:01.559 --> 01:02:02.990 align:start position:0%
to uh get a a very solid shorter list of
recommendations<01:02:02.160> and<01:02:02.400> summaries<01:02:02.760> of

01:02:02.990 --> 01:02:03.000 align:start position:0%
recommendations and summaries of
 

01:02:03.000 --> 01:02:05.549 align:start position:0%
recommendations and summaries of
activities<01:02:04.000> in<01:02:04.079> the<01:02:04.200> past<01:02:04.920> the<01:02:05.000> authority<01:02:05.359> has

01:02:05.549 --> 01:02:05.559 align:start position:0%
activities in the past the authority has
 

01:02:05.559 --> 01:02:07.589 align:start position:0%
activities in the past the authority has
never<01:02:05.799> made<01:02:06.039> any<01:02:06.400> recommendations<01:02:07.400> they

01:02:07.589 --> 01:02:07.599 align:start position:0%
never made any recommendations they
 

01:02:07.599 --> 01:02:09.750 align:start position:0%
never made any recommendations they
chose<01:02:07.920> to<01:02:08.160> instead<01:02:08.480> do<01:02:08.680> this<01:02:08.880> very

01:02:09.750 --> 01:02:09.760 align:start position:0%
chose to instead do this very
 

01:02:09.760 --> 01:02:11.589 align:start position:0%
chose to instead do this very
long<01:02:10.760> you

01:02:11.589 --> 01:02:11.599 align:start position:0%
long you
 

01:02:11.599 --> 01:02:13.710 align:start position:0%
long you
know<01:02:12.599> narrative<01:02:13.000> on<01:02:13.160> what's<01:02:13.359> going<01:02:13.480> on<01:02:13.599> in

01:02:13.710 --> 01:02:13.720 align:start position:0%
know narrative on what's going on in
 

01:02:13.720 --> 01:02:17.430 align:start position:0%
know narrative on what's going on in
Virginia<01:02:14.359> can<01:02:14.480> I<01:02:14.599> make<01:02:14.720> a<01:02:14.839> comment<01:02:15.240> please<01:02:15.920> um

01:02:17.430 --> 01:02:17.440 align:start position:0%
Virginia can I make a comment please um
 

01:02:17.440 --> 01:02:20.789 align:start position:0%
Virginia can I make a comment please um
so<01:02:18.440> I<01:02:18.960> I<01:02:19.039> don't<01:02:19.240> remember<01:02:19.760> this<01:02:19.880> bill<01:02:20.119> in<01:02:20.240> 2015

01:02:20.789 --> 01:02:20.799 align:start position:0%
so I I don't remember this bill in 2015
 

01:02:20.799 --> 01:02:22.510 align:start position:0%
so I I don't remember this bill in 2015
when<01:02:20.880> we<01:02:21.000> voted<01:02:21.279> on<01:02:21.400> it<01:02:21.520> so<01:02:21.680> I<01:02:21.960> apologize<01:02:22.440> I

01:02:22.510 --> 01:02:22.520 align:start position:0%
when we voted on it so I apologize I
 

01:02:22.520 --> 01:02:24.390 align:start position:0%
when we voted on it so I apologize I
don't<01:02:22.680> remember<01:02:22.960> the<01:02:23.119> pitch<01:02:23.400> of<01:02:23.520> it<01:02:23.960> but<01:02:24.079> it's

01:02:24.390 --> 01:02:24.400 align:start position:0%
don't remember the pitch of it but it's
 

01:02:24.400 --> 01:02:25.870 align:start position:0%
don't remember the pitch of it but it's
inter<01:02:24.599> in<01:02:24.680> to<01:02:24.799> me<01:02:25.000> that<01:02:25.119> this<01:02:25.240> is<01:02:25.400> not<01:02:25.599> a

01:02:25.870 --> 01:02:25.880 align:start position:0%
inter in to me that this is not a
 

01:02:25.880 --> 01:02:29.230 align:start position:0%
inter in to me that this is not a
commission<01:02:26.440> it's<01:02:26.559> an<01:02:27.119> authority<01:02:28.119> um<01:02:28.799> and<01:02:29.079> it's

01:02:29.230 --> 01:02:29.240 align:start position:0%
commission it's an authority um and it's
 

01:02:29.240 --> 01:02:32.510 align:start position:0%
commission it's an authority um and it's
a<01:02:29.559> political<01:02:30.039> subdivision<01:02:31.039> and<01:02:31.200> it<01:02:31.520> has

01:02:32.510 --> 01:02:32.520 align:start position:0%
a political subdivision and it has
 

01:02:32.520 --> 01:02:36.029 align:start position:0%
a political subdivision and it has
significant<01:02:33.520> Powers<01:02:34.039> Beyond<01:02:34.920> advising<01:02:35.880> and

01:02:36.029 --> 01:02:36.039 align:start position:0%
significant Powers Beyond advising and
 

01:02:36.039 --> 01:02:39.269 align:start position:0%
significant Powers Beyond advising and
making<01:02:36.359> suggestions<01:02:37.200> I<01:02:37.279> mean<01:02:37.760> in<01:02:38.079> theory<01:02:39.079> this

01:02:39.269 --> 01:02:39.279 align:start position:0%
making suggestions I mean in theory this
 

01:02:39.279 --> 01:02:41.910 align:start position:0%
making suggestions I mean in theory this
Authority<01:02:39.760> could<01:02:40.079> develop<01:02:40.559> solar<01:02:40.960> projects

01:02:41.910 --> 01:02:41.920 align:start position:0%
Authority could develop solar projects
 

01:02:41.920 --> 01:02:45.549 align:start position:0%
Authority could develop solar projects
I'm<01:02:42.000> not<01:02:42.160> suggesting<01:02:42.559> that's<01:02:42.760> a<01:02:42.960> good<01:02:43.640> idea<01:02:44.640> um

01:02:45.549 --> 01:02:45.559 align:start position:0%
I'm not suggesting that's a good idea um
 

01:02:45.559 --> 01:02:48.430 align:start position:0%
I'm not suggesting that's a good idea um
but<01:02:46.440> I<01:02:46.520> mean<01:02:47.240> I<01:02:47.480> you<01:02:47.599> know<01:02:47.720> I<01:02:47.799> was<01:02:47.920> on<01:02:48.039> the<01:02:48.119> code

01:02:48.430 --> 01:02:48.440 align:start position:0%
but I mean I you know I was on the code
 

01:02:48.440 --> 01:02:51.150 align:start position:0%
but I mean I you know I was on the code
commission<01:02:48.920> the<01:02:49.039> code<01:02:49.359> commission<01:02:50.359> evaluates

01:02:51.150 --> 01:02:51.160 align:start position:0%
commission the code commission evaluates
 

01:02:51.160 --> 01:02:53.029 align:start position:0%
commission the code commission evaluates
legislative<01:02:51.720> ideas<01:02:52.119> Valu<01:02:52.440> proposals<01:02:52.799> takes

01:02:53.029 --> 01:02:53.039 align:start position:0%
legislative ideas Valu proposals takes
 

01:02:53.039 --> 01:02:54.549 align:start position:0%
legislative ideas Valu proposals takes
feedback<01:02:53.520> and<01:02:53.640> makes<01:02:53.880> recommendations

01:02:54.549 --> 01:02:54.559 align:start position:0%
feedback and makes recommendations
 

01:02:54.559 --> 01:02:56.390 align:start position:0%
feedback and makes recommendations
that's<01:02:54.680> what<01:02:54.760> a<01:02:54.839> commission<01:02:55.240> does<01:02:55.599> it's<01:02:55.839> not

01:02:56.390 --> 01:02:56.400 align:start position:0%
that's what a commission does it's not
 

01:02:56.400 --> 01:02:57.910 align:start position:0%
that's what a commission does it's not
it's<01:02:56.559> not<01:02:56.720> an<01:02:56.880> authority<01:02:57.319> it's<01:02:57.440> not<01:02:57.559> a<01:02:57.640> PL

01:02:57.910 --> 01:02:57.920 align:start position:0%
it's not an authority it's not a PL
 

01:02:57.920 --> 01:03:00.549 align:start position:0%
it's not an authority it's not a PL
subdivision<01:02:58.920> plal<01:02:59.240> subdivisions<01:02:59.799> can<01:03:00.240> borrow

01:03:00.549 --> 01:03:00.559 align:start position:0%
subdivision plal subdivisions can borrow
 

01:03:00.559 --> 01:03:03.390 align:start position:0%
subdivision plal subdivisions can borrow
money<01:03:00.920> invest<01:03:01.319> money<01:03:01.720> run<01:03:02.200> programs<01:03:03.200> all

01:03:03.390 --> 01:03:03.400 align:start position:0%
money invest money run programs all
 

01:03:03.400 --> 01:03:04.430 align:start position:0%
money invest money run programs all
kinds<01:03:03.599> of

01:03:04.430 --> 01:03:04.440 align:start position:0%
kinds of
 

01:03:04.440 --> 01:03:08.510 align:start position:0%
kinds of
things<01:03:05.440> to<01:03:05.680> me<01:03:06.319> like<01:03:07.200> and<01:03:07.440> I<01:03:07.839> I<01:03:07.920> don't<01:03:08.240> again<01:03:08.440> I

01:03:08.510 --> 01:03:08.520 align:start position:0%
things to me like and I I don't again I
 

01:03:08.520 --> 01:03:12.870 align:start position:0%
things to me like and I I don't again I
don't<01:03:08.799> remember<01:03:09.279> how<01:03:09.440> it<01:03:09.559> was<01:03:10.000> pitched<01:03:11.000> but<01:03:12.000> um

01:03:12.870 --> 01:03:12.880 align:start position:0%
don't remember how it was pitched but um
 

01:03:12.880 --> 01:03:14.710 align:start position:0%
don't remember how it was pitched but um
I<01:03:13.000> feel<01:03:13.359> like<01:03:13.640> my<01:03:13.799> impression<01:03:14.160> is<01:03:14.440> it's<01:03:14.599> kind

01:03:14.710 --> 01:03:14.720 align:start position:0%
I feel like my impression is it's kind
 

01:03:14.720 --> 01:03:17.190 align:start position:0%
I feel like my impression is it's kind
of<01:03:14.960> act<01:03:15.240> as<01:03:15.559> acted<01:03:15.839> as<01:03:15.960> a<01:03:16.079> commission<01:03:16.960> maybe

01:03:17.190 --> 01:03:17.200 align:start position:0%
of act as acted as a commission maybe
 

01:03:17.200 --> 01:03:18.789 align:start position:0%
of act as acted as a commission maybe
that's<01:03:17.359> what<01:03:17.440> it<01:03:17.559> ought<01:03:17.680> to<01:03:17.880> be<01:03:18.400> and<01:03:18.520> maybe

01:03:18.789 --> 01:03:18.799 align:start position:0%
that's what it ought to be and maybe
 

01:03:18.799 --> 01:03:20.269 align:start position:0%
that's what it ought to be and maybe
ought<01:03:19.000> be<01:03:19.119> reenacted<01:03:19.640> as<01:03:19.720> a<01:03:19.839> commission<01:03:20.160> not

01:03:20.269 --> 01:03:20.279 align:start position:0%
ought be reenacted as a commission not
 

01:03:20.279 --> 01:03:23.069 align:start position:0%
ought be reenacted as a commission not
an<01:03:20.520> authority<01:03:21.520> um<01:03:21.960> but<01:03:22.119> I'd<01:03:22.319> be<01:03:22.520> curious<01:03:22.839> for

01:03:23.069 --> 01:03:23.079 align:start position:0%
an authority um but I'd be curious for
 

01:03:23.079 --> 01:03:25.950 align:start position:0%
an authority um but I'd be curious for
folks<01:03:24.000> to<01:03:24.359> spend<01:03:24.559> some<01:03:24.720> time<01:03:25.079> actually

01:03:25.950 --> 01:03:25.960 align:start position:0%
folks to spend some time actually
 

01:03:25.960 --> 01:03:29.029 align:start position:0%
folks to spend some time actually
reading<01:03:27.000> 1902<01:03:28.000> what<01:03:28.119> it<01:03:28.240> can<01:03:28.440> actually<01:03:28.640> do<01:03:28.839> and

01:03:29.029 --> 01:03:29.039 align:start position:0%
reading 1902 what it can actually do and
 

01:03:29.039 --> 01:03:33.390 align:start position:0%
reading 1902 what it can actually do and
is<01:03:29.240> there<01:03:29.680> space<01:03:30.680> to<01:03:31.279> actually<01:03:32.279> um<01:03:33.079> make

01:03:33.390 --> 01:03:33.400 align:start position:0%
is there space to actually um make
 

01:03:33.400 --> 01:03:35.910 align:start position:0%
is there space to actually um make
advances<01:03:34.079> using<01:03:34.520> the<01:03:34.720> unique<01:03:35.279> powers<01:03:35.680> given

01:03:35.910 --> 01:03:35.920 align:start position:0%
advances using the unique powers given
 

01:03:35.920 --> 01:03:36.829 align:start position:0%
advances using the unique powers given
to<01:03:36.039> an

01:03:36.829 --> 01:03:36.839 align:start position:0%
to an
 

01:03:36.839 --> 01:03:39.670 align:start position:0%
to an
authority<01:03:37.839> I<01:03:37.920> don't<01:03:38.039> have<01:03:38.160> any<01:03:38.319> answers<01:03:39.279> I<01:03:39.520> had

01:03:39.670 --> 01:03:39.680 align:start position:0%
authority I don't have any answers I had
 

01:03:39.680 --> 01:03:41.630 align:start position:0%
authority I don't have any answers I had
never<01:03:39.839> read<01:03:40.079> the<01:03:40.319> enabling<01:03:40.760> legislation<01:03:41.200> till

01:03:41.630 --> 01:03:41.640 align:start position:0%
never read the enabling legislation till
 

01:03:41.640 --> 01:03:43.630 align:start position:0%
never read the enabling legislation till
I'm<01:03:41.760> sure<01:03:41.920> I<01:03:42.039> read<01:03:42.240> when<01:03:42.319> I<01:03:42.400> voted<01:03:42.640> on<01:03:42.799> it<01:03:43.039> but

01:03:43.630 --> 01:03:43.640 align:start position:0%
I'm sure I read when I voted on it but
 

01:03:43.640 --> 01:03:47.150 align:start position:0%
I'm sure I read when I voted on it but
yeah<01:03:44.440> was<01:03:44.880> a<01:03:45.079> Hugo<01:03:45.599> bill<01:03:46.599> from<01:03:46.799> what<01:03:46.920> I've<01:03:47.039> been

01:03:47.150 --> 01:03:47.160 align:start position:0%
yeah was a Hugo bill from what I've been
 

01:03:47.160 --> 01:03:50.549 align:start position:0%
yeah was a Hugo bill from what I've been
able<01:03:47.359> to<01:03:47.640> gather<01:03:48.640> but<01:03:48.960> um<01:03:49.960> I<01:03:50.039> was<01:03:50.200> one<01:03:50.319> of<01:03:50.400> the

01:03:50.549 --> 01:03:50.559 align:start position:0%
able to gather but um I was one of the
 

01:03:50.559 --> 01:03:52.390 align:start position:0%
able to gather but um I was one of the
people<01:03:50.760> that<01:03:50.880> lobed<01:03:51.279> for<01:03:51.480> it<01:03:51.720> back<01:03:51.839> in<01:03:51.960> the<01:03:52.160> day

01:03:52.390 --> 01:03:52.400 align:start position:0%
people that lobed for it back in the day
 

01:03:52.400 --> 01:03:53.269 align:start position:0%
people that lobed for it back in the day
but

01:03:53.269 --> 01:03:53.279 align:start position:0%
but
 

01:03:53.279 --> 01:03:56.950 align:start position:0%
but
um<01:03:54.440> it's<01:03:54.599> been<01:03:54.760> a<01:03:54.880> long<01:03:55.400> time<01:03:56.400> it<01:03:56.520> was<01:03:56.680> just<01:03:56.839> at

01:03:56.950 --> 01:03:56.960 align:start position:0%
um it's been a long time it was just at
 

01:03:56.960 --> 01:03:58.190 align:start position:0%
um it's been a long time it was just at
that<01:03:57.079> point<01:03:57.240> in<01:03:57.400> time<01:03:57.599> we<01:03:57.760> wanted<01:03:57.960> to<01:03:58.079> get

01:03:58.190 --> 01:03:58.200 align:start position:0%
that point in time we wanted to get
 

01:03:58.200 --> 01:04:00.390 align:start position:0%
that point in time we wanted to get
something<01:03:58.440> going<01:03:58.640> in<01:03:58.760> Virginia<01:03:59.359> regarding<01:03:59.799> so

01:04:00.390 --> 01:04:00.400 align:start position:0%
something going in Virginia regarding so
 

01:04:00.400 --> 01:04:02.470 align:start position:0%
something going in Virginia regarding so
we<01:04:00.640> kind<01:04:00.760> of<01:04:00.960> throwing<01:04:01.680> spting<01:04:02.119> on<01:04:02.160> the<01:04:02.279> while

01:04:02.470 --> 01:04:02.480 align:start position:0%
we kind of throwing spting on the while
 

01:04:02.480 --> 01:04:04.670 align:start position:0%
we kind of throwing spting on the while
see<01:04:02.799> see<01:04:03.000> what<01:04:03.119> might<01:04:03.319> stick<01:04:03.960> yeah<01:04:04.400> and<01:04:04.520> we

01:04:04.670 --> 01:04:04.680 align:start position:0%
see see what might stick yeah and we
 

01:04:04.680 --> 01:04:07.829 align:start position:0%
see see what might stick yeah and we
thought<01:04:04.920> having<01:04:05.119> an<01:04:05.279> authority<01:04:05.960> um<01:04:06.960> like<01:04:07.279> this

01:04:07.829 --> 01:04:07.839 align:start position:0%
thought having an authority um like this
 

01:04:07.839 --> 01:04:09.670 align:start position:0%
thought having an authority um like this
would<01:04:08.079> would<01:04:08.240> help<01:04:08.559> that<01:04:08.839> but<01:04:09.160> you<01:04:09.279> know<01:04:09.559> at

01:04:09.670 --> 01:04:09.680 align:start position:0%
would would help that but you know at
 

01:04:09.680 --> 01:04:11.069 align:start position:0%
would would help that but you know at
the<01:04:09.799> same<01:04:10.000> time<01:04:10.240> we<01:04:10.319> were<01:04:10.440> also<01:04:10.640> working<01:04:10.920> with

01:04:11.069 --> 01:04:11.079 align:start position:0%
the same time we were also working with
 

01:04:11.079 --> 01:04:14.390 align:start position:0%
the same time we were also working with
the<01:04:11.400> minion<01:04:11.720> to<01:04:11.960> get<01:04:12.440> the<01:04:13.440> 500<01:04:13.920> megawatt<01:04:14.319> and

01:04:14.390 --> 01:04:14.400 align:start position:0%
the minion to get the 500 megawatt and
 

01:04:14.400 --> 01:04:18.589 align:start position:0%
the minion to get the 500 megawatt and
then<01:04:14.520> the<01:04:14.720> 5<01:04:14.920> gwatt<01:04:15.799> everything<01:04:16.000> else<01:04:16.279> P<01:04:16.799> so<01:04:17.799> um

01:04:18.589 --> 01:04:18.599 align:start position:0%
then the 5 gwatt everything else P so um
 

01:04:18.599 --> 01:04:21.069 align:start position:0%
then the 5 gwatt everything else P so um
anyway<01:04:18.960> here<01:04:19.119> we<01:04:19.279> are<01:04:20.119> yeah<01:04:20.319> and<01:04:20.480> maybe<01:04:20.720> in<01:04:20.799> a

01:04:21.069 --> 01:04:21.079 align:start position:0%
anyway here we are yeah and maybe in a
 

01:04:21.079 --> 01:04:22.910 align:start position:0%
anyway here we are yeah and maybe in a
pre-<01:04:21.359> clean<01:04:21.640> economy<01:04:22.000> act<01:04:22.279> World<01:04:22.559> maybe<01:04:22.799> there

01:04:22.910 --> 01:04:22.920 align:start position:0%
pre- clean economy act World maybe there
 

01:04:22.920 --> 01:04:25.549 align:start position:0%
pre- clean economy act World maybe there
was<01:04:23.359> different<01:04:23.599> vision<01:04:23.839> for<01:04:23.920> how<01:04:24.000> you

01:04:25.549 --> 01:04:25.559 align:start position:0%
was different vision for how you
 

01:04:25.559 --> 01:04:28.150 align:start position:0%
was different vision for how you
you<01:04:25.640> don't<01:04:25.839> need<01:04:26.480> Authority<01:04:27.480> yeah<01:04:27.920> I'm<01:04:28.039> not

01:04:28.150 --> 01:04:28.160 align:start position:0%
you don't need Authority yeah I'm not
 

01:04:28.160 --> 01:04:29.789 align:start position:0%
you don't need Authority yeah I'm not
saying<01:04:28.319> we<01:04:28.400> don't<01:04:28.559> need<01:04:28.720> it<01:04:29.400> I'm<01:04:29.480> not<01:04:29.599> saying

01:04:29.789 --> 01:04:29.799 align:start position:0%
saying we don't need it I'm not saying
 

01:04:29.799 --> 01:04:31.430 align:start position:0%
saying we don't need it I'm not saying
that<01:04:29.920> at<01:04:30.000> all<01:04:30.160> I'm<01:04:30.279> just<01:04:30.400> saying<01:04:31.079> at<01:04:31.240> that

01:04:31.430 --> 01:04:31.440 align:start position:0%
that at all I'm just saying at that
 

01:04:31.440 --> 01:04:33.710 align:start position:0%
that at all I'm just saying at that
point<01:04:31.599> in<01:04:31.839> time<01:04:32.760> I<01:04:32.839> think<01:04:33.039> it<01:04:33.119> was<01:04:33.319> developed

01:04:33.710 --> 01:04:33.720 align:start position:0%
point in time I think it was developed
 

01:04:33.720 --> 01:04:36.670 align:start position:0%
point in time I think it was developed
for<01:04:33.880> something<01:04:34.240> different<01:04:35.200> we're<01:04:35.440> here<01:04:35.720> now

01:04:36.670 --> 01:04:36.680 align:start position:0%
for something different we're here now
 

01:04:36.680 --> 01:04:40.910 align:start position:0%
for something different we're here now
yeah<01:04:37.359> try<01:04:37.640> to<01:04:38.640> look<01:04:38.839> at<01:04:39.279> um<01:04:39.760> what<01:04:39.880> we<01:04:40.000> have<01:04:40.240> here

01:04:40.910 --> 01:04:40.920 align:start position:0%
yeah try to look at um what we have here
 

01:04:40.920 --> 01:04:42.950 align:start position:0%
yeah try to look at um what we have here
and<01:04:41.200> and<01:04:41.480> and<01:04:41.599> do<01:04:41.799> what<01:04:41.920> we<01:04:42.079> can<01:04:42.440> I<01:04:42.720> you<01:04:42.839> know

01:04:42.950 --> 01:04:42.960 align:start position:0%
and and and do what we can I you know
 

01:04:42.960 --> 01:04:44.390 align:start position:0%
and and and do what we can I you know
I've<01:04:43.119> talked<01:04:43.319> about<01:04:43.480> this<01:04:43.680> before<01:04:43.920> I<01:04:44.000> know

01:04:44.390 --> 01:04:44.400 align:start position:0%
I've talked about this before I know
 

01:04:44.400 --> 01:04:46.950 align:start position:0%
I've talked about this before I know
focus<01:04:44.720> a<01:04:44.799> lot<01:04:44.920> on<01:04:45.079> f<01:04:45.400> scale<01:04:45.760> solar<01:04:46.599> there's<01:04:46.839> so

01:04:46.950 --> 01:04:46.960 align:start position:0%
focus a lot on f scale solar there's so
 

01:04:46.960 --> 01:04:48.549 align:start position:0%
focus a lot on f scale solar there's so
many<01:04:47.160> working<01:04:47.480> groups<01:04:47.799> working<01:04:48.039> on<01:04:48.200> util

01:04:48.549 --> 01:04:48.559 align:start position:0%
many working groups working on util
 

01:04:48.559 --> 01:04:49.470 align:start position:0%
many working groups working on util
scale

01:04:49.470 --> 01:04:49.480 align:start position:0%
scale
 

01:04:49.480 --> 01:04:51.950 align:start position:0%
scale
solar<01:04:50.480> um<01:04:50.920> I<01:04:51.079> always<01:04:51.319> kind<01:04:51.440> of<01:04:51.559> thought<01:04:51.799> that

01:04:51.950 --> 01:04:51.960 align:start position:0%
solar um I always kind of thought that
 

01:04:51.960 --> 01:04:54.589 align:start position:0%
solar um I always kind of thought that
maybe<01:04:52.200> this<01:04:52.359> group<01:04:52.599> should<01:04:52.799> focus<01:04:53.119> on<01:04:53.760> uh<01:04:54.400> know

01:04:54.589 --> 01:04:54.599 align:start position:0%
maybe this group should focus on uh know
 

01:04:54.599 --> 01:04:57.630 align:start position:0%
maybe this group should focus on uh know
behind<01:04:54.880> the<01:04:55.000> meter<01:04:55.520> installations

01:04:57.630 --> 01:04:57.640 align:start position:0%
behind the meter installations
 

01:04:57.640 --> 01:05:01.470 align:start position:0%
behind the meter installations
but<01:04:58.640> that's<01:04:58.799> just<01:04:59.000> my<01:04:59.559> thought<01:05:00.559> well<01:05:00.799> cly

01:05:01.470 --> 01:05:01.480 align:start position:0%
but that's just my thought well cly
 

01:05:01.480 --> 01:05:05.789 align:start position:0%
but that's just my thought well cly
right<01:05:01.680> now<01:05:02.680> the<01:05:02.839> SEC<01:05:03.480> work<01:05:03.799> group<01:05:04.200> on<01:05:05.200> the

01:05:05.789 --> 01:05:05.799 align:start position:0%
right now the SEC work group on the
 

01:05:05.799 --> 01:05:09.150 align:start position:0%
right now the SEC work group on the
resources<01:05:06.520> is<01:05:06.680> meeting<01:05:07.279> was<01:05:07.520> BR

01:05:09.150 --> 01:05:09.160 align:start position:0%
resources is meeting was BR
 

01:05:09.160 --> 01:05:11.549 align:start position:0%
resources is meeting was BR
yeah<01:05:10.160> all<01:05:10.319> includes<01:05:10.680> all<01:05:10.839> the<01:05:10.960> above<01:05:11.400> right

01:05:11.549 --> 01:05:11.559 align:start position:0%
yeah all includes all the above right
 

01:05:11.559 --> 01:05:14.829 align:start position:0%
yeah all includes all the above right
how<01:05:12.520> go<01:05:12.680> in<01:05:13.279> and<01:05:13.400> I<01:05:13.520> think<01:05:13.760> initially<01:05:14.599> that

01:05:14.829 --> 01:05:14.839 align:start position:0%
how go in and I think initially that
 

01:05:14.839 --> 01:05:19.349 align:start position:0%
how go in and I think initially that
then<01:05:15.319> the<01:05:16.240> a<01:05:16.319> lot<01:05:16.440> of<01:05:16.559> the<01:05:16.640> intent<01:05:17.079> was<01:05:17.599> for<01:05:18.599> um

01:05:19.349 --> 01:05:19.359 align:start position:0%
then the a lot of the intent was for um
 

01:05:19.359 --> 01:05:21.630 align:start position:0%
then the a lot of the intent was for um
with<01:05:19.520> the<01:05:19.640> authority<01:05:20.039> to<01:05:20.240> focus<01:05:20.599> on<01:05:21.200> behind

01:05:21.630 --> 01:05:21.640 align:start position:0%
with the authority to focus on behind
 

01:05:21.640 --> 01:05:24.950 align:start position:0%
with the authority to focus on behind
met<01:05:22.119> meter<01:05:23.079> installation

01:05:24.950 --> 01:05:24.960 align:start position:0%
met meter installation
 

01:05:24.960 --> 01:05:27.990 align:start position:0%
met meter installation
but<01:05:25.480> uh<01:05:26.279> again<01:05:26.799> the<01:05:27.000> market<01:05:27.319> of<01:05:27.440> Virginia<01:05:27.839> has

01:05:27.990 --> 01:05:28.000 align:start position:0%
but uh again the market of Virginia has
 

01:05:28.000 --> 01:05:31.549 align:start position:0%
but uh again the market of Virginia has
become<01:05:28.279> something<01:05:28.640> different<01:05:29.440> yeah<01:05:30.440> so<01:05:30.960> great

01:05:31.549 --> 01:05:31.559 align:start position:0%
become something different yeah so great
 

01:05:31.559 --> 01:05:34.309 align:start position:0%
become something different yeah so great
so<01:05:32.160> to<01:05:32.400> that<01:05:32.680> point<01:05:33.039> that<01:05:33.200> you<01:05:33.319> bring<01:05:33.599> up<01:05:34.039> right

01:05:34.309 --> 01:05:34.319 align:start position:0%
so to that point that you bring up right
 

01:05:34.319 --> 01:05:37.910 align:start position:0%
so to that point that you bring up right
so<01:05:35.000> you're<01:05:35.279> right<01:05:35.559> we<01:05:35.680> do<01:05:35.960> have<01:05:36.440> broad<01:05:36.920> po

01:05:37.910 --> 01:05:37.920 align:start position:0%
so you're right we do have broad po
 

01:05:37.920 --> 01:05:41.630 align:start position:0%
so you're right we do have broad po
right<01:05:38.079> we<01:05:38.200> have<01:05:38.359> no<01:05:38.799> budget<01:05:39.799> no<01:05:40.279> Forum<01:05:41.279> well

01:05:41.630 --> 01:05:41.640 align:start position:0%
right we have no budget no Forum well
 

01:05:41.640 --> 01:05:43.789 align:start position:0%
right we have no budget no Forum well
right

01:05:43.789 --> 01:05:43.799 align:start position:0%
right
 

01:05:43.799 --> 01:05:47.150 align:start position:0%
right
now<01:05:44.799> not<01:05:44.920> worry<01:05:45.160> about<01:05:45.440> that

01:05:47.150 --> 01:05:47.160 align:start position:0%
now not worry about that
 

01:05:47.160 --> 01:05:50.470 align:start position:0%
now not worry about that
but<01:05:48.160> one<01:05:48.279> of<01:05:48.359> the<01:05:48.520> things<01:05:48.720> in<01:05:49.000> Ken<01:05:49.799> by<01:05:50.000> saying

01:05:50.470 --> 01:05:50.480 align:start position:0%
but one of the things in Ken by saying
 

01:05:50.480 --> 01:05:52.470 align:start position:0%
but one of the things in Ken by saying
you<01:05:50.599> know<01:05:50.760> we<01:05:50.880> haven't<01:05:51.119> made<01:05:51.480> recommendations

01:05:52.470 --> 01:05:52.480 align:start position:0%
you know we haven't made recommendations
 

01:05:52.480 --> 01:05:55.269 align:start position:0%
you know we haven't made recommendations
I<01:05:52.559> mean<01:05:52.799> clearly<01:05:53.480> there<01:05:53.599> have<01:05:53.760> been<01:05:54.279> some

01:05:55.269 --> 01:05:55.279 align:start position:0%
I mean clearly there have been some
 

01:05:55.279 --> 01:05:59.750 align:start position:0%
I mean clearly there have been some
opportunities<01:05:56.039> for<01:05:56.319> us<01:05:56.920> to<01:05:57.920> either<01:05:58.839> call<01:05:59.079> in

01:05:59.750 --> 01:05:59.760 align:start position:0%
opportunities for us to either call in
 

01:05:59.760 --> 01:06:02.510 align:start position:0%
opportunities for us to either call in
Specialists<01:06:00.760> and<01:06:01.400> get

01:06:02.510 --> 01:06:02.520 align:start position:0%
Specialists and get
 

01:06:02.520 --> 01:06:06.029 align:start position:0%
Specialists and get
invis<01:06:03.520> um<01:06:04.440> there<01:06:04.599> are<01:06:05.039> the<01:06:05.279> disconnects<01:06:05.880> that

01:06:06.029 --> 01:06:06.039 align:start position:0%
invis um there are the disconnects that
 

01:06:06.039 --> 01:06:07.670 align:start position:0%
invis um there are the disconnects that
we<01:06:06.119> see<01:06:06.359> at<01:06:06.480> the<01:06:06.640> state<01:06:06.880> level<01:06:07.240> versus<01:06:07.559> the

01:06:07.670 --> 01:06:07.680 align:start position:0%
we see at the state level versus the
 

01:06:07.680 --> 01:06:11.150 align:start position:0%
we see at the state level versus the
federal<01:06:08.119> level<01:06:08.799> and<01:06:09.039> those<01:06:09.240> are

01:06:11.150 --> 01:06:11.160 align:start position:0%
federal level and those are
 

01:06:11.160 --> 01:06:13.789 align:start position:0%
federal level and those are
creating<01:06:12.160> basically<01:06:12.599> impediments<01:06:13.240> for<01:06:13.640> for

01:06:13.789 --> 01:06:13.799 align:start position:0%
creating basically impediments for for
 

01:06:13.799 --> 01:06:15.510 align:start position:0%
creating basically impediments for for
forward<01:06:14.279> progress<01:06:14.640> and<01:06:14.799> some<01:06:15.000> of<01:06:15.119> the<01:06:15.279> things

01:06:15.510 --> 01:06:15.520 align:start position:0%
forward progress and some of the things
 

01:06:15.520 --> 01:06:17.990 align:start position:0%
forward progress and some of the things
of<01:06:15.760> which<01:06:16.039> we<01:06:16.279> have<01:06:16.599> this<01:06:16.920> the<01:06:17.079> right<01:06:17.240> to<01:06:17.400> say

01:06:17.990 --> 01:06:18.000 align:start position:0%
of which we have this the right to say
 

01:06:18.000 --> 01:06:22.269 align:start position:0%
of which we have this the right to say
something<01:06:19.039> so<01:06:20.200> perhaps<01:06:21.200> this<01:06:21.400> is<01:06:21.640> our

01:06:22.269 --> 01:06:22.279 align:start position:0%
something so perhaps this is our
 

01:06:22.279 --> 01:06:24.870 align:start position:0%
something so perhaps this is our
opportunity<01:06:22.760> in<01:06:22.880> those<01:06:23.079> 15<01:06:23.480> pages<01:06:23.799> to<01:06:24.079> to

01:06:24.870 --> 01:06:24.880 align:start position:0%
opportunity in those 15 pages to to
 

01:06:24.880 --> 01:06:26.349 align:start position:0%
opportunity in those 15 pages to to
address<01:06:25.319> one<01:06:25.480> of<01:06:25.640> the<01:06:25.839> problems<01:06:26.119> that<01:06:26.240> we're

01:06:26.349 --> 01:06:26.359 align:start position:0%
address one of the problems that we're
 

01:06:26.359 --> 01:06:27.950 align:start position:0%
address one of the problems that we're
seeing<01:06:26.599> or<01:06:26.799> several<01:06:27.079> of<01:06:27.200> the<01:06:27.400> problems<01:06:27.799> and

01:06:27.950 --> 01:06:27.960 align:start position:0%
seeing or several of the problems and
 

01:06:27.960 --> 01:06:29.870 align:start position:0%
seeing or several of the problems and
come<01:06:28.160> up<01:06:28.359> with<01:06:28.559> Rec<01:06:29.079> strong

01:06:29.870 --> 01:06:29.880 align:start position:0%
come up with Rec strong
 

01:06:29.880 --> 01:06:32.670 align:start position:0%
come up with Rec strong
recommendations<01:06:30.880> whether<01:06:31.160> they're<01:06:31.640> accepted

01:06:32.670 --> 01:06:32.680 align:start position:0%
recommendations whether they're accepted
 

01:06:32.680 --> 01:06:35.269 align:start position:0%
recommendations whether they're accepted
by<01:06:33.680> leadership<01:06:34.279> State

01:06:35.269 --> 01:06:35.279 align:start position:0%
by leadership State
 

01:06:35.279 --> 01:06:36.789 align:start position:0%
by leadership State
leadership

01:06:36.789 --> 01:06:36.799 align:start position:0%
leadership
 

01:06:36.799 --> 01:06:40.029 align:start position:0%
leadership
is<01:06:37.799> you<01:06:37.920> know<01:06:38.119> to<01:06:38.279> be<01:06:38.599> determined<01:06:39.319> but<01:06:39.599> of

01:06:40.029 --> 01:06:40.039 align:start position:0%
is you know to be determined but of
 

01:06:40.039 --> 01:06:43.069 align:start position:0%
is you know to be determined but of
course<01:06:41.039> I<01:06:41.160> think<01:06:41.400> that's<01:06:41.680> what<01:06:42.440> the<01:06:42.599> authority

01:06:43.069 --> 01:06:43.079 align:start position:0%
course I think that's what the authority
 

01:06:43.079 --> 01:06:47.190 align:start position:0%
course I think that's what the authority
could<01:06:43.520> do<01:06:44.119> and<01:06:44.799> and<01:06:45.799> we<01:06:45.960> would<01:06:46.160> have<01:06:46.279> a<01:06:46.440> basis<01:06:46.880> a

01:06:47.190 --> 01:06:47.200 align:start position:0%
could do and and we would have a basis a
 

01:06:47.200 --> 01:06:49.750 align:start position:0%
could do and and we would have a basis a
path<01:06:47.839> and<01:06:48.039> that's<01:06:48.359> often<01:06:49.359> all<01:06:49.559> that

01:06:49.750 --> 01:06:49.760 align:start position:0%
path and that's often all that
 

01:06:49.760 --> 01:06:52.670 align:start position:0%
path and that's often all that
leadership<01:06:50.400> needs<01:06:50.839> is<01:06:51.039> a<01:06:51.400> potential<01:06:52.160> path<01:06:52.400> for

01:06:52.670 --> 01:06:52.680 align:start position:0%
leadership needs is a potential path for
 

01:06:52.680 --> 01:06:56.069 align:start position:0%
leadership needs is a potential path for
people<01:06:53.000> to<01:06:53.359> look<01:06:53.599> at<01:06:54.079> and<01:06:54.839> then<01:06:55.160> iterate<01:06:55.760> to

01:06:56.069 --> 01:06:56.079 align:start position:0%
people to look at and then iterate to
 

01:06:56.079 --> 01:06:59.630 align:start position:0%
people to look at and then iterate to
reality<01:06:56.960> how<01:06:57.119> do<01:06:57.279> we<01:06:57.480> actually<01:06:57.760> impl<01:06:58.640> things

01:06:59.630 --> 01:06:59.640 align:start position:0%
reality how do we actually impl things
 

01:06:59.640 --> 01:07:03.269 align:start position:0%
reality how do we actually impl things
so<01:06:59.839> I<01:06:59.960> think<01:07:00.240> as<01:07:00.359> a<01:07:00.559> starting<01:07:00.960> point<01:07:01.359> Skylar<01:07:02.279> I

01:07:03.269 --> 01:07:03.279 align:start position:0%
so I think as a starting point Skylar I
 

01:07:03.279 --> 01:07:04.870 align:start position:0%
so I think as a starting point Skylar I
I<01:07:03.400> think<01:07:03.599> if<01:07:03.760> we<01:07:03.880> could<01:07:04.079> do<01:07:04.279> something<01:07:04.640> like

01:07:04.870 --> 01:07:04.880 align:start position:0%
I think if we could do something like
 

01:07:04.880 --> 01:07:07.630 align:start position:0%
I think if we could do something like
that<01:07:05.119> that<01:07:05.279> could<01:07:05.480> be<01:07:06.480> useful<01:07:07.160> and<01:07:07.359> and<01:07:07.480> not

01:07:07.630 --> 01:07:07.640 align:start position:0%
that that could be useful and and not
 

01:07:07.640 --> 01:07:09.910 align:start position:0%
that that could be useful and and not
necessarily<01:07:08.079> require<01:07:08.359> a<01:07:08.520> budget<01:07:08.880> per<01:07:09.079> se<01:07:09.640> but

01:07:09.910 --> 01:07:09.920 align:start position:0%
necessarily require a budget per se but
 

01:07:09.920 --> 01:07:12.470 align:start position:0%
necessarily require a budget per se but
would<01:07:10.160> require<01:07:10.680> folks<01:07:11.000> to<01:07:11.200> think<01:07:11.480> about<01:07:12.240> what

01:07:12.470 --> 01:07:12.480 align:start position:0%
would require folks to think about what
 

01:07:12.480 --> 01:07:14.670 align:start position:0%
would require folks to think about what
budgets<01:07:12.880> would<01:07:13.039> be<01:07:13.319> required<01:07:13.920> if<01:07:14.079> we<01:07:14.200> were<01:07:14.400> to

01:07:14.670 --> 01:07:14.680 align:start position:0%
budgets would be required if we were to
 

01:07:14.680 --> 01:07:17.069 align:start position:0%
budgets would be required if we were to
implement<01:07:15.599> this<01:07:15.880> type<01:07:16.079> of<01:07:16.240> road<01:07:16.520> map<01:07:16.799> which<01:07:16.920> is

01:07:17.069 --> 01:07:17.079 align:start position:0%
implement this type of road map which is
 

01:07:17.079 --> 01:07:19.870 align:start position:0%
implement this type of road map which is
something<01:07:17.640> that<01:07:18.640> and<01:07:18.760> you<01:07:18.880> were<01:07:19.279> appointed<01:07:19.760> as

01:07:19.870 --> 01:07:19.880 align:start position:0%
something that and you were appointed as
 

01:07:19.880 --> 01:07:21.670 align:start position:0%
something that and you were appointed as
an<01:07:20.119> independent

01:07:21.670 --> 01:07:21.680 align:start position:0%
an independent
 

01:07:21.680 --> 01:07:24.069 align:start position:0%
an independent
Authority<01:07:22.680> make<01:07:22.920> the<01:07:23.119> recommendations

01:07:24.069 --> 01:07:24.079 align:start position:0%
Authority make the recommendations
 

01:07:24.079 --> 01:07:25.230 align:start position:0%
Authority make the recommendations
regardless<01:07:24.559> of<01:07:24.720> what<01:07:24.839> you<01:07:24.960> think<01:07:25.119> they're

01:07:25.230 --> 01:07:25.240 align:start position:0%
regardless of what you think they're
 

01:07:25.240 --> 01:07:27.269 align:start position:0%
regardless of what you think they're
going<01:07:25.359> to<01:07:25.480> think<01:07:25.680> about<01:07:25.960> them<01:07:26.640> that's<01:07:27.039> that's

01:07:27.269 --> 01:07:27.279 align:start position:0%
going to think about them that's that's
 

01:07:27.279 --> 01:07:29.309 align:start position:0%
going to think about them that's that's
my<01:07:27.480> advice<01:07:28.079> they<01:07:28.240> might<01:07:28.440> not<01:07:28.640> like<01:07:28.880> them<01:07:29.160> but

01:07:29.309 --> 01:07:29.319 align:start position:0%
my advice they might not like them but
 

01:07:29.319 --> 01:07:32.430 align:start position:0%
my advice they might not like them but
if<01:07:29.520> you<01:07:30.200> as<01:07:30.319> a<01:07:30.680> group<01:07:31.000> feel<01:07:31.400> these<01:07:31.559> are

01:07:32.430 --> 01:07:32.440 align:start position:0%
if you as a group feel these are
 

01:07:32.440 --> 01:07:34.109 align:start position:0%
if you as a group feel these are
important<01:07:32.960> things<01:07:33.240> that<01:07:33.359> need<01:07:33.559> to<01:07:33.720> take<01:07:33.920> place

01:07:34.109 --> 01:07:34.119 align:start position:0%
important things that need to take place
 

01:07:34.119 --> 01:07:37.430 align:start position:0%
important things that need to take place
to<01:07:34.279> move<01:07:34.520> the<01:07:34.640> market<01:07:34.960> forward<01:07:35.720> and<01:07:35.880> make<01:07:36.039> the

01:07:37.430 --> 01:07:37.440 align:start position:0%
to move the market forward and make the
 

01:07:37.440 --> 01:07:40.470 align:start position:0%
to move the market forward and make the
recommendations<01:07:38.440> I<01:07:38.559> see<01:07:39.119> several<01:07:40.119> right<01:07:40.279> from

01:07:40.470 --> 01:07:40.480 align:start position:0%
recommendations I see several right from
 

01:07:40.480 --> 01:07:42.390 align:start position:0%
recommendations I see several right from
this<01:07:40.680> presentation<01:07:41.319> we<01:07:41.440> just<01:07:41.559> saw<01:07:42.160> what<01:07:42.279> we

01:07:42.390 --> 01:07:42.400 align:start position:0%
this presentation we just saw what we
 

01:07:42.400 --> 01:07:45.190 align:start position:0%
this presentation we just saw what we
can<01:07:42.599> put<01:07:42.799> forward<01:07:43.480> to<01:07:43.839> add<01:07:44.119> just<01:07:44.359> on<01:07:44.680> the<01:07:45.039> what

01:07:45.190 --> 01:07:45.200 align:start position:0%
can put forward to add just on the what
 

01:07:45.200 --> 01:07:46.510 align:start position:0%
can put forward to add just on the what
have<01:07:45.319> we<01:07:45.440> done<01:07:45.599> in<01:07:45.720> the<01:07:45.880> past<01:07:46.119> I<01:07:46.200> want<01:07:46.319> to

01:07:46.510 --> 01:07:46.520 align:start position:0%
have we done in the past I want to
 

01:07:46.520 --> 01:07:51.390 align:start position:0%
have we done in the past I want to
remind<01:07:47.240> the<01:07:47.559> group<01:07:47.960> that<01:07:48.200> we<01:07:48.799> have<01:07:49.799> executed<01:07:50.559> a

01:07:51.390 --> 01:07:51.400 align:start position:0%
remind the group that we have executed a
 

01:07:51.400 --> 01:07:55.349 align:start position:0%
remind the group that we have executed a
storage<01:07:52.119> in<01:07:52.319> Virginia<01:07:52.920> study<01:07:54.359> that<01:07:54.520> was<01:07:54.760> in<01:07:55.279> I

01:07:55.349 --> 01:07:55.359 align:start position:0%
storage in Virginia study that was in I
 

01:07:55.359 --> 01:07:59.109 align:start position:0%
storage in Virginia study that was in I
want<01:07:55.480> to<01:07:55.599> say<01:07:56.119> 2018<01:07:57.119> I<01:07:57.240> believe<01:07:57.599> yeah<01:07:58.319> and<01:07:59.000> I

01:07:59.109 --> 01:07:59.119 align:start position:0%
want to say 2018 I believe yeah and I
 

01:07:59.119 --> 01:08:02.990 align:start position:0%
want to say 2018 I believe yeah and I
forget<01:07:59.599> how<01:07:59.960> we<01:08:00.799> received<01:08:01.079> funds<01:08:01.880> to<01:08:02.480> execute

01:08:02.990 --> 01:08:03.000 align:start position:0%
forget how we received funds to execute
 

01:08:03.000 --> 01:08:05.549 align:start position:0%
forget how we received funds to execute
that<01:08:03.880> we<01:08:04.079> paid<01:08:04.319> for<01:08:04.480> it<01:08:04.960> we<01:08:05.160> paid<01:08:05.440> the

01:08:05.549 --> 01:08:05.559 align:start position:0%
that we paid for it we paid the
 

01:08:05.559 --> 01:08:09.390 align:start position:0%
that we paid for it we paid the
authority<01:08:06.440> no<01:08:07.440> the<01:08:08.000> okay<01:08:08.920> was<01:08:09.000> a<01:08:09.119> budget

01:08:09.390 --> 01:08:09.400 align:start position:0%
authority no the okay was a budget
 

01:08:09.400 --> 01:08:12.069 align:start position:0%
authority no the okay was a budget
amendment<01:08:09.880> too<01:08:10.200> right<01:08:10.480> was<01:08:11.480> you<01:08:11.559> know<01:08:11.720> I<01:08:11.839> can't

01:08:12.069 --> 01:08:12.079 align:start position:0%
amendment too right was you know I can't
 

01:08:12.079 --> 01:08:13.670 align:start position:0%
amendment too right was you know I can't
remember<01:08:12.480> whether<01:08:12.720> that<01:08:12.839> was<01:08:13.039> State<01:08:13.279> funds<01:08:13.559> or

01:08:13.670 --> 01:08:13.680 align:start position:0%
remember whether that was State funds or
 

01:08:13.680 --> 01:08:15.109 align:start position:0%
remember whether that was State funds or
whether<01:08:13.880> we<01:08:14.000> used<01:08:14.200> federal<01:08:14.520> funds<01:08:14.799> for<01:08:14.960> that

01:08:15.109 --> 01:08:15.119 align:start position:0%
whether we used federal funds for that
 

01:08:15.119 --> 01:08:16.430 align:start position:0%
whether we used federal funds for that
to<01:08:15.240> be<01:08:15.359> honest<01:08:15.599> with<01:08:15.720> that<01:08:15.880> I<01:08:15.960> have<01:08:16.080> to<01:08:16.159> go<01:08:16.319> back

01:08:16.430 --> 01:08:16.440 align:start position:0%
to be honest with that I have to go back
 

01:08:16.440 --> 01:08:19.590 align:start position:0%
to be honest with that I have to go back
and<01:08:16.640> look<01:08:17.600> and<01:08:17.759> I<01:08:18.040> I<01:08:18.159> believe<01:08:18.839> that<01:08:19.000> was<01:08:19.279> I<01:08:19.359> mean

01:08:19.590 --> 01:08:19.600 align:start position:0%
and look and I I believe that was I mean
 

01:08:19.600 --> 01:08:21.030 align:start position:0%
and look and I I believe that was I mean
the<01:08:19.759> recommendation<01:08:20.319> coming<01:08:20.520> out<01:08:20.679> of<01:08:20.839> that

01:08:21.030 --> 01:08:21.040 align:start position:0%
the recommendation coming out of that
 

01:08:21.040 --> 01:08:24.630 align:start position:0%
the recommendation coming out of that
report<01:08:21.440> was<01:08:21.759> some<01:08:22.600> 3,000<01:08:23.159> to<01:08:23.319> 5,000<01:08:24.159> megawatts

01:08:24.630 --> 01:08:24.640 align:start position:0%
report was some 3,000 to 5,000 megawatts
 

01:08:24.640 --> 01:08:26.229 align:start position:0%
report was some 3,000 to 5,000 megawatts
of<01:08:24.799> energy<01:08:25.080> storage<01:08:25.440> in<01:08:25.560> the<01:08:25.679> public<01:08:25.960> interest

01:08:26.229 --> 01:08:26.239 align:start position:0%
of energy storage in the public interest
 

01:08:26.239 --> 01:08:29.669 align:start position:0%
of energy storage in the public interest
of<01:08:26.400> Virginia<01:08:26.920> Which<01:08:27.839> then<01:08:28.839> that<01:08:29.319> next

01:08:29.669 --> 01:08:29.679 align:start position:0%
of Virginia Which then that next
 

01:08:29.679 --> 01:08:32.390 align:start position:0%
of Virginia Which then that next
legislative<01:08:30.359> session<01:08:31.319> well<01:08:31.480> actually<01:08:31.759> that

01:08:32.390 --> 01:08:32.400 align:start position:0%
legislative session well actually that
 

01:08:32.400 --> 01:08:35.829 align:start position:0%
legislative session well actually that
they<01:08:32.520> only<01:08:32.719> shot<01:08:33.279> for<01:08:34.279> maybe<01:08:34.560> less<01:08:34.880> thousand

01:08:35.829 --> 01:08:35.839 align:start position:0%
they only shot for maybe less thousand
 

01:08:35.839 --> 01:08:38.110 align:start position:0%
they only shot for maybe less thousand
okay<01:08:36.080> and<01:08:36.279> then<01:08:37.199> in<01:08:37.359> the

01:08:38.110 --> 01:08:38.120 align:start position:0%
okay and then in the
 

01:08:38.120 --> 01:08:40.789 align:start position:0%
okay and then in the
legislation<01:08:39.120> they<01:08:40.000> they<01:08:40.199> exceed<01:08:40.600> far

01:08:40.789 --> 01:08:40.799 align:start position:0%
legislation they they exceed far
 

01:08:40.799 --> 01:08:42.110 align:start position:0%
legislation they they exceed far
exceeded<01:08:41.239> that<01:08:41.440> they<01:08:41.520> far<01:08:41.640> exceeded<01:08:42.000> but

01:08:42.110 --> 01:08:42.120 align:start position:0%
exceeded that they far exceeded but
 

01:08:42.120 --> 01:08:43.430 align:start position:0%
exceeded that they far exceeded but
there<01:08:42.199> were<01:08:42.359> other<01:08:42.920> lots<01:08:43.120> of<01:08:43.239> other

01:08:43.430 --> 01:08:43.440 align:start position:0%
there were other lots of other
 

01:08:43.440 --> 01:08:45.430 align:start position:0%
there were other lots of other
recommendations<01:08:44.040> in<01:08:44.199> there<01:08:44.440> also<01:08:44.920> that<01:08:45.239> may

01:08:45.430 --> 01:08:45.440 align:start position:0%
recommendations in there also that may
 

01:08:45.440 --> 01:08:47.510 align:start position:0%
recommendations in there also that may
or<01:08:45.640> may<01:08:45.799> not<01:08:46.040> still<01:08:46.400> still<01:08:46.600> be<01:08:46.839> valid<01:08:47.279> I<01:08:47.319> don't

01:08:47.510 --> 01:08:47.520 align:start position:0%
or may not still still be valid I don't
 

01:08:47.520 --> 01:08:49.070 align:start position:0%
or may not still still be valid I don't
know<01:08:47.839> you<01:08:47.960> know<01:08:48.080> the<01:08:48.159> world<01:08:48.359> has<01:08:48.520> changed<01:08:48.880> so

01:08:49.070 --> 01:08:49.080 align:start position:0%
know you know the world has changed so
 

01:08:49.080 --> 01:08:51.749 align:start position:0%
know you know the world has changed so
much<01:08:49.480> in<01:08:49.600> the<01:08:49.759> last<01:08:49.960> four<01:08:50.239> years<01:08:50.719> yeah<01:08:51.359> yeah

01:08:51.749 --> 01:08:51.759 align:start position:0%
much in the last four years yeah yeah
 

01:08:51.759 --> 01:08:54.470 align:start position:0%
much in the last four years yeah yeah
but<01:08:52.400> go<01:08:52.560> back<01:08:52.679> to<01:08:52.759> the<01:08:52.839> Strat<01:08:53.239> and<01:08:53.400> Report<01:08:54.239> see

01:08:54.470 --> 01:08:54.480 align:start position:0%
but go back to the Strat and Report see
 

01:08:54.480 --> 01:08:56.189 align:start position:0%
but go back to the Strat and Report see
what<01:08:54.640> they<01:08:54.880> got<01:08:55.120> right<01:08:55.719> yeah<01:08:55.880> remind

01:08:56.189 --> 01:08:56.199 align:start position:0%
what they got right yeah remind
 

01:08:56.199 --> 01:08:58.709 align:start position:0%
what they got right yeah remind
ourselves

01:08:58.709 --> 01:08:58.719 align:start position:0%
ourselves
 

01:08:58.719 --> 01:09:01.950 align:start position:0%
ourselves
yeah<01:08:59.719> so<01:09:00.000> we<01:09:00.159> will

01:09:01.950 --> 01:09:01.960 align:start position:0%
yeah so we will
 

01:09:01.960 --> 01:09:04.990 align:start position:0%
yeah so we will
have<01:09:02.960> can<01:09:03.279> please<01:09:03.719> chime<01:09:04.040> in<01:09:04.279> here<01:09:04.600> we<01:09:04.679> will

01:09:04.990 --> 01:09:05.000 align:start position:0%
have can please chime in here we will
 

01:09:05.000 --> 01:09:08.749 align:start position:0%
have can please chime in here we will
have<01:09:05.799> um<01:09:06.520> the<01:09:06.600> summary<01:09:06.880> of<01:09:07.000> minutes<01:09:07.279> from<01:09:07.759> the

01:09:08.749 --> 01:09:08.759 align:start position:0%
have um the summary of minutes from the
 

01:09:08.759 --> 01:09:11.550 align:start position:0%
have um the summary of minutes from the
presentations<01:09:09.319> we<01:09:09.480> heard<01:09:10.080> on<01:09:10.640> the<01:09:10.839> 28th<01:09:11.359> of

01:09:11.550 --> 01:09:11.560 align:start position:0%
presentations we heard on the 28th of
 

01:09:11.560 --> 01:09:14.110 align:start position:0%
presentations we heard on the 28th of
April<01:09:12.520> we'll<01:09:12.679> have<01:09:12.839> AJ's<01:09:13.319> report<01:09:13.679> and<01:09:13.799> then

01:09:14.110 --> 01:09:14.120 align:start position:0%
April we'll have AJ's report and then
 

01:09:14.120 --> 01:09:16.269 align:start position:0%
April we'll have AJ's report and then
hopefully<01:09:15.120> next<01:09:15.319> agenda<01:09:15.640> item<01:09:15.880> talk<01:09:16.080> about

01:09:16.269 --> 01:09:16.279 align:start position:0%
hopefully next agenda item talk about
 

01:09:16.279 --> 01:09:18.510 align:start position:0%
hopefully next agenda item talk about
who<01:09:16.440> else<01:09:16.640> we<01:09:16.880> want<01:09:17.040> to<01:09:17.279> hear<01:09:17.520> from<01:09:18.040> in<01:09:18.159> order

01:09:18.510 --> 01:09:18.520 align:start position:0%
who else we want to hear from in order
 

01:09:18.520 --> 01:09:21.149 align:start position:0%
who else we want to hear from in order
to<01:09:19.480> um<01:09:19.799> summarize<01:09:20.279> our<01:09:20.480> current<01:09:20.799> activities

01:09:21.149 --> 01:09:21.159 align:start position:0%
to um summarize our current activities
 

01:09:21.159 --> 01:09:23.309 align:start position:0%
to um summarize our current activities
and<01:09:21.279> then<01:09:21.440> take<01:09:21.679> that<01:09:21.920> step<01:09:22.159> forward<01:09:22.520> to<01:09:22.799> make

01:09:23.309 --> 01:09:23.319 align:start position:0%
and then take that step forward to make
 

01:09:23.319 --> 01:09:26.390 align:start position:0%
and then take that step forward to make
recommend<01:09:24.080> ations<01:09:25.080> how<01:09:25.319> do<01:09:25.560> we<01:09:25.759> as<01:09:26.199> an

01:09:26.390 --> 01:09:26.400 align:start position:0%
recommend ations how do we as an
 

01:09:26.400 --> 01:09:30.030 align:start position:0%
recommend ations how do we as an
authority<01:09:27.040> want<01:09:27.640> to<01:09:28.640> uh<01:09:28.799> begin<01:09:29.120> drafting<01:09:29.679> this

01:09:30.030 --> 01:09:30.040 align:start position:0%
authority want to uh begin drafting this
 

01:09:30.040 --> 01:09:34.709 align:start position:0%
authority want to uh begin drafting this
how<01:09:30.239> do<01:09:30.400> we<01:09:30.640> want<01:09:31.440> to<01:09:32.520> um<01:09:33.520> formulate<01:09:34.239> this

01:09:34.709 --> 01:09:34.719 align:start position:0%
how do we want to um formulate this
 

01:09:34.719 --> 01:09:36.789 align:start position:0%
how do we want to um formulate this
report<01:09:35.120> are<01:09:35.279> we<01:09:35.400> going<01:09:35.480> to<01:09:35.719> ask<01:09:36.239> Ken<01:09:36.480> and<01:09:36.640> his

01:09:36.789 --> 01:09:36.799 align:start position:0%
report are we going to ask Ken and his
 

01:09:36.799 --> 01:09:39.030 align:start position:0%
report are we going to ask Ken and his
team<01:09:37.040> to<01:09:37.279> develop<01:09:37.640> a<01:09:37.799> draft<01:09:38.400> maybe<01:09:38.719> first

01:09:39.030 --> 01:09:39.040 align:start position:0%
team to develop a draft maybe first
 

01:09:39.040 --> 01:09:42.189 align:start position:0%
team to develop a draft maybe first
compile<01:09:39.400> a<01:09:39.480> lot<01:09:39.640> of<01:09:39.759> the<01:09:39.920> minutes<01:09:40.400> take<01:09:40.679> a<01:09:41.679> um

01:09:42.189 --> 01:09:42.199 align:start position:0%
compile a lot of the minutes take a um
 

01:09:42.199 --> 01:09:43.669 align:start position:0%
compile a lot of the minutes take a um
take<01:09:42.359> some<01:09:42.520> of<01:09:42.600> the<01:09:42.719> takeaways<01:09:43.199> from<01:09:43.440> each<01:09:43.560> of

01:09:43.669 --> 01:09:43.679 align:start position:0%
take some of the takeaways from each of
 

01:09:43.679 --> 01:09:46.630 align:start position:0%
take some of the takeaways from each of
the<01:09:44.040> presentations<01:09:45.040> and<01:09:45.600> and<01:09:45.759> list<01:09:46.080> those<01:09:46.279> out

01:09:46.630 --> 01:09:46.640 align:start position:0%
the presentations and and list those out
 

01:09:46.640 --> 01:09:48.269 align:start position:0%
the presentations and and list those out
how<01:09:46.759> do<01:09:46.880> we<01:09:47.040> want<01:09:47.239> to<01:09:47.560> operate<01:09:48.000> as<01:09:48.120> an

01:09:48.269 --> 01:09:48.279 align:start position:0%
how do we want to operate as an
 

01:09:48.279 --> 01:09:50.749 align:start position:0%
how do we want to operate as an
authority<01:09:48.719> to<01:09:49.400> get<01:09:49.640> this<01:09:49.839> document

01:09:50.749 --> 01:09:50.759 align:start position:0%
authority to get this document
 

01:09:50.759 --> 01:09:53.070 align:start position:0%
authority to get this document
started<01:09:51.759> before<01:09:52.279> our<01:09:52.480> next<01:09:52.640> meeting<01:09:52.920> in

01:09:53.070 --> 01:09:53.080 align:start position:0%
started before our next meeting in
 

01:09:53.080 --> 01:09:57.110 align:start position:0%
started before our next meeting in
September<01:09:53.759> that<01:09:53.880> we<01:09:53.960> can<01:09:54.080> meet<01:09:54.320> that<01:09:54.520> October

01:09:57.110 --> 01:09:57.120 align:start position:0%
 
 

01:09:57.120 --> 01:09:59.709 align:start position:0%
 
deadline<01:09:58.120> let<01:09:58.239> me<01:09:58.400> ask<01:09:58.560> a<01:09:58.719> question<01:09:59.000> so<01:09:59.400> in<01:09:59.520> the

01:09:59.709 --> 01:09:59.719 align:start position:0%
deadline let me ask a question so in the
 

01:09:59.719 --> 01:10:01.030 align:start position:0%
deadline let me ask a question so in the
past<01:09:59.960> I'm<01:10:00.080> not<01:10:00.239> saying<01:10:00.520> that<01:10:00.640> I<01:10:00.760> think<01:10:00.880> it's

01:10:01.030 --> 01:10:01.040 align:start position:0%
past I'm not saying that I think it's
 

01:10:01.040 --> 01:10:02.910 align:start position:0%
past I'm not saying that I think it's
what<01:10:01.159> we<01:10:01.239> should<01:10:01.440> do<01:10:01.960> we<01:10:02.120> had<01:10:02.320> always<01:10:02.679> kind<01:10:02.800> of

01:10:02.910 --> 01:10:02.920 align:start position:0%
what we should do we had always kind of
 

01:10:02.920 --> 01:10:05.870 align:start position:0%
what we should do we had always kind of
shi<01:10:03.440> away<01:10:03.719> from<01:10:04.320> we've<01:10:04.560> been<01:10:04.840> kind<01:10:04.960> of<01:10:05.679> been

01:10:05.870 --> 01:10:05.880 align:start position:0%
shi away from we've been kind of been
 

01:10:05.880 --> 01:10:08.030 align:start position:0%
shi away from we've been kind of been
factual<01:10:06.800> for<01:10:07.159> information<01:10:07.600> I<01:10:07.679> don't<01:10:07.840> know<01:10:07.920> if

01:10:08.030 --> 01:10:08.040 align:start position:0%
factual for information I don't know if
 

01:10:08.040 --> 01:10:09.110 align:start position:0%
factual for information I don't know if
we<01:10:08.159> had

01:10:09.110 --> 01:10:09.120 align:start position:0%
we had
 

01:10:09.120 --> 01:10:12.390 align:start position:0%
we had
really<01:10:10.120> um<01:10:10.480> been<01:10:11.080> out<01:10:11.320> there<01:10:11.600> putting<01:10:12.000> out

01:10:12.390 --> 01:10:12.400 align:start position:0%
really um been out there putting out
 

01:10:12.400 --> 01:10:14.990 align:start position:0%
really um been out there putting out
recommendations<01:10:13.080> on<01:10:13.760> for

01:10:14.990 --> 01:10:15.000 align:start position:0%
recommendations on for
 

01:10:15.000 --> 01:10:19.270 align:start position:0%
recommendations on for
Action<01:10:16.000> um<01:10:16.360> am<01:10:16.480> I<01:10:16.679> am<01:10:16.760> I<01:10:16.920> wrong<01:10:17.600> what<01:10:18.600> in<01:10:18.800> our<01:10:19.199> in

01:10:19.270 --> 01:10:19.280 align:start position:0%
Action um am I am I wrong what in our in
 

01:10:19.280 --> 01:10:21.990 align:start position:0%
Action um am I am I wrong what in our in
the<01:10:19.440> anual<01:10:19.760> annual<01:10:20.080> report<01:10:20.560> have<01:10:20.719> we<01:10:21.640> it<01:10:21.760> seems

01:10:21.990 --> 01:10:22.000 align:start position:0%
the anual annual report have we it seems
 

01:10:22.000 --> 01:10:23.950 align:start position:0%
the anual annual report have we it seems
like<01:10:22.120> we've<01:10:22.320> been<01:10:22.520> kind<01:10:22.679> of<01:10:23.719> this<01:10:23.800> is<01:10:23.880> the

01:10:23.950 --> 01:10:23.960 align:start position:0%
like we've been kind of this is the
 

01:10:23.960 --> 01:10:26.430 align:start position:0%
like we've been kind of this is the
state<01:10:24.159> of<01:10:24.239> the<01:10:24.320> solar<01:10:24.640> industry<01:10:25.000> in<01:10:25.440> Virginia

01:10:26.430 --> 01:10:26.440 align:start position:0%
state of the solar industry in Virginia
 

01:10:26.440 --> 01:10:29.950 align:start position:0%
state of the solar industry in Virginia
have<01:10:26.679> we<01:10:27.239> provided

01:10:29.950 --> 01:10:29.960 align:start position:0%
have we provided
 

01:10:29.960 --> 01:10:32.149 align:start position:0%
have we provided
um<01:10:30.960> actual<01:10:31.280> recommendations<01:10:31.880> for

01:10:32.149 --> 01:10:32.159 align:start position:0%
um actual recommendations for
 

01:10:32.159 --> 01:10:34.590 align:start position:0%
um actual recommendations for
legislation<01:10:32.880> you<01:10:33.040> have<01:10:33.239> not<01:10:33.880> I<01:10:34.000> didn't<01:10:34.239> think

01:10:34.590 --> 01:10:34.600 align:start position:0%
legislation you have not I didn't think
 

01:10:34.600 --> 01:10:38.270 align:start position:0%
legislation you have not I didn't think
so<01:10:35.600> would<01:10:35.760> it<01:10:35.920> be<01:10:36.640> inappropriate<01:10:37.520> to<01:10:37.719> do<01:10:37.960> that

01:10:38.270 --> 01:10:38.280 align:start position:0%
so would it be inappropriate to do that
 

01:10:38.280 --> 01:10:40.110 align:start position:0%
so would it be inappropriate to do that
I<01:10:38.480> I<01:10:38.719> nope

01:10:40.110 --> 01:10:40.120 align:start position:0%
I I nope
 

01:10:40.120 --> 01:10:43.750 align:start position:0%
I I nope
okay<01:10:41.120> the<01:10:41.480> BL<01:10:42.159> report<01:10:42.440> is<01:10:42.640> this<01:10:43.360> thing<01:10:43.600> what

01:10:43.750 --> 01:10:43.760 align:start position:0%
okay the BL report is this thing what
 

01:10:43.760 --> 01:10:45.550 align:start position:0%
okay the BL report is this thing what
Ken<01:10:43.960> was<01:10:44.080> mentioning<01:10:44.440> earlier<01:10:45.280> with<01:10:45.400> a

01:10:45.550 --> 01:10:45.560 align:start position:0%
Ken was mentioning earlier with a
 

01:10:45.560 --> 01:10:47.310 align:start position:0%
Ken was mentioning earlier with a
direction<01:10:46.040> from<01:10:46.640> the<01:10:46.760> director<01:10:47.080> of<01:10:47.159> the

01:10:47.310 --> 01:10:47.320 align:start position:0%
direction from the director of the
 

01:10:47.320 --> 01:10:50.350 align:start position:0%
direction from the director of the
department<01:10:47.960> is<01:10:48.960> don't<01:10:49.239> give<01:10:49.440> a<01:10:49.679> summary<01:10:50.120> of

01:10:50.350 --> 01:10:50.360 align:start position:0%
department is don't give a summary of
 

01:10:50.360 --> 01:10:52.950 align:start position:0%
department is don't give a summary of
what<01:10:50.560> the<01:10:50.719> industry<01:10:51.199> looks<01:10:51.520> like<01:10:52.280> summarize

01:10:52.950 --> 01:10:52.960 align:start position:0%
what the industry looks like summarize
 

01:10:52.960 --> 01:10:55.470 align:start position:0%
what the industry looks like summarize
your<01:10:53.199> activity<01:10:54.080> and<01:10:54.320> make<01:10:54.560> recommendations

01:10:55.470 --> 01:10:55.480 align:start position:0%
your activity and make recommendations
 

01:10:55.480 --> 01:10:57.229 align:start position:0%
your activity and make recommendations
to<01:10:55.719> the<01:10:55.880> governor<01:10:56.360> and<01:10:56.480> to<01:10:56.640> the<01:10:56.760> general

01:10:57.229 --> 01:10:57.239 align:start position:0%
to the governor and to the general
 

01:10:57.239 --> 01:10:59.550 align:start position:0%
to the governor and to the general
assembly<01:10:58.239> so<01:10:58.600> that's<01:10:58.920> it's<01:10:59.040> going<01:10:59.159> to<01:10:59.239> free<01:10:59.480> us

01:10:59.550 --> 01:10:59.560 align:start position:0%
assembly so that's it's going to free us
 

01:10:59.560 --> 01:11:01.189 align:start position:0%
assembly so that's it's going to free us
up<01:10:59.719> to<01:10:59.840> give<01:10:59.960> a<01:11:00.040> short<01:11:00.400> report<01:11:00.760> and<01:11:00.920> give<01:11:01.040> us

01:11:01.189 --> 01:11:01.199 align:start position:0%
up to give a short report and give us
 

01:11:01.199 --> 01:11:04.390 align:start position:0%
up to give a short report and give us
the<01:11:01.320> opportunity<01:11:01.960> to<01:11:02.239> make<01:11:02.600> those<01:11:03.280> yes

01:11:04.390 --> 01:11:04.400 align:start position:0%
the opportunity to make those yes
 

01:11:04.400 --> 01:11:06.550 align:start position:0%
the opportunity to make those yes
recommendations<01:11:05.400> and<01:11:05.600> and<01:11:05.800> we<01:11:05.960> have<01:11:06.120> a

01:11:06.550 --> 01:11:06.560 align:start position:0%
recommendations and and we have a
 

01:11:06.560 --> 01:11:09.750 align:start position:0%
recommendations and and we have a
director<01:11:07.040> who<01:11:07.239> is<01:11:08.080> very<01:11:08.400> tuned<01:11:08.800> to<01:11:09.600> these

01:11:09.750 --> 01:11:09.760 align:start position:0%
director who is very tuned to these
 

01:11:09.760 --> 01:11:12.270 align:start position:0%
director who is very tuned to these
issues<01:11:10.000> and<01:11:10.120> he's<01:11:10.280> looking<01:11:10.520> for<01:11:11.440> feedback

01:11:12.270 --> 01:11:12.280 align:start position:0%
issues and he's looking for feedback
 

01:11:12.280 --> 01:11:14.630 align:start position:0%
issues and he's looking for feedback
yeah<01:11:12.880> and<01:11:13.360> in<01:11:13.520> conversations<01:11:14.159> with<01:11:14.400> folks

01:11:14.630 --> 01:11:14.640 align:start position:0%
yeah and in conversations with folks
 

01:11:14.640 --> 01:11:16.510 align:start position:0%
yeah and in conversations with folks
within<01:11:14.880> the<01:11:15.040> administration<01:11:16.040> they

01:11:16.510 --> 01:11:16.520 align:start position:0%
within the administration they
 

01:11:16.520 --> 01:11:18.229 align:start position:0%
within the administration they
understand<01:11:16.719> how<01:11:16.880> important<01:11:17.320> this<01:11:17.520> is<01:11:17.760> they

01:11:18.229 --> 01:11:18.239 align:start position:0%
understand how important this is they
 

01:11:18.239 --> 01:11:20.390 align:start position:0%
understand how important this is they
understand<01:11:18.719> how<01:11:19.000> much<01:11:19.320> demand<01:11:19.719> there<01:11:19.920> is<01:11:20.120> for

01:11:20.390 --> 01:11:20.400 align:start position:0%
understand how much demand there is for
 

01:11:20.400 --> 01:11:22.390 align:start position:0%
understand how much demand there is for
new<01:11:20.640> energy<01:11:21.560> and<01:11:21.760> they're<01:11:21.920> looking<01:11:22.159> for

01:11:22.390 --> 01:11:22.400 align:start position:0%
new energy and they're looking for
 

01:11:22.400 --> 01:11:24.390 align:start position:0%
new energy and they're looking for
advice<01:11:22.760> and<01:11:22.920> recommendations<01:11:23.719> so<01:11:24.120> I<01:11:24.199> think

01:11:24.390 --> 01:11:24.400 align:start position:0%
advice and recommendations so I think
 

01:11:24.400 --> 01:11:26.189 align:start position:0%
advice and recommendations so I think
that<01:11:24.560> there<01:11:24.679> will<01:11:24.840> be<01:11:25.440> more<01:11:25.719> interest<01:11:26.080> this

01:11:26.189 --> 01:11:26.199 align:start position:0%
that there will be more interest this
 

01:11:26.199 --> 01:11:28.990 align:start position:0%
that there will be more interest this
year<01:11:26.360> in<01:11:26.480> reading<01:11:26.760> this<01:11:26.960> 15-page<01:11:27.840> report<01:11:28.840> than

01:11:28.990 --> 01:11:29.000 align:start position:0%
year in reading this 15-page report than
 

01:11:29.000 --> 01:11:30.790 align:start position:0%
year in reading this 15-page report than
in<01:11:29.080> the<01:11:29.199> years's<01:11:29.520> past<01:11:30.000> the<01:11:30.120> director<01:11:30.440> was<01:11:30.600> at

01:11:30.790 --> 01:11:30.800 align:start position:0%
in the years's past the director was at
 

01:11:30.800 --> 01:11:32.430 align:start position:0%
in the years's past the director was at
our<01:11:31.120> last<01:11:31.400> imp<01:11:31.600> person<01:11:31.800> meeting<01:11:32.080> and<01:11:32.159> so<01:11:32.320> it's

01:11:32.430 --> 01:11:32.440 align:start position:0%
our last imp person meeting and so it's
 

01:11:32.440 --> 01:11:34.510 align:start position:0%
our last imp person meeting and so it's
the<01:11:32.560> deputy<01:11:32.880> secretary<01:11:33.360> of<01:11:34.080> Commerce<01:11:34.400> and

01:11:34.510 --> 01:11:34.520 align:start position:0%
the deputy secretary of Commerce and
 

01:11:34.520 --> 01:11:36.470 align:start position:0%
the deputy secretary of Commerce and
trade<01:11:34.840> so<01:11:34.960> they<01:11:35.080> are<01:11:35.199> checking<01:11:35.520> on<01:11:35.760> us<01:11:36.199> on<01:11:36.320> a

01:11:36.470 --> 01:11:36.480 align:start position:0%
trade so they are checking on us on a
 

01:11:36.480 --> 01:11:39.229 align:start position:0%
trade so they are checking on us on a
regular<01:11:36.840> basis<01:11:37.239> and<01:11:37.600> I<01:11:37.719> want<01:11:37.840> to<01:11:37.960> see<01:11:38.239> this<01:11:38.840> and

01:11:39.229 --> 01:11:39.239 align:start position:0%
regular basis and I want to see this and
 

01:11:39.239 --> 01:11:42.229 align:start position:0%
regular basis and I want to see this and
and<01:11:39.360> so<01:11:39.719> what<01:11:39.880> my<01:11:40.120> comment<01:11:40.560> is<01:11:41.440> to<01:11:41.679> the<01:11:41.800> role<01:11:42.000> of

01:11:42.229 --> 01:11:42.239 align:start position:0%
and so what my comment is to the role of
 

01:11:42.239 --> 01:11:45.830 align:start position:0%
and so what my comment is to the role of
authority<01:11:42.760> is<01:11:43.440> it<01:11:43.560> doesn't<01:11:44.159> just<01:11:44.520> have<01:11:44.679> to<01:11:44.880> be

01:11:45.830 --> 01:11:45.840 align:start position:0%
authority is it doesn't just have to be
 

01:11:45.840 --> 01:11:47.590 align:start position:0%
authority is it doesn't just have to be
Hey<01:11:46.040> Jo<01:11:46.320> somebody<01:11:46.560> should<01:11:46.719> pass<01:11:46.920> this<01:11:47.120> policy

01:11:47.590 --> 01:11:47.600 align:start position:0%
Hey Jo somebody should pass this policy
 

01:11:47.600 --> 01:11:49.709 align:start position:0%
Hey Jo somebody should pass this policy
it<01:11:47.719> could<01:11:47.920> be<01:11:48.320> heyj<01:11:48.840> somebody<01:11:49.239> use<01:11:49.520> the

01:11:49.709 --> 01:11:49.719 align:start position:0%
it could be heyj somebody use the
 

01:11:49.719 --> 01:11:52.750 align:start position:0%
it could be heyj somebody use the
authority<01:11:50.440> this<01:11:50.719> way<01:11:51.719> to<01:11:51.880> help<01:11:52.159> Advance<01:11:52.600> the

01:11:52.750 --> 01:11:52.760 align:start position:0%
authority this way to help Advance the
 

01:11:52.760 --> 01:11:55.709 align:start position:0%
authority this way to help Advance the
policy<01:11:53.080> that<01:11:53.199> you're<01:11:53.880> looking<01:11:54.360> for<01:11:55.360> um<01:11:55.520> and

01:11:55.709 --> 01:11:55.719 align:start position:0%
policy that you're looking for um and
 

01:11:55.719 --> 01:11:58.550 align:start position:0%
policy that you're looking for um and
whether<01:11:55.960> it's<01:11:56.159> a<01:11:57.120> place<01:11:57.320> to<01:11:57.719> receive<01:11:58.199> federal

01:11:58.550 --> 01:11:58.560 align:start position:0%
whether it's a place to receive federal
 

01:11:58.560 --> 01:12:01.669 align:start position:0%
whether it's a place to receive federal
monies<01:11:58.960> and<01:11:59.600> issue<01:12:00.280> grants<01:12:00.719> to<01:12:00.920> try<01:12:01.080> to<01:12:01.360> run

01:12:01.669 --> 01:12:01.679 align:start position:0%
monies and issue grants to try to run
 

01:12:01.679 --> 01:12:03.070 align:start position:0%
monies and issue grants to try to run
pilots<01:12:02.000> on<01:12:02.120> some<01:12:02.239> of<01:12:02.360> these<01:12:02.520> programs<01:12:02.880> they're

01:12:03.070 --> 01:12:03.080 align:start position:0%
pilots on some of these programs they're
 

01:12:03.080 --> 01:12:05.990 align:start position:0%
pilots on some of these programs they're
like<01:12:03.320> it<01:12:03.480> could<01:12:03.679> literally<01:12:04.080> be<01:12:04.719> that<01:12:05.719> again

01:12:05.990 --> 01:12:06.000 align:start position:0%
like it could literally be that again
 

01:12:06.000 --> 01:12:07.110 align:start position:0%
like it could literally be that again
I'm<01:12:06.120> not<01:12:06.280> saying<01:12:06.560> that's<01:12:06.760> right<01:12:06.920> I'm<01:12:07.040> not

01:12:07.110 --> 01:12:07.120 align:start position:0%
I'm not saying that's right I'm not
 

01:12:07.120 --> 01:12:08.270 align:start position:0%
I'm not saying that's right I'm not
saying<01:12:07.320> the<01:12:07.400> administration<01:12:07.840> wants<01:12:08.000> to<01:12:08.120> give

01:12:08.270 --> 01:12:08.280 align:start position:0%
saying the administration wants to give
 

01:12:08.280 --> 01:12:11.990 align:start position:0%
saying the administration wants to give
up<01:12:08.960> control<01:12:09.440> I'm<01:12:09.639> not<01:12:10.280> whatever<01:12:11.280> but<01:12:11.840> the

01:12:11.990 --> 01:12:12.000 align:start position:0%
up control I'm not whatever but the
 

01:12:12.000 --> 01:12:14.750 align:start position:0%
up control I'm not whatever but the
recommendations<01:12:12.920> could<01:12:13.159> be<01:12:13.320> a<01:12:13.520> role<01:12:13.840> for<01:12:14.280> this

01:12:14.750 --> 01:12:14.760 align:start position:0%
recommendations could be a role for this
 

01:12:14.760 --> 01:12:17.550 align:start position:0%
recommendations could be a role for this
group<01:12:15.080> to<01:12:15.239> play<01:12:15.560> not<01:12:15.880> just<01:12:16.400> suggesting<01:12:17.000> ideas

01:12:17.550 --> 01:12:17.560 align:start position:0%
group to play not just suggesting ideas
 

01:12:17.560 --> 01:12:19.669 align:start position:0%
group to play not just suggesting ideas
but<01:12:17.760> actually<01:12:17.960> implementing<01:12:18.880> things<01:12:19.159> to<01:12:19.400> ADV

01:12:19.669 --> 01:12:19.679 align:start position:0%
but actually implementing things to ADV
 

01:12:19.679 --> 01:12:22.470 align:start position:0%
but actually implementing things to ADV
the

01:12:22.470 --> 01:12:22.480 align:start position:0%
 
 

01:12:22.480 --> 01:12:27.149 align:start position:0%
 
industry

01:12:27.149 --> 01:12:27.159 align:start position:0%
 
 

01:12:27.159 --> 01:12:29.149 align:start position:0%
 
anybody<01:12:27.440> else<01:12:27.600> have<01:12:27.760> any<01:12:27.960> thoughts<01:12:28.199> on<01:12:28.840> how<01:12:29.000> to

01:12:29.149 --> 01:12:29.159 align:start position:0%
anybody else have any thoughts on how to
 

01:12:29.159 --> 01:12:33.830 align:start position:0%
anybody else have any thoughts on how to
move<01:12:29.400> for<01:12:29.639> with<01:12:29.840> the

01:12:33.830 --> 01:12:33.840 align:start position:0%
 
 

01:12:33.840 --> 01:12:37.110 align:start position:0%
 
report<01:12:34.840> Ken<01:12:35.080> would<01:12:35.199> you<01:12:35.320> be<01:12:35.480> willing<01:12:35.840> to<01:12:36.840> work

01:12:37.110 --> 01:12:37.120 align:start position:0%
report Ken would you be willing to work
 

01:12:37.120 --> 01:12:39.590 align:start position:0%
report Ken would you be willing to work
with<01:12:37.320> your<01:12:37.600> team<01:12:38.120> to<01:12:38.800> develop<01:12:39.199> kind<01:12:39.320> of<01:12:39.440> a

01:12:39.590 --> 01:12:39.600 align:start position:0%
with your team to develop kind of a
 

01:12:39.600 --> 01:12:42.070 align:start position:0%
with your team to develop kind of a
framework<01:12:40.320> for<01:12:40.480> us<01:12:40.639> to<01:12:40.840> take<01:12:40.960> a<01:12:41.159> look<01:12:41.480> at<01:12:41.840> over

01:12:42.070 --> 01:12:42.080 align:start position:0%
framework for us to take a look at over
 

01:12:42.080 --> 01:12:45.910 align:start position:0%
framework for us to take a look at over
the<01:12:42.239> next<01:12:42.800> month<01:12:43.080> or<01:12:43.239> so<01:12:44.239> um<01:12:44.760> summarizing<01:12:45.760> what

01:12:45.910 --> 01:12:45.920 align:start position:0%
the next month or so um summarizing what
 

01:12:45.920 --> 01:12:48.990 align:start position:0%
the next month or so um summarizing what
we've<01:12:46.480> heard<01:12:47.480> during<01:12:47.719> our<01:12:47.840> meetings<01:12:48.199> in

01:12:48.990 --> 01:12:49.000 align:start position:0%
we've heard during our meetings in
 

01:12:49.000 --> 01:12:52.550 align:start position:0%
we've heard during our meetings in
2023<01:12:50.000> and<01:12:50.719> um<01:12:51.360> at<01:12:51.480> least<01:12:51.760> listing<01:12:52.120> out<01:12:52.320> some<01:12:52.440> of

01:12:52.550 --> 01:12:52.560 align:start position:0%
2023 and um at least listing out some of
 

01:12:52.560 --> 01:12:54.189 align:start position:0%
2023 and um at least listing out some of
the<01:12:52.719> recommendations<01:12:53.560> that<01:12:53.719> have<01:12:53.840> been<01:12:53.960> made

01:12:54.189 --> 01:12:54.199 align:start position:0%
the recommendations that have been made
 

01:12:54.199 --> 01:12:55.990 align:start position:0%
the recommendations that have been made
by<01:12:54.280> our<01:12:54.520> presenters<01:12:54.960> for<01:12:55.159> our<01:12:55.400> consideration

01:12:55.990 --> 01:12:56.000 align:start position:0%
by our presenters for our consideration
 

01:12:56.000 --> 01:12:57.430 align:start position:0%
by our presenters for our consideration
at<01:12:56.120> the<01:12:56.280> next

01:12:57.430 --> 01:12:57.440 align:start position:0%
at the next
 

01:12:57.440 --> 01:13:00.870 align:start position:0%
at the next
meeting<01:12:58.440> sure<01:12:59.280> appreciate<01:12:59.800> that<01:13:00.520> my<01:13:00.679> team

01:13:00.870 --> 01:13:00.880 align:start position:0%
meeting sure appreciate that my team
 

01:13:00.880 --> 01:13:01.709 align:start position:0%
meeting sure appreciate that my team
will<01:13:01.000> be

01:13:01.709 --> 01:13:01.719 align:start position:0%
will be
 

01:13:01.719 --> 01:13:04.629 align:start position:0%
will be
made<01:13:02.719> I<01:13:02.880> hoping<01:13:03.159> I'm<01:13:03.280> hoping<01:13:03.480> Aaron<01:13:03.719> will<01:13:03.880> help

01:13:04.629 --> 01:13:04.639 align:start position:0%
made I hoping I'm hoping Aaron will help
 

01:13:04.639 --> 01:13:08.310 align:start position:0%
made I hoping I'm hoping Aaron will help
you<01:13:05.639> is<01:13:05.760> he<01:13:06.280> online<01:13:07.280> he

01:13:08.310 --> 01:13:08.320 align:start position:0%
you is he online he
 

01:13:08.320 --> 01:13:10.669 align:start position:0%
you is he online he
was<01:13:09.320> yeah<01:13:09.880> I'm<01:13:09.960> sure<01:13:10.159> I<01:13:10.239> can<01:13:10.360> get<01:13:10.480> some

01:13:10.669 --> 01:13:10.679 align:start position:0%
was yeah I'm sure I can get some
 

01:13:10.679 --> 01:13:12.390 align:start position:0%
was yeah I'm sure I can get some
information<01:13:11.199> he's<01:13:11.400> been<01:13:11.560> working<01:13:12.080> very

01:13:12.390 --> 01:13:12.400 align:start position:0%
information he's been working very
 

01:13:12.400 --> 01:13:14.750 align:start position:0%
information he's been working very
closely<01:13:12.880> with<01:13:13.040> the<01:13:13.320> localities<01:13:14.120> and<01:13:14.639> there

01:13:14.750 --> 01:13:14.760 align:start position:0%
closely with the localities and there
 

01:13:14.760 --> 01:13:19.229 align:start position:0%
closely with the localities and there
are<01:13:15.000> issues<01:13:15.320> out<01:13:15.560> there<01:13:16.400> great<01:13:16.840> and<01:13:17.320> I<01:13:18.080> um<01:13:19.080> love

01:13:19.229 --> 01:13:19.239 align:start position:0%
are issues out there great and I um love
 

01:13:19.239 --> 01:13:20.990 align:start position:0%
are issues out there great and I um love
to<01:13:19.360> get<01:13:19.520> the<01:13:19.880> some<01:13:20.080> eyes<01:13:20.320> on<01:13:20.440> this<01:13:20.560> and<01:13:20.719> send<01:13:20.920> it

01:13:20.990 --> 01:13:21.000 align:start position:0%
to get the some eyes on this and send it
 

01:13:21.000 --> 01:13:22.830 align:start position:0%
to get the some eyes on this and send it
out<01:13:21.120> to<01:13:21.280> the<01:13:21.400> authority<01:13:21.880> as<01:13:21.960> soon<01:13:22.199> as<01:13:22.600> we're

01:13:22.830 --> 01:13:22.840 align:start position:0%
out to the authority as soon as we're
 

01:13:22.840 --> 01:13:26.030 align:start position:0%
out to the authority as soon as we're
ready<01:13:23.040> to<01:13:23.560> first<01:13:24.159> comments<01:13:24.639> before<01:13:25.040> the<01:13:25.920> the

01:13:26.030 --> 01:13:26.040 align:start position:0%
ready to first comments before the the
 

01:13:26.040 --> 01:13:29.790 align:start position:0%
ready to first comments before the the
hopeful<01:13:26.440> September

01:13:29.790 --> 01:13:29.800 align:start position:0%
 
 

01:13:29.800 --> 01:13:33.629 align:start position:0%
 
meeting<01:13:30.800> no<01:13:30.960> further<01:13:31.360> discussion<01:13:32.360> um<01:13:32.880> let's

01:13:33.629 --> 01:13:33.639 align:start position:0%
meeting no further discussion um let's
 

01:13:33.639 --> 01:13:35.990 align:start position:0%
meeting no further discussion um let's
move<01:13:34.080> on<01:13:34.440> to

01:13:35.990 --> 01:13:36.000 align:start position:0%
move on to
 

01:13:36.000 --> 01:13:37.550 align:start position:0%
move on to
a

01:13:37.550 --> 01:13:37.560 align:start position:0%
a
 

01:13:37.560 --> 01:13:41.430 align:start position:0%
a
brainstorm<01:13:38.560> of<01:13:39.480> future<01:13:39.920> presentation<01:13:40.600> topics

01:13:41.430 --> 01:13:41.440 align:start position:0%
brainstorm of future presentation topics
 

01:13:41.440 --> 01:13:42.990 align:start position:0%
brainstorm of future presentation topics
uh<01:13:41.600> Colleen<01:13:42.000> believe<01:13:42.239> you<01:13:42.360> mentioned<01:13:42.679> this<01:13:42.840> in

01:13:42.990 --> 01:13:43.000 align:start position:0%
uh Colleen believe you mentioned this in
 

01:13:43.000 --> 01:13:46.790 align:start position:0%
uh Colleen believe you mentioned this in
our<01:13:43.520> last<01:13:44.400> last<01:13:44.639> meeting<01:13:45.560> we<01:13:45.719> discussed

01:13:46.790 --> 01:13:46.800 align:start position:0%
our last last meeting we discussed
 

01:13:46.800 --> 01:13:51.430 align:start position:0%
our last last meeting we discussed
offline<01:13:47.800> um<01:13:48.000> a<01:13:48.159> desire<01:13:48.560> to<01:13:48.840> have<01:13:49.440> the<01:13:49.880> data

01:13:51.430 --> 01:13:51.440 align:start position:0%
offline um a desire to have the data
 

01:13:51.440 --> 01:13:54.470 align:start position:0%
offline um a desire to have the data
center<01:13:52.440> uh<01:13:53.000> data<01:13:53.600> companies<01:13:54.000> or<01:13:54.120> the<01:13:54.239> data

01:13:54.470 --> 01:13:54.480 align:start position:0%
center uh data companies or the data
 

01:13:54.480 --> 01:13:56.229 align:start position:0%
center uh data companies or the data
center<01:13:54.760> coalitions<01:13:55.320> to<01:13:55.480> Come<01:13:55.679> Share<01:13:56.000> their

01:13:56.229 --> 01:13:56.239 align:start position:0%
center coalitions to Come Share their
 

01:13:56.239 --> 01:13:58.550 align:start position:0%
center coalitions to Come Share their
perspectives<01:13:56.840> on<01:13:57.120> how<01:13:57.360> they<01:13:57.480> want<01:13:57.639> to<01:13:57.840> consume

01:13:58.550 --> 01:13:58.560 align:start position:0%
perspectives on how they want to consume
 

01:13:58.560 --> 01:14:01.070 align:start position:0%
perspectives on how they want to consume
solar<01:13:59.040> energy<01:13:59.480> and<01:13:59.719> how<01:13:59.960> quickly<01:14:00.400> they<01:14:00.719> need

01:14:01.070 --> 01:14:01.080 align:start position:0%
solar energy and how quickly they need
 

01:14:01.080 --> 01:14:04.149 align:start position:0%
solar energy and how quickly they need
to<01:14:02.080> um<01:14:02.280> see<01:14:02.560> this<01:14:02.719> new<01:14:02.840> energy<01:14:03.199> come<01:14:03.400> online<01:14:03.920> as

01:14:04.149 --> 01:14:04.159 align:start position:0%
to um see this new energy come online as
 

01:14:04.159 --> 01:14:06.709 align:start position:0%
to um see this new energy come online as
demonstrated<01:14:04.679> by<01:14:04.840> AJ's<01:14:05.400> report<01:14:06.280> um<01:14:06.400> I<01:14:06.520> had

01:14:06.709 --> 01:14:06.719 align:start position:0%
demonstrated by AJ's report um I had
 

01:14:06.719 --> 01:14:08.430 align:start position:0%
demonstrated by AJ's report um I had
conversations<01:14:07.520> with<01:14:07.679> a<01:14:07.880> data<01:14:08.120> center

01:14:08.430 --> 01:14:08.440 align:start position:0%
conversations with a data center
 

01:14:08.440 --> 01:14:10.470 align:start position:0%
conversations with a data center
operator<01:14:09.000> who<01:14:09.400> is<01:14:09.560> going<01:14:09.760> to<01:14:09.920> point<01:14:10.120> us<01:14:10.239> in<01:14:10.360> the

01:14:10.470 --> 01:14:10.480 align:start position:0%
operator who is going to point us in the
 

01:14:10.480 --> 01:14:12.430 align:start position:0%
operator who is going to point us in the
direction<01:14:10.880> of<01:14:11.000> the<01:14:11.120> data<01:14:11.400> center<01:14:11.800> Coalition

01:14:12.430 --> 01:14:12.440 align:start position:0%
direction of the data center Coalition
 

01:14:12.440 --> 01:14:14.390 align:start position:0%
direction of the data center Coalition
that's<01:14:12.639> active<01:14:12.920> in<01:14:13.080> Virginia<01:14:13.960> thinking<01:14:14.280> that

01:14:14.390 --> 01:14:14.400 align:start position:0%
that's active in Virginia thinking that
 

01:14:14.400 --> 01:14:15.950 align:start position:0%
that's active in Virginia thinking that
the<01:14:14.520> data<01:14:14.760> center<01:14:15.040> Coalition<01:14:15.400> will<01:14:15.560> be<01:14:15.840> a

01:14:15.950 --> 01:14:15.960 align:start position:0%
the data center Coalition will be a
 

01:14:15.960 --> 01:14:18.270 align:start position:0%
the data center Coalition will be a
little<01:14:16.120> bit<01:14:16.320> more<01:14:16.520> free<01:14:16.960> to<01:14:17.520> share<01:14:17.920> some

01:14:18.270 --> 01:14:18.280 align:start position:0%
little bit more free to share some
 

01:14:18.280 --> 01:14:19.270 align:start position:0%
little bit more free to share some
thoughts<01:14:18.520> and

01:14:19.270 --> 01:14:19.280 align:start position:0%
thoughts and
 

01:14:19.280 --> 01:14:21.110 align:start position:0%
thoughts and
recommendations<01:14:20.280> uh<01:14:20.400> that<01:14:20.520> an<01:14:20.639> individual

01:14:21.110 --> 01:14:21.120 align:start position:0%
recommendations uh that an individual
 

01:14:21.120 --> 01:14:24.350 align:start position:0%
recommendations uh that an individual
company<01:14:21.440> might<01:14:21.600> not<01:14:21.800> be<01:14:21.960> able<01:14:22.280> to<01:14:23.480> um<01:14:24.000> so

01:14:24.350 --> 01:14:24.360 align:start position:0%
company might not be able to um so
 

01:14:24.360 --> 01:14:26.550 align:start position:0%
company might not be able to um so
there's<01:14:24.760> one<01:14:25.040> opportunity<01:14:25.560> that<01:14:25.679> we<01:14:25.840> can

01:14:26.550 --> 01:14:26.560 align:start position:0%
there's one opportunity that we can
 

01:14:26.560 --> 01:14:29.709 align:start position:0%
there's one opportunity that we can
reach<01:14:26.800> out<01:14:27.000> to<01:14:27.320> thank<01:14:27.480> you<01:14:27.600> for<01:14:27.920> for<01:14:28.120> that

01:14:29.709 --> 01:14:29.719 align:start position:0%
reach out to thank you for for that
 

01:14:29.719 --> 01:14:32.910 align:start position:0%
reach out to thank you for for that
recommendation<01:14:30.719> um<01:14:31.440> I'd<01:14:31.560> like<01:14:31.719> to<01:14:31.880> hear

01:14:32.910 --> 01:14:32.920 align:start position:0%
recommendation um I'd like to hear
 

01:14:32.920 --> 01:14:35.790 align:start position:0%
recommendation um I'd like to hear
the<01:14:33.920> um<01:14:34.239> thoughts<01:14:34.639> of<01:14:34.800> the<01:14:35.000> authority<01:14:35.520> but

01:14:35.790 --> 01:14:35.800 align:start position:0%
the um thoughts of the authority but
 

01:14:35.800 --> 01:14:38.110 align:start position:0%
the um thoughts of the authority but
last<01:14:36.040> time<01:14:36.560> I<01:14:37.159> I<01:14:37.280> mentioned<01:14:37.600> the<01:14:37.760> desire<01:14:38.000> to

01:14:38.110 --> 01:14:38.120 align:start position:0%
last time I I mentioned the desire to
 

01:14:38.120 --> 01:14:40.229 align:start position:0%
last time I I mentioned the desire to
hear<01:14:38.280> from<01:14:38.480> local<01:14:38.760> leaders<01:14:39.520> I've<01:14:39.679> since<01:14:39.960> had<01:14:40.080> a

01:14:40.229 --> 01:14:40.239 align:start position:0%
hear from local leaders I've since had a
 

01:14:40.239 --> 01:14:42.550 align:start position:0%
hear from local leaders I've since had a
convers<01:14:40.800> have<01:14:41.360> had<01:14:41.600> conversations<01:14:42.320> with<01:14:42.480> a

01:14:42.550 --> 01:14:42.560 align:start position:0%
convers have had conversations with a
 

01:14:42.560 --> 01:14:45.270 align:start position:0%
convers have had conversations with a
few<01:14:42.760> different<01:14:43.040> counties<01:14:44.000> as<01:14:44.080> well<01:14:44.239> as<01:14:44.400> Veo

01:14:45.270 --> 01:14:45.280 align:start position:0%
few different counties as well as Veo
 

01:14:45.280 --> 01:14:48.070 align:start position:0%
few different counties as well as Veo
with<01:14:45.719> some

01:14:48.070 --> 01:14:48.080 align:start position:0%
with some
 

01:14:48.080 --> 01:14:50.750 align:start position:0%
with some
wishy-washy<01:14:49.080> um<01:14:49.880> commitments<01:14:50.320> on<01:14:50.560> whether

01:14:50.750 --> 01:14:50.760 align:start position:0%
wishy-washy um commitments on whether
 

01:14:50.760 --> 01:14:52.709 align:start position:0%
wishy-washy um commitments on whether
they<01:14:50.880> would<01:14:51.040> want<01:14:51.199> to<01:14:51.400> or<01:14:51.560> whether<01:14:51.800> they<01:14:52.000> can

01:14:52.709 --> 01:14:52.719 align:start position:0%
they would want to or whether they can
 

01:14:52.719 --> 01:14:54.790 align:start position:0%
they would want to or whether they can
come<01:14:52.960> present<01:14:53.280> present<01:14:53.800> their<01:14:54.080> perspective

01:14:54.790 --> 01:14:54.800 align:start position:0%
come present present their perspective
 

01:14:54.800 --> 01:14:57.870 align:start position:0%
come present present their perspective
on<01:14:55.159> local<01:14:55.480> permitting<01:14:56.320> to<01:14:56.560> the<01:14:56.800> authority<01:14:57.800> um

01:14:57.870 --> 01:14:57.880 align:start position:0%
on local permitting to the authority um
 

01:14:57.880 --> 01:14:59.390 align:start position:0%
on local permitting to the authority um
I<01:14:58.000> believe<01:14:58.199> the<01:14:58.320> line<01:14:58.520> from<01:14:58.679> Vego<01:14:59.080> is<01:14:59.239> they

01:14:59.390 --> 01:14:59.400 align:start position:0%
I believe the line from Vego is they
 

01:14:59.400 --> 01:15:01.470 align:start position:0%
I believe the line from Vego is they
might<01:14:59.560> be<01:14:59.679> able<01:14:59.880> to<01:15:00.560> after<01:15:00.880> their<01:15:01.120> annual

01:15:01.470 --> 01:15:01.480 align:start position:0%
might be able to after their annual
 

01:15:01.480 --> 01:15:03.870 align:start position:0%
might be able to after their annual
meeting<01:15:02.120> this<01:15:02.320> fall<01:15:03.000> that<01:15:03.080> would<01:15:03.199> be<01:15:03.320> too<01:15:03.520> late

01:15:03.870 --> 01:15:03.880 align:start position:0%
meeting this fall that would be too late
 

01:15:03.880 --> 01:15:06.189 align:start position:0%
meeting this fall that would be too late
but<01:15:04.239> like<01:15:04.360> to<01:15:04.520> extend<01:15:05.120> a<01:15:05.239> second<01:15:05.560> formal

01:15:06.189 --> 01:15:06.199 align:start position:0%
but like to extend a second formal
 

01:15:06.199 --> 01:15:08.310 align:start position:0%
but like to extend a second formal
invitation<01:15:07.199> uh<01:15:07.320> to<01:15:07.520> them<01:15:07.679> to<01:15:07.840> come<01:15:08.000> share

01:15:08.310 --> 01:15:08.320 align:start position:0%
invitation uh to them to come share
 

01:15:08.320 --> 01:15:10.350 align:start position:0%
invitation uh to them to come share
their<01:15:08.600> thoughts<01:15:09.400> um<01:15:09.639> and<01:15:09.800> that<01:15:09.960> they're<01:15:10.120> very

01:15:10.350 --> 01:15:10.360 align:start position:0%
their thoughts um and that they're very
 

01:15:10.360 --> 01:15:14.310 align:start position:0%
their thoughts um and that they're very
active<01:15:10.880> in<01:15:11.280> this<01:15:12.280> in<01:15:12.360> the<01:15:12.480> Solar<01:15:13.280> pering

01:15:14.310 --> 01:15:14.320 align:start position:0%
active in this in the Solar pering
 

01:15:14.320 --> 01:15:16.910 align:start position:0%
active in this in the Solar pering
conversations<01:15:15.320> at<01:15:15.600> the<01:15:15.920> the<01:15:16.080> county<01:15:16.440> level

01:15:16.910 --> 01:15:16.920 align:start position:0%
conversations at the the county level
 

01:15:16.920 --> 01:15:18.629 align:start position:0%
conversations at the the county level
and<01:15:17.040> serve<01:15:17.320> as<01:15:17.440> a<01:15:17.520> resource<01:15:17.840> to<01:15:18.000> many<01:15:18.280> counties

01:15:18.629 --> 01:15:18.639 align:start position:0%
and serve as a resource to many counties
 

01:15:18.639 --> 01:15:21.270 align:start position:0%
and serve as a resource to many counties
and<01:15:18.840> I<01:15:18.960> figured<01:15:19.280> Veo<01:15:19.679> would<01:15:19.800> be<01:15:20.000> a<01:15:20.760> phenomenal

01:15:21.270 --> 01:15:21.280 align:start position:0%
and I figured Veo would be a phenomenal
 

01:15:21.280 --> 01:15:23.870 align:start position:0%
and I figured Veo would be a phenomenal
way<01:15:21.480> to<01:15:22.480> uh<01:15:22.639> consolidate

01:15:23.870 --> 01:15:23.880 align:start position:0%
way to uh consolidate
 

01:15:23.880 --> 01:15:25.990 align:start position:0%
way to uh consolidate
the<01:15:24.239> the<01:15:24.400> thoughts<01:15:24.600> and<01:15:24.719> the<01:15:24.840> feelings<01:15:25.320> of

01:15:25.990 --> 01:15:26.000 align:start position:0%
the the thoughts and the feelings of
 

01:15:26.000 --> 01:15:28.510 align:start position:0%
the the thoughts and the feelings of
folks<01:15:26.280> at<01:15:26.400> the<01:15:26.520> county<01:15:26.880> level<01:15:27.520> so<01:15:28.080> put<01:15:28.199> a<01:15:28.320> pin

01:15:28.510 --> 01:15:28.520 align:start position:0%
folks at the county level so put a pin
 

01:15:28.520 --> 01:15:32.629 align:start position:0%
folks at the county level so put a pin
in<01:15:28.679> that<01:15:28.880> but<01:15:29.080> I<01:15:29.199> have<01:15:29.719> tried<01:15:30.719> um<01:15:31.400> also<01:15:32.120> wanted

01:15:32.629 --> 01:15:32.639 align:start position:0%
in that but I have tried um also wanted
 

01:15:32.639 --> 01:15:35.270 align:start position:0%
in that but I have tried um also wanted
to<01:15:33.560> potentially<01:15:34.000> get<01:15:34.120> an<01:15:34.239> update<01:15:34.679> from

01:15:35.270 --> 01:15:35.280 align:start position:0%
to potentially get an update from
 

01:15:35.280 --> 01:15:37.790 align:start position:0%
to potentially get an update from
Storage<01:15:35.920> developers<01:15:36.920> um<01:15:37.040> I<01:15:37.120> know<01:15:37.320> we<01:15:37.480> have

01:15:37.790 --> 01:15:37.800 align:start position:0%
Storage developers um I know we have
 

01:15:37.800 --> 01:15:40.030 align:start position:0%
Storage developers um I know we have
DeLorean<01:15:38.400> represented<01:15:39.239> on<01:15:39.480> the<01:15:39.600> authority

01:15:40.030 --> 01:15:40.040 align:start position:0%
DeLorean represented on the authority
 

01:15:40.040 --> 01:15:42.629 align:start position:0%
DeLorean represented on the authority
but<01:15:40.199> there<01:15:40.320> are<01:15:40.600> several<01:15:40.960> other<01:15:41.639> developers

01:15:42.629 --> 01:15:42.639 align:start position:0%
but there are several other developers
 

01:15:42.639 --> 01:15:44.470 align:start position:0%
but there are several other developers
uh<01:15:42.800> developing<01:15:43.159> standal<01:15:43.600> load<01:15:43.800> storage<01:15:44.159> in

01:15:44.470 --> 01:15:44.480 align:start position:0%
uh developing standal load storage in
 

01:15:44.480 --> 01:15:47.830 align:start position:0%
uh developing standal load storage in
Virginia<01:15:45.480> um<01:15:45.760> I've<01:15:45.880> shared<01:15:46.360> the<01:15:46.480> 2018<01:15:47.080> Report

01:15:47.830 --> 01:15:47.840 align:start position:0%
Virginia um I've shared the 2018 Report
 

01:15:47.840 --> 01:15:49.910 align:start position:0%
Virginia um I've shared the 2018 Report
with<01:15:48.280> with<01:15:48.520> one<01:15:48.679> of<01:15:48.840> them<01:15:49.080> and<01:15:49.239> asked<01:15:49.639> hey<01:15:49.800> is

01:15:49.910 --> 01:15:49.920 align:start position:0%
with with one of them and asked hey is
 

01:15:49.920 --> 01:15:51.470 align:start position:0%
with with one of them and asked hey is
this<01:15:50.159> still<01:15:50.480> what<01:15:50.600> you're<01:15:50.719> seeing<01:15:51.000> or<01:15:51.239> do<01:15:51.320> you

01:15:51.470 --> 01:15:51.480 align:start position:0%
this still what you're seeing or do you
 

01:15:51.480 --> 01:15:54.590 align:start position:0%
this still what you're seeing or do you
have<01:15:51.639> any<01:15:51.840> updates<01:15:52.320> for<01:15:53.400> um<01:15:54.000> or<01:15:54.239> thoughts<01:15:54.480> that

01:15:54.590 --> 01:15:54.600 align:start position:0%
have any updates for um or thoughts that
 

01:15:54.600 --> 01:15:55.629 align:start position:0%
have any updates for um or thoughts that
you'd<01:15:54.760> be<01:15:54.880> willing<01:15:55.080> to<01:15:55.159> share<01:15:55.400> with<01:15:55.520> the

01:15:55.629 --> 01:15:55.639 align:start position:0%
you'd be willing to share with the
 

01:15:55.639 --> 01:15:58.070 align:start position:0%
you'd be willing to share with the
authority<01:15:56.320> I<01:15:56.440> think<01:15:56.600> they're<01:15:56.840> interested<01:15:57.639> in

01:15:58.070 --> 01:15:58.080 align:start position:0%
authority I think they're interested in
 

01:15:58.080 --> 01:15:59.870 align:start position:0%
authority I think they're interested in
sharing<01:15:58.440> an<01:15:58.600> update<01:15:58.880> of<01:15:59.159> development<01:15:59.679> from

01:15:59.870 --> 01:15:59.880 align:start position:0%
sharing an update of development from
 

01:15:59.880 --> 01:16:02.149 align:start position:0%
sharing an update of development from
their<01:16:00.320> perspective<01:16:01.320> um<01:16:01.480> this<01:16:01.600> being<01:16:01.880> East

01:16:02.149 --> 01:16:02.159 align:start position:0%
their perspective um this being East
 

01:16:02.159 --> 01:16:05.070 align:start position:0%
their perspective um this being East
Point<01:16:02.320> Energy<01:16:02.760> based<01:16:03.080> in<01:16:03.480> in<01:16:04.080> Charlottesville

01:16:05.070 --> 01:16:05.080 align:start position:0%
Point Energy based in in Charlottesville
 

01:16:05.080 --> 01:16:06.990 align:start position:0%
Point Energy based in in Charlottesville
very<01:16:05.280> open<01:16:05.560> to<01:16:05.760> others<01:16:06.000> and<01:16:06.239> I<01:16:06.400> i'<01:16:06.560> hope

01:16:06.990 --> 01:16:07.000 align:start position:0%
very open to others and I i' hope
 

01:16:07.000 --> 01:16:09.189 align:start position:0%
very open to others and I i' hope
DeLorean<01:16:07.480> would<01:16:07.639> be<01:16:07.719> able<01:16:07.840> to<01:16:07.960> chime<01:16:08.239> in<01:16:08.440> as

01:16:09.189 --> 01:16:09.199 align:start position:0%
DeLorean would be able to chime in as
 

01:16:09.199 --> 01:16:11.990 align:start position:0%
DeLorean would be able to chime in as
well<01:16:10.480> and

01:16:11.990 --> 01:16:12.000 align:start position:0%
well and
 

01:16:12.000 --> 01:16:15.390 align:start position:0%
well and
lastly<01:16:13.199> um<01:16:14.199> there's<01:16:14.480> been<01:16:14.800> talk<01:16:15.080> over<01:16:15.280> the

01:16:15.390 --> 01:16:15.400 align:start position:0%
lastly um there's been talk over the
 

01:16:15.400 --> 01:16:17.750 align:start position:0%
lastly um there's been talk over the
last<01:16:15.560> several<01:16:15.840> years<01:16:16.159> about<01:16:16.679> a<01:16:16.960> a<01:16:17.159> change<01:16:17.600> in

01:16:17.750 --> 01:16:17.760 align:start position:0%
last several years about a a change in
 

01:16:17.760 --> 01:16:18.430 align:start position:0%
last several years about a a change in
the

01:16:18.430 --> 01:16:18.440 align:start position:0%
the
 

01:16:18.440 --> 01:16:21.990 align:start position:0%
the
way<01:16:19.440> permitting<01:16:20.040> and<01:16:20.199> sighting<01:16:20.679> takes<01:16:21.120> place

01:16:21.990 --> 01:16:22.000 align:start position:0%
way permitting and sighting takes place
 

01:16:22.000 --> 01:16:23.470 align:start position:0%
way permitting and sighting takes place
uh<01:16:22.080> in<01:16:22.280> Virginia<01:16:22.760> we<01:16:22.880> saw<01:16:23.000> the<01:16:23.239> budget

01:16:23.470 --> 01:16:23.480 align:start position:0%
uh in Virginia we saw the budget
 

01:16:23.480 --> 01:16:26.390 align:start position:0%
uh in Virginia we saw the budget
amendment<01:16:23.920> this<01:16:24.120> past<01:16:24.360> session<01:16:24.920> to<01:16:25.920> create<01:16:26.199> a

01:16:26.390 --> 01:16:26.400 align:start position:0%
amendment this past session to create a
 

01:16:26.400 --> 01:16:30.790 align:start position:0%
amendment this past session to create a
task<01:16:26.719> force<01:16:27.000> to<01:16:27.840> study<01:16:28.840> um<01:16:29.400> ways<01:16:29.760> to<01:16:30.360> alter

01:16:30.790 --> 01:16:30.800 align:start position:0%
task force to study um ways to alter
 

01:16:30.800 --> 01:16:32.750 align:start position:0%
task force to study um ways to alter
local<01:16:31.199> control<01:16:31.520> or<01:16:31.719> local<01:16:32.040> authority<01:16:32.440> over

01:16:32.750 --> 01:16:32.760 align:start position:0%
local control or local authority over
 

01:16:32.760 --> 01:16:35.110 align:start position:0%
local control or local authority over
sighting<01:16:33.120> agreements<01:16:33.560> with<01:16:33.760> these<01:16:34.120> projects

01:16:35.110 --> 01:16:35.120 align:start position:0%
sighting agreements with these projects
 

01:16:35.120 --> 01:16:37.709 align:start position:0%
sighting agreements with these projects
um<01:16:35.440> our<01:16:36.320> friend<01:16:36.679> in<01:16:36.840> the<01:16:36.960> energy<01:16:37.320> Department

01:16:37.709 --> 01:16:37.719 align:start position:0%
um our friend in the energy Department
 

01:16:37.719 --> 01:16:40.390 align:start position:0%
um our friend in the energy Department
Aaron<01:16:38.000> Barry<01:16:38.320> Hill<01:16:38.719> is<01:16:39.000> aware<01:16:39.600> of<01:16:39.920> the<01:16:40.040> models

01:16:40.390 --> 01:16:40.400 align:start position:0%
Aaron Barry Hill is aware of the models
 

01:16:40.400 --> 01:16:44.430 align:start position:0%
Aaron Barry Hill is aware of the models
that<01:16:40.600> other<01:16:40.800> states<01:16:41.400> have<01:16:41.840> pursued<01:16:42.840> and<01:16:43.440> uh

01:16:44.430 --> 01:16:44.440 align:start position:0%
that other states have pursued and uh
 

01:16:44.440 --> 01:16:46.870 align:start position:0%
that other states have pursued and uh
their<01:16:45.440> how<01:16:45.639> how<01:16:45.840> other<01:16:46.000> models<01:16:46.320> of<01:16:46.480> citing

01:16:46.870 --> 01:16:46.880 align:start position:0%
their how how other models of citing
 

01:16:46.880 --> 01:16:49.590 align:start position:0%
their how how other models of citing
have<01:16:47.159> happened<01:16:48.159> uh<01:16:48.639> if<01:16:48.800> it's<01:16:49.320> if<01:16:49.440> it's

01:16:49.590 --> 01:16:49.600 align:start position:0%
have happened uh if it's if it's
 

01:16:49.600 --> 01:16:51.430 align:start position:0%
have happened uh if it's if it's
interesting<01:16:50.000> to<01:16:50.199> the<01:16:50.320> authority<01:16:51.159> I<01:16:51.239> think

01:16:51.430 --> 01:16:51.440 align:start position:0%
interesting to the authority I think
 

01:16:51.440 --> 01:16:53.910 align:start position:0%
interesting to the authority I think
Aaron<01:16:51.760> would<01:16:51.880> be<01:16:52.080> up<01:16:52.280> for<01:16:52.639> presenting

01:16:53.910 --> 01:16:53.920 align:start position:0%
Aaron would be up for presenting
 

01:16:53.920 --> 01:16:56.270 align:start position:0%
Aaron would be up for presenting
um<01:16:54.040> a<01:16:54.159> summary<01:16:54.480> of<01:16:54.639> other<01:16:54.880> states

01:16:56.270 --> 01:16:56.280 align:start position:0%
um a summary of other states
 

01:16:56.280 --> 01:16:59.310 align:start position:0%
um a summary of other states
to<01:16:57.280> share<01:16:57.600> with<01:16:57.760> authority<01:16:58.120> members<01:16:58.520> other

01:16:59.310 --> 01:16:59.320 align:start position:0%
to share with authority members other
 

01:16:59.320 --> 01:17:01.550 align:start position:0%
to share with authority members other
models<01:16:59.880> that<01:17:00.040> maybe<01:17:00.320> don't<01:17:00.600> take<01:17:00.920> the<01:17:01.120> control

01:17:01.550 --> 01:17:01.560 align:start position:0%
models that maybe don't take the control
 

01:17:01.560 --> 01:17:03.229 align:start position:0%
models that maybe don't take the control
completely<01:17:02.000> away<01:17:02.199> from<01:17:02.400> localities<01:17:02.920> maybe

01:17:03.229 --> 01:17:03.239 align:start position:0%
completely away from localities maybe
 

01:17:03.239 --> 01:17:05.430 align:start position:0%
completely away from localities maybe
you're<01:17:03.440> split<01:17:03.840> it<01:17:03.960> may<01:17:04.120> be<01:17:04.520> some<01:17:04.800> examples<01:17:05.199> of

01:17:05.430 --> 01:17:05.440 align:start position:0%
you're split it may be some examples of
 

01:17:05.440 --> 01:17:09.550 align:start position:0%
you're split it may be some examples of
where<01:17:05.960> no<01:17:06.520> local<01:17:07.520> um<01:17:07.960> zoning<01:17:08.440> Authority<01:17:08.880> is<01:17:09.280> is

01:17:09.550 --> 01:17:09.560 align:start position:0%
where no local um zoning Authority is is
 

01:17:09.560 --> 01:17:12.990 align:start position:0%
where no local um zoning Authority is is
exercise<01:17:10.560> so<01:17:10.920> just<01:17:11.040> a<01:17:11.199> few<01:17:11.440> ideas<01:17:11.960> but<01:17:12.719> very

01:17:12.990 --> 01:17:13.000 align:start position:0%
exercise so just a few ideas but very
 

01:17:13.000 --> 01:17:16.629 align:start position:0%
exercise so just a few ideas but very
open<01:17:13.400> to<01:17:14.400> recommendations<01:17:15.040> of<01:17:15.239> others<01:17:15.639> here

01:17:16.629 --> 01:17:16.639 align:start position:0%
open to recommendations of others here
 

01:17:16.639 --> 01:17:19.669 align:start position:0%
open to recommendations of others here
um<01:17:17.120> we'll<01:17:17.280> need<01:17:17.440> to<01:17:17.639> start<01:17:18.120> planning<01:17:18.800> and

01:17:19.669 --> 01:17:19.679 align:start position:0%
um we'll need to start planning and
 

01:17:19.679 --> 01:17:21.990 align:start position:0%
um we'll need to start planning and
getting<01:17:20.360> some<01:17:20.800> presentations<01:17:21.400> lined<01:17:21.719> up<01:17:21.840> for

01:17:21.990 --> 01:17:22.000 align:start position:0%
getting some presentations lined up for
 

01:17:22.000 --> 01:17:28.430 align:start position:0%
getting some presentations lined up for
a<01:17:22.239> September<01:17:22.639> meeting

01:17:28.430 --> 01:17:28.440 align:start position:0%
 
 

01:17:28.440 --> 01:17:30.110 align:start position:0%
 
we<01:17:28.960> dat

01:17:30.110 --> 01:17:30.120 align:start position:0%
we dat
 

01:17:30.120 --> 01:17:33.229 align:start position:0%
we dat
Fort<01:17:31.120> the<01:17:31.199> doodle<01:17:31.600> poll<01:17:32.600> no<01:17:32.760> I<01:17:32.840> didn't<01:17:33.040> send

01:17:33.229 --> 01:17:33.239 align:start position:0%
Fort the doodle poll no I didn't send
 

01:17:33.239 --> 01:17:35.550 align:start position:0%
Fort the doodle poll no I didn't send
the<01:17:33.320> doodle<01:17:33.639> poll<01:17:34.400> that<01:17:34.560> was<01:17:35.040> that<01:17:35.159> was<01:17:35.480> what

01:17:35.550 --> 01:17:35.560 align:start position:0%
the doodle poll that was that was what
 

01:17:35.560 --> 01:17:38.830 align:start position:0%
the doodle poll that was that was what
you<01:17:35.639> wanted<01:17:35.840> to<01:17:36.000> discuss<01:17:36.480> is<01:17:37.000> locking<01:17:37.840> in

01:17:38.830 --> 01:17:38.840 align:start position:0%
you wanted to discuss is locking in
 

01:17:38.840 --> 01:17:41.629 align:start position:0%
you wanted to discuss is locking in
dates<01:17:39.360> for<01:17:39.560> the<01:17:39.719> whole<01:17:39.920> year<01:17:40.719> yeah<01:17:40.920> in

01:17:41.629 --> 01:17:41.639 align:start position:0%
dates for the whole year yeah in
 

01:17:41.639 --> 01:17:45.470 align:start position:0%
dates for the whole year yeah in
2024<01:17:42.639> I<01:17:42.719> would<01:17:42.960> like<01:17:43.120> to<01:17:43.800> I<01:17:43.920> wish<01:17:44.159> cther<01:17:44.520> were

01:17:45.470 --> 01:17:45.480 align:start position:0%
2024 I would like to I wish cther were
 

01:17:45.480 --> 01:17:48.830 align:start position:0%
2024 I would like to I wish cther were
here<01:17:46.480> so<01:17:46.639> I<01:17:46.760> would<01:17:46.880> like<01:17:47.040> to<01:17:47.159> hear<01:17:47.840> Dominion

01:17:48.830 --> 01:17:48.840 align:start position:0%
here so I would like to hear Dominion
 

01:17:48.840 --> 01:17:50.189 align:start position:0%
here so I would like to hear Dominion
like<01:17:48.960> to<01:17:49.080> have<01:17:49.239> somebody<01:17:49.639> from<01:17:49.880> both<01:17:50.040> the

01:17:50.189 --> 01:17:50.199 align:start position:0%
like to have somebody from both the
 

01:17:50.199 --> 01:17:52.149 align:start position:0%
like to have somebody from both the
operations<01:17:50.760> transmission<01:17:51.320> operations<01:17:51.840> group

01:17:52.149 --> 01:17:52.159 align:start position:0%
operations transmission operations group
 

01:17:52.159 --> 01:17:54.590 align:start position:0%
operations transmission operations group
as<01:17:52.280> well<01:17:52.440> as<01:17:52.600> from<01:17:53.440> Planning<01:17:53.880> Group<01:17:54.239> just<01:17:54.400> to

01:17:54.590 --> 01:17:54.600 align:start position:0%
as well as from Planning Group just to
 

01:17:54.600 --> 01:17:57.070 align:start position:0%
as well as from Planning Group just to
get<01:17:54.880> how<01:17:55.199> they<01:17:55.320> do<01:17:55.560> their<01:17:55.840> processes<01:17:56.840> and<01:17:57.000> what

01:17:57.070 --> 01:17:57.080 align:start position:0%
get how they do their processes and what
 

01:17:57.080 --> 01:17:58.990 align:start position:0%
get how they do their processes and what
do<01:17:57.320> they<01:17:57.480> see<01:17:57.719> as<01:17:57.840> the<01:17:58.000> impediments<01:17:58.719> because<01:17:58.920> I

01:17:58.990 --> 01:17:59.000 align:start position:0%
do they see as the impediments because I
 

01:17:59.000 --> 01:18:01.350 align:start position:0%
do they see as the impediments because I
know<01:17:59.199> they're<01:17:59.639> challenged<01:18:00.639> they<01:18:00.760> are

01:18:01.350 --> 01:18:01.360 align:start position:0%
know they're challenged they are
 

01:18:01.360 --> 01:18:04.629 align:start position:0%
know they're challenged they are
frustrated<01:18:02.360> in<01:18:02.760> disclosure<01:18:03.760> company<01:18:04.120> I<01:18:04.320> work

01:18:04.629 --> 01:18:04.639 align:start position:0%
frustrated in disclosure company I work
 

01:18:04.639 --> 01:18:07.629 align:start position:0%
frustrated in disclosure company I work
for<01:18:05.080> we<01:18:05.280> have<01:18:05.400> a<01:18:05.560> relationship<01:18:06.080> with

01:18:07.629 --> 01:18:07.639 align:start position:0%
for we have a relationship with
 

01:18:07.639 --> 01:18:09.950 align:start position:0%
for we have a relationship with
dominum<01:18:08.639> we<01:18:08.760> know<01:18:09.080> some<01:18:09.239> of<01:18:09.320> the<01:18:09.480> challenges

01:18:09.950 --> 01:18:09.960 align:start position:0%
dominum we know some of the challenges
 

01:18:09.960 --> 01:18:14.350 align:start position:0%
dominum we know some of the challenges
they<01:18:10.080> are<01:18:10.400> facing<01:18:11.600> and<01:18:12.600> I<01:18:12.719> don't<01:18:13.280> know<01:18:13.719> if<01:18:14.239> you

01:18:14.350 --> 01:18:14.360 align:start position:0%
they are facing and I don't know if you
 

01:18:14.360 --> 01:18:15.790 align:start position:0%
they are facing and I don't know if you
know<01:18:14.520> they're<01:18:14.760> easily<01:18:15.159> overcome<01:18:15.679> just

01:18:15.790 --> 01:18:15.800 align:start position:0%
know they're easily overcome just
 

01:18:15.800 --> 01:18:17.430 align:start position:0%
know they're easily overcome just
because<01:18:16.040> the<01:18:16.199> regulatory<01:18:16.960> things<01:18:17.159> that

01:18:17.430 --> 01:18:17.440 align:start position:0%
because the regulatory things that
 

01:18:17.440 --> 01:18:21.350 align:start position:0%
because the regulatory things that
talked<01:18:17.920> about<01:18:19.360> earlier<01:18:20.360> uh<01:18:20.560> but<01:18:20.719> we<01:18:20.840> also<01:18:21.120> have

01:18:21.350 --> 01:18:21.360 align:start position:0%
talked about earlier uh but we also have
 

01:18:21.360 --> 01:18:23.270 align:start position:0%
talked about earlier uh but we also have
in<01:18:21.600> in<01:18:21.719> the<01:18:21.880> Commonwealth<01:18:22.440> we<01:18:22.639> have<01:18:23.000> American

01:18:23.270 --> 01:18:23.280 align:start position:0%
in in the Commonwealth we have American
 

01:18:23.280 --> 01:18:26.110 align:start position:0%
in in the Commonwealth we have American
Electric<01:18:23.639> Power<01:18:24.239> right<01:18:24.560> a<01:18:24.960> orol

01:18:26.110 --> 01:18:26.120 align:start position:0%
Electric Power right a orol
 

01:18:26.120 --> 01:18:29.629 align:start position:0%
Electric Power right a orol
Elric<01:18:27.120> and<01:18:27.239> I<01:18:27.320> think<01:18:27.600> they<01:18:28.280> they<01:18:28.440> too<01:18:29.360> although

01:18:29.629 --> 01:18:29.639 align:start position:0%
Elric and I think they they too although
 

01:18:29.639 --> 01:18:31.629 align:start position:0%
Elric and I think they they too although
they<01:18:29.760> have<01:18:29.920> a<01:18:30.199> very<01:18:30.560> very<01:18:30.760> small<01:18:31.120> footprint

01:18:31.629 --> 01:18:31.639 align:start position:0%
they have a very very small footprint
 

01:18:31.639 --> 01:18:33.950 align:start position:0%
they have a very very small footprint
relative<01:18:32.120> to<01:18:32.719> what<01:18:32.920> Dominion<01:18:33.400> has<01:18:33.639> I<01:18:33.719> think

01:18:33.950 --> 01:18:33.960 align:start position:0%
relative to what Dominion has I think
 

01:18:33.960 --> 01:18:35.629 align:start position:0%
relative to what Dominion has I think
they<01:18:34.120> too<01:18:34.639> have<01:18:34.760> some<01:18:35.080> perspective

01:18:35.629 --> 01:18:35.639 align:start position:0%
they too have some perspective
 

01:18:35.639 --> 01:18:36.709 align:start position:0%
they too have some perspective
especially<01:18:35.960> in

01:18:36.709 --> 01:18:36.719 align:start position:0%
especially in
 

01:18:36.719 --> 01:18:38.669 align:start position:0%
especially in
Appalachia<01:18:37.719> in<01:18:37.880> general<01:18:38.239> so<01:18:38.400> there's<01:18:38.560> going

01:18:38.669 --> 01:18:38.679 align:start position:0%
Appalachia in general so there's going
 

01:18:38.679 --> 01:18:40.830 align:start position:0%
Appalachia in general so there's going
to<01:18:38.760> be<01:18:39.000> some<01:18:39.120> of<01:18:39.239> the<01:18:39.360> same<01:18:39.639> resource

01:18:40.830 --> 01:18:40.840 align:start position:0%
to be some of the same resource
 

01:18:40.840 --> 01:18:45.669 align:start position:0%
to be some of the same resource
allocation<01:18:42.239> challenges<01:18:43.239> in<01:18:43.440> PJ<01:18:44.320> so<01:18:45.320> I<01:18:45.400> mean<01:18:45.520> to

01:18:45.669 --> 01:18:45.679 align:start position:0%
allocation challenges in PJ so I mean to
 

01:18:45.679 --> 01:18:47.870 align:start position:0%
allocation challenges in PJ so I mean to
the<01:18:45.800> extent<01:18:46.120> that<01:18:46.239> we<01:18:46.360> can<01:18:46.600> get<01:18:47.560> you<01:18:47.679> know

01:18:47.870 --> 01:18:47.880 align:start position:0%
the extent that we can get you know
 

01:18:47.880 --> 01:18:50.709 align:start position:0%
the extent that we can get you know
let's<01:18:48.080> let's<01:18:48.320> let's<01:18:48.520> talk<01:18:48.719> with<01:18:48.920> c<01:18:49.400> and<01:18:49.520> see<01:18:49.760> if

01:18:50.709 --> 01:18:50.719 align:start position:0%
let's let's let's talk with c and see if
 

01:18:50.719 --> 01:18:52.270 align:start position:0%
let's let's let's talk with c and see if
it<01:18:50.960> makes<01:18:51.199> sense<01:18:51.639> and<01:18:51.760> if<01:18:51.880> there's<01:18:52.080> no

01:18:52.270 --> 01:18:52.280 align:start position:0%
it makes sense and if there's no
 

01:18:52.280 --> 01:18:55.750 align:start position:0%
it makes sense and if there's no
conflict<01:18:53.040> love<01:18:53.199> to<01:18:53.440> have<01:18:54.199> dominion<01:18:55.199> tell<01:18:55.480> us

01:18:55.750 --> 01:18:55.760 align:start position:0%
conflict love to have dominion tell us
 

01:18:55.760 --> 01:18:57.350 align:start position:0%
conflict love to have dominion tell us
what<01:18:55.920> their<01:18:56.040> UPS<01:18:56.600> one<01:18:56.719> of<01:18:56.800> the<01:18:56.960> things<01:18:57.199> that

01:18:57.350 --> 01:18:57.360 align:start position:0%
what their UPS one of the things that
 

01:18:57.360 --> 01:19:00.350 align:start position:0%
what their UPS one of the things that
we're<01:18:57.679> ignoring<01:18:58.320> is<01:18:58.920> the<01:18:59.040> properties<01:18:59.960> and

01:19:00.350 --> 01:19:00.360 align:start position:0%
we're ignoring is the properties and
 

01:19:00.360 --> 01:19:02.550 align:start position:0%
we're ignoring is the properties and
they<01:19:00.480> have<01:19:00.600> a<01:19:00.719> lot<01:19:01.080> more<01:19:01.600> latitude<01:19:02.120> to<01:19:02.280> do

01:19:02.550 --> 01:19:02.560 align:start position:0%
they have a lot more latitude to do
 

01:19:02.560 --> 01:19:03.750 align:start position:0%
they have a lot more latitude to do
really<01:19:02.760> whatever<01:19:03.080> they<01:19:03.159> want<01:19:03.320> to<01:19:03.480> do

01:19:03.750 --> 01:19:03.760 align:start position:0%
really whatever they want to do
 

01:19:03.760 --> 01:19:05.390 align:start position:0%
really whatever they want to do
provideed<01:19:04.320> their

01:19:05.390 --> 01:19:05.400 align:start position:0%
provideed their
 

01:19:05.400 --> 01:19:11.629 align:start position:0%
provideed their
their<01:19:06.400> their<01:19:07.040> amers<01:19:08.400> agre<01:19:09.400> so<01:19:10.239> um<01:19:10.639> if<01:19:11.000> if<01:19:11.560> I

01:19:11.629 --> 01:19:11.639 align:start position:0%
their their amers agre so um if if I
 

01:19:11.639 --> 01:19:14.390 align:start position:0%
their their amers agre so um if if I
don't<01:19:12.000> know<01:19:13.000> if<01:19:13.320> I<01:19:13.400> don't<01:19:13.639> I'm<01:19:13.760> not<01:19:13.920> in<01:19:14.120> that

01:19:14.390 --> 01:19:14.400 align:start position:0%
don't know if I don't I'm not in that
 

01:19:14.400 --> 01:19:18.669 align:start position:0%
don't know if I don't I'm not in that
sector<01:19:14.960> though<01:19:15.520> but<01:19:16.360> well<01:19:16.520> I<01:19:17.080> I<01:19:17.760> I<01:19:17.840> am<01:19:18.440> okay

01:19:18.669 --> 01:19:18.679 align:start position:0%
sector though but well I I I am okay
 

01:19:18.679 --> 01:19:21.310 align:start position:0%
sector though but well I I I am okay
well<01:19:19.320> as<01:19:19.480> far<01:19:19.600> as<01:19:19.840> as<01:19:19.960> far<01:19:20.120> as<01:19:20.480> uh<01:19:20.719> the<01:19:20.840> gets<01:19:21.199> I'm

01:19:21.310 --> 01:19:21.320 align:start position:0%
well as far as as far as uh the gets I'm
 

01:19:21.320 --> 01:19:25.470 align:start position:0%
well as far as as far as uh the gets I'm
not<01:19:21.920> a<01:19:22.000> dealr<01:19:22.440> and<01:19:22.560> all<01:19:22.679> that<01:19:23.239> but<01:19:24.239> if<01:19:25.000> if<01:19:25.320> we

01:19:25.470 --> 01:19:25.480 align:start position:0%
not a dealr and all that but if if we
 

01:19:25.480 --> 01:19:27.229 align:start position:0%
not a dealr and all that but if if we
know<01:19:25.760> that<01:19:25.920> there<01:19:26.040> is<01:19:26.280> a<01:19:26.520> Cooperative<01:19:27.000> out

01:19:27.229 --> 01:19:27.239 align:start position:0%
know that there is a Cooperative out
 

01:19:27.239 --> 01:19:28.550 align:start position:0%
know that there is a Cooperative out
there<01:19:27.480> that

01:19:28.550 --> 01:19:28.560 align:start position:0%
there that
 

01:19:28.560 --> 01:19:32.750 align:start position:0%
there that
is<01:19:29.560> open<01:19:30.000> to<01:19:31.000> to<01:19:31.199> really<01:19:31.600> get<01:19:31.840> into<01:19:32.120> that<01:19:32.280> deter

01:19:32.750 --> 01:19:32.760 align:start position:0%
is open to to really get into that deter
 

01:19:32.760 --> 01:19:37.910 align:start position:0%
is open to to really get into that deter
how<01:19:32.920> much<01:19:33.080> it<01:19:33.400> does<01:19:34.400> open

01:19:37.910 --> 01:19:37.920 align:start position:0%
 
 

01:19:37.920 --> 01:19:40.550 align:start position:0%
 
upd<01:19:38.920> we<01:19:39.040> should

01:19:40.550 --> 01:19:40.560 align:start position:0%
upd we should
 

01:19:40.560 --> 01:19:44.110 align:start position:0%
upd we should
so<01:19:41.560> so<01:19:42.080> obviously<01:19:42.679> the<01:19:43.199> the<01:19:43.320> RO<01:19:43.600> Electric

01:19:44.110 --> 01:19:44.120 align:start position:0%
so so obviously the the RO Electric
 

01:19:44.120 --> 01:19:48.350 align:start position:0%
so so obviously the the RO Electric
Cooperative<01:19:45.600> groups<01:19:46.600> in<01:19:46.960> the<01:19:47.199> Commonwealth<01:19:48.199> I

01:19:48.350 --> 01:19:48.360 align:start position:0%
Cooperative groups in the Commonwealth I
 

01:19:48.360 --> 01:19:50.390 align:start position:0%
Cooperative groups in the Commonwealth I
I<01:19:48.440> think<01:19:48.600> there<01:19:48.679> are<01:19:48.800> a<01:19:48.960> couple<01:19:49.400> that<01:19:50.040> could<01:19:50.280> at

01:19:50.390 --> 01:19:50.400 align:start position:0%
I think there are a couple that could at
 

01:19:50.400 --> 01:19:52.709 align:start position:0%
I think there are a couple that could at
least<01:19:50.719> touch<01:19:51.040> base<01:19:51.400> with<01:19:52.040> they're<01:19:52.239> surrounded

01:19:52.709 --> 01:19:52.719 align:start position:0%
least touch base with they're surrounded
 

01:19:52.719 --> 01:19:55.510 align:start position:0%
least touch base with they're surrounded
they<01:19:52.960> get<01:19:53.080> their<01:19:53.239> power<01:19:53.560> from<01:19:54.280> from<01:19:54.440> Dominion

01:19:55.510 --> 01:19:55.520 align:start position:0%
they get their power from from Dominion
 

01:19:55.520 --> 01:19:58.470 align:start position:0%
they get their power from from Dominion
yeah<01:19:56.520> that<01:19:56.719> group<01:19:57.159> exactly<01:19:57.960> so<01:19:58.159> I<01:19:58.280> think

01:19:58.470 --> 01:19:58.480 align:start position:0%
yeah that group exactly so I think
 

01:19:58.480 --> 01:20:01.669 align:start position:0%
yeah that group exactly so I think
there's<01:19:59.159> that<01:19:59.480> I<01:19:59.600> think<01:19:59.760> there's<01:20:00.000> NOC<01:20:00.679> that

01:20:01.669 --> 01:20:01.679 align:start position:0%
there's that I think there's NOC that
 

01:20:01.679 --> 01:20:03.629 align:start position:0%
there's that I think there's NOC that
also<01:20:02.120> has<01:20:02.400> you<01:20:02.520> know

01:20:03.629 --> 01:20:03.639 align:start position:0%
also has you know
 

01:20:03.639 --> 01:20:06.189 align:start position:0%
also has you know
surrounded<01:20:04.639> get<01:20:04.840> of<01:20:05.120> power<01:20:05.400> so<01:20:05.880> there<01:20:05.960> are

01:20:06.189 --> 01:20:06.199 align:start position:0%
surrounded get of power so there are
 

01:20:06.199 --> 01:20:08.950 align:start position:0%
surrounded get of power so there are
certain<01:20:06.679> challenges<01:20:07.400> that<01:20:07.639> they

01:20:08.950 --> 01:20:08.960 align:start position:0%
certain challenges that they
 

01:20:08.960 --> 01:20:12.149 align:start position:0%
certain challenges that they
have<01:20:09.960> I<01:20:10.080> think<01:20:10.239> would<01:20:10.480> also<01:20:10.719> be<01:20:11.040> useful<01:20:12.040> and

01:20:12.149 --> 01:20:12.159 align:start position:0%
have I think would also be useful and
 

01:20:12.159 --> 01:20:14.149 align:start position:0%
have I think would also be useful and
you're<01:20:12.400> right<01:20:12.639> they<01:20:12.760> don't<01:20:13.000> have<01:20:13.199> nearly<01:20:13.600> the

01:20:14.149 --> 01:20:14.159 align:start position:0%
you're right they don't have nearly the
 

01:20:14.159 --> 01:20:17.070 align:start position:0%
you're right they don't have nearly the
constraint<01:20:15.159> issues<01:20:15.880> from<01:20:16.040> the<01:20:16.199> regulatory

01:20:17.070 --> 01:20:17.080 align:start position:0%
constraint issues from the regulatory
 

01:20:17.080 --> 01:20:20.149 align:start position:0%
constraint issues from the regulatory
they<01:20:17.159> don't<01:20:17.280> have<01:20:17.520> share<01:20:18.520> to<01:20:18.679> they<01:20:19.159> members

01:20:20.149 --> 01:20:20.159 align:start position:0%
they don't have share to they members
 

01:20:20.159 --> 01:20:20.750 align:start position:0%
they don't have share to they members
the

01:20:20.750 --> 01:20:20.760 align:start position:0%
the
 

01:20:20.760 --> 01:20:24.550 align:start position:0%
the
members<01:20:21.760> situation<01:20:22.480> yes

01:20:24.550 --> 01:20:24.560 align:start position:0%
members situation yes
 

01:20:24.560 --> 01:20:25.950 align:start position:0%
members situation yes
and<01:20:24.719> and<01:20:24.840> they<01:20:24.960> all<01:20:25.080> have<01:20:25.199> to<01:20:25.280> work<01:20:25.560> together

01:20:25.950 --> 01:20:25.960 align:start position:0%
and and they all have to work together
 

01:20:25.960 --> 01:20:27.750 align:start position:0%
and and they all have to work together
right<01:20:26.560> so<01:20:26.880> that<01:20:27.040> that's<01:20:27.199> the<01:20:27.360> nice<01:20:27.600> thing

01:20:27.750 --> 01:20:27.760 align:start position:0%
right so that that's the nice thing
 

01:20:27.760 --> 01:20:29.430 align:start position:0%
right so that that's the nice thing
about<01:20:28.000> it<01:20:28.199> is<01:20:28.360> that<01:20:28.520> if<01:20:28.639> you<01:20:28.760> can<01:20:29.000> get<01:20:29.199> some<01:20:29.320> of

01:20:29.430 --> 01:20:29.440 align:start position:0%
about it is that if you can get some of
 

01:20:29.440 --> 01:20:31.629 align:start position:0%
about it is that if you can get some of
the<01:20:29.560> smaller<01:20:29.880> clockers<01:20:30.440> to<01:20:31.199> and<01:20:31.320> then<01:20:31.480> there

01:20:31.629 --> 01:20:31.639 align:start position:0%
the smaller clockers to and then there
 

01:20:31.639 --> 01:20:36.709 align:start position:0%
the smaller clockers to and then there
are<01:20:32.199> with<01:20:32.400> Public<01:20:32.760> Power<01:20:33.679> there's<01:20:33.920> also<01:20:34.280> that

01:20:36.709 --> 01:20:36.719 align:start position:0%
 
 

01:20:36.719 --> 01:20:40.350 align:start position:0%
 
Avenue<01:20:37.719> although<01:20:38.000> no<01:20:38.480> is<01:20:38.600> not<01:20:38.920> in<01:20:39.120> that<01:20:39.360> group

01:20:40.350 --> 01:20:40.360 align:start position:0%
Avenue although no is not in that group
 

01:20:40.360 --> 01:20:43.070 align:start position:0%
Avenue although no is not in that group
they're<01:20:41.280> they're<01:20:41.440> not<01:20:41.639> in

01:20:43.070 --> 01:20:43.080 align:start position:0%
they're they're not in
 

01:20:43.080 --> 01:20:47.590 align:start position:0%
they're they're not in
the<01:20:44.080> the<01:20:44.239> managed<01:20:44.719> Cooperative

01:20:47.590 --> 01:20:47.600 align:start position:0%
 
 

01:20:47.600 --> 01:20:49.669 align:start position:0%
 
group<01:20:48.600> but<01:20:48.719> they're<01:20:48.840> still<01:20:49.400> the<01:20:49.520> same

01:20:49.669 --> 01:20:49.679 align:start position:0%
group but they're still the same
 

01:20:49.679 --> 01:20:51.709 align:start position:0%
group but they're still the same
pressure<01:20:50.159> stor<01:20:50.719> right<01:20:50.880> they<01:20:51.000> have<01:20:51.159> the<01:20:51.239> same

01:20:51.709 --> 01:20:51.719 align:start position:0%
pressure stor right they have the same
 

01:20:51.719 --> 01:20:54.390 align:start position:0%
pressure stor right they have the same
operations

01:20:54.390 --> 01:20:54.400 align:start position:0%
operations
 

01:20:54.400 --> 01:20:59.149 align:start position:0%
operations
so<01:20:54.719> Paul<01:20:55.000> if<01:20:55.440> uh<01:20:55.679> Dominion<01:20:56.199> a<01:20:56.719> or<01:20:57.600> co-ops<01:20:58.600> U

01:20:59.149 --> 01:20:59.159 align:start position:0%
so Paul if uh Dominion a or co-ops U
 

01:20:59.159 --> 01:21:01.910 align:start position:0%
so Paul if uh Dominion a or co-ops U
would<01:20:59.360> come<01:20:59.480> to<01:20:59.920> would<01:21:00.040> you<01:21:00.120> be<01:21:00.239> willing<01:21:00.480> to<01:21:01.120> uh

01:21:01.910 --> 01:21:01.920 align:start position:0%
would come to would you be willing to uh
 

01:21:01.920 --> 01:21:05.830 align:start position:0%
would come to would you be willing to uh
quarterback<01:21:02.639> that<01:21:03.280> for<01:21:04.280> and<01:21:04.520> check<01:21:04.800> in

01:21:05.830 --> 01:21:05.840 align:start position:0%
quarterback that for and check in
 

01:21:05.840 --> 01:21:08.110 align:start position:0%
quarterback that for and check in
and<01:21:06.840> see<01:21:07.040> if<01:21:07.199> they<01:21:07.320> have<01:21:07.440> an<01:21:07.600> interest<01:21:07.880> in

01:21:08.110 --> 01:21:08.120 align:start position:0%
and see if they have an interest in
 

01:21:08.120 --> 01:21:12.590 align:start position:0%
and see if they have an interest in
availability<01:21:09.120> to<01:21:10.120> perspectives<01:21:10.639> J<01:21:11.360> I'll<01:21:12.360> I<01:21:12.480> I

01:21:12.590 --> 01:21:12.600 align:start position:0%
availability to perspectives J I'll I I
 

01:21:12.600 --> 01:21:14.830 align:start position:0%
availability to perspectives J I'll I I
talk<01:21:12.800> to<01:21:12.920> Sam<01:21:13.159> Bromberg<01:21:13.679> for<01:21:13.960> the

01:21:14.830 --> 01:21:14.840 align:start position:0%
talk to Sam Bromberg for the
 

01:21:14.840 --> 01:21:17.030 align:start position:0%
talk to Sam Bromberg for the
co-ops<01:21:15.840> he's<01:21:15.960> sort<01:21:16.120> of<01:21:16.199> the<01:21:16.280> regulatory<01:21:16.719> brain

01:21:17.030 --> 01:21:17.040 align:start position:0%
co-ops he's sort of the regulatory brain
 

01:21:17.040 --> 01:21:19.070 align:start position:0%
co-ops he's sort of the regulatory brain
for<01:21:17.199> all<01:21:17.360> of<01:21:17.520> them

01:21:19.070 --> 01:21:19.080 align:start position:0%
for all of them
 

01:21:19.080 --> 01:21:21.629 align:start position:0%
for all of them
okay

01:21:21.629 --> 01:21:21.639 align:start position:0%
okay
 

01:21:21.639 --> 01:21:23.510 align:start position:0%
okay
so

01:21:23.510 --> 01:21:23.520 align:start position:0%
so
 

01:21:23.520 --> 01:21:25.790 align:start position:0%
so
another<01:21:23.840> issue<01:21:24.560> on<01:21:24.719> the<01:21:24.880> horizon<01:21:25.360> is<01:21:25.600> what

01:21:25.790 --> 01:21:25.800 align:start position:0%
another issue on the horizon is what
 

01:21:25.800 --> 01:21:28.390 align:start position:0%
another issue on the horizon is what
comes<01:21:26.000> out<01:21:26.120> of<01:21:26.280> this<01:21:26.440> HB<01:21:26.880> 206<01:21:27.560> group<01:21:28.000> I<01:21:28.080> went<01:21:28.239> to

01:21:28.390 --> 01:21:28.400 align:start position:0%
comes out of this HB 206 group I went to
 

01:21:28.400 --> 01:21:31.350 align:start position:0%
comes out of this HB 206 group I went to
that<01:21:28.560> meeting<01:21:29.000> yesterday<01:21:30.000> and<01:21:30.239> I'm<01:21:30.719> a<01:21:30.880> cynic

01:21:31.350 --> 01:21:31.360 align:start position:0%
that meeting yesterday and I'm a cynic
 

01:21:31.360 --> 01:21:34.149 align:start position:0%
that meeting yesterday and I'm a cynic
by<01:21:31.560> nature<01:21:32.159> but<01:21:33.159> whatever<01:21:33.520> comes<01:21:33.719> out<01:21:33.840> of<01:21:34.000> that

01:21:34.149 --> 01:21:34.159 align:start position:0%
by nature but whatever comes out of that
 

01:21:34.159 --> 01:21:36.110 align:start position:0%
by nature but whatever comes out of that
PBR<01:21:34.719> modification<01:21:35.400> can<01:21:35.560> have<01:21:35.679> a<01:21:35.880> really

01:21:36.110 --> 01:21:36.120 align:start position:0%
PBR modification can have a really
 

01:21:36.120 --> 01:21:39.510 align:start position:0%
PBR modification can have a really
chilling<01:21:36.600> effect<01:21:37.000> on<01:21:37.159> the<01:21:37.800> market<01:21:38.800> and

01:21:39.510 --> 01:21:39.520 align:start position:0%
chilling effect on the market and
 

01:21:39.520 --> 01:21:42.149 align:start position:0%
chilling effect on the market and
I<01:21:40.520> might<01:21:40.840> put<01:21:41.080> one<01:21:41.199> of<01:21:41.320> our<01:21:41.480> guests<01:21:41.840> on<01:21:42.000> the

01:21:42.149 --> 01:21:42.159 align:start position:0%
I might put one of our guests on the
 

01:21:42.159 --> 01:21:46.110 align:start position:0%
I might put one of our guests on the
spot<01:21:42.480> here<01:21:42.719> to<01:21:43.040> get<01:21:43.280> his

01:21:46.110 --> 01:21:46.120 align:start position:0%
 
 

01:21:46.120 --> 01:21:50.790 align:start position:0%
 
opinion

01:21:50.790 --> 01:21:50.800 align:start position:0%
 
 

01:21:50.800 --> 01:21:54.990 align:start position:0%
 
well<01:21:51.800> part<01:21:52.360> C

01:21:54.990 --> 01:21:55.000 align:start position:0%
 
 

01:21:55.000 --> 01:21:57.750 align:start position:0%
 
richer<01:21:56.000> with<01:21:56.239> me<01:21:56.480> all<01:21:56.600> right<01:21:56.719> I<01:21:57.199> the<01:21:57.320> camera<01:21:57.639> on

01:21:57.750 --> 01:21:57.760 align:start position:0%
richer with me all right I the camera on
 

01:21:57.760 --> 01:21:59.390 align:start position:0%
richer with me all right I the camera on
me<01:21:57.960> too

01:21:59.390 --> 01:21:59.400 align:start position:0%
me too
 

01:21:59.400 --> 01:22:02.990 align:start position:0%
me too
so<01:22:00.400> uh<01:22:01.000> I<01:22:01.199> I<01:22:01.280> can<01:22:01.440> appreciate<01:22:02.040> you<01:22:02.120> know<01:22:02.360> the

01:22:02.990 --> 01:22:03.000 align:start position:0%
so uh I I can appreciate you know the
 

01:22:03.000 --> 01:22:06.950 align:start position:0%
so uh I I can appreciate you know the
perspective<01:22:03.760> on<01:22:04.040> that<01:22:04.880> um<01:22:05.719> part<01:22:05.840> of<01:22:05.960> my<01:22:06.600> job

01:22:06.950 --> 01:22:06.960 align:start position:0%
perspective on that um part of my job
 

01:22:06.960 --> 01:22:09.510 align:start position:0%
perspective on that um part of my job
responsibilities<01:22:07.639> is<01:22:07.800> to<01:22:08.239> be<01:22:08.440> The<01:22:08.600> Optimist

01:22:09.510 --> 01:22:09.520 align:start position:0%
responsibilities is to be The Optimist
 

01:22:09.520 --> 01:22:11.990 align:start position:0%
responsibilities is to be The Optimist
sometimes<01:22:09.800> as<01:22:09.960> the<01:22:10.080> solar<01:22:10.480> developer<01:22:11.480> uh<01:22:11.719> and

01:22:11.990 --> 01:22:12.000 align:start position:0%
sometimes as the solar developer uh and
 

01:22:12.000 --> 01:22:14.510 align:start position:0%
sometimes as the solar developer uh and
having<01:22:12.280> worked<01:22:12.560> on<01:22:12.760> that<01:22:13.080> two6<01:22:14.080> regulatory

01:22:14.510 --> 01:22:14.520 align:start position:0%
having worked on that two6 regulatory
 

01:22:14.520 --> 01:22:16.990 align:start position:0%
having worked on that two6 regulatory
advisory<01:22:14.960> panel<01:22:15.520> both<01:22:15.800> last<01:22:16.040> summer<01:22:16.520> and<01:22:16.760> this

01:22:16.990 --> 01:22:17.000 align:start position:0%
advisory panel both last summer and this
 

01:22:17.000 --> 01:22:19.910 align:start position:0%
advisory panel both last summer and this
summer<01:22:18.000> I<01:22:18.080> see<01:22:18.239> a<01:22:18.360> lot<01:22:18.520> more<01:22:18.800> progress<01:22:19.639> being

01:22:19.910 --> 01:22:19.920 align:start position:0%
summer I see a lot more progress being
 

01:22:19.920 --> 01:22:23.270 align:start position:0%
summer I see a lot more progress being
made<01:22:20.199> this<01:22:20.400> year<01:22:21.159> um<01:22:21.560> in

01:22:23.270 --> 01:22:23.280 align:start position:0%
made this year um in
 

01:22:23.280 --> 01:22:28.350 align:start position:0%
made this year um in
Bally<01:22:24.320> uh<01:22:25.320> finding<01:22:25.679> a<01:22:26.239> structure<01:22:27.239> that<01:22:27.920> allows

01:22:28.350 --> 01:22:28.360 align:start position:0%
Bally uh finding a structure that allows
 

01:22:28.360 --> 01:22:31.270 align:start position:0%
Bally uh finding a structure that allows
for<01:22:28.800> inputs<01:22:29.320> from<01:22:29.560> various<01:22:29.880> stakeholders<01:22:30.800> to

01:22:31.270 --> 01:22:31.280 align:start position:0%
for inputs from various stakeholders to
 

01:22:31.280 --> 01:22:33.070 align:start position:0%
for inputs from various stakeholders to
calculate<01:22:31.800> what<01:22:31.920> the<01:22:32.000> ultimate<01:22:32.360> mitigation

01:22:33.070 --> 01:22:33.080 align:start position:0%
calculate what the ultimate mitigation
 

01:22:33.080 --> 01:22:36.189 align:start position:0%
calculate what the ultimate mitigation
would<01:22:33.440> be<01:22:34.440> um<01:22:35.320> I<01:22:35.400> don't<01:22:35.520> know<01:22:35.719> that<01:22:35.960> you<01:22:36.080> know

01:22:36.189 --> 01:22:36.199 align:start position:0%
would be um I don't know that you know
 

01:22:36.199 --> 01:22:37.709 align:start position:0%
would be um I don't know that you know
it<01:22:36.280> would<01:22:36.440> be<01:22:36.719> certainly<01:22:37.159> time<01:22:37.400> here<01:22:37.600> to

01:22:37.709 --> 01:22:37.719 align:start position:0%
it would be certainly time here to
 

01:22:37.719 --> 01:22:39.070 align:start position:0%
it would be certainly time here to
require<01:22:38.040> this<01:22:38.159> agenda<01:22:38.440> to<01:22:38.520> go<01:22:38.679> into<01:22:38.800> any<01:22:38.960> of

01:22:39.070 --> 01:22:39.080 align:start position:0%
require this agenda to go into any of
 

01:22:39.080 --> 01:22:40.430 align:start position:0%
require this agenda to go into any of
those<01:22:39.280> details<01:22:39.679> and<01:22:39.800> there<01:22:39.920> are<01:22:40.040> a<01:22:40.159> bunch<01:22:40.320> of

01:22:40.430 --> 01:22:40.440 align:start position:0%
those details and there are a bunch of
 

01:22:40.440 --> 01:22:43.750 align:start position:0%
those details and there are a bunch of
other<01:22:40.600> like<01:22:41.000> for<01:22:42.000> uh<01:22:42.159> limitations<01:22:42.760> on<01:22:42.920> it<01:22:43.560> um

01:22:43.750 --> 01:22:43.760 align:start position:0%
other like for uh limitations on it um
 

01:22:43.760 --> 01:22:45.470 align:start position:0%
other like for uh limitations on it um
but<01:22:43.880> what<01:22:43.960> I<01:22:44.080> would<01:22:44.199> say<01:22:44.360> is<01:22:44.520> just<01:22:44.719> that<01:22:45.360> it's

01:22:45.470 --> 01:22:45.480 align:start position:0%
but what I would say is just that it's
 

01:22:45.480 --> 01:22:48.550 align:start position:0%
but what I would say is just that it's
been<01:22:45.600> a<01:22:45.679> lengthy<01:22:46.159> process<01:22:46.960> and<01:22:47.120> I<01:22:47.239> think<01:22:47.600> that

01:22:48.550 --> 01:22:48.560 align:start position:0%
been a lengthy process and I think that
 

01:22:48.560 --> 01:22:50.790 align:start position:0%
been a lengthy process and I think that
you<01:22:48.840> everyone<01:22:49.280> has<01:22:49.920> recognized<01:22:50.520> need<01:22:50.679> to

01:22:50.790 --> 01:22:50.800 align:start position:0%
you everyone has recognized need to
 

01:22:50.800 --> 01:22:53.870 align:start position:0%
you everyone has recognized need to
acknowledge<01:22:51.239> the<01:22:51.440> fact<01:22:51.639> that<01:22:52.159> house<01:22:52.840> six<01:22:53.679> has

01:22:53.870 --> 01:22:53.880 align:start position:0%
acknowledge the fact that house six has
 

01:22:53.880 --> 01:22:55.830 align:start position:0%
acknowledge the fact that house six has
already<01:22:54.280> set<01:22:54.639> the<01:22:54.840> fact<01:22:55.120> that<01:22:55.400> there<01:22:55.560> needs<01:22:55.719> to

01:22:55.830 --> 01:22:55.840 align:start position:0%
already set the fact that there needs to
 

01:22:55.840 --> 01:22:58.030 align:start position:0%
already set the fact that there needs to
be<01:22:56.080> mitigation<01:22:57.080> for<01:22:57.199> solar<01:22:57.520> projects<01:22:57.840> have

01:22:58.030 --> 01:22:58.040 align:start position:0%
be mitigation for solar projects have
 

01:22:58.040 --> 01:23:01.110 align:start position:0%
be mitigation for solar projects have
more<01:22:58.159> than<01:22:58.280> 10<01:22:58.440> acres<01:22:58.679> of<01:22:58.800> Prim<01:22:59.360> farmway<01:23:00.360> or<01:23:00.800> 50

01:23:01.110 --> 01:23:01.120 align:start position:0%
more than 10 acres of Prim farmway or 50
 

01:23:01.120 --> 01:23:03.950 align:start position:0%
more than 10 acres of Prim farmway or 50
acres<01:23:01.480> of<01:23:01.760> of<01:23:01.920> for<01:23:02.280> land<01:23:03.280> and<01:23:03.360> so<01:23:03.560> when<01:23:03.679> you

01:23:03.950 --> 01:23:03.960 align:start position:0%
acres of of for land and so when you
 

01:23:03.960 --> 01:23:06.149 align:start position:0%
acres of of for land and so when you
when<01:23:04.040> you<01:23:04.239> hit<01:23:04.480> those<01:23:04.719> thresholds<01:23:05.719> that<01:23:05.960> needs

01:23:06.149 --> 01:23:06.159 align:start position:0%
when you hit those thresholds that needs
 

01:23:06.159 --> 01:23:08.790 align:start position:0%
when you hit those thresholds that needs
a<01:23:06.239> tribal<01:23:06.800> process<01:23:07.679> and<01:23:07.800> so<01:23:08.199> the<01:23:08.360> productive

01:23:08.790 --> 01:23:08.800 align:start position:0%
a tribal process and so the productive
 

01:23:08.800 --> 01:23:11.990 align:start position:0%
a tribal process and so the productive
part<01:23:09.040> has<01:23:09.239> been<01:23:10.120> now<01:23:10.440> there<01:23:10.560> is<01:23:10.719> a<01:23:11.000> construct

01:23:11.990 --> 01:23:12.000 align:start position:0%
part has been now there is a construct
 

01:23:12.000 --> 01:23:14.149 align:start position:0%
part has been now there is a construct
to<01:23:12.199> facilitate<01:23:12.840> that<01:23:13.120> starting<01:23:13.560> with

01:23:14.149 --> 01:23:14.159 align:start position:0%
to facilitate that starting with
 

01:23:14.159 --> 01:23:15.990 align:start position:0%
to facilitate that starting with
calculating<01:23:14.639> the<01:23:14.800> amount<01:23:14.960> of<01:23:15.080> land<01:23:15.719> based

01:23:15.990 --> 01:23:16.000 align:start position:0%
calculating the amount of land based
 

01:23:16.000 --> 01:23:18.790 align:start position:0%
calculating the amount of land based
upon<01:23:16.239> certain<01:23:16.679> macro<01:23:17.000> level<01:23:17.360> data<01:23:18.120> onsite

01:23:18.790 --> 01:23:18.800 align:start position:0%
upon certain macro level data onsite
 

01:23:18.800 --> 01:23:20.950 align:start position:0%
upon certain macro level data onsite
verifications<01:23:19.800> and<01:23:19.960> other<01:23:20.239> types<01:23:20.400> of<01:23:20.600> credits

01:23:20.950 --> 01:23:20.960 align:start position:0%
verifications and other types of credits
 

01:23:20.960 --> 01:23:22.910 align:start position:0%
verifications and other types of credits
that<01:23:21.040> can<01:23:21.199> be<01:23:21.360> applied<01:23:21.719> to<01:23:21.960> projects<01:23:22.679> even

01:23:22.910 --> 01:23:22.920 align:start position:0%
that can be applied to projects even
 

01:23:22.920 --> 01:23:24.870 align:start position:0%
that can be applied to projects even
they<01:23:23.040> incorporate<01:23:23.520> AC<01:23:23.719> Vols<01:23:24.280> or<01:23:24.440> other<01:23:24.679> types

01:23:24.870 --> 01:23:24.880 align:start position:0%
they incorporate AC Vols or other types
 

01:23:24.880 --> 01:23:27.669 align:start position:0%
they incorporate AC Vols or other types
of<01:23:25.239> elements<01:23:26.239> um<01:23:26.480> that<01:23:26.719> still<01:23:27.199> you<01:23:27.320> know<01:23:27.440> help

01:23:27.669 --> 01:23:27.679 align:start position:0%
of elements um that still you know help
 

01:23:27.679 --> 01:23:30.310 align:start position:0%
of elements um that still you know help
sustain<01:23:28.199> mul<01:23:28.760> qualic<01:23:29.199> economies<01:23:29.960> so<01:23:30.120> all

01:23:30.310 --> 01:23:30.320 align:start position:0%
sustain mul qualic economies so all
 

01:23:30.320 --> 01:23:32.270 align:start position:0%
sustain mul qualic economies so all
that's<01:23:30.600> being<01:23:30.880> put<01:23:31.199> together<01:23:31.880> um<01:23:32.080> kind<01:23:32.199> of

01:23:32.270 --> 01:23:32.280 align:start position:0%
that's being put together um kind of
 

01:23:32.280 --> 01:23:35.270 align:start position:0%
that's being put together um kind of
like<01:23:32.360> you<01:23:32.719> do<01:23:32.920> like<01:23:33.120> big<01:23:33.360> old<01:23:33.840> big<01:23:34.040> old<01:23:34.320> pot<01:23:35.040> for

01:23:35.270 --> 01:23:35.280 align:start position:0%
like you do like big old big old pot for
 

01:23:35.280 --> 01:23:38.149 align:start position:0%
like you do like big old big old pot for
folks<01:23:35.480> to<01:23:35.600> stir<01:23:35.960> up<01:23:36.239> and<01:23:36.960> make<01:23:37.199> comments<01:23:37.520> on

01:23:38.149 --> 01:23:38.159 align:start position:0%
folks to stir up and make comments on
 

01:23:38.159 --> 01:23:40.430 align:start position:0%
folks to stir up and make comments on
but<01:23:38.280> I<01:23:38.360> do<01:23:38.560> think<01:23:38.840> we're<01:23:39.800> um<01:23:39.920> in<01:23:40.000> a<01:23:40.120> much<01:23:40.239> better

01:23:40.430 --> 01:23:40.440 align:start position:0%
but I do think we're um in a much better
 

01:23:40.440 --> 01:23:42.750 align:start position:0%
but I do think we're um in a much better
place<01:23:40.600> than<01:23:40.719> we<01:23:40.800> were<01:23:41.040> last<01:23:41.280> year<01:23:41.920> and<01:23:42.360> um<01:23:42.639> you

01:23:42.750 --> 01:23:42.760 align:start position:0%
place than we were last year and um you
 

01:23:42.760 --> 01:23:44.350 align:start position:0%
place than we were last year and um you
know<01:23:42.880> feeling<01:23:43.360> more<01:23:43.520> optimistic<01:23:43.960> that<01:23:44.080> we

01:23:44.350 --> 01:23:44.360 align:start position:0%
know feeling more optimistic that we
 

01:23:44.360 --> 01:23:49.709 align:start position:0%
know feeling more optimistic that we
have<01:23:45.000> something<01:23:45.440> that<01:23:46.320> D<01:23:47.320> submit<01:23:47.679> the<01:23:48.040> years

01:23:49.709 --> 01:23:49.719 align:start position:0%
have something that D submit the years
 

01:23:49.719 --> 01:23:53.390 align:start position:0%
have something that D submit the years
rep<01:23:50.719> let<01:23:50.800> me<01:23:51.000> ask<01:23:51.920> I'm<01:23:52.040> kind<01:23:52.159> of<01:23:52.280> about<01:23:52.760> on<01:23:52.920> stre

01:23:53.390 --> 01:23:53.400 align:start position:0%
rep let me ask I'm kind of about on stre
 

01:23:53.400 --> 01:23:55.310 align:start position:0%
rep let me ask I'm kind of about on stre
so<01:23:54.360> the

01:23:55.310 --> 01:23:55.320 align:start position:0%
so the
 

01:23:55.320 --> 01:23:58.950 align:start position:0%
so the
uh<01:23:56.320> I<01:23:56.440> was<01:23:56.560> on<01:23:56.639> the<01:23:56.760> ride<01:23:57.639> three<01:23:57.840> years<01:23:58.040> ago<01:23:58.840> The

01:23:58.950 --> 01:23:58.960 align:start position:0%
uh I was on the ride three years ago The
 

01:23:58.960 --> 01:24:03.070 align:start position:0%
uh I was on the ride three years ago The
regat<01:23:59.440> Advisory<01:23:59.880> panel<01:24:00.560> for<01:24:00.800> the<01:24:00.960> the<01:24:01.360> new<01:24:02.000> PBR

01:24:03.070 --> 01:24:03.080 align:start position:0%
regat Advisory panel for the the new PBR
 

01:24:03.080 --> 01:24:04.590 align:start position:0%
regat Advisory panel for the the new PBR
rules

01:24:04.590 --> 01:24:04.600 align:start position:0%
rules
 

01:24:04.600 --> 01:24:07.390 align:start position:0%
rules
um<01:24:05.600> that<01:24:05.880> I<01:24:06.080> I<01:24:06.280> I'm<01:24:06.440> pretty<01:24:06.600> sure<01:24:06.880> that's<01:24:07.080> never

01:24:07.390 --> 01:24:07.400 align:start position:0%
um that I I I'm pretty sure that's never
 

01:24:07.400 --> 01:24:09.110 align:start position:0%
um that I I I'm pretty sure that's never
been<01:24:07.600> implemented<01:24:08.080> that's<01:24:08.239> still<01:24:08.480> sitting

01:24:09.110 --> 01:24:09.120 align:start position:0%
been implemented that's still sitting
 

01:24:09.120 --> 01:24:11.830 align:start position:0%
been implemented that's still sitting
somewhere<01:24:10.080> being<01:24:10.400> reviewed<01:24:11.400> so<01:24:11.560> is<01:24:11.679> this

01:24:11.830 --> 01:24:11.840 align:start position:0%
somewhere being reviewed so is this
 

01:24:11.840 --> 01:24:13.910 align:start position:0%
somewhere being reviewed so is this
sueding<01:24:12.520> that<01:24:12.760> is<01:24:12.840> that<01:24:13.000> going<01:24:13.120> to<01:24:13.560> so<01:24:13.719> it's

01:24:13.910 --> 01:24:13.920 align:start position:0%
sueding that is that going to so it's
 

01:24:13.920 --> 01:24:16.510 align:start position:0%
sueding that is that going to so it's
gonna<01:24:14.400> it<01:24:14.600> does<01:24:15.000> they<01:24:15.239> they're<01:24:16.000> moving<01:24:16.320> a

01:24:16.510 --> 01:24:16.520 align:start position:0%
gonna it does they they're moving a
 

01:24:16.520 --> 01:24:19.229 align:start position:0%
gonna it does they they're moving a
parallel<01:24:16.920> so<01:24:17.040> you<01:24:17.120> are<01:24:17.360> correct<01:24:18.120> that<01:24:18.840> the<01:24:19.080> the

01:24:19.229 --> 01:24:19.239 align:start position:0%
parallel so you are correct that the the
 

01:24:19.239 --> 01:24:23.030 align:start position:0%
parallel so you are correct that the the
W<01:24:19.600> that<01:24:19.760> addressed<01:24:20.480> eqs<01:24:21.480> uh

01:24:23.030 --> 01:24:23.040 align:start position:0%
W that addressed eqs uh
 

01:24:23.040 --> 01:24:26.070 align:start position:0%
W that addressed eqs uh
modifications<01:24:24.040> for<01:24:24.199> solar<01:24:25.159> a<01:24:25.239> couple<01:24:25.520> years

01:24:26.070 --> 01:24:26.080 align:start position:0%
modifications for solar a couple years
 

01:24:26.080 --> 01:24:28.790 align:start position:0%
modifications for solar a couple years
ago<01:24:27.080> that<01:24:27.280> process<01:24:27.800> more<01:24:27.920> or<01:24:28.080> less<01:24:28.239> can<01:24:28.440> puted

01:24:28.790 --> 01:24:28.800 align:start position:0%
ago that process more or less can puted
 

01:24:28.800 --> 01:24:31.430 align:start position:0%
ago that process more or less can puted
through<01:24:28.960> the<01:24:29.080> state<01:24:29.679> discussions<01:24:30.280> but<01:24:30.560> then

01:24:31.430 --> 01:24:31.440 align:start position:0%
through the state discussions but then
 

01:24:31.440 --> 01:24:33.590 align:start position:0%
through the state discussions but then
um<01:24:31.719> didn't<01:24:32.040> proceed<01:24:32.400> into<01:24:32.639> actually<01:24:32.960> being

01:24:33.590 --> 01:24:33.600 align:start position:0%
um didn't proceed into actually being
 

01:24:33.600 --> 01:24:36.229 align:start position:0%
um didn't proceed into actually being
and<01:24:33.679> then<01:24:33.840> Co<01:24:34.159> kind<01:24:34.239> of<01:24:34.320> shut<01:24:34.560> down<01:24:34.760> the<01:24:35.239> talks

01:24:36.229 --> 01:24:36.239 align:start position:0%
and then Co kind of shut down the talks
 

01:24:36.239 --> 01:24:39.430 align:start position:0%
and then Co kind of shut down the talks
and<01:24:36.400> so<01:24:37.400> a<01:24:37.560> part<01:24:37.719> of<01:24:37.880> this<01:24:38.120> yes<01:24:38.320> BQ<01:24:38.760> I<01:24:38.880> think<01:24:39.080> is

01:24:39.430 --> 01:24:39.440 align:start position:0%
and so a part of this yes BQ I think is
 

01:24:39.440 --> 01:24:42.709 align:start position:0%
and so a part of this yes BQ I think is
envisioning<01:24:40.440> um<01:24:40.960> folding<01:24:41.360> in<01:24:41.520> some<01:24:41.719> elements

01:24:42.709 --> 01:24:42.719 align:start position:0%
envisioning um folding in some elements
 

01:24:42.719 --> 01:24:45.310 align:start position:0%
envisioning um folding in some elements
from<01:24:43.119> those<01:24:43.639> discussions<01:24:44.639> as<01:24:44.719> a<01:24:44.920> part<01:24:45.080> of

01:24:45.310 --> 01:24:45.320 align:start position:0%
from those discussions as a part of
 

01:24:45.320 --> 01:24:48.430 align:start position:0%
from those discussions as a part of
their

01:24:48.430 --> 01:24:48.440 align:start position:0%
 
 

01:24:48.440 --> 01:24:50.870 align:start position:0%
 
reations<01:24:49.440> the<01:24:49.600> one<01:24:49.880> thing<01:24:50.239> that<01:24:50.360> was<01:24:50.600> just

01:24:50.870 --> 01:24:50.880 align:start position:0%
reations the one thing that was just
 

01:24:50.880 --> 01:24:53.510 align:start position:0%
reations the one thing that was just
huge<01:24:51.440> in<01:24:51.719> in<01:24:51.800> the<01:24:52.480> the<01:24:52.800> recommendations<01:24:53.320> that

01:24:53.510 --> 01:24:53.520 align:start position:0%
huge in in the the recommendations that
 

01:24:53.520 --> 01:24:56.510 align:start position:0%
huge in in the the recommendations that
came<01:24:53.679> out<01:24:53.800> of<01:24:53.960> that<01:24:54.119> group<01:24:54.920> was<01:24:55.920> mitigation

01:24:56.510 --> 01:24:56.520 align:start position:0%
came out of that group was mitigation
 

01:24:56.520 --> 01:25:00.950 align:start position:0%
came out of that group was mitigation
for<01:24:56.840> the<01:24:57.360> environmental<01:24:58.560> zones<01:24:59.560> I<01:24:59.760> can't

01:25:00.950 --> 01:25:00.960 align:start position:0%
for the environmental zones I can't
 

01:25:00.960 --> 01:25:05.990 align:start position:0%
for the environmental zones I can't
that<01:25:01.960> yes<01:25:02.480> the<01:25:02.679> cores<01:25:03.360> yeah<01:25:04.360> um<01:25:04.880> that<01:25:05.080> was<01:25:05.600> I<01:25:05.880> it

01:25:05.990 --> 01:25:06.000 align:start position:0%
that yes the cores yeah um that was I it
 

01:25:06.000 --> 01:25:07.950 align:start position:0%
that yes the cores yeah um that was I it
was<01:25:06.159> just<01:25:06.360> so<01:25:06.679> vague<01:25:07.000> and<01:25:07.400> the<01:25:07.520> mitigation

01:25:07.950 --> 01:25:07.960 align:start position:0%
was just so vague and the mitigation
 

01:25:07.960 --> 01:25:10.510 align:start position:0%
was just so vague and the mitigation
that<01:25:08.080> would<01:25:08.239> be<01:25:08.400> required<01:25:08.960> that<01:25:09.239> it<01:25:09.440> it<01:25:09.600> just

01:25:10.510 --> 01:25:10.520 align:start position:0%
that would be required that it it just
 

01:25:10.520 --> 01:25:11.870 align:start position:0%
that would be required that it it just
that<01:25:10.719> was<01:25:10.880> is<01:25:11.000> that<01:25:11.119> going<01:25:11.239> to<01:25:11.320> be<01:25:11.480> addressed

01:25:11.870 --> 01:25:11.880 align:start position:0%
that was is that going to be addressed
 

01:25:11.880 --> 01:25:14.109 align:start position:0%
that was is that going to be addressed
at<01:25:12.000> all<01:25:12.239> is<01:25:12.400> that<01:25:12.679> I<01:25:12.760> think<01:25:12.880> it<01:25:12.960> will<01:25:13.159> be<01:25:13.560> y<01:25:13.760> so

01:25:14.109 --> 01:25:14.119 align:start position:0%
at all is that I think it will be y so
 

01:25:14.119 --> 01:25:16.390 align:start position:0%
at all is that I think it will be y so
it's<01:25:14.280> all<01:25:14.679> to<01:25:14.880> be<01:25:15.080> determined<01:25:15.480> in<01:25:15.600> terms<01:25:15.840> of

01:25:16.390 --> 01:25:16.400 align:start position:0%
it's all to be determined in terms of
 

01:25:16.400 --> 01:25:19.030 align:start position:0%
it's all to be determined in terms of
what<01:25:16.600> the<01:25:16.840> deposit<01:25:17.239> puts<01:25:17.480> out<01:25:18.000> but<01:25:18.400> uh<01:25:18.800> that's

01:25:19.030 --> 01:25:19.040 align:start position:0%
what the deposit puts out but uh that's
 

01:25:19.040 --> 01:25:21.950 align:start position:0%
what the deposit puts out but uh that's
one<01:25:19.159> of<01:25:19.280> the<01:25:19.480> factors<01:25:20.040> it<01:25:20.159> would<01:25:20.360> be<01:25:21.159> way<01:25:21.719> when

01:25:21.950 --> 01:25:21.960 align:start position:0%
one of the factors it would be way when
 

01:25:21.960 --> 01:25:22.830 align:start position:0%
one of the factors it would be way when
C

01:25:22.830 --> 01:25:22.840 align:start position:0%
C
 

01:25:22.840 --> 01:25:24.229 align:start position:0%
C
what's<01:25:23.080> the<01:25:23.199> amount<01:25:23.400> of

01:25:24.229 --> 01:25:24.239 align:start position:0%
what's the amount of
 

01:25:24.239 --> 01:25:27.229 align:start position:0%
what's the amount of
mitigation<01:25:25.239> maybe<01:25:26.080> problem<01:25:26.600> because<01:25:26.800> when

01:25:27.229 --> 01:25:27.239 align:start position:0%
mitigation maybe problem because when
 

01:25:27.239 --> 01:25:29.990 align:start position:0%
mitigation maybe problem because when
DEQ<01:25:28.239> um<01:25:28.560> sent<01:25:28.840> their<01:25:29.040> final

01:25:29.990 --> 01:25:30.000 align:start position:0%
DEQ um sent their final
 

01:25:30.000 --> 01:25:31.590 align:start position:0%
DEQ um sent their final
recommendations

01:25:31.590 --> 01:25:31.600 align:start position:0%
recommendations
 

01:25:31.600 --> 01:25:34.669 align:start position:0%
recommendations
to<01:25:32.600> I<01:25:32.760> work<01:25:32.960> with<01:25:33.080> the<01:25:33.199> governor<01:25:34.119> or

01:25:34.669 --> 01:25:34.679 align:start position:0%
to I work with the governor or
 

01:25:34.679 --> 01:25:38.030 align:start position:0%
to I work with the governor or
Department<01:25:34.960> of<01:25:35.080> energy<01:25:35.400> whoever<01:25:35.719> went<01:25:36.239> to<01:25:37.239> um

01:25:38.030 --> 01:25:38.040 align:start position:0%
Department of energy whoever went to um
 

01:25:38.040 --> 01:25:40.470 align:start position:0%
Department of energy whoever went to um
we<01:25:38.320> respond<01:25:39.159> I<01:25:39.239> don't<01:25:39.880> have<01:25:39.960> you<01:25:40.040> seen<01:25:40.239> that

01:25:40.470 --> 01:25:40.480 align:start position:0%
we respond I don't have you seen that
 

01:25:40.480 --> 01:25:42.750 align:start position:0%
we respond I don't have you seen that
response<01:25:40.840> from<01:25:41.119> I<01:25:41.199> think<01:25:41.639> from<01:25:41.840> will

01:25:42.750 --> 01:25:42.760 align:start position:0%
response from I think from will
 

01:25:42.760 --> 01:25:45.070 align:start position:0%
response from I think from will
ringer<01:25:43.760> yeah<01:25:44.040> yeah<01:25:44.320> I<01:25:44.360> mean<01:25:44.520> never<01:25:44.800> been<01:25:44.960> a

01:25:45.070 --> 01:25:45.080 align:start position:0%
ringer yeah yeah I mean never been a
 

01:25:45.080 --> 01:25:47.990 align:start position:0%
ringer yeah yeah I mean never been a
couple<01:25:45.320> years<01:25:45.480> ago<01:25:46.320> right<01:25:47.320> but<01:25:47.440> it<01:25:47.600> addressed

01:25:47.990 --> 01:25:48.000 align:start position:0%
couple years ago right but it addressed
 

01:25:48.000 --> 01:25:49.669 align:start position:0%
couple years ago right but it addressed
all<01:25:48.159> those<01:25:48.360> issues<01:25:48.679> that<01:25:48.880> we<01:25:49.119> had<01:25:49.560> the

01:25:49.669 --> 01:25:49.679 align:start position:0%
all those issues that we had the
 

01:25:49.679 --> 01:25:51.270 align:start position:0%
all those issues that we had the
industry

01:25:51.270 --> 01:25:51.280 align:start position:0%
industry
 

01:25:51.280 --> 01:25:53.550 align:start position:0%
industry
had

01:25:53.550 --> 01:25:53.560 align:start position:0%
had
 

01:25:53.560 --> 01:25:55.310 align:start position:0%
had
I<01:25:53.679> think<01:25:54.000> the<01:25:54.119> broader<01:25:54.480> point<01:25:54.719> is<01:25:54.880> that<01:25:55.119> yes

01:25:55.310 --> 01:25:55.320 align:start position:0%
I think the broader point is that yes
 

01:25:55.320 --> 01:25:57.189 align:start position:0%
I think the broader point is that yes
these<01:25:55.480> things<01:25:55.639> are<01:25:55.880> all<01:25:56.440> interconnected<01:25:57.080> in

01:25:57.189 --> 01:25:57.199 align:start position:0%
these things are all interconnected in
 

01:25:57.199 --> 01:26:00.229 align:start position:0%
these things are all interconnected in
terms<01:25:57.480> of<01:25:58.199> to<01:25:58.480> how<01:25:58.560> do<01:25:58.719> we<01:25:59.400> make<01:25:59.639> this

01:26:00.229 --> 01:26:00.239 align:start position:0%
terms of to how do we make this
 

01:26:00.239 --> 01:26:03.030 align:start position:0%
terms of to how do we make this
transition<01:26:01.239> effectively<01:26:01.920> timely<01:26:02.760> cost

01:26:03.030 --> 01:26:03.040 align:start position:0%
transition effectively timely cost
 

01:26:03.040 --> 01:26:04.669 align:start position:0%
transition effectively timely cost
effectively<01:26:03.639> how<01:26:03.760> we<01:26:03.920> do<01:26:04.040> all<01:26:04.159> these<01:26:04.320> things

01:26:04.669 --> 01:26:04.679 align:start position:0%
effectively how we do all these things
 

01:26:04.679 --> 01:26:06.750 align:start position:0%
effectively how we do all these things
it's<01:26:04.920> it's<01:26:05.119> transmission<01:26:06.040> addressing

01:26:06.750 --> 01:26:06.760 align:start position:0%
it's it's transmission addressing
 

01:26:06.760 --> 01:26:08.709 align:start position:0%
it's it's transmission addressing
transmission<01:26:07.159> constraints<01:26:07.800> address

01:26:08.709 --> 01:26:08.719 align:start position:0%
transmission constraints address
 

01:26:08.719 --> 01:26:11.270 align:start position:0%
transmission constraints address
constraints<01:26:09.360> addressing<01:26:10.199> number<01:26:10.440> of<01:26:10.719> factors

01:26:11.270 --> 01:26:11.280 align:start position:0%
constraints addressing number of factors
 

01:26:11.280 --> 01:26:13.310 align:start position:0%
constraints addressing number of factors
so<01:26:11.880> yeah<01:26:12.159> there's<01:26:12.280> a<01:26:12.360> lot<01:26:12.480> of<01:26:12.600> activi<01:26:13.040> also

01:26:13.310 --> 01:26:13.320 align:start position:0%
so yeah there's a lot of activi also
 

01:26:13.320 --> 01:26:15.189 align:start position:0%
so yeah there's a lot of activi also
grandfathering<01:26:14.159> projects<01:26:14.639> that<01:26:15.000> have

01:26:15.189 --> 01:26:15.199 align:start position:0%
grandfathering projects that have
 

01:26:15.199 --> 01:26:20.870 align:start position:0%
grandfathering projects that have
assumed<01:26:15.600> things<01:26:15.760> are<01:26:15.880> going<01:26:15.960> to<01:26:16.080> be<01:26:16.280> certain

01:26:20.870 --> 01:26:20.880 align:start position:0%
 
 

01:26:20.880 --> 01:26:26.229 align:start position:0%
 
way<01:26:21.880> well<01:26:22.280> moving<01:26:22.520> on<01:26:23.320> um<01:26:24.320> setting<01:26:25.080> times<01:26:26.040> and

01:26:26.229 --> 01:26:26.239 align:start position:0%
way well moving on um setting times and
 

01:26:26.239 --> 01:26:30.070 align:start position:0%
way well moving on um setting times and
days<01:26:26.560> for<01:26:26.840> our<01:26:27.080> future<01:26:27.800> meetings<01:26:28.920> um<01:26:29.920> would

01:26:30.070 --> 01:26:30.080 align:start position:0%
days for our future meetings um would
 

01:26:30.080 --> 01:26:32.109 align:start position:0%
days for our future meetings um would
like<01:26:30.400> to<01:26:30.560> first<01:26:30.760> set<01:26:30.960> a<01:26:31.159> date<01:26:31.360> for<01:26:31.679> this

01:26:32.109 --> 01:26:32.119 align:start position:0%
like to first set a date for this
 

01:26:32.119 --> 01:26:34.550 align:start position:0%
like to first set a date for this
September<01:26:33.119> and<01:26:33.440> for<01:26:33.679> the<01:26:33.920> conversation<01:26:34.400> on

01:26:34.550 --> 01:26:34.560 align:start position:0%
September and for the conversation on
 

01:26:34.560 --> 01:26:36.950 align:start position:0%
September and for the conversation on
the<01:26:34.719> last<01:26:34.920> meeting<01:26:35.679> would<01:26:35.880> like<01:26:36.040> to<01:26:36.360> propose

01:26:36.950 --> 01:26:36.960 align:start position:0%
the last meeting would like to propose
 

01:26:36.960 --> 01:26:41.910 align:start position:0%
the last meeting would like to propose
Wednesday<01:26:37.800> September<01:26:38.520> 13th<01:26:39.520> venue<01:26:40.440> TBD<01:26:41.440> but

01:26:41.910 --> 01:26:41.920 align:start position:0%
Wednesday September 13th venue TBD but
 

01:26:41.920 --> 01:26:44.310 align:start position:0%
Wednesday September 13th venue TBD but
um<01:26:42.159> the<01:26:42.639> second<01:26:43.600> I<01:26:43.679> guess<01:26:43.800> that<01:26:43.920> would<01:26:44.040> put<01:26:44.199> us

01:26:44.310 --> 01:26:44.320 align:start position:0%
um the second I guess that would put us
 

01:26:44.320 --> 01:26:48.430 align:start position:0%
um the second I guess that would put us
a<01:26:44.480> week<01:26:45.239> after<01:26:46.239> the<01:26:46.600> Labor<01:26:47.000> Day

01:26:48.430 --> 01:26:48.440 align:start position:0%
a week after the Labor Day
 

01:26:48.440 --> 01:26:49.950 align:start position:0%
a week after the Labor Day
holiday

01:26:49.950 --> 01:26:49.960 align:start position:0%
holiday
 

01:26:49.960 --> 01:26:53.030 align:start position:0%
holiday
and<01:26:50.960> so<01:26:51.119> let's<01:26:51.320> start<01:26:51.560> with<01:26:51.760> that<01:26:52.360> um<01:26:52.639> I<01:26:52.760> know

01:26:53.030 --> 01:26:53.040 align:start position:0%
and so let's start with that um I know
 

01:26:53.040 --> 01:26:54.910 align:start position:0%
and so let's start with that um I know
folks<01:26:53.320> said<01:26:53.560> generally<01:26:53.920> said<01:26:54.119> Wednesday's

01:26:54.910 --> 01:26:54.920 align:start position:0%
folks said generally said Wednesday's
 

01:26:54.920 --> 01:26:58.669 align:start position:0%
folks said generally said Wednesday's
work<01:26:55.920> um<01:26:56.159> hoping<01:26:56.760> a<01:26:57.040> date<01:26:57.880> two<01:26:58.080> or<01:26:58.199> so<01:26:58.440> months

01:26:58.669 --> 01:26:58.679 align:start position:0%
work um hoping a date two or so months
 

01:26:58.679 --> 01:27:00.590 align:start position:0%
work um hoping a date two or so months
from<01:26:58.880> now<01:26:59.440> with<01:26:59.600> some<01:26:59.760> notifications<01:27:00.360> to

01:27:00.590 --> 01:27:00.600 align:start position:0%
from now with some notifications to
 

01:27:00.600 --> 01:27:03.510 align:start position:0%
from now with some notifications to
members<01:27:01.440> would<01:27:01.679> be<01:27:02.679> sufficient<01:27:03.080> to<01:27:03.239> have<01:27:03.360> a

01:27:03.510 --> 01:27:03.520 align:start position:0%
members would be sufficient to have a
 

01:27:03.520 --> 01:27:05.709 align:start position:0%
members would be sufficient to have a
quorum<01:27:04.159> does<01:27:04.400> that<01:27:04.600> pose<01:27:04.880> any<01:27:05.119> issues<01:27:05.440> for

01:27:05.709 --> 01:27:05.719 align:start position:0%
quorum does that pose any issues for
 

01:27:05.719 --> 01:27:08.350 align:start position:0%
quorum does that pose any issues for
folks<01:27:06.080> here<01:27:06.480> 10<01:27:06.679> o'clock<01:27:07.600> you<01:27:07.800> talking<01:27:08.040> about

01:27:08.350 --> 01:27:08.360 align:start position:0%
folks here 10 o'clock you talking about
 

01:27:08.360 --> 01:27:11.030 align:start position:0%
folks here 10 o'clock you talking about
same<01:27:08.760> time<01:27:09.760> unless<01:27:10.119> we<01:27:10.199> wanted<01:27:10.400> to<01:27:10.600> push<01:27:10.719> it<01:27:10.840> to

01:27:11.030 --> 01:27:11.040 align:start position:0%
same time unless we wanted to push it to
 

01:27:11.040 --> 01:27:12.950 align:start position:0%
same time unless we wanted to push it to
the<01:27:11.239> afternoon<01:27:12.239> I<01:27:12.320> can<01:27:12.440> do<01:27:12.560> the<01:27:12.639> morning<01:27:12.880> I

01:27:12.950 --> 01:27:12.960 align:start position:0%
the afternoon I can do the morning I
 

01:27:12.960 --> 01:27:17.470 align:start position:0%
the afternoon I can do the morning I
can't<01:27:13.119> do<01:27:13.280> the<01:27:13.400> afternoon<01:27:14.360> can<01:27:14.560> do<01:27:14.719> in<01:27:14.800> the

01:27:17.470 --> 01:27:17.480 align:start position:0%
 
 

01:27:17.480 --> 01:27:19.990 align:start position:0%
 
morning<01:27:18.480> does<01:27:18.679> morning<01:27:19.199> work<01:27:19.440> better<01:27:19.639> for<01:27:19.840> the

01:27:19.990 --> 01:27:20.000 align:start position:0%
morning does morning work better for the
 

01:27:20.000 --> 01:27:22.510 align:start position:0%
morning does morning work better for the
folks<01:27:20.320> coming<01:27:20.560> from<01:27:20.760> up<01:27:20.960> North<01:27:21.840> espec<01:27:22.360> if<01:27:22.440> you

01:27:22.510 --> 01:27:22.520 align:start position:0%
folks coming from up North espec if you
 

01:27:22.520 --> 01:27:24.709 align:start position:0%
folks coming from up North espec if you
know<01:27:22.719> you<01:27:22.840> can<01:27:23.320> take<01:27:23.520> the<01:27:23.639> train<01:27:23.960> now<01:27:24.440> well<01:27:24.639> if

01:27:24.709 --> 01:27:24.719 align:start position:0%
know you can take the train now well if
 

01:27:24.719 --> 01:27:25.990 align:start position:0%
know you can take the train now well if
we're<01:27:24.880> coming<01:27:25.159> here<01:27:25.480> yeah<01:27:25.639> I<01:27:25.719> think<01:27:25.880> that

01:27:25.990 --> 01:27:26.000 align:start position:0%
we're coming here yeah I think that
 

01:27:26.000 --> 01:27:28.229 align:start position:0%
we're coming here yeah I think that
works<01:27:26.280> very<01:27:26.520> well<01:27:26.960> okay<01:27:27.239> if<01:27:27.679> yeah<01:27:27.960> that<01:27:28.080> means

01:27:28.229 --> 01:27:28.239 align:start position:0%
works very well okay if yeah that means
 

01:27:28.239 --> 01:27:30.830 align:start position:0%
works very well okay if yeah that means
we'll<01:27:28.600> get<01:27:28.719> the<01:27:28.880> spot<01:27:29.199> but<01:27:29.360> that's<01:27:29.480> all<01:27:29.840> right

01:27:30.830 --> 01:27:30.840 align:start position:0%
we'll get the spot but that's all right
 

01:27:30.840 --> 01:27:33.070 align:start position:0%
we'll get the spot but that's all right
well<01:27:31.520> I<01:27:31.880> 10<01:27:32.040> a<01:27:32.280> might<01:27:32.400> not<01:27:32.600> work<01:27:32.800> here<01:27:32.880> if<01:27:33.000> they

01:27:33.070 --> 01:27:33.080 align:start position:0%
well I 10 a might not work here if they
 

01:27:33.080 --> 01:27:35.790 align:start position:0%
well I 10 a might not work here if they
don't<01:27:33.199> open<01:27:33.520> until<01:27:33.679> 10<01:27:34.000> oh<01:27:34.159> good<01:27:34.360> point<01:27:35.000> 10

01:27:35.790 --> 01:27:35.800 align:start position:0%
don't open until 10 oh good point 10
 

01:27:35.800 --> 01:27:40.709 align:start position:0%
don't open until 10 oh good point 10
10:30<01:27:36.800> but<01:27:37.679> um<01:27:38.639> what<01:27:39.199> Paul<01:27:39.480> was<01:27:40.280> sharing

01:27:40.709 --> 01:27:40.719 align:start position:0%
10:30 but um what Paul was sharing
 

01:27:40.719 --> 01:27:43.669 align:start position:0%
10:30 but um what Paul was sharing
comments<01:27:41.119> before<01:27:41.600> the<01:27:42.440> the<01:27:42.560> meeting<01:27:43.159> did<01:27:43.560> the

01:27:43.669 --> 01:27:43.679 align:start position:0%
comments before the the meeting did the
 

01:27:43.679 --> 01:27:46.270 align:start position:0%
comments before the the meeting did the
authority<01:27:44.040> used<01:27:44.199> to<01:27:44.320> meet<01:27:44.639> at<01:27:44.920> the<01:27:45.600> this<01:27:45.880> state

01:27:46.270 --> 01:27:46.280 align:start position:0%
authority used to meet at the this state
 

01:27:46.280 --> 01:27:49.149 align:start position:0%
authority used to meet at the this state
capital<01:27:46.880> yep<01:27:47.480> and<01:27:47.760> won't<01:27:48.000> let<01:27:48.080> us<01:27:48.280> anymore<01:27:49.040> and

01:27:49.149 --> 01:27:49.159 align:start position:0%
capital yep and won't let us anymore and
 

01:27:49.159 --> 01:27:51.750 align:start position:0%
capital yep and won't let us anymore and
who<01:27:49.320> makes<01:27:49.600> that<01:27:50.000> call<01:27:51.000> someone<01:27:51.480> in<01:27:51.600> the

01:27:51.750 --> 01:27:51.760 align:start position:0%
who makes that call someone in the
 

01:27:51.760 --> 01:27:54.550 align:start position:0%
who makes that call someone in the
capital

01:27:54.550 --> 01:27:54.560 align:start position:0%
 
 

01:27:54.560 --> 01:27:59.550 align:start position:0%
 
CL<01:27:55.119> M<01:27:55.800> CL<01:27:56.800> I<01:27:56.960> believe<01:27:57.360> so<01:27:58.239> yeah<01:27:59.239> that<01:27:59.360> was

01:27:59.550 --> 01:27:59.560 align:start position:0%
CL M CL I believe so yeah that was
 

01:27:59.560 --> 01:28:02.790 align:start position:0%
CL M CL I believe so yeah that was
convenient<01:28:00.480> it<01:28:00.679> was<01:28:01.600> except<01:28:01.840> for<01:28:02.080> parking<01:28:02.560> was

01:28:02.790 --> 01:28:02.800 align:start position:0%
convenient it was except for parking was
 

01:28:02.800 --> 01:28:05.669 align:start position:0%
convenient it was except for parking was
a<01:28:02.880> little<01:28:03.040> more<01:28:03.600> well<01:28:04.199> the

01:28:05.669 --> 01:28:05.679 align:start position:0%
a little more well the
 

01:28:05.679 --> 01:28:10.550 align:start position:0%
a little more well the
new<01:28:06.679> a<01:28:06.760> lot<01:28:06.920> more

01:28:10.550 --> 01:28:10.560 align:start position:0%
 
 

01:28:10.560 --> 01:28:13.950 align:start position:0%
 
availability<01:28:11.560> um<01:28:12.560> and<01:28:12.679> then<01:28:12.840> we<01:28:13.000> used<01:28:13.199> to<01:28:13.719> also

01:28:13.950 --> 01:28:13.960 align:start position:0%
availability um and then we used to also
 

01:28:13.960 --> 01:28:17.109 align:start position:0%
availability um and then we used to also
be<01:28:14.080> met<01:28:14.239> a<01:28:14.320> couple<01:28:14.600> times<01:28:14.840> at<01:28:15.040> DEQ<01:28:15.840> down<01:28:16.199> at<01:28:16.719> uh

01:28:17.109 --> 01:28:17.119 align:start position:0%
be met a couple times at DEQ down at uh
 

01:28:17.119 --> 01:28:19.629 align:start position:0%
be met a couple times at DEQ down at uh
what's<01:28:17.280> it<01:28:17.880> 12th<01:28:18.239> in<01:28:18.400> Maine<01:28:19.119> and<01:28:19.320> we<01:28:19.440> can't

01:28:19.629 --> 01:28:19.639 align:start position:0%
what's it 12th in Maine and we can't
 

01:28:19.639 --> 01:28:23.149 align:start position:0%
what's it 12th in Maine and we can't
meet<01:28:19.840> there<01:28:20.040> anymore<01:28:20.440> either<01:28:21.040> so

01:28:23.149 --> 01:28:23.159 align:start position:0%
meet there anymore either so
 

01:28:23.159 --> 01:28:25.790 align:start position:0%
meet there anymore either so
there's<01:28:23.600> another<01:28:24.119> Library<01:28:25.119> um<01:28:25.320> not<01:28:25.520> the<01:28:25.639> one

01:28:25.790 --> 01:28:25.800 align:start position:0%
there's another Library um not the one
 

01:28:25.800 --> 01:28:27.709 align:start position:0%
there's another Library um not the one
we<01:28:25.920> met<01:28:26.080> at<01:28:26.320> last<01:28:26.560> time<01:28:26.840> but<01:28:27.040> maybe<01:28:27.280> one<01:28:27.440> or<01:28:27.560> two

01:28:27.709 --> 01:28:27.719 align:start position:0%
we met at last time but maybe one or two
 

01:28:27.719 --> 01:28:30.270 align:start position:0%
we met at last time but maybe one or two
meetings<01:28:28.239> before<01:28:28.639> that<01:28:29.440> also<01:28:29.880> that<01:28:30.040> I

01:28:30.270 --> 01:28:30.280 align:start position:0%
meetings before that also that I
 

01:28:30.280 --> 01:28:32.830 align:start position:0%
meetings before that also that I
Fairfield<01:28:30.920> I<01:28:31.000> believe<01:28:31.320> the<01:28:31.520> really<01:28:31.880> fancy<01:28:32.280> new

01:28:32.830 --> 01:28:32.840 align:start position:0%
Fairfield I believe the really fancy new
 

01:28:32.840 --> 01:28:34.870 align:start position:0%
Fairfield I believe the really fancy new
really<01:28:33.000> new<01:28:33.159> one<01:28:33.480> yeah<01:28:34.040> that's<01:28:34.400> that's<01:28:34.520> a<01:28:34.679> nice

01:28:34.870 --> 01:28:34.880 align:start position:0%
really new one yeah that's that's a nice
 

01:28:34.880 --> 01:28:37.790 align:start position:0%
really new one yeah that's that's a nice
one<01:28:35.280> was<01:28:35.480> yesterday's<01:28:36.000> rap<01:28:36.280> at<01:28:36.440> theq<01:28:37.400> it<01:28:37.600> was

01:28:37.790 --> 01:28:37.800 align:start position:0%
one was yesterday's rap at theq it was
 

01:28:37.800 --> 01:28:39.430 align:start position:0%
one was yesterday's rap at theq it was
that's<01:28:37.960> what<01:28:38.080> it<01:28:38.159> was<01:28:38.320> the<01:28:38.440> first<01:28:38.639> one<01:28:39.239> that

01:28:39.430 --> 01:28:39.440 align:start position:0%
that's what it was the first one that
 

01:28:39.440 --> 01:28:42.870 align:start position:0%
that's what it was the first one that
building<01:28:39.840> out<01:28:40.320> in<01:28:40.960> Brook<01:28:41.880> we<01:28:42.000> can<01:28:42.119> do<01:28:42.440> well<01:28:42.639> and

01:28:42.870 --> 01:28:42.880 align:start position:0%
building out in Brook we can do well and
 

01:28:42.880 --> 01:28:44.870 align:start position:0%
building out in Brook we can do well and
that<01:28:43.320> that's<01:28:43.480> an<01:28:43.880> option<01:28:44.159> too<01:28:44.440> I<01:28:44.520> can<01:28:44.639> see

01:28:44.870 --> 01:28:44.880 align:start position:0%
that that's an option too I can see
 

01:28:44.880 --> 01:28:47.590 align:start position:0%
that that's an option too I can see
about<01:28:45.239> whether<01:28:45.440> we<01:28:45.760> can<01:28:46.760> get<01:28:46.960> that<01:28:47.159> space<01:28:47.520> I

01:28:47.590 --> 01:28:47.600 align:start position:0%
about whether we can get that space I
 

01:28:47.600 --> 01:28:48.510 align:start position:0%
about whether we can get that space I
don't<01:28:47.679> know<01:28:47.760> if<01:28:47.880> people<01:28:48.040> want<01:28:48.159> to<01:28:48.280> come

01:28:48.510 --> 01:28:48.520 align:start position:0%
don't know if people want to come
 

01:28:48.520 --> 01:28:50.189 align:start position:0%
don't know if people want to come
downtown<01:28:49.040> but<01:28:49.159> we've<01:28:49.320> got<01:28:49.520> space<01:28:49.920> I<01:28:49.960> mean<01:28:50.040> one

01:28:50.189 --> 01:28:50.199 align:start position:0%
downtown but we've got space I mean one
 

01:28:50.199 --> 01:28:51.590 align:start position:0%
downtown but we've got space I mean one
of<01:28:50.280> the<01:28:50.360> truest<01:28:50.639> buildings<01:28:50.960> that<01:28:51.159> we've<01:28:51.320> got

01:28:51.590 --> 01:28:51.600 align:start position:0%
of the truest buildings that we've got
 

01:28:51.600 --> 01:28:52.910 align:start position:0%
of the truest buildings that we've got
there's<01:28:51.760> tons<01:28:52.080> the<01:28:52.159> conference<01:28:52.440> rooms<01:28:52.679> in

01:28:52.910 --> 01:28:52.920 align:start position:0%
there's tons the conference rooms in
 

01:28:52.920 --> 01:28:55.149 align:start position:0%
there's tons the conference rooms in
there<01:28:53.920> you<01:28:54.040> can<01:28:54.159> always<01:28:54.440> get<01:28:54.719> I<01:28:54.800> mean<01:28:54.920> it's<01:28:55.000> a

01:28:55.149 --> 01:28:55.159 align:start position:0%
there you can always get I mean it's a
 

01:28:55.159 --> 01:28:56.390 align:start position:0%
there you can always get I mean it's a
pain<01:28:55.360> for<01:28:55.520> people<01:28:55.719> who<01:28:55.840> don't<01:28:56.000> aren't<01:28:56.159> used<01:28:56.320> to

01:28:56.390 --> 01:28:56.400 align:start position:0%
pain for people who don't aren't used to
 

01:28:56.400 --> 01:28:59.149 align:start position:0%
pain for people who don't aren't used to
going<01:28:56.600> down

01:28:59.149 --> 01:28:59.159 align:start position:0%
 
 

01:28:59.159 --> 01:29:01.830 align:start position:0%
 
time<01:29:00.159> um<01:29:00.440> I<01:29:00.560> looked<01:29:00.800> into<01:29:01.000> Fredericksburg

01:29:01.830 --> 01:29:01.840 align:start position:0%
time um I looked into Fredericksburg
 

01:29:01.840 --> 01:29:03.350 align:start position:0%
time um I looked into Fredericksburg
their<01:29:02.000> Library<01:29:02.440> System<01:29:02.719> I<01:29:02.800> need<01:29:02.960> to<01:29:03.080> get<01:29:03.159> a

01:29:03.350 --> 01:29:03.360 align:start position:0%
their Library System I need to get a
 

01:29:03.360 --> 01:29:06.830 align:start position:0%
their Library System I need to get a
library

01:29:06.830 --> 01:29:06.840 align:start position:0%
 
 

01:29:06.840 --> 01:29:09.950 align:start position:0%
 
card<01:29:07.840> um<01:29:08.800> into

01:29:09.950 --> 01:29:09.960 align:start position:0%
card um into
 

01:29:09.960 --> 01:29:13.550 align:start position:0%
card um into
2024<01:29:10.960> uh<01:29:11.840> going<01:29:12.119> back<01:29:12.239> to<01:29:12.360> the<01:29:12.520> last

01:29:13.550 --> 01:29:13.560 align:start position:0%
2024 uh going back to the last
 

01:29:13.560 --> 01:29:15.470 align:start position:0%
2024 uh going back to the last
meeting<01:29:14.560> can't<01:29:14.760> remember<01:29:15.000> if<01:29:15.080> it<01:29:15.199> was<01:29:15.280> the<01:29:15.360> one

01:29:15.470 --> 01:29:15.480 align:start position:0%
meeting can't remember if it was the one
 

01:29:15.480 --> 01:29:17.990 align:start position:0%
meeting can't remember if it was the one
we<01:29:15.600> have<01:29:15.760> virtually<01:29:16.360> before<01:29:16.960> um<01:29:17.159> we<01:29:17.440> pitched

01:29:17.990 --> 01:29:18.000 align:start position:0%
we have virtually before um we pitched
 

01:29:18.000 --> 01:29:21.030 align:start position:0%
we have virtually before um we pitched
having<01:29:18.239> a<01:29:18.400> quarterly<01:29:18.920> date<01:29:19.800> where<01:29:20.560> uh<01:29:20.719> it<01:29:20.960> it

01:29:21.030 --> 01:29:21.040 align:start position:0%
having a quarterly date where uh it it
 

01:29:21.040 --> 01:29:23.990 align:start position:0%
having a quarterly date where uh it it
would<01:29:21.560> uh<01:29:22.000> Ur<01:29:22.560> as<01:29:22.760> the<01:29:23.199> first<01:29:23.679> second

01:29:23.990 --> 01:29:24.000 align:start position:0%
would uh Ur as the first second
 

01:29:24.000 --> 01:29:26.870 align:start position:0%
would uh Ur as the first second
Wednesday<01:29:24.560> of<01:29:24.719> every<01:29:25.080> quarter<01:29:26.080> taking<01:29:26.360> a<01:29:26.560> look

01:29:26.870 --> 01:29:26.880 align:start position:0%
Wednesday of every quarter taking a look
 

01:29:26.880 --> 01:29:30.310 align:start position:0%
Wednesday of every quarter taking a look
at<01:29:27.199> the<01:29:27.639> calendar<01:29:28.000> for<01:29:28.440> 2024<01:29:29.440> it<01:29:29.639> looks<01:29:29.880> like

01:29:30.310 --> 01:29:30.320 align:start position:0%
at the calendar for 2024 it looks like
 

01:29:30.320 --> 01:29:33.149 align:start position:0%
at the calendar for 2024 it looks like
the<01:29:30.520> second<01:29:30.840> Wednesday<01:29:31.480> of<01:29:31.639> each<01:29:32.159> quarter

01:29:33.149 --> 01:29:33.159 align:start position:0%
the second Wednesday of each quarter
 

01:29:33.159 --> 01:29:35.790 align:start position:0%
the second Wednesday of each quarter
misses<01:29:33.560> a<01:29:33.679> lot<01:29:33.800> of<01:29:33.920> major<01:29:34.280> holidays<01:29:35.199> and<01:29:35.719> I

01:29:35.790 --> 01:29:35.800 align:start position:0%
misses a lot of major holidays and I
 

01:29:35.800 --> 01:29:39.669 align:start position:0%
misses a lot of major holidays and I
would<01:29:36.080> propose<01:29:36.679> that<01:29:37.199> as<01:29:37.679> uh<01:29:38.400> meeting<01:29:38.920> times

01:29:39.669 --> 01:29:39.679 align:start position:0%
would propose that as uh meeting times
 

01:29:39.679 --> 01:29:42.950 align:start position:0%
would propose that as uh meeting times
or<01:29:39.840> meeting<01:29:40.159> dates<01:29:40.639> for<01:29:40.960> 2024<01:29:41.880> that<01:29:41.960> would<01:29:42.119> be

01:29:42.950 --> 01:29:42.960 align:start position:0%
or meeting dates for 2024 that would be
 

01:29:42.960 --> 01:29:45.990 align:start position:0%
or meeting dates for 2024 that would be
January<01:29:43.400> 10th<01:29:43.840> April<01:29:44.199> 10th<01:29:44.679> July<01:29:45.080> 10th<01:29:45.600> and

01:29:45.990 --> 01:29:46.000 align:start position:0%
January 10th April 10th July 10th and
 

01:29:46.000 --> 01:29:47.030 align:start position:0%
January 10th April 10th July 10th and
October

01:29:47.030 --> 01:29:47.040 align:start position:0%
October
 

01:29:47.040 --> 01:29:50.310 align:start position:0%
October
9th<01:29:48.360> um<01:29:49.360> anybody<01:29:49.679> have<01:29:49.800> any<01:29:50.040> thoughts

01:29:50.310 --> 01:29:50.320 align:start position:0%
9th um anybody have any thoughts
 

01:29:50.320 --> 01:29:53.350 align:start position:0%
9th um anybody have any thoughts
comments<01:29:50.679> to<01:29:50.800> share<01:29:51.440> on<01:29:52.159> I<01:29:52.280> mean<01:29:52.960> that

01:29:53.350 --> 01:29:53.360 align:start position:0%
comments to share on I mean that
 

01:29:53.360 --> 01:29:55.070 align:start position:0%
comments to share on I mean that
proposal<01:29:53.960> I<01:29:54.040> don't<01:29:54.360> imagine<01:29:54.679> anybody<01:29:54.920> else

01:29:55.070 --> 01:29:55.080 align:start position:0%
proposal I don't imagine anybody else
 

01:29:55.080 --> 01:29:56.790 align:start position:0%
proposal I don't imagine anybody else
January<01:29:55.400> 10's<01:29:55.639> first<01:29:55.800> day<01:29:55.920> of

01:29:56.790 --> 01:29:56.800 align:start position:0%
January 10's first day of
 

01:29:56.800 --> 01:29:58.669 align:start position:0%
January 10's first day of
session<01:29:57.800> I<01:29:57.880> don't<01:29:58.000> know<01:29:58.080> if<01:29:58.199> anybody<01:29:58.440> cares

01:29:58.669 --> 01:29:58.679 align:start position:0%
session I don't know if anybody cares
 

01:29:58.679 --> 01:30:00.870 align:start position:0%
session I don't know if anybody cares
about

01:30:00.870 --> 01:30:00.880 align:start position:0%
about
 

01:30:00.880 --> 01:30:04.189 align:start position:0%
about
that<01:30:01.880> I<01:30:02.040> I<01:30:02.119> won't<01:30:02.440> be<01:30:02.639> at<01:30:02.800> this<01:30:02.920> meeting

01:30:04.189 --> 01:30:04.199 align:start position:0%
that I I won't be at this meeting
 

01:30:04.199 --> 01:30:06.270 align:start position:0%
that I I won't be at this meeting
J<01:30:05.199> but<01:30:05.360> that's

01:30:06.270 --> 01:30:06.280 align:start position:0%
J but that's
 

01:30:06.280 --> 01:30:09.070 align:start position:0%
J but that's
okay<01:30:07.280> can<01:30:07.440> we<01:30:07.560> get<01:30:07.679> back<01:30:07.800> to<01:30:08.600> we<01:30:08.719> said<01:30:08.920> on

01:30:09.070 --> 01:30:09.080 align:start position:0%
okay can we get back to we said on
 

01:30:09.080 --> 01:30:10.669 align:start position:0%
okay can we get back to we said on
September<01:30:09.440> 13th<01:30:09.960> then<01:30:10.199> we<01:30:10.280> don't<01:30:10.480> have<01:30:10.560> a

01:30:10.669 --> 01:30:10.679 align:start position:0%
September 13th then we don't have a
 

01:30:10.679 --> 01:30:14.030 align:start position:0%
September 13th then we don't have a
location<01:30:11.119> is<01:30:11.199> that<01:30:11.400> correct<01:30:11.880> correct

01:30:14.030 --> 01:30:14.040 align:start position:0%
location is that correct correct
 

01:30:14.040 --> 01:30:16.310 align:start position:0%
location is that correct correct
yes<01:30:15.040> what<01:30:15.199> about<01:30:15.360> the<01:30:15.560> December<01:30:15.960> meeting<01:30:16.239> do

01:30:16.310 --> 01:30:16.320 align:start position:0%
yes what about the December meeting do
 

01:30:16.320 --> 01:30:18.430 align:start position:0%
yes what about the December meeting do
you<01:30:16.400> want<01:30:16.520> to<01:30:16.600> have<01:30:16.719> a<01:30:16.880> December<01:30:17.199> meeting<01:30:18.080> of

01:30:18.430 --> 01:30:18.440 align:start position:0%
you want to have a December meeting of
 

01:30:18.440 --> 01:30:20.830 align:start position:0%
you want to have a December meeting of
this<01:30:18.600> year<01:30:19.040> yeah

01:30:20.830 --> 01:30:20.840 align:start position:0%
this year yeah
 

01:30:20.840 --> 01:30:25.030 align:start position:0%
this year yeah
um<01:30:22.280> it<01:30:22.400> is<01:30:22.520> at<01:30:22.719> the<01:30:22.840> will<01:30:23.000> of<01:30:23.159> the<01:30:23.280> authority<01:30:24.280> I

01:30:25.030 --> 01:30:25.040 align:start position:0%
um it is at the will of the authority I
 

01:30:25.040 --> 01:30:27.709 align:start position:0%
um it is at the will of the authority I
so<01:30:25.280> to<01:30:25.440> stick<01:30:25.679> on<01:30:25.840> the<01:30:26.000> conversation<01:30:26.440> of<01:30:26.719> 2023

01:30:27.709 --> 01:30:27.719 align:start position:0%
so to stick on the conversation of 2023
 

01:30:27.719 --> 01:30:29.470 align:start position:0%
so to stick on the conversation of 2023
the<01:30:27.880> thought<01:30:28.159> with<01:30:28.360> September<01:30:28.760> 13th<01:30:29.239> would<01:30:29.360> be

01:30:29.470 --> 01:30:29.480 align:start position:0%
the thought with September 13th would be
 

01:30:29.480 --> 01:30:32.629 align:start position:0%
the thought with September 13th would be
to<01:30:29.600> hear<01:30:29.920> final<01:30:30.840> comments<01:30:31.360> from<01:30:31.960> presenters

01:30:32.629 --> 01:30:32.639 align:start position:0%
to hear final comments from presenters
 

01:30:32.639 --> 01:30:35.870 align:start position:0%
to hear final comments from presenters
to<01:30:32.880> have<01:30:33.199> a<01:30:33.560> wider<01:30:33.880> group<01:30:34.239> discussion<01:30:34.800> on<01:30:35.199> the

01:30:35.870 --> 01:30:35.880 align:start position:0%
to have a wider group discussion on the
 

01:30:35.880 --> 01:30:39.229 align:start position:0%
to have a wider group discussion on the
report<01:30:36.480> with<01:30:36.719> draft<01:30:37.040> in<01:30:37.280> hand<01:30:38.199> and<01:30:38.360> then<01:30:38.600> to

01:30:39.229 --> 01:30:39.239 align:start position:0%
report with draft in hand and then to
 

01:30:39.239 --> 01:30:41.270 align:start position:0%
report with draft in hand and then to
have<01:30:39.440> it<01:30:39.639> ready<01:30:40.000> by<01:30:40.199> the<01:30:40.320> October<01:30:40.760> 15th

01:30:41.270 --> 01:30:41.280 align:start position:0%
have it ready by the October 15th
 

01:30:41.280 --> 01:30:44.470 align:start position:0%
have it ready by the October 15th
deadline<01:30:42.159> we<01:30:42.360> could<01:30:42.960> utilize<01:30:43.800> the<01:30:43.960> first<01:30:44.239> week

01:30:44.470 --> 01:30:44.480 align:start position:0%
deadline we could utilize the first week
 

01:30:44.480 --> 01:30:46.830 align:start position:0%
deadline we could utilize the first week
of<01:30:44.679> October<01:30:45.480> to<01:30:45.639> do<01:30:45.920> a<01:30:46.040> virtual<01:30:46.360> meeting<01:30:46.679> to

01:30:46.830 --> 01:30:46.840 align:start position:0%
of October to do a virtual meeting to
 

01:30:46.840 --> 01:30:49.270 align:start position:0%
of October to do a virtual meeting to
take<01:30:47.000> a<01:30:47.239> final<01:30:47.600> look<01:30:47.920> at<01:30:48.199> the<01:30:48.600> report<01:30:49.040> if<01:30:49.159> we

01:30:49.270 --> 01:30:49.280 align:start position:0%
take a final look at the report if we
 

01:30:49.280 --> 01:30:50.950 align:start position:0%
take a final look at the report if we
would<01:30:49.440> like<01:30:49.800> well<01:30:50.080> again<01:30:50.280> remember<01:30:50.600> it<01:30:50.719> needs

01:30:50.950 --> 01:30:50.960 align:start position:0%
would like well again remember it needs
 

01:30:50.960 --> 01:30:53.229 align:start position:0%
would like well again remember it needs
to<01:30:51.119> go<01:30:51.280> through<01:30:51.480> the<01:30:51.840> secretary's<01:30:52.480> office

01:30:53.229 --> 01:30:53.239 align:start position:0%
to go through the secretary's office
 

01:30:53.239 --> 01:30:55.149 align:start position:0%
to go through the secretary's office
before<01:30:53.560> it's<01:30:53.760> submitted<01:30:54.360> officially<01:30:54.880> so

01:30:55.149 --> 01:30:55.159 align:start position:0%
before it's submitted officially so
 

01:30:55.159 --> 01:30:58.109 align:start position:0%
before it's submitted officially so
that's<01:30:55.400> why<01:30:56.159> we<01:30:56.320> need<01:30:56.520> to<01:30:57.440> you<01:30:57.639> need<01:30:57.800> to<01:30:58.000> have

01:30:58.109 --> 01:30:58.119 align:start position:0%
that's why we need to you need to have
 

01:30:58.119 --> 01:31:01.229 align:start position:0%
that's why we need to you need to have
it<01:30:58.280> done<01:30:58.840> sometime<01:30:59.840> as<01:31:00.239> soon<01:31:00.520> in<01:31:00.719> September<01:31:01.119> as

01:31:01.229 --> 01:31:01.239 align:start position:0%
it done sometime as soon in September as
 

01:31:01.239 --> 01:31:03.629 align:start position:0%
it done sometime as soon in September as
you<01:31:01.400> can<01:31:01.600> so<01:31:01.760> we<01:31:01.880> can<01:31:02.000> get<01:31:02.239> their<01:31:02.639> review<01:31:02.960> on<01:31:03.119> it

01:31:03.629 --> 01:31:03.639 align:start position:0%
you can so we can get their review on it
 

01:31:03.639 --> 01:31:05.109 align:start position:0%
you can so we can get their review on it
like<01:31:03.840> when<01:31:03.960> we<01:31:04.080> talked<01:31:04.320> on<01:31:04.440> the<01:31:04.520> phone<01:31:04.840> I<01:31:04.960> think

01:31:05.109 --> 01:31:05.119 align:start position:0%
like when we talked on the phone I think
 

01:31:05.119 --> 01:31:07.350 align:start position:0%
like when we talked on the phone I think
now<01:31:05.360> that<01:31:05.480> with<01:31:05.639> these<01:31:05.760> new<01:31:06.239> guidelines<01:31:07.239> it's

01:31:07.350 --> 01:31:07.360 align:start position:0%
now that with these new guidelines it's
 

01:31:07.360 --> 01:31:09.430 align:start position:0%
now that with these new guidelines it's
more<01:31:07.600> likely<01:31:08.280> that<01:31:08.520> they<01:31:08.639> can<01:31:08.800> turn<01:31:09.000> it<01:31:09.119> around

01:31:09.430 --> 01:31:09.440 align:start position:0%
more likely that they can turn it around
 

01:31:09.440 --> 01:31:12.790 align:start position:0%
more likely that they can turn it around
quickly<01:31:10.000> versus<01:31:10.800> 165<01:31:11.440> page

01:31:12.790 --> 01:31:12.800 align:start position:0%
quickly versus 165 page
 

01:31:12.800 --> 01:31:15.870 align:start position:0%
quickly versus 165 page
report<01:31:13.800> okay<01:31:14.520> well<01:31:14.639> we'll<01:31:14.800> put<01:31:14.920> a<01:31:15.080> pin<01:31:15.280> in<01:31:15.600> a

01:31:15.870 --> 01:31:15.880 align:start position:0%
report okay well we'll put a pin in a
 

01:31:15.880 --> 01:31:20.750 align:start position:0%
report okay well we'll put a pin in a
potential<01:31:16.280> virtual<01:31:16.639> meeting<01:31:16.960> in<01:31:17.280> October<01:31:18.280> but

01:31:20.750 --> 01:31:20.760 align:start position:0%
 
 

01:31:20.760 --> 01:31:23.149 align:start position:0%
 
um<01:31:21.960> still<01:31:22.119> being<01:31:22.320> the<01:31:22.480> thought<01:31:22.719> for<01:31:22.920> the

01:31:23.149 --> 01:31:23.159 align:start position:0%
um still being the thought for the
 

01:31:23.159 --> 01:31:24.750 align:start position:0%
um still being the thought for the
September<01:31:23.560> 13th

01:31:24.750 --> 01:31:24.760 align:start position:0%
September 13th
 

01:31:24.760 --> 01:31:28.310 align:start position:0%
September 13th
meeting<01:31:25.760> um<01:31:26.400> with<01:31:26.600> the<01:31:27.080> potential<01:31:28.080> difficulty

01:31:28.310 --> 01:31:28.320 align:start position:0%
meeting um with the potential difficulty
 

01:31:28.320 --> 01:31:30.910 align:start position:0%
meeting um with the potential difficulty
of<01:31:28.520> January

01:31:30.910 --> 01:31:30.920 align:start position:0%
of January
 

01:31:30.920 --> 01:31:33.350 align:start position:0%
of January
10<01:31:31.920> does<01:31:32.199> this<01:31:32.360> sound<01:31:32.600> good<01:31:32.719> to<01:31:32.840> you<01:31:32.960> all<01:31:33.159> would

01:31:33.350 --> 01:31:33.360 align:start position:0%
10 does this sound good to you all would
 

01:31:33.360 --> 01:31:36.390 align:start position:0%
10 does this sound good to you all would
we<01:31:33.719> propose<01:31:34.199> moving<01:31:34.480> into<01:31:34.800> January<01:31:35.159> 9<01:31:36.080> yeah

01:31:36.390 --> 01:31:36.400 align:start position:0%
we propose moving into January 9 yeah
 

01:31:36.400 --> 01:31:37.870 align:start position:0%
we propose moving into January 9 yeah
that<01:31:36.600> Tuesday

01:31:37.870 --> 01:31:37.880 align:start position:0%
that Tuesday
 

01:31:37.880 --> 01:31:39.830 align:start position:0%
that Tuesday
proba

01:31:39.830 --> 01:31:39.840 align:start position:0%
proba
 

01:31:39.840 --> 01:31:43.270 align:start position:0%
proba
okay<01:31:40.840> so<01:31:41.320> Ken<01:31:41.560> let's<01:31:41.920> share<01:31:42.520> um<01:31:42.880> calendar

01:31:43.270 --> 01:31:43.280 align:start position:0%
okay so Ken let's share um calendar
 

01:31:43.280 --> 01:31:45.870 align:start position:0%
okay so Ken let's share um calendar
invites<01:31:43.719> with<01:31:43.880> members<01:31:44.159> of<01:31:44.280> The<01:31:44.880> Authority

01:31:45.870 --> 01:31:45.880 align:start position:0%
invites with members of The Authority
 

01:31:45.880 --> 01:31:50.590 align:start position:0%
invites with members of The Authority
we'll<01:31:46.199> do<01:31:47.199> second<01:31:47.760> Tuesday<01:31:48.760> of<01:31:48.960> the<01:31:49.400> year<01:31:50.400> and

01:31:50.590 --> 01:31:50.600 align:start position:0%
we'll do second Tuesday of the year and
 

01:31:50.600 --> 01:31:53.149 align:start position:0%
we'll do second Tuesday of the year and
2024<01:31:51.280> to<01:31:51.760> to<01:31:52.040> remove<01:31:52.400> that<01:31:52.560> conflict<01:31:52.960> with<01:31:53.080> the

01:31:53.149 --> 01:31:53.159 align:start position:0%
2024 to to remove that conflict with the
 

01:31:53.159 --> 01:31:54.950 align:start position:0%
2024 to to remove that conflict with the
first<01:31:53.360> day<01:31:53.520> of<01:31:53.679> session<01:31:54.320> and<01:31:54.440> then<01:31:54.679> just<01:31:54.800> for

01:31:54.950 --> 01:31:54.960 align:start position:0%
first day of session and then just for
 

01:31:54.960 --> 01:31:57.510 align:start position:0%
first day of session and then just for
January<01:31:55.480> just<01:31:55.600> for<01:31:55.800> January<01:31:56.639> and<01:31:56.840> then<01:31:57.360> we'll

01:31:57.510 --> 01:31:57.520 align:start position:0%
January just for January and then we'll
 

01:31:57.520 --> 01:32:00.030 align:start position:0%
January just for January and then we'll
stick<01:31:57.719> with<01:31:57.880> the<01:31:57.960> winesday<01:31:58.679> that<01:31:59.360> folks<01:31:59.719> said

01:32:00.030 --> 01:32:00.040 align:start position:0%
stick with the winesday that folks said
 

01:32:00.040 --> 01:32:02.270 align:start position:0%
stick with the winesday that folks said
were<01:32:00.400> convenient<01:32:01.199> for<01:32:01.440> the<01:32:01.560> second<01:32:01.840> Tuesday

01:32:02.270 --> 01:32:02.280 align:start position:0%
were convenient for the second Tuesday
 

01:32:02.280 --> 01:32:05.270 align:start position:0%
were convenient for the second Tuesday
of<01:32:02.440> every<01:32:02.679> other<01:32:02.920> quarter<01:32:03.800> in<01:32:04.080> 2024<01:32:05.080> second

01:32:05.270 --> 01:32:05.280 align:start position:0%
of every other quarter in 2024 second
 

01:32:05.280 --> 01:32:08.510 align:start position:0%
of every other quarter in 2024 second
Wednesday<01:32:05.840> EXC<01:32:06.480> yes<01:32:06.800> yes<01:32:07.440> um<01:32:07.719> April<01:32:07.960> 10<01:32:08.239> July

01:32:08.510 --> 01:32:08.520 align:start position:0%
Wednesday EXC yes yes um April 10 July
 

01:32:08.520 --> 01:32:09.950 align:start position:0%
Wednesday EXC yes yes um April 10 July
10

01:32:09.950 --> 01:32:09.960 align:start position:0%
10
 

01:32:09.960 --> 01:32:12.470 align:start position:0%
10
October<01:32:10.960> great<01:32:11.639> I<01:32:11.760> can't<01:32:11.920> remember<01:32:12.239> if<01:32:12.360> you

01:32:12.470 --> 01:32:12.480 align:start position:0%
October great I can't remember if you
 

01:32:12.480 --> 01:32:13.470 align:start position:0%
October great I can't remember if you
said

01:32:13.470 --> 01:32:13.480 align:start position:0%
said
 

01:32:13.480 --> 01:32:16.310 align:start position:0%
said
it<01:32:14.480> um<01:32:14.639> are<01:32:14.800> we<01:32:14.920> going<01:32:15.040> to<01:32:15.719> recommend<01:32:16.119> in<01:32:16.239> the

01:32:16.310 --> 01:32:16.320 align:start position:0%
it um are we going to recommend in the
 

01:32:16.320 --> 01:32:18.550 align:start position:0%
it um are we going to recommend in the
2024<01:32:17.080> session<01:32:17.400> that<01:32:17.520> they<01:32:17.679> extend<01:32:18.040> the

01:32:18.550 --> 01:32:18.560 align:start position:0%
2024 session that they extend the
 

01:32:18.560 --> 01:32:20.189 align:start position:0%
2024 session that they extend the
deadline<01:32:18.960> on<01:32:19.119> the

01:32:20.189 --> 01:32:20.199 align:start position:0%
deadline on the
 

01:32:20.199 --> 01:32:22.350 align:start position:0%
deadline on the
authority<01:32:21.199> um<01:32:21.840> that<01:32:21.960> could<01:32:22.119> be<01:32:22.199> a

01:32:22.350 --> 01:32:22.360 align:start position:0%
authority um that could be a
 

01:32:22.360 --> 01:32:23.830 align:start position:0%
authority um that could be a
recommendation<01:32:22.880> that<01:32:23.000> we<01:32:23.119> make<01:32:23.320> in<01:32:23.440> our

01:32:23.830 --> 01:32:23.840 align:start position:0%
recommendation that we make in our
 

01:32:23.840 --> 01:32:26.510 align:start position:0%
recommendation that we make in our
report<01:32:24.760> um<01:32:24.960> I<01:32:25.040> think<01:32:25.280> it's

01:32:26.510 --> 01:32:26.520 align:start position:0%
report um I think it's
 

01:32:26.520 --> 01:32:29.229 align:start position:0%
report um I think it's
the<01:32:27.520> you<01:32:27.679> know<01:32:28.040> it<01:32:28.119> is<01:32:28.239> up<01:32:28.400> to<01:32:28.560> the<01:32:28.719> legislature

01:32:29.229 --> 01:32:29.239 align:start position:0%
the you know it is up to the legislature
 

01:32:29.239 --> 01:32:31.189 align:start position:0%
the you know it is up to the legislature
and<01:32:29.360> the<01:32:29.440> governor<01:32:29.840> if<01:32:29.960> they<01:32:30.080> want<01:32:30.239> to<01:32:30.679> I<01:32:30.760> think

01:32:31.189 --> 01:32:31.199 align:start position:0%
and the governor if they want to I think
 

01:32:31.199 --> 01:32:34.270 align:start position:0%
and the governor if they want to I think
the<01:32:31.560> governor<01:32:31.920> has<01:32:32.199> priority

01:32:34.270 --> 01:32:34.280 align:start position:0%
the governor has priority
 

01:32:34.280 --> 01:32:37.310 align:start position:0%
the governor has priority
of<01:32:35.280> not<01:32:35.840> having<01:32:36.199> authorities<01:32:36.880> that<01:32:37.040> aren't

01:32:37.310 --> 01:32:37.320 align:start position:0%
of not having authorities that aren't
 

01:32:37.320 --> 01:32:40.070 align:start position:0%
of not having authorities that aren't
being<01:32:37.679> helpful<01:32:38.280> they've<01:32:38.520> expressed<01:32:39.040> that<01:32:39.880> um

01:32:40.070 --> 01:32:40.080 align:start position:0%
being helpful they've expressed that um
 

01:32:40.080 --> 01:32:41.629 align:start position:0%
being helpful they've expressed that um
I<01:32:40.159> think<01:32:40.280> we<01:32:40.400> need<01:32:40.480> to<01:32:40.639> prove<01:32:40.840> ourselves<01:32:41.159> to<01:32:41.320> be

01:32:41.629 --> 01:32:41.639 align:start position:0%
I think we need to prove ourselves to be
 

01:32:41.639 --> 01:32:45.830 align:start position:0%
I think we need to prove ourselves to be
helpful<01:32:42.080> and<01:32:43.239> um<01:32:44.239> you<01:32:44.360> know<01:32:44.480> a<01:32:44.600> tool<01:32:44.880> for<01:32:45.159> them

01:32:45.830 --> 01:32:45.840 align:start position:0%
helpful and um you know a tool for them
 

01:32:45.840 --> 01:32:48.109 align:start position:0%
helpful and um you know a tool for them
they<01:32:45.960> do<01:32:46.119> want<01:32:46.239> to<01:32:46.800> to<01:32:47.199> shrink<01:32:47.600> the<01:32:47.760> size<01:32:47.960> of

01:32:48.109 --> 01:32:48.119 align:start position:0%
they do want to to shrink the size of
 

01:32:48.119 --> 01:32:49.950 align:start position:0%
they do want to to shrink the size of
government<01:32:48.800> but

01:32:49.950 --> 01:32:49.960 align:start position:0%
government but
 

01:32:49.960 --> 01:32:53.070 align:start position:0%
government but
um<01:32:50.960> but<01:32:51.159> we<01:32:51.280> could<01:32:51.440> make<01:32:51.719> that<01:32:52.080> recommendation

01:32:53.070 --> 01:32:53.080 align:start position:0%
um but we could make that recommendation
 

01:32:53.080 --> 01:32:54.990 align:start position:0%
um but we could make that recommendation
this<01:32:53.199> is<01:32:53.360> not<01:32:53.560> costing<01:32:53.920> them<01:32:54.159> anything<01:32:54.800> I<01:32:54.840> mean

01:32:54.990 --> 01:32:55.000 align:start position:0%
this is not costing them anything I mean
 

01:32:55.000 --> 01:32:57.990 align:start position:0%
this is not costing them anything I mean
you're<01:32:55.119> a<01:32:55.320> volunteer<01:32:55.800> Authority<01:32:56.239> so<01:32:57.000> well

01:32:57.990 --> 01:32:58.000 align:start position:0%
you're a volunteer Authority so well
 

01:32:58.000 --> 01:32:59.629 align:start position:0%
you're a volunteer Authority so well
it's<01:32:58.199> true<01:32:58.480> it's<01:32:58.639> costing<01:32:59.040> every<01:32:59.280> member

01:32:59.629 --> 01:32:59.639 align:start position:0%
it's true it's costing every member
 

01:32:59.639 --> 01:33:02.390 align:start position:0%
it's true it's costing every member
their<01:32:59.840> time<01:33:00.119> and<01:33:00.639> their<01:33:00.840> commitment<01:33:01.520> but<01:33:01.960> um

01:33:02.390 --> 01:33:02.400 align:start position:0%
their time and their commitment but um
 

01:33:02.400 --> 01:33:04.390 align:start position:0%
their time and their commitment but um
that's<01:33:02.600> still<01:33:02.880> their<01:33:03.159> their

01:33:04.390 --> 01:33:04.400 align:start position:0%
that's still their their
 

01:33:04.400 --> 01:33:06.750 align:start position:0%
that's still their their
position

01:33:06.750 --> 01:33:06.760 align:start position:0%
position
 

01:33:06.760 --> 01:33:08.550 align:start position:0%
position
um

01:33:08.550 --> 01:33:08.560 align:start position:0%
um
 

01:33:08.560 --> 01:33:11.950 align:start position:0%
um
so<01:33:09.560> couple<01:33:10.000> couple<01:33:10.280> last<01:33:10.560> things<01:33:10.800> to<01:33:11.040> mention

01:33:11.950 --> 01:33:11.960 align:start position:0%
so couple couple last things to mention
 

01:33:11.960 --> 01:33:14.550 align:start position:0%
so couple couple last things to mention
we<01:33:12.080> have<01:33:12.199> at<01:33:12.320> least<01:33:12.520> one<01:33:12.719> vacancy<01:33:13.480> now<01:33:14.080> Angela

01:33:14.550 --> 01:33:14.560 align:start position:0%
we have at least one vacancy now Angela
 

01:33:14.560 --> 01:33:17.430 align:start position:0%
we have at least one vacancy now Angela
King<01:33:15.159> sent<01:33:15.440> us<01:33:15.639> an<01:33:15.840> email<01:33:16.480> and<01:33:16.679> she<01:33:16.960> is

01:33:17.430 --> 01:33:17.440 align:start position:0%
King sent us an email and she is
 

01:33:17.440 --> 01:33:20.750 align:start position:0%
King sent us an email and she is
resigning<01:33:18.440> from<01:33:19.080> The<01:33:19.280> Authority<01:33:20.159> um<01:33:20.360> just

01:33:20.750 --> 01:33:20.760 align:start position:0%
resigning from The Authority um just
 

01:33:20.760 --> 01:33:23.669 align:start position:0%
resigning from The Authority um just
citing<01:33:21.800> uh<01:33:21.920> work<01:33:22.239> complications<01:33:23.159> and<01:33:23.560> the

01:33:23.669 --> 01:33:23.679 align:start position:0%
citing uh work complications and the
 

01:33:23.679 --> 01:33:27.030 align:start position:0%
citing uh work complications and the
need<01:33:24.440> uh<01:33:24.639> the<01:33:24.760> need<01:33:24.960> for<01:33:25.199> her<01:33:25.400> time<01:33:25.760> down<01:33:26.119> in

01:33:27.030 --> 01:33:27.040 align:start position:0%
need uh the need for her time down in
 

01:33:27.040 --> 01:33:30.109 align:start position:0%
need uh the need for her time down in
Hampton<01:33:28.040> and<01:33:28.800> we<01:33:29.000> also<01:33:29.400> received<01:33:29.600> an<01:33:29.719> email

01:33:30.109 --> 01:33:30.119 align:start position:0%
Hampton and we also received an email
 

01:33:30.119 --> 01:33:33.030 align:start position:0%
Hampton and we also received an email
from<01:33:30.520> Chase<01:33:31.040> counts<01:33:32.040> and<01:33:32.159> it<01:33:32.280> did<01:33:32.480> not<01:33:32.800> come

01:33:33.030 --> 01:33:33.040 align:start position:0%
from Chase counts and it did not come
 

01:33:33.040 --> 01:33:35.750 align:start position:0%
from Chase counts and it did not come
with<01:33:33.480> a<01:33:34.480> official<01:33:34.880> resignation<01:33:35.440> but<01:33:35.560> he<01:33:35.639> is

01:33:35.750 --> 01:33:35.760 align:start position:0%
with a official resignation but he is
 

01:33:35.760 --> 01:33:37.870 align:start position:0%
with a official resignation but he is
moving<01:33:36.040> out<01:33:36.199> of<01:33:36.400> state<01:33:36.719> so<01:33:36.960> that<01:33:37.159> might<01:33:37.320> mean

01:33:37.870 --> 01:33:37.880 align:start position:0%
moving out of state so that might mean
 

01:33:37.880 --> 01:33:40.149 align:start position:0%
moving out of state so that might mean
that<01:33:38.400> yeah<01:33:38.800> you<01:33:38.920> have<01:33:39.040> to<01:33:39.119> be<01:33:39.280> a<01:33:39.639> citizen<01:33:40.000> of

01:33:40.149 --> 01:33:40.159 align:start position:0%
that yeah you have to be a citizen of
 

01:33:40.159 --> 01:33:43.629 align:start position:0%
that yeah you have to be a citizen of
Virginia<01:33:40.600> to<01:33:40.719> serve<01:33:41.360> so<01:33:41.840> two<01:33:42.840> additional

01:33:43.629 --> 01:33:43.639 align:start position:0%
Virginia to serve so two additional
 

01:33:43.639 --> 01:33:47.590 align:start position:0%
Virginia to serve so two additional
vacancies<01:33:44.960> their<01:33:45.960> which<01:33:46.199> STS<01:33:46.719> do<01:33:46.920> they

01:33:47.590 --> 01:33:47.600 align:start position:0%
vacancies their which STS do they
 

01:33:47.600 --> 01:33:52.390 align:start position:0%
vacancies their which STS do they
fil<01:33:48.719> so<01:33:49.719> uh<01:33:49.840> kle<01:33:50.480> was<01:33:50.840> a<01:33:51.800> the<01:33:52.000> governor's

01:33:52.390 --> 01:33:52.400 align:start position:0%
fil so uh kle was a the governor's
 

01:33:52.400 --> 01:33:54.790 align:start position:0%
fil so uh kle was a the governor's
appoint<01:33:52.800> Governor's<01:33:53.320> appointee<01:33:54.320> and<01:33:54.440> I<01:33:54.600> can't

01:33:54.790 --> 01:33:54.800 align:start position:0%
appoint Governor's appointee and I can't
 

01:33:54.800 --> 01:33:57.149 align:start position:0%
appoint Governor's appointee and I can't
remember<01:33:55.159> whether<01:33:55.760> Chase<01:33:56.119> was

01:33:57.149 --> 01:33:57.159 align:start position:0%
remember whether Chase was
 

01:33:57.159 --> 01:34:01.350 align:start position:0%
remember whether Chase was
Senate<01:33:58.159> Chase<01:33:58.880> is<01:33:59.080> from<01:33:59.280> the<01:33:59.840> Senate<01:34:00.840> and

01:34:01.350 --> 01:34:01.360 align:start position:0%
Senate Chase is from the Senate and
 

01:34:01.360 --> 01:34:04.870 align:start position:0%
Senate Chase is from the Senate and
Angela<01:34:02.080> was<01:34:02.239> from<01:34:02.440> the<01:34:02.560> speaker<01:34:03.239> so<01:34:03.480> there<01:34:03.880> are

01:34:04.870 --> 01:34:04.880 align:start position:0%
Angela was from the speaker so there are
 

01:34:04.880 --> 01:34:07.070 align:start position:0%
Angela was from the speaker so there are
a<01:34:05.000> few

01:34:07.070 --> 01:34:07.080 align:start position:0%
a few
 

01:34:07.080 --> 01:34:09.270 align:start position:0%
a few
availabilities<01:34:08.080> and<01:34:08.280> senate<01:34:08.719> senate<01:34:08.960> rules

01:34:09.270 --> 01:34:09.280 align:start position:0%
availabilities and senate senate rules
 

01:34:09.280 --> 01:34:12.590 align:start position:0%
availabilities and senate senate rules
makes<01:34:09.480> the<01:34:09.639> appoint<01:34:09.920> on<01:34:10.239> it<01:34:11.239> yes

01:34:12.590 --> 01:34:12.600 align:start position:0%
makes the appoint on it yes
 

01:34:12.600 --> 01:34:14.629 align:start position:0%
makes the appoint on it yes
sir<01:34:13.600> well<01:34:13.760> they<01:34:13.840> won't<01:34:14.040> do<01:34:14.159> anything<01:34:14.400> till

01:34:14.629 --> 01:34:14.639 align:start position:0%
sir well they won't do anything till
 

01:34:14.639 --> 01:34:15.750 align:start position:0%
sir well they won't do anything till
next

01:34:15.750 --> 01:34:15.760 align:start position:0%
next
 

01:34:15.760 --> 01:34:19.990 align:start position:0%
next
year<01:34:16.760> but<01:34:17.400> Point<01:34:17.600> somebody<01:34:17.960> if<01:34:18.040> you<01:34:18.199> ask<01:34:18.840> to<01:34:19.840> I

01:34:19.990 --> 01:34:20.000 align:start position:0%
year but Point somebody if you ask to I
 

01:34:20.000 --> 01:34:22.390 align:start position:0%
year but Point somebody if you ask to I
need<01:34:20.159> to<01:34:20.880> sounds<01:34:21.199> like<01:34:21.360> it

01:34:22.390 --> 01:34:22.400 align:start position:0%
need to sounds like it
 

01:34:22.400 --> 01:34:23.870 align:start position:0%
need to sounds like it
unless<01:34:22.679> he<01:34:22.800> wants<01:34:23.000> to<01:34:23.119> kill<01:34:23.320> the<01:34:23.440> authority

01:34:23.870 --> 01:34:23.880 align:start position:0%
unless he wants to kill the authority
 

01:34:23.880 --> 01:34:27.350 align:start position:0%
unless he wants to kill the authority
then<01:34:24.000> he<01:34:24.239> won't<01:34:25.239> is<01:34:25.719> off<01:34:26.719> since<01:34:26.880> he<01:34:27.040> voted

01:34:27.350 --> 01:34:27.360 align:start position:0%
then he won't is off since he voted
 

01:34:27.360 --> 01:34:30.270 align:start position:0%
then he won't is off since he voted
against<01:34:27.600> the<01:34:27.760> bill

01:34:30.270 --> 01:34:30.280 align:start position:0%
against the bill
 

01:34:30.280 --> 01:34:32.870 align:start position:0%
against the bill
2015<01:34:31.280> um<01:34:31.560> so<01:34:31.840> wanted<01:34:32.040> to<01:34:32.199> raise<01:34:32.480> that<01:34:32.600> for<01:34:32.760> you

01:34:32.870 --> 01:34:32.880 align:start position:0%
2015 um so wanted to raise that for you
 

01:34:32.880 --> 01:34:34.830 align:start position:0%
2015 um so wanted to raise that for you
all<01:34:33.119> they<01:34:33.239> sent<01:34:33.480> their<01:34:33.719> regrets<01:34:34.360> but<01:34:34.560> we

01:34:34.830 --> 01:34:34.840 align:start position:0%
all they sent their regrets but we
 

01:34:34.840 --> 01:34:36.350 align:start position:0%
all they sent their regrets but we
course<01:34:35.119> thank<01:34:35.360> them<01:34:35.480> for<01:34:35.679> their<01:34:35.800> service<01:34:36.199> to

01:34:36.350 --> 01:34:36.360 align:start position:0%
course thank them for their service to
 

01:34:36.360 --> 01:34:38.669 align:start position:0%
course thank them for their service to
the<01:34:36.560> authority<01:34:37.560> um<01:34:37.719> and<01:34:37.840> then<01:34:38.000> also<01:34:38.199> wanted<01:34:38.480> to

01:34:38.669 --> 01:34:38.679 align:start position:0%
the authority um and then also wanted to
 

01:34:38.679 --> 01:34:41.590 align:start position:0%
the authority um and then also wanted to
raise<01:34:38.960> the<01:34:39.080> issue<01:34:39.280> of<01:34:39.360> a<01:34:39.560> web<01:34:40.000> of<01:34:40.199> the<01:34:40.600> website

01:34:41.590 --> 01:34:41.600 align:start position:0%
raise the issue of a web of the website
 

01:34:41.600 --> 01:34:44.030 align:start position:0%
raise the issue of a web of the website
um<01:34:41.800> got<01:34:41.960> an<01:34:42.119> email<01:34:42.440> last<01:34:42.639> week<01:34:42.920> asking<01:34:43.360> about

01:34:44.030 --> 01:34:44.040 align:start position:0%
um got an email last week asking about
 

01:34:44.040 --> 01:34:46.950 align:start position:0%
um got an email last week asking about
the<01:34:44.159> Sol<01:34:44.560> authorities<01:34:45.119> website<01:34:46.040> and<01:34:46.719> uh

01:34:46.950 --> 01:34:46.960 align:start position:0%
the Sol authorities website and uh
 

01:34:46.960 --> 01:34:48.310 align:start position:0%
the Sol authorities website and uh
whether<01:34:47.199> that<01:34:47.320> will<01:34:47.520> be<01:34:47.679> a<01:34:47.840> tool<01:34:48.080> that<01:34:48.199> the

01:34:48.310 --> 01:34:48.320 align:start position:0%
whether that will be a tool that the
 

01:34:48.320 --> 01:34:50.270 align:start position:0%
whether that will be a tool that the
authority<01:34:48.679> uses<01:34:48.960> to<01:34:49.119> keep<01:34:49.440> the<01:34:49.639> public

01:34:50.270 --> 01:34:50.280 align:start position:0%
authority uses to keep the public
 

01:34:50.280 --> 01:34:53.149 align:start position:0%
authority uses to keep the public
updated<01:34:51.000> and<01:34:51.159> engaged<01:34:51.520> P<01:34:52.239> can<01:34:52.520> let<01:34:52.639> me<01:34:52.800> know

01:34:53.149 --> 01:34:53.159 align:start position:0%
updated and engaged P can let me know
 

01:34:53.159 --> 01:34:55.990 align:start position:0%
updated and engaged P can let me know
that<01:34:53.639> the<01:34:54.400> website<01:34:54.880> along<01:34:55.119> with<01:34:55.280> many<01:34:55.560> others

01:34:55.990 --> 01:34:56.000 align:start position:0%
that the website along with many others
 

01:34:56.000 --> 01:34:59.830 align:start position:0%
that the website along with many others
are<01:34:56.960> undergoing<01:34:57.800> an<01:34:58.119> overhaul<01:34:59.119> by<01:34:59.239> the<01:34:59.440> F<01:34:59.639> down

01:34:59.830 --> 01:34:59.840 align:start position:0%
are undergoing an overhaul by the F down
 

01:34:59.840 --> 01:35:03.189 align:start position:0%
are undergoing an overhaul by the F down
the<01:34:59.960> big<01:35:00.960> moved<01:35:01.360> behind<01:35:01.719> the<01:35:02.199> Commonwealth's

01:35:03.189 --> 01:35:03.199 align:start position:0%
the big moved behind the Commonwealth's
 

01:35:03.199 --> 01:35:06.830 align:start position:0%
the big moved behind the Commonwealth's
domain<01:35:04.119> excellent<01:35:04.840> so<01:35:05.040> we'll<01:35:06.040> probably<01:35:06.520> say

01:35:06.830 --> 01:35:06.840 align:start position:0%
domain excellent so we'll probably say
 

01:35:06.840 --> 01:35:09.310 align:start position:0%
domain excellent so we'll probably say
goodbye<01:35:07.199> to<01:35:07.320> that<01:35:07.520> old<01:35:07.880> website<01:35:08.880> sometime

01:35:09.310 --> 01:35:09.320 align:start position:0%
goodbye to that old website sometime
 

01:35:09.320 --> 01:35:11.590 align:start position:0%
goodbye to that old website sometime
soon<01:35:09.800> and<01:35:09.960> that<01:35:10.159> the<01:35:10.360> new<01:35:10.560> website<01:35:11.199> whenever

01:35:11.590 --> 01:35:11.600 align:start position:0%
soon and that the new website whenever
 

01:35:11.600 --> 01:35:15.109 align:start position:0%
soon and that the new website whenever
that<01:35:11.800> takes<01:35:12.119> place<01:35:12.400> can<01:35:12.600> be<01:35:13.600> a

01:35:15.109 --> 01:35:15.119 align:start position:0%
that takes place can be a
 

01:35:15.119 --> 01:35:17.830 align:start position:0%
that takes place can be a
more<01:35:16.119> a<01:35:16.239> more<01:35:16.440> out<01:35:16.639> today<01:35:17.159> representation<01:35:17.719> of

01:35:17.830 --> 01:35:17.840 align:start position:0%
more a more out today representation of
 

01:35:17.840 --> 01:35:19.109 align:start position:0%
more a more out today representation of
the

01:35:19.109 --> 01:35:19.119 align:start position:0%
the
 

01:35:19.119 --> 01:35:22.870 align:start position:0%
the
authority<01:35:20.400> great

01:35:22.870 --> 01:35:22.880 align:start position:0%
authority great
 

01:35:22.880 --> 01:35:26.189 align:start position:0%
authority great
um<01:35:23.880> that<01:35:24.040> is<01:35:24.119> there<01:35:24.280> any<01:35:24.480> other<01:35:25.440> discussion

01:35:26.189 --> 01:35:26.199 align:start position:0%
um that is there any other discussion
 

01:35:26.199 --> 01:35:29.950 align:start position:0%
um that is there any other discussion
from<01:35:26.920> any<01:35:27.080> of<01:35:27.639> the<01:35:28.639> members<01:35:29.000> on<01:35:29.199> any<01:35:29.480> topic<01:35:29.800> any

01:35:29.950 --> 01:35:29.960 align:start position:0%
from any of the members on any topic any
 

01:35:29.960 --> 01:35:32.990 align:start position:0%
from any of the members on any topic any
more<01:35:30.199> questions<01:35:30.520> for<01:35:31.119> AJ<01:35:32.119> in<01:35:32.239> terms<01:35:32.480> of<01:35:32.639> the

01:35:32.990 --> 01:35:33.000 align:start position:0%
more questions for AJ in terms of the
 

01:35:33.000 --> 01:35:35.910 align:start position:0%
more questions for AJ in terms of the
vacancies<01:35:34.000> um<01:35:34.440> is<01:35:34.679> there<01:35:34.880> an<01:35:35.080> announcement

01:35:35.910 --> 01:35:35.920 align:start position:0%
vacancies um is there an announcement
 

01:35:35.920 --> 01:35:38.149 align:start position:0%
vacancies um is there an announcement
anywhere<01:35:36.719> that<01:35:37.000> I<01:35:37.159> could<01:35:37.360> reference<01:35:37.840> if<01:35:38.000> I

01:35:38.149 --> 01:35:38.159 align:start position:0%
anywhere that I could reference if I
 

01:35:38.159 --> 01:35:38.990 align:start position:0%
anywhere that I could reference if I
have

01:35:38.990 --> 01:35:39.000 align:start position:0%
have
 

01:35:39.000 --> 01:35:42.629 align:start position:0%
have
recommendations<01:35:40.000> of<01:35:40.199> people<01:35:40.440> to

01:35:42.629 --> 01:35:42.639 align:start position:0%
recommendations of people to
 

01:35:42.639 --> 01:35:45.430 align:start position:0%
recommendations of people to
apply<01:35:43.639> if<01:35:43.719> you<01:35:43.840> have<01:35:44.199> recommendations<01:35:45.199> I

01:35:45.430 --> 01:35:45.440 align:start position:0%
apply if you have recommendations I
 

01:35:45.440 --> 01:35:48.270 align:start position:0%
apply if you have recommendations I
would<01:35:45.840> Rec<01:35:46.600> recommend<01:35:47.119> you<01:35:47.560> recommend<01:35:48.040> to

01:35:48.270 --> 01:35:48.280 align:start position:0%
would Rec recommend you recommend to
 

01:35:48.280 --> 01:35:50.390 align:start position:0%
would Rec recommend you recommend to
them<01:35:48.840> that<01:35:49.040> they<01:35:49.199> go<01:35:49.360> on<01:35:49.560> to<01:35:49.760> the

01:35:50.390 --> 01:35:50.400 align:start position:0%
them that they go on to the
 

01:35:50.400 --> 01:35:52.830 align:start position:0%
them that they go on to the
governor's<01:35:51.440> website<01:35:51.840> and<01:35:52.000> there's<01:35:52.199> a<01:35:52.400> page<01:35:52.600> on

01:35:52.830 --> 01:35:52.840 align:start position:0%
governor's website and there's a page on
 

01:35:52.840 --> 01:35:54.669 align:start position:0%
governor's website and there's a page on
there<01:35:53.040> where<01:35:53.199> you<01:35:53.400> can<01:35:53.880> put<01:35:54.040> your<01:35:54.199> name<01:35:54.360> in<01:35:54.480> the

01:35:54.669 --> 01:35:54.679 align:start position:0%
there where you can put your name in the
 

01:35:54.679 --> 01:35:57.109 align:start position:0%
there where you can put your name in the
Hat<01:35:55.000> to<01:35:55.320> serve<01:35:55.679> on<01:35:56.360> different<01:35:56.639> boards<01:35:56.960> and

01:35:57.109 --> 01:35:57.119 align:start position:0%
Hat to serve on different boards and
 

01:35:57.119 --> 01:35:59.149 align:start position:0%
Hat to serve on different boards and
authorities<01:35:57.960> and<01:35:58.119> that's<01:35:58.239> for<01:35:58.440> the<01:35:58.600> governor

01:35:59.149 --> 01:35:59.159 align:start position:0%
authorities and that's for the governor
 

01:35:59.159 --> 01:36:02.350 align:start position:0%
authorities and that's for the governor
appoint<01:35:59.800> and<01:36:00.119> Senate<01:36:00.719> it<01:36:00.880> is<01:36:01.520> I<01:36:01.639> believe<01:36:01.960> so<01:36:02.280> I

01:36:02.350 --> 01:36:02.360 align:start position:0%
appoint and Senate it is I believe so I
 

01:36:02.360 --> 01:36:03.590 align:start position:0%
appoint and Senate it is I believe so I
don't<01:36:02.560> think<01:36:02.719> there's<01:36:02.920> anything<01:36:03.280> separate

01:36:03.590 --> 01:36:03.600 align:start position:0%
don't think there's anything separate
 

01:36:03.600 --> 01:36:05.430 align:start position:0%
don't think there's anything separate
for<01:36:03.719> the<01:36:03.840> House<01:36:04.000> and<01:36:04.159> Senate<01:36:04.600> okay<01:36:05.119> go<01:36:05.280> to<01:36:05.360> the

01:36:05.430 --> 01:36:05.440 align:start position:0%
for the House and Senate okay go to the
 

01:36:05.440 --> 01:36:06.830 align:start position:0%
for the House and Senate okay go to the
House<01:36:05.560> and<01:36:05.639> Senate<01:36:05.920> use<01:36:06.080> that

01:36:06.830 --> 01:36:06.840 align:start position:0%
House and Senate use that
 

01:36:06.840 --> 01:36:09.109 align:start position:0%
House and Senate use that
list

01:36:09.109 --> 01:36:09.119 align:start position:0%
list
 

01:36:09.119 --> 01:36:13.750 align:start position:0%
list
just<01:36:10.119> I<01:36:10.239> have<01:36:10.400> no<01:36:10.600> idea<01:36:11.119> yeah<01:36:11.880> I<01:36:12.000> know<01:36:12.760> that

01:36:13.750 --> 01:36:13.760 align:start position:0%
just I have no idea yeah I know that
 

01:36:13.760 --> 01:36:15.990 align:start position:0%
just I have no idea yeah I know that
Governor's<01:36:14.280> appointees<01:36:14.960> tend<01:36:15.199> to<01:36:15.600> happen

01:36:15.990 --> 01:36:16.000 align:start position:0%
Governor's appointees tend to happen
 

01:36:16.000 --> 01:36:18.709 align:start position:0%
Governor's appointees tend to happen
much<01:36:16.320> sooner<01:36:16.840> than<01:36:17.080> House<01:36:17.320> and<01:36:17.480> Senate

01:36:18.709 --> 01:36:18.719 align:start position:0%
much sooner than House and Senate
 

01:36:18.719 --> 01:36:20.910 align:start position:0%
much sooner than House and Senate
Appo<01:36:19.719> yeah<01:36:19.880> I<01:36:20.040> suggest<01:36:20.320> if<01:36:20.440> you<01:36:20.520> have<01:36:20.639> someone

01:36:20.910 --> 01:36:20.920 align:start position:0%
Appo yeah I suggest if you have someone
 

01:36:20.920 --> 01:36:22.430 align:start position:0%
Appo yeah I suggest if you have someone
who<01:36:21.000> you<01:36:21.119> want<01:36:21.400> speaker<01:36:21.679> to<01:36:21.800> a<01:36:21.880> point<01:36:22.119> you<01:36:22.280> talk

01:36:22.430 --> 01:36:22.440 align:start position:0%
who you want speaker to a point you talk
 

01:36:22.440 --> 01:36:26.030 align:start position:0%
who you want speaker to a point you talk
to<01:36:22.639> Dr<01:36:23.000> Skyler<01:36:24.000> and<01:36:24.159> ask<01:36:24.360> him<01:36:24.480> to<01:36:25.040> communicate

01:36:26.030 --> 01:36:26.040 align:start position:0%
to Dr Skyler and ask him to communicate
 

01:36:26.040 --> 01:36:27.790 align:start position:0%
to Dr Skyler and ask him to communicate
I<01:36:26.159> don't<01:36:26.280> you<01:36:26.480> do<01:36:26.639> it<01:36:27.000> I<01:36:27.080> mean<01:36:27.199> i'<01:36:27.320> be<01:36:27.440> happy<01:36:27.719> we

01:36:27.790 --> 01:36:27.800 align:start position:0%
I don't you do it I mean i' be happy we
 

01:36:27.800 --> 01:36:30.590 align:start position:0%
I don't you do it I mean i' be happy we
have<01:36:28.000> an<01:36:28.119> email<01:36:28.800> um<01:36:29.040> yeah<01:36:29.239> we<01:36:29.679> I<01:36:29.880> know<01:36:30.080> the

01:36:30.590 --> 01:36:30.600 align:start position:0%
have an email um yeah we I know the
 

01:36:30.600 --> 01:36:32.790 align:start position:0%
have an email um yeah we I know the
person<01:36:30.880> who<01:36:31.040> takes<01:36:31.360> care<01:36:31.520> of<01:36:31.719> that

01:36:32.790 --> 01:36:32.800 align:start position:0%
person who takes care of that
 

01:36:32.800 --> 01:36:35.950 align:start position:0%
person who takes care of that
and<01:36:33.800> they're<01:36:34.000> usually<01:36:34.320> avable

01:36:35.950 --> 01:36:35.960 align:start position:0%
and they're usually avable
 

01:36:35.960 --> 01:36:37.470 align:start position:0%
and they're usually avable
to

01:36:37.470 --> 01:36:37.480 align:start position:0%
to
 

01:36:37.480 --> 01:36:41.070 align:start position:0%
to
recommendations

01:36:41.070 --> 01:36:41.080 align:start position:0%
 
 

01:36:41.080 --> 01:36:43.709 align:start position:0%
 
okay<01:36:42.080> all<01:36:42.239> right<01:36:42.639> I<01:36:42.800> I<01:36:42.920> know<01:36:43.080> we<01:36:43.239> still<01:36:43.520> have

01:36:43.709 --> 01:36:43.719 align:start position:0%
okay all right I I know we still have
 

01:36:43.719 --> 01:36:45.750 align:start position:0%
okay all right I I know we still have
several<01:36:44.159> members<01:36:44.800> or<01:36:44.960> several<01:36:45.320> members<01:36:45.520> of

01:36:45.750 --> 01:36:45.760 align:start position:0%
several members or several members of
 

01:36:45.760 --> 01:36:48.270 align:start position:0%
several members or several members of
public<01:36:46.480> still<01:36:46.800> joining<01:36:47.280> online<01:36:47.800> so<01:36:48.000> I<01:36:48.080> will

01:36:48.270 --> 01:36:48.280 align:start position:0%
public still joining online so I will
 

01:36:48.280 --> 01:36:50.830 align:start position:0%
public still joining online so I will
open<01:36:48.480> it<01:36:48.639> up<01:36:48.840> for<01:36:49.440> a<01:36:49.719> public<01:36:50.080> comment<01:36:50.639> if

01:36:50.830 --> 01:36:50.840 align:start position:0%
open it up for a public comment if
 

01:36:50.840 --> 01:36:52.270 align:start position:0%
open it up for a public comment if
anybody

01:36:52.270 --> 01:36:52.280 align:start position:0%
anybody
 

01:36:52.280 --> 01:36:55.270 align:start position:0%
anybody
in<01:36:53.000> person<01:36:54.000> that's<01:36:54.239> Tyson<01:36:54.560> or<01:36:54.760> my<01:36:54.920> colleague

01:36:55.270 --> 01:36:55.280 align:start position:0%
in person that's Tyson or my colleague
 

01:36:55.280 --> 01:36:57.910 align:start position:0%
in person that's Tyson or my colleague
Jak<01:36:55.719> carella<01:36:56.520> with<01:36:56.679> enview<01:36:57.280> right<01:36:57.679> would<01:36:57.800> like

01:36:57.910 --> 01:36:57.920 align:start position:0%
Jak carella with enview right would like
 

01:36:57.920 --> 01:37:00.790 align:start position:0%
Jak carella with enview right would like
to<01:36:58.000> share<01:36:58.239> any<01:36:58.719> public<01:36:59.400> comments<01:37:00.400> K<01:37:00.600> do<01:37:00.719> we

01:37:00.790 --> 01:37:00.800 align:start position:0%
to share any public comments K do we
 

01:37:00.800 --> 01:37:10.830 align:start position:0%
to share any public comments K do we
need<01:37:00.920> to<01:37:01.119> unmute<01:37:01.560> anybody<01:37:02.159> or<01:37:02.920> no<01:37:03.920> all

01:37:10.830 --> 01:37:10.840 align:start position:0%
 
 

01:37:10.840 --> 01:37:15.430 align:start position:0%
 
well<01:37:11.840> how<01:37:12.000> do<01:37:12.119> you<01:37:12.360> unmute

01:37:15.430 --> 01:37:15.440 align:start position:0%
 
 

01:37:15.440 --> 01:37:20.189 align:start position:0%
 
all<01:37:16.440> they<01:37:16.560> can<01:37:16.960> back<01:37:17.239> again

01:37:20.189 --> 01:37:20.199 align:start position:0%
 
 

01:37:20.199 --> 01:37:27.910 align:start position:0%
 
or

01:37:27.910 --> 01:37:27.920 align:start position:0%
 
 

01:37:27.920 --> 01:37:30.510 align:start position:0%
 
once<01:37:28.199> or<01:37:28.400> twice<01:37:28.679> anybody<01:37:29.000> on<01:37:29.159> the<01:37:29.679> teams<01:37:30.119> link

01:37:30.510 --> 01:37:30.520 align:start position:0%
once or twice anybody on the teams link
 

01:37:30.520 --> 01:37:40.470 align:start position:0%
once or twice anybody on the teams link
want<01:37:30.639> to<01:37:30.760> share<01:37:31.040> public<01:37:31.320> comment<01:37:31.639> with<01:37:31.719> the

01:37:40.470 --> 01:37:40.480 align:start position:0%
 
 

01:37:40.480 --> 01:37:45.109 align:start position:0%
 
authority<01:37:41.480> hand

01:37:45.109 --> 01:37:45.119 align:start position:0%
 
 

01:37:45.119 --> 01:37:48.629 align:start position:0%
 
to<01:37:46.119> well<01:37:46.440> with<01:37:46.800> that<01:37:47.679> um<01:37:47.880> thank<01:37:48.040> you<01:37:48.280> everyone

01:37:48.629 --> 01:37:48.639 align:start position:0%
to well with that um thank you everyone
 

01:37:48.639 --> 01:37:50.310 align:start position:0%
to well with that um thank you everyone
for<01:37:48.880> coming<01:37:49.239> I<01:37:49.320> think<01:37:49.480> we<01:37:49.599> have<01:37:49.719> our<01:37:49.880> work<01:37:50.159> cut

01:37:50.310 --> 01:37:50.320 align:start position:0%
for coming I think we have our work cut
 

01:37:50.320 --> 01:37:53.030 align:start position:0%
for coming I think we have our work cut
out<01:37:50.520> for<01:37:50.719> us<01:37:51.320> prior<01:37:51.639> to<01:37:51.840> the<01:37:52.040> September<01:37:52.480> 13th

01:37:53.030 --> 01:37:53.040 align:start position:0%
out for us prior to the September 13th
 

01:37:53.040 --> 01:37:56.189 align:start position:0%
out for us prior to the September 13th
meeting<01:37:54.040> lining<01:37:54.520> up<01:37:55.040> additional<01:37:55.480> quotes<01:37:55.920> to

01:37:56.189 --> 01:37:56.199 align:start position:0%
meeting lining up additional quotes to
 

01:37:56.199 --> 01:37:59.350 align:start position:0%
meeting lining up additional quotes to
present<01:37:56.599> to<01:37:57.159> the<01:37:57.520> authority<01:37:58.520> developing<01:37:59.199> a

01:37:59.350 --> 01:37:59.360 align:start position:0%
present to the authority developing a
 

01:37:59.360 --> 01:38:04.470 align:start position:0%
present to the authority developing a
framework<01:37:59.960> for<01:38:00.199> the<01:38:00.360> 105<01:38:01.199> page<01:38:02.239> report<01:38:03.239> and

01:38:04.470 --> 01:38:04.480 align:start position:0%
framework for the 105 page report and
 

01:38:04.480 --> 01:38:07.510 align:start position:0%
framework for the 105 page report and
um<01:38:05.480> moving<01:38:06.000> moving<01:38:06.280> towards<01:38:06.599> that<01:38:06.800> report<01:38:07.159> and

01:38:07.510 --> 01:38:07.520 align:start position:0%
um moving moving towards that report and
 

01:38:07.520 --> 01:38:10.430 align:start position:0%
um moving moving towards that report and
making<01:38:07.800> it<01:38:08.040> as<01:38:08.360> sing<01:38:08.960> and<01:38:09.119> useful<01:38:09.639> to<01:38:10.239> the

01:38:10.430 --> 01:38:10.440 align:start position:0%
making it as sing and useful to the
 

01:38:10.440 --> 01:38:14.229 align:start position:0%
making it as sing and useful to the
governor<01:38:10.880> general<01:38:11.159> assembly<01:38:11.639> as<01:38:11.960> possible<01:38:13.239> um

01:38:14.229 --> 01:38:14.239 align:start position:0%
governor general assembly as possible um
 

01:38:14.239 --> 01:38:16.790 align:start position:0%
governor general assembly as possible um
I<01:38:14.520> will<01:38:15.239> entertain<01:38:15.679> a<01:38:15.840> motion<01:38:16.119> to<01:38:16.320> adjourn

01:38:16.790 --> 01:38:16.800 align:start position:0%
I will entertain a motion to adjourn
 

01:38:16.800 --> 01:38:19.830 align:start position:0%
I will entertain a motion to adjourn
until<01:38:17.199> 10:00<01:38:17.440> a.m.<01:38:17.840> on<01:38:18.080> September<01:38:18.560> 13th<01:38:19.239> so

01:38:19.830 --> 01:38:19.840 align:start position:0%
until 10:00 a.m. on September 13th so
 

01:38:19.840 --> 01:38:22.229 align:start position:0%
until 10:00 a.m. on September 13th so
moved<01:38:20.840> have<01:38:20.920> a

01:38:22.229 --> 01:38:22.239 align:start position:0%
moved have a
 

01:38:22.239 --> 01:38:24.910 align:start position:0%
moved have a
second<01:38:23.239> all<01:38:23.360> those<01:38:23.520> in<01:38:23.679> favor<01:38:24.080> please<01:38:24.800> by

01:38:24.910 --> 01:38:24.920 align:start position:0%
second all those in favor please by
 

01:38:24.920 --> 01:38:25.830 align:start position:0%
second all those in favor please by
saying

01:38:25.830 --> 01:38:25.840 align:start position:0%
saying
 

01:38:25.840 --> 01:38:27.950 align:start position:0%
saying
I<01:38:26.840> all<01:38:26.960> those

01:38:27.950 --> 01:38:27.960 align:start position:0%
I all those
 

01:38:27.960 --> 01:38:50.109 align:start position:0%
I all those
oppos<01:38:28.960> meting<01:38:29.840> thank<01:38:30.000> you

01:38:50.109 --> 01:38:50.119 align:start position:0%
 
 

01:38:50.119 --> 01:38:53.119 align:start position:0%
 
all