WEBVTT Kind: captions Language: en 00:00:07.759 --> 00:00:14.629 align:start position:0% all<00:00:07.839> right<00:00:08.480> a<00:00:08.720> new<00:00:08.880> gavel<00:00:09.200> today 00:00:14.629 --> 00:00:14.639 align:start position:0% 00:00:14.639 --> 00:00:15.910 align:start position:0% this<00:00:14.880> meeting<00:00:15.120> of<00:00:15.200> the<00:00:15.280> public<00:00:15.599> utility 00:00:15.910 --> 00:00:15.920 align:start position:0% this meeting of the public utility 00:00:15.920 --> 00:00:17.189 align:start position:0% this meeting of the public utility commission<00:00:16.240> of<00:00:16.320> texas<00:00:16.640> will<00:00:16.720> come<00:00:16.880> to<00:00:16.960> order 00:00:17.189 --> 00:00:17.199 align:start position:0% commission of texas will come to order 00:00:17.199 --> 00:00:18.550 align:start position:0% commission of texas will come to order to<00:00:17.279> consider<00:00:17.680> matters<00:00:18.000> have<00:00:18.080> been<00:00:18.240> duly 00:00:18.550 --> 00:00:18.560 align:start position:0% to consider matters have been duly 00:00:18.560 --> 00:00:19.830 align:start position:0% to consider matters have been duly posted<00:00:18.880> with<00:00:18.960> the<00:00:19.039> secretary<00:00:19.439> of<00:00:19.520> state<00:00:19.680> of 00:00:19.830 --> 00:00:19.840 align:start position:0% posted with the secretary of state of 00:00:19.840 --> 00:00:22.870 align:start position:0% posted with the secretary of state of texas<00:00:20.320> for<00:00:20.480> november<00:00:21.119> 4th<00:00:21.600> 2021.<00:00:22.640> for<00:00:22.800> the 00:00:22.870 --> 00:00:22.880 align:start position:0% texas for november 4th 2021. for the 00:00:22.880 --> 00:00:24.870 align:start position:0% texas for november 4th 2021. for the record<00:00:23.119> my<00:00:23.279> name<00:00:23.359> is<00:00:23.439> peter<00:00:23.760> lake<00:00:24.400> and<00:00:24.560> with<00:00:24.720> me 00:00:24.870 --> 00:00:24.880 align:start position:0% record my name is peter lake and with me 00:00:24.880 --> 00:00:26.710 align:start position:0% record my name is peter lake and with me today<00:00:25.119> are<00:00:25.199> will<00:00:25.439> mcadams<00:00:26.000> lori<00:00:26.320> kovas<00:00:26.640> and 00:00:26.710 --> 00:00:26.720 align:start position:0% today are will mcadams lori kovas and 00:00:26.720 --> 00:00:29.509 align:start position:0% today are will mcadams lori kovas and jimmy<00:00:27.039> glotfelty<00:00:28.160> our<00:00:28.480> primary<00:00:28.800> focus<00:00:29.199> today 00:00:29.509 --> 00:00:29.519 align:start position:0% jimmy glotfelty our primary focus today 00:00:29.519 --> 00:00:32.870 align:start position:0% jimmy glotfelty our primary focus today will<00:00:29.679> be<00:00:30.080> on<00:00:30.640> market<00:00:30.960> redesign 00:00:32.870 --> 00:00:32.880 align:start position:0% will be on market redesign 00:00:32.880 --> 00:00:35.430 align:start position:0% will be on market redesign but<00:00:33.360> first 00:00:35.430 --> 00:00:35.440 align:start position:0% but first 00:00:35.440 --> 00:00:37.110 align:start position:0% but first if<00:00:35.600> my<00:00:35.760> colleagues<00:00:36.160> will 00:00:37.110 --> 00:00:37.120 align:start position:0% if my colleagues will 00:00:37.120 --> 00:00:38.549 align:start position:0% if my colleagues will accommodate<00:00:37.680> me 00:00:38.549 --> 00:00:38.559 align:start position:0% accommodate me 00:00:38.559 --> 00:00:42.310 align:start position:0% accommodate me i<00:00:38.719> want<00:00:38.879> to<00:00:39.040> touch<00:00:39.360> on<00:00:39.760> item<00:00:40.320> 22<00:00:40.879> docket<00:00:41.239> 52631 00:00:42.310 --> 00:00:42.320 align:start position:0% i want to touch on item 22 docket 52631 00:00:42.320 --> 00:00:46.470 align:start position:0% i want to touch on item 22 docket 52631 regarding<00:00:42.719> the<00:00:42.800> rule<00:00:43.040> making<00:00:43.360> to<00:00:43.520> adjust<00:00:44.000> hcap 00:00:46.470 --> 00:00:46.480 align:start position:0% regarding the rule making to adjust hcap 00:00:46.480 --> 00:00:48.869 align:start position:0% regarding the rule making to adjust hcap i<00:00:46.559> think<00:00:46.960> very<00:00:47.280> appropriately<00:00:48.000> we 00:00:48.869 --> 00:00:48.879 align:start position:0% i think very appropriately we 00:00:48.879 --> 00:00:50.389 align:start position:0% i think very appropriately we accelerated<00:00:49.360> that<00:00:49.520> process<00:00:49.920> to<00:00:50.000> make<00:00:50.160> sure<00:00:50.320> we 00:00:50.389 --> 00:00:50.399 align:start position:0% accelerated that process to make sure we 00:00:50.399 --> 00:00:52.229 align:start position:0% accelerated that process to make sure we can<00:00:50.480> have<00:00:50.640> the<00:00:50.719> change<00:00:50.960> in<00:00:51.120> place<00:00:51.360> by<00:00:51.680> january 00:00:52.229 --> 00:00:52.239 align:start position:0% can have the change in place by january 00:00:52.239 --> 00:00:54.790 align:start position:0% can have the change in place by january 1st 00:00:54.790 --> 00:00:54.800 align:start position:0% 00:00:54.800 --> 00:00:56.709 align:start position:0% and<00:00:54.960> more<00:00:55.120> importantly<00:00:55.920> i<00:00:56.079> want<00:00:56.239> to<00:00:56.320> thank<00:00:56.559> a 00:00:56.709 --> 00:00:56.719 align:start position:0% and more importantly i want to thank a 00:00:56.719 --> 00:01:00.310 align:start position:0% and more importantly i want to thank a staff<00:00:57.280> for<00:00:57.600> the<00:00:57.760> incredible<00:00:58.239> turnaround<00:00:59.280> on 00:01:00.310 --> 00:01:00.320 align:start position:0% staff for the incredible turnaround on 00:01:00.320 --> 00:01:01.990 align:start position:0% staff for the incredible turnaround on processing<00:01:00.960> and<00:01:01.039> responding<00:01:01.440> to<00:01:01.680> all<00:01:01.840> of<00:01:01.840> the 00:01:01.990 --> 00:01:02.000 align:start position:0% processing and responding to all of the 00:01:02.000 --> 00:01:03.590 align:start position:0% processing and responding to all of the stakeholder<00:01:02.640> comments 00:01:03.590 --> 00:01:03.600 align:start position:0% stakeholder comments 00:01:03.600 --> 00:01:05.750 align:start position:0% stakeholder comments in<00:01:03.680> an<00:01:03.840> incredibly<00:01:04.400> short<00:01:04.720> amount<00:01:05.040> of<00:01:05.199> time 00:01:05.750 --> 00:01:05.760 align:start position:0% in an incredibly short amount of time 00:01:05.760 --> 00:01:07.429 align:start position:0% in an incredibly short amount of time thank<00:01:06.000> you<00:01:06.240> very<00:01:06.400> much<00:01:06.560> for<00:01:06.720> the<00:01:06.799> hard<00:01:07.040> work<00:01:07.280> on 00:01:07.429 --> 00:01:07.439 align:start position:0% thank you very much for the hard work on 00:01:07.439 --> 00:01:08.789 align:start position:0% thank you very much for the hard work on that 00:01:08.789 --> 00:01:08.799 align:start position:0% that 00:01:08.799 --> 00:01:11.350 align:start position:0% that as<00:01:09.040> we<00:01:09.200> all<00:01:09.360> know<00:01:09.920> hcap<00:01:10.400> is<00:01:10.560> an<00:01:10.640> integral<00:01:11.040> part 00:01:11.350 --> 00:01:11.360 align:start position:0% as we all know hcap is an integral part 00:01:11.360 --> 00:01:14.950 align:start position:0% as we all know hcap is an integral part of<00:01:11.760> ordc<00:01:12.479> the<00:01:12.560> various<00:01:12.880> mechanisms<00:01:13.439> of<00:01:13.600> ordc 00:01:14.950 --> 00:01:14.960 align:start position:0% of ordc the various mechanisms of ordc 00:01:14.960 --> 00:01:15.670 align:start position:0% of ordc the various mechanisms of ordc so 00:01:15.670 --> 00:01:15.680 align:start position:0% so 00:01:15.680 --> 00:01:18.070 align:start position:0% so in<00:01:15.840> order<00:01:16.080> to<00:01:16.240> retain<00:01:16.479> the<00:01:16.640> flexibility<00:01:17.680> uh<00:01:18.000> on 00:01:18.070 --> 00:01:18.080 align:start position:0% in order to retain the flexibility uh on 00:01:18.080 --> 00:01:21.350 align:start position:0% in order to retain the flexibility uh on the<00:01:18.240> rdc<00:01:19.119> i<00:01:19.200> think<00:01:19.759> i'd<00:01:19.920> like<00:01:20.080> to<00:01:20.240> table<00:01:20.799> the 00:01:21.350 --> 00:01:21.360 align:start position:0% the rdc i think i'd like to table the 00:01:21.360 --> 00:01:24.070 align:start position:0% the rdc i think i'd like to table the official<00:01:21.840> decision<00:01:22.400> for<00:01:22.640> adoption 00:01:24.070 --> 00:01:24.080 align:start position:0% official decision for adoption 00:01:24.080 --> 00:01:26.390 align:start position:0% official decision for adoption until<00:01:24.320> a<00:01:24.400> later<00:01:24.720> date<00:01:24.960> so<00:01:25.119> we<00:01:25.280> can 00:01:26.390 --> 00:01:26.400 align:start position:0% until a later date so we can 00:01:26.400 --> 00:01:29.429 align:start position:0% until a later date so we can do<00:01:26.560> that<00:01:26.799> in<00:01:26.960> conjunction<00:01:27.759> with 00:01:29.429 --> 00:01:29.439 align:start position:0% do that in conjunction with 00:01:29.439 --> 00:01:31.510 align:start position:0% do that in conjunction with whatever<00:01:29.759> we<00:01:30.320> settle<00:01:30.640> on<00:01:30.720> for<00:01:30.880> the<00:01:30.960> rdc 00:01:31.510 --> 00:01:31.520 align:start position:0% whatever we settle on for the rdc 00:01:31.520 --> 00:01:33.270 align:start position:0% whatever we settle on for the rdc changes 00:01:33.270 --> 00:01:33.280 align:start position:0% changes 00:01:33.280 --> 00:01:34.550 align:start position:0% changes but 00:01:34.550 --> 00:01:34.560 align:start position:0% but 00:01:34.560 --> 00:01:36.390 align:start position:0% but we'll<00:01:34.720> table<00:01:34.960> that<00:01:35.119> for<00:01:35.280> today<00:01:35.759> but<00:01:36.079> know<00:01:36.240> that 00:01:36.390 --> 00:01:36.400 align:start position:0% we'll table that for today but know that 00:01:36.400 --> 00:01:38.710 align:start position:0% we'll table that for today but know that it<00:01:36.560> is<00:01:36.799> the<00:01:37.040> rulemaking<00:01:37.600> is<00:01:37.680> ready<00:01:38.159> loaded<00:01:38.560> and 00:01:38.710 --> 00:01:38.720 align:start position:0% it is the rulemaking is ready loaded and 00:01:38.720 --> 00:01:39.749 align:start position:0% it is the rulemaking is ready loaded and ready<00:01:38.960> to<00:01:39.040> go 00:01:39.749 --> 00:01:39.759 align:start position:0% ready to go 00:01:39.759 --> 00:01:41.749 align:start position:0% ready to go whenever 00:01:41.749 --> 00:01:41.759 align:start position:0% whenever 00:01:41.759 --> 00:01:43.109 align:start position:0% whenever this<00:01:42.000> commission<00:01:42.320> decides<00:01:42.720> to<00:01:42.799> make<00:01:42.960> that 00:01:43.109 --> 00:01:43.119 align:start position:0% this commission decides to make that 00:01:43.119 --> 00:01:45.429 align:start position:0% this commission decides to make that change<00:01:43.360> does<00:01:43.439> that<00:01:43.600> work<00:01:43.759> for<00:01:43.920> you<00:01:44.000> all 00:01:45.429 --> 00:01:45.439 align:start position:0% change does that work for you all 00:01:45.439 --> 00:01:47.270 align:start position:0% change does that work for you all yes<00:01:45.600> sir<00:01:45.840> mr<00:01:46.079> chairman<00:01:46.560> and<00:01:46.720> i'd<00:01:46.799> just<00:01:46.960> like<00:01:47.119> to 00:01:47.270 --> 00:01:47.280 align:start position:0% yes sir mr chairman and i'd just like to 00:01:47.280 --> 00:01:49.270 align:start position:0% yes sir mr chairman and i'd just like to echo<00:01:47.600> your<00:01:47.759> comments<00:01:48.240> uh<00:01:48.560> compliments<00:01:49.119> to 00:01:49.270 --> 00:01:49.280 align:start position:0% echo your comments uh compliments to 00:01:49.280 --> 00:01:50.550 align:start position:0% echo your comments uh compliments to staff 00:01:50.550 --> 00:01:50.560 align:start position:0% staff 00:01:50.560 --> 00:01:52.710 align:start position:0% staff they're<00:01:50.720> working<00:01:51.040> on<00:01:51.200> this<00:01:51.680> at<00:01:52.159> all<00:01:52.320> hours<00:01:52.640> of 00:01:52.710 --> 00:01:52.720 align:start position:0% they're working on this at all hours of 00:01:52.720 --> 00:01:54.230 align:start position:0% they're working on this at all hours of the<00:01:52.799> day<00:01:53.040> all<00:01:53.119> these<00:01:53.360> different<00:01:53.600> rule<00:01:53.840> makings 00:01:54.230 --> 00:01:54.240 align:start position:0% the day all these different rule makings 00:01:54.240 --> 00:01:56.069 align:start position:0% the day all these different rule makings and<00:01:54.320> we're<00:01:54.479> seeing<00:01:54.720> that<00:01:55.040> show<00:01:55.280> up 00:01:56.069 --> 00:01:56.079 align:start position:0% and we're seeing that show up 00:01:56.079 --> 00:01:57.990 align:start position:0% and we're seeing that show up you<00:01:56.159> know<00:01:56.320> when<00:01:56.560> we<00:01:56.640> get<00:01:56.799> the<00:01:56.960> emails<00:01:57.439> at<00:01:57.520> 2am 00:01:57.990 --> 00:01:58.000 align:start position:0% you know when we get the emails at 2am 00:01:58.000 --> 00:01:59.190 align:start position:0% you know when we get the emails at 2am in<00:01:58.079> the<00:01:58.159> morning<00:01:58.399> so<00:01:58.560> they're<00:01:58.719> doing<00:01:58.960> good 00:01:59.190 --> 00:01:59.200 align:start position:0% in the morning so they're doing good 00:01:59.200 --> 00:02:00.950 align:start position:0% in the morning so they're doing good work<00:01:59.520> and<00:01:59.759> i<00:01:59.920> just<00:02:00.079> want<00:02:00.240> to<00:02:00.320> give<00:02:00.399> them<00:02:00.560> kudos 00:02:00.950 --> 00:02:00.960 align:start position:0% work and i just want to give them kudos 00:02:00.960 --> 00:02:02.230 align:start position:0% work and i just want to give them kudos for<00:02:01.119> that 00:02:02.230 --> 00:02:02.240 align:start position:0% for that 00:02:02.240 --> 00:02:03.510 align:start position:0% for that yeah<00:02:02.719> and 00:02:03.510 --> 00:02:03.520 align:start position:0% yeah and 00:02:03.520 --> 00:02:04.870 align:start position:0% yeah and on 00:02:04.870 --> 00:02:04.880 align:start position:0% on 00:02:04.880 --> 00:02:07.109 align:start position:0% on incredible<00:02:05.920> quality<00:02:06.320> work 00:02:07.109 --> 00:02:07.119 align:start position:0% incredible quality work 00:02:07.119 --> 00:02:09.029 align:start position:0% incredible quality work volume<00:02:07.520> of<00:02:07.680> work 00:02:09.029 --> 00:02:09.039 align:start position:0% volume of work 00:02:09.039 --> 00:02:10.949 align:start position:0% volume of work and<00:02:09.200> they<00:02:09.360> have<00:02:09.520> already<00:02:09.840> knocked<00:02:10.160> out 00:02:10.949 --> 00:02:10.959 align:start position:0% and they have already knocked out 00:02:10.959 --> 00:02:12.869 align:start position:0% and they have already knocked out some<00:02:11.200> major<00:02:11.599> items<00:02:12.080> and<00:02:12.160> rule<00:02:12.400> makings<00:02:12.720> like 00:02:12.869 --> 00:02:12.879 align:start position:0% some major items and rule makings like 00:02:12.879 --> 00:02:15.350 align:start position:0% some major items and rule makings like our<00:02:13.040> weatherization<00:02:13.840> that<00:02:14.239> in<00:02:14.400> any<00:02:14.640> other 00:02:15.350 --> 00:02:15.360 align:start position:0% our weatherization that in any other 00:02:15.360 --> 00:02:16.790 align:start position:0% our weatherization that in any other time<00:02:15.599> and<00:02:15.760> place 00:02:16.790 --> 00:02:16.800 align:start position:0% time and place 00:02:16.800 --> 00:02:18.150 align:start position:0% time and place on<00:02:16.959> its<00:02:17.200> own<00:02:17.599> would<00:02:17.760> have<00:02:17.840> been<00:02:18.000> an 00:02:18.150 --> 00:02:18.160 align:start position:0% on its own would have been an 00:02:18.160 --> 00:02:20.150 align:start position:0% on its own would have been an extraordinary<00:02:18.640> accomplishment<00:02:19.360> so 00:02:20.150 --> 00:02:20.160 align:start position:0% extraordinary accomplishment so 00:02:20.160 --> 00:02:22.710 align:start position:0% extraordinary accomplishment so can't<00:02:20.400> thank<00:02:20.560> them<00:02:20.800> enough 00:02:22.710 --> 00:02:22.720 align:start position:0% can't thank them enough 00:02:22.720 --> 00:02:24.150 align:start position:0% can't thank them enough i<00:02:22.800> don't<00:02:22.959> have<00:02:23.040> anything<00:02:23.360> for<00:02:23.520> items<00:02:23.920> two 00:02:24.150 --> 00:02:24.160 align:start position:0% i don't have anything for items two 00:02:24.160 --> 00:02:26.949 align:start position:0% i don't have anything for items two through<00:02:24.400> twenty<00:02:24.800> any<00:02:24.959> of<00:02:25.040> y'all<00:02:25.599> that's<00:02:25.840> true 00:02:26.949 --> 00:02:26.959 align:start position:0% through twenty any of y'all that's true 00:02:26.959 --> 00:02:29.589 align:start position:0% through twenty any of y'all that's true all<00:02:27.120> right<00:02:27.360> that<00:02:27.599> will<00:02:27.840> bring<00:02:28.160> us<00:02:28.480> to 00:02:29.589 --> 00:02:29.599 align:start position:0% all right that will bring us to 00:02:29.599 --> 00:02:35.110 align:start position:0% all right that will bring us to item<00:02:30.080> 21<00:02:30.800> project<00:02:31.120> number<00:02:31.360> 52373 00:02:35.110 --> 00:02:35.120 align:start position:0% 00:02:35.120 --> 00:02:36.550 align:start position:0% first<00:02:35.360> and<00:02:35.440> foremost<00:02:35.840> thanks<00:02:36.080> to<00:02:36.239> all<00:02:36.319> of<00:02:36.400> our 00:02:36.550 --> 00:02:36.560 align:start position:0% first and foremost thanks to all of our 00:02:36.560 --> 00:02:39.110 align:start position:0% first and foremost thanks to all of our stakeholders<00:02:37.200> who<00:02:37.760> provided<00:02:38.319> thoughtful 00:02:39.110 --> 00:02:39.120 align:start position:0% stakeholders who provided thoughtful 00:02:39.120 --> 00:02:41.110 align:start position:0% stakeholders who provided thoughtful comments<00:02:39.760> and<00:02:39.920> insights 00:02:41.110 --> 00:02:41.120 align:start position:0% comments and insights 00:02:41.120 --> 00:02:43.430 align:start position:0% comments and insights as<00:02:41.360> always<00:02:41.599> we<00:02:41.760> appreciate<00:02:42.560> the<00:02:43.040> the<00:02:43.200> work 00:02:43.430 --> 00:02:43.440 align:start position:0% as always we appreciate the the work 00:02:43.440 --> 00:02:45.750 align:start position:0% as always we appreciate the the work that<00:02:43.599> goes<00:02:43.840> into<00:02:44.000> that<00:02:44.319> i<00:02:44.400> know<00:02:44.640> that's<00:02:44.879> not<00:02:45.519> a 00:02:45.750 --> 00:02:45.760 align:start position:0% that goes into that i know that's not a 00:02:45.760 --> 00:02:49.350 align:start position:0% that goes into that i know that's not a trivial<00:02:46.239> effort<00:02:46.560> and<00:02:46.800> often<00:02:47.120> includes 00:02:49.350 --> 00:02:49.360 align:start position:0% trivial effort and often includes 00:02:49.360 --> 00:02:51.750 align:start position:0% trivial effort and often includes retaining<00:02:49.840> outside<00:02:50.239> vendors<00:02:50.720> and<00:02:51.360> uh 00:02:51.750 --> 00:02:51.760 align:start position:0% retaining outside vendors and uh 00:02:51.760 --> 00:02:53.910 align:start position:0% retaining outside vendors and uh consultants<00:02:52.400> and<00:02:52.959> analysts 00:02:53.910 --> 00:02:53.920 align:start position:0% consultants and analysts 00:02:53.920 --> 00:02:55.990 align:start position:0% consultants and analysts who<00:02:54.160> appreciate<00:02:54.640> that 00:02:55.990 --> 00:02:56.000 align:start position:0% who appreciate that 00:02:56.000 --> 00:02:57.190 align:start position:0% who appreciate that uh 00:02:57.190 --> 00:02:57.200 align:start position:0% uh 00:02:57.200 --> 00:03:00.869 align:start position:0% uh however<00:02:57.920> as<00:02:58.319> i've<00:02:58.560> said<00:02:58.959> many<00:02:59.200> times<00:02:59.519> before 00:03:00.869 --> 00:03:00.879 align:start position:0% however as i've said many times before 00:03:00.879 --> 00:03:04.630 align:start position:0% however as i've said many times before uh<00:03:01.599> sb3<00:03:02.720> said<00:03:03.040> nothing<00:03:03.920> about<00:03:04.159> maintaining 00:03:04.630 --> 00:03:04.640 align:start position:0% uh sb3 said nothing about maintaining 00:03:04.640 --> 00:03:06.309 align:start position:0% uh sb3 said nothing about maintaining the<00:03:04.800> status<00:03:05.200> quo 00:03:06.309 --> 00:03:06.319 align:start position:0% the status quo 00:03:06.319 --> 00:03:08.630 align:start position:0% the status quo or<00:03:06.640> preserving<00:03:07.280> or<00:03:07.440> enhancing<00:03:08.319> certain 00:03:08.630 --> 00:03:08.640 align:start position:0% or preserving or enhancing certain 00:03:08.640 --> 00:03:10.309 align:start position:0% or preserving or enhancing certain business<00:03:09.040> models 00:03:10.309 --> 00:03:10.319 align:start position:0% business models 00:03:10.319 --> 00:03:12.470 align:start position:0% business models so<00:03:10.800> i<00:03:10.879> will<00:03:11.040> say<00:03:11.200> it<00:03:11.360> again<00:03:11.680> if<00:03:11.840> your<00:03:12.080> comments 00:03:12.470 --> 00:03:12.480 align:start position:0% so i will say it again if your comments 00:03:12.480 --> 00:03:15.750 align:start position:0% so i will say it again if your comments are<00:03:12.640> suggesting<00:03:13.120> to<00:03:13.280> do<00:03:13.440> nothing<00:03:14.239> or 00:03:15.750 --> 00:03:15.760 align:start position:0% are suggesting to do nothing or 00:03:15.760 --> 00:03:17.990 align:start position:0% are suggesting to do nothing or very<00:03:16.080> specifically<00:03:16.800> adjusting<00:03:17.440> our<00:03:17.519> market 00:03:17.990 --> 00:03:18.000 align:start position:0% very specifically adjusting our market 00:03:18.000 --> 00:03:19.750 align:start position:0% very specifically adjusting our market to<00:03:18.239> enhance<00:03:18.640> your<00:03:18.879> particular<00:03:19.440> business 00:03:19.750 --> 00:03:19.760 align:start position:0% to enhance your particular business 00:03:19.760 --> 00:03:20.790 align:start position:0% to enhance your particular business model 00:03:20.790 --> 00:03:20.800 align:start position:0% model 00:03:20.800 --> 00:03:25.430 align:start position:0% model you<00:03:20.959> can<00:03:21.280> save<00:03:21.519> your<00:03:21.760> breath 00:03:25.430 --> 00:03:25.440 align:start position:0% 00:03:25.440 --> 00:03:27.589 align:start position:0% starting<00:03:25.840> out<00:03:26.239> i<00:03:26.799> think<00:03:26.959> we<00:03:27.120> laid<00:03:27.360> out<00:03:27.440> an 00:03:27.589 --> 00:03:27.599 align:start position:0% starting out i think we laid out an 00:03:27.599 --> 00:03:30.949 align:start position:0% starting out i think we laid out an agenda<00:03:28.560> for<00:03:28.959> to<00:03:29.200> start<00:03:29.519> with<00:03:30.080> the 00:03:30.949 --> 00:03:30.959 align:start position:0% agenda for to start with the 00:03:30.959 --> 00:03:33.190 align:start position:0% agenda for to start with the uh<00:03:31.840> kind<00:03:32.000> of 00:03:33.190 --> 00:03:33.200 align:start position:0% uh kind of 00:03:33.200 --> 00:03:35.589 align:start position:0% uh kind of no<00:03:33.440> regrets<00:03:33.920> low-hanging<00:03:34.400> fruit 00:03:35.589 --> 00:03:35.599 align:start position:0% no regrets low-hanging fruit 00:03:35.599 --> 00:03:37.990 align:start position:0% no regrets low-hanging fruit items<00:03:36.000> already<00:03:36.640> in<00:03:36.879> process<00:03:37.599> and<00:03:37.680> then<00:03:37.840> we'll 00:03:37.990 --> 00:03:38.000 align:start position:0% items already in process and then we'll 00:03:38.000 --> 00:03:40.229 align:start position:0% items already in process and then we'll move<00:03:38.239> to<00:03:38.400> the<00:03:38.640> broader 00:03:40.229 --> 00:03:40.239 align:start position:0% move to the broader 00:03:40.239 --> 00:03:42.149 align:start position:0% move to the broader conversation<00:03:40.879> about 00:03:42.149 --> 00:03:42.159 align:start position:0% conversation about 00:03:42.159 --> 00:03:44.830 align:start position:0% conversation about a<00:03:42.319> more<00:03:42.560> fundamental<00:03:43.040> farming<00:03:43.360> mechanism 00:03:44.830 --> 00:03:44.840 align:start position:0% a more fundamental farming mechanism 00:03:44.840 --> 00:03:46.710 align:start position:0% a more fundamental farming mechanism so 00:03:46.710 --> 00:03:46.720 align:start position:0% so 00:03:46.720 --> 00:03:49.110 align:start position:0% so first<00:03:47.040> on<00:03:47.120> the<00:03:47.200> list<00:03:47.519> we've<00:03:47.760> got<00:03:48.080> the 00:03:49.110 --> 00:03:49.120 align:start position:0% first on the list we've got the 00:03:49.120 --> 00:03:52.149 align:start position:0% first on the list we've got the ordc<00:03:50.239> unfortunately<00:03:50.959> our<00:03:51.120> scenario<00:03:51.599> analysis 00:03:52.149 --> 00:03:52.159 align:start position:0% ordc unfortunately our scenario analysis 00:03:52.159 --> 00:03:54.710 align:start position:0% ordc unfortunately our scenario analysis that<00:03:52.400> we<00:03:52.720> discussed<00:03:53.200> last<00:03:53.439> time<00:03:53.760> is<00:03:54.239> not<00:03:54.480> quite 00:03:54.710 --> 00:03:54.720 align:start position:0% that we discussed last time is not quite 00:03:54.720 --> 00:03:57.350 align:start position:0% that we discussed last time is not quite ready<00:03:55.200> so<00:03:55.680> i<00:03:55.760> think<00:03:55.920> that<00:03:56.400> limits<00:03:56.720> our<00:03:56.879> ability 00:03:57.350 --> 00:03:57.360 align:start position:0% ready so i think that limits our ability 00:03:57.360 --> 00:03:58.550 align:start position:0% ready so i think that limits our ability to 00:03:58.550 --> 00:03:58.560 align:start position:0% to 00:03:58.560 --> 00:04:01.750 align:start position:0% to uh<00:04:00.000> really<00:04:00.319> make<00:04:00.560> much<00:04:00.799> progress<00:04:01.280> on<00:04:01.439> that 00:04:01.750 --> 00:04:01.760 align:start position:0% uh really make much progress on that 00:04:01.760 --> 00:04:03.990 align:start position:0% uh really make much progress on that there<00:04:02.000> is<00:04:02.159> the<00:04:02.319> question<00:04:02.879> of<00:04:03.360> seasonal<00:04:03.840> or 00:04:03.990 --> 00:04:04.000 align:start position:0% there is the question of seasonal or 00:04:04.000 --> 00:04:05.670 align:start position:0% there is the question of seasonal or single<00:04:04.319> curve<00:04:04.720> again 00:04:05.670 --> 00:04:05.680 align:start position:0% single curve again 00:04:05.680 --> 00:04:07.030 align:start position:0% single curve again hard<00:04:06.000> to 00:04:07.030 --> 00:04:07.040 align:start position:0% hard to 00:04:07.040 --> 00:04:09.110 align:start position:0% hard to nail<00:04:07.280> that<00:04:07.519> down<00:04:08.239> with<00:04:08.480> without<00:04:08.879> that 00:04:09.110 --> 00:04:09.120 align:start position:0% nail that down with without that 00:04:09.120 --> 00:04:10.949 align:start position:0% nail that down with without that analysis<00:04:09.840> which 00:04:10.949 --> 00:04:10.959 align:start position:0% analysis which 00:04:10.959 --> 00:04:13.750 align:start position:0% analysis which i<00:04:11.280> promise<00:04:11.599> is<00:04:11.760> forthcoming 00:04:13.750 --> 00:04:13.760 align:start position:0% i promise is forthcoming 00:04:13.760 --> 00:04:16.710 align:start position:0% i promise is forthcoming we<00:04:14.159> certainly<00:04:15.040> happy<00:04:15.360> to<00:04:15.439> discuss<00:04:15.840> it<00:04:16.000> on<00:04:16.160> a 00:04:16.710 --> 00:04:16.720 align:start position:0% we certainly happy to discuss it on a 00:04:16.720 --> 00:04:18.229 align:start position:0% we certainly happy to discuss it on a continuing<00:04:17.120> conversation<00:04:17.680> on<00:04:18.160> a 00:04:18.229 --> 00:04:18.239 align:start position:0% continuing conversation on a 00:04:18.239 --> 00:04:19.830 align:start position:0% continuing conversation on a philosophical<00:04:18.959> level<00:04:19.199> having<00:04:19.440> gone<00:04:19.680> through 00:04:19.830 --> 00:04:19.840 align:start position:0% philosophical level having gone through 00:04:19.840 --> 00:04:21.670 align:start position:0% philosophical level having gone through the<00:04:19.919> comments<00:04:20.400> and 00:04:21.670 --> 00:04:21.680 align:start position:0% the comments and 00:04:21.680 --> 00:04:23.030 align:start position:0% the comments and and 00:04:23.030 --> 00:04:23.040 align:start position:0% and 00:04:23.040 --> 00:04:23.990 align:start position:0% and heard<00:04:23.360> a<00:04:23.440> variety<00:04:23.680> of<00:04:23.759> different 00:04:23.990 --> 00:04:24.000 align:start position:0% heard a variety of different 00:04:24.000 --> 00:04:25.670 align:start position:0% heard a variety of different perspectives 00:04:25.670 --> 00:04:25.680 align:start position:0% perspectives 00:04:25.680 --> 00:04:27.110 align:start position:0% perspectives at<00:04:25.840> this<00:04:26.000> point<00:04:26.320> i'm 00:04:27.110 --> 00:04:27.120 align:start position:0% at this point i'm 00:04:27.120 --> 00:04:28.870 align:start position:0% at this point i'm i<00:04:27.280> think<00:04:27.520> the<00:04:27.680> single<00:04:28.000> curve<00:04:28.240> makes<00:04:28.479> a<00:04:28.560> lot<00:04:28.720> of 00:04:28.870 --> 00:04:28.880 align:start position:0% i think the single curve makes a lot of 00:04:28.880 --> 00:04:30.230 align:start position:0% i think the single curve makes a lot of sense 00:04:30.230 --> 00:04:30.240 align:start position:0% sense 00:04:30.240 --> 00:04:31.510 align:start position:0% sense i<00:04:30.320> don't<00:04:30.479> know<00:04:30.639> the<00:04:30.880> seasonal<00:04:31.280> curve 00:04:31.510 --> 00:04:31.520 align:start position:0% i don't know the seasonal curve 00:04:31.520 --> 00:04:33.590 align:start position:0% i don't know the seasonal curve accomplishes<00:04:32.160> much<00:04:32.960> but<00:04:33.199> i<00:04:33.280> know<00:04:33.440> that's 00:04:33.590 --> 00:04:33.600 align:start position:0% accomplishes much but i know that's 00:04:33.600 --> 00:04:35.909 align:start position:0% accomplishes much but i know that's something<00:04:33.919> you've<00:04:34.080> thought<00:04:34.320> a<00:04:34.320> lot<00:04:34.560> about 00:04:35.909 --> 00:04:35.919 align:start position:0% something you've thought a lot about 00:04:35.919 --> 00:04:37.990 align:start position:0% something you've thought a lot about i<00:04:36.080> mean<00:04:36.400> i'm 00:04:37.990 --> 00:04:38.000 align:start position:0% i mean i'm 00:04:38.000 --> 00:04:40.390 align:start position:0% i mean i'm trying<00:04:38.160> to<00:04:38.240> think<00:04:38.400> about<00:04:38.639> the<00:04:38.800> rdc<00:04:39.360> as<00:04:39.600> a 00:04:40.390 --> 00:04:40.400 align:start position:0% trying to think about the rdc as a 00:04:40.400 --> 00:04:42.390 align:start position:0% trying to think about the rdc as a a<00:04:40.560> market-based<00:04:41.120> rucking<00:04:41.440> mechanism<00:04:42.000> we<00:04:42.160> need 00:04:42.390 --> 00:04:42.400 align:start position:0% a market-based rucking mechanism we need 00:04:42.400 --> 00:04:45.030 align:start position:0% a market-based rucking mechanism we need units<00:04:42.800> on<00:04:43.120> let's<00:04:43.600> get<00:04:43.759> the<00:04:43.919> price<00:04:44.240> up 00:04:45.030 --> 00:04:45.040 align:start position:0% units on let's get the price up 00:04:45.040 --> 00:04:49.430 align:start position:0% units on let's get the price up in<00:04:45.199> a<00:04:45.280> scarcity<00:04:45.759> event 00:04:49.430 --> 00:04:49.440 align:start position:0% 00:04:49.440 --> 00:04:51.189 align:start position:0% i'm<00:04:49.520> not 00:04:51.189 --> 00:04:51.199 align:start position:0% i'm not 00:04:51.199 --> 00:04:52.710 align:start position:0% i'm not tremendously<00:04:51.759> slayed<00:04:52.000> one<00:04:52.160> way<00:04:52.320> or<00:04:52.400> the<00:04:52.479> other 00:04:52.710 --> 00:04:52.720 align:start position:0% tremendously slayed one way or the other 00:04:52.720 --> 00:04:54.070 align:start position:0% tremendously slayed one way or the other but<00:04:52.880> if<00:04:53.280> if 00:04:54.070 --> 00:04:54.080 align:start position:0% but if if 00:04:54.080 --> 00:04:56.550 align:start position:0% but if if if<00:04:54.240> a<00:04:54.320> single<00:04:54.560> one<00:04:54.720> gets<00:04:54.880> the<00:04:55.040> units<00:04:55.360> on<00:04:56.320> no 00:04:56.550 --> 00:04:56.560 align:start position:0% if a single one gets the units on no 00:04:56.560 --> 00:04:58.310 align:start position:0% if a single one gets the units on no need<00:04:56.720> to<00:04:56.800> add<00:04:56.960> the<00:04:57.120> complexity<00:04:57.759> but<00:04:57.919> happy<00:04:58.160> to 00:04:58.310 --> 00:04:58.320 align:start position:0% need to add the complexity but happy to 00:04:58.320 --> 00:04:59.749 align:start position:0% need to add the complexity but happy to hear<00:04:58.479> thoughts<00:04:58.800> and<00:04:59.040> certainly<00:04:59.360> no<00:04:59.520> need<00:04:59.680> to 00:04:59.749 --> 00:04:59.759 align:start position:0% hear thoughts and certainly no need to 00:04:59.759 --> 00:05:01.909 align:start position:0% hear thoughts and certainly no need to make<00:04:59.919> a<00:05:00.000> decision<00:05:00.400> today<00:05:00.800> right<00:05:01.199> and<00:05:01.600> that's 00:05:01.909 --> 00:05:01.919 align:start position:0% make a decision today right and that's 00:05:01.919 --> 00:05:03.189 align:start position:0% make a decision today right and that's that's<00:05:02.160> relief 00:05:03.189 --> 00:05:03.199 align:start position:0% that's relief 00:05:03.199 --> 00:05:05.029 align:start position:0% that's relief i<00:05:03.360> do<00:05:03.600> think<00:05:03.840> we<00:05:04.000> should 00:05:05.029 --> 00:05:05.039 align:start position:0% i do think we should 00:05:05.039 --> 00:05:07.909 align:start position:0% i do think we should continue<00:05:05.520> to<00:05:06.000> think<00:05:06.400> on 00:05:07.909 --> 00:05:07.919 align:start position:0% continue to think on 00:05:07.919 --> 00:05:09.510 align:start position:0% continue to think on seasonal<00:05:08.400> curves 00:05:09.510 --> 00:05:09.520 align:start position:0% seasonal curves 00:05:09.520 --> 00:05:12.150 align:start position:0% seasonal curves for<00:05:09.680> the<00:05:09.840> purposes<00:05:10.400> of<00:05:10.880> possible<00:05:11.440> consistency 00:05:12.150 --> 00:05:12.160 align:start position:0% for the purposes of possible consistency 00:05:12.160 --> 00:05:13.909 align:start position:0% for the purposes of possible consistency with<00:05:12.320> policies<00:05:12.880> that<00:05:13.039> we<00:05:13.199> may<00:05:13.440> choose<00:05:13.680> to 00:05:13.909 --> 00:05:13.919 align:start position:0% with policies that we may choose to 00:05:13.919 --> 00:05:16.469 align:start position:0% with policies that we may choose to adopt<00:05:14.320> in<00:05:14.479> other<00:05:14.720> areas<00:05:15.120> again<00:05:15.759> a<00:05:16.000> seasonal 00:05:16.469 --> 00:05:16.479 align:start position:0% adopt in other areas again a seasonal 00:05:16.479 --> 00:05:17.430 align:start position:0% adopt in other areas again a seasonal approach 00:05:17.430 --> 00:05:17.440 align:start position:0% approach 00:05:17.440 --> 00:05:19.110 align:start position:0% approach to<00:05:17.680> pricing 00:05:19.110 --> 00:05:19.120 align:start position:0% to pricing 00:05:19.120 --> 00:05:21.990 align:start position:0% to pricing and<00:05:19.440> once<00:05:19.759> we<00:05:20.080> have<00:05:20.720> frankly<00:05:21.039> mr<00:05:21.280> chairman 00:05:21.990 --> 00:05:22.000 align:start position:0% and once we have frankly mr chairman 00:05:22.000 --> 00:05:24.870 align:start position:0% and once we have frankly mr chairman it's<00:05:22.240> kind<00:05:22.400> of<00:05:22.479> good<00:05:22.639> that<00:05:22.800> we<00:05:22.960> may<00:05:24.240> delay<00:05:24.639> any 00:05:24.870 --> 00:05:24.880 align:start position:0% it's kind of good that we may delay any 00:05:24.880 --> 00:05:26.230 align:start position:0% it's kind of good that we may delay any decision<00:05:25.280> on<00:05:25.360> that<00:05:25.520> today<00:05:25.840> or<00:05:26.000> any 00:05:26.230 --> 00:05:26.240 align:start position:0% decision on that today or any 00:05:26.240 --> 00:05:27.670 align:start position:0% decision on that today or any substantive<00:05:26.720> feedback<00:05:27.120> on<00:05:27.199> that<00:05:27.360> today 00:05:27.670 --> 00:05:27.680 align:start position:0% substantive feedback on that today 00:05:27.680 --> 00:05:28.790 align:start position:0% substantive feedback on that today because<00:05:27.840> the<00:05:28.080> other 00:05:28.790 --> 00:05:28.800 align:start position:0% because the other 00:05:28.800 --> 00:05:29.670 align:start position:0% because the other uh 00:05:29.670 --> 00:05:29.680 align:start position:0% uh 00:05:29.680 --> 00:05:31.830 align:start position:0% uh issues<00:05:30.080> ancillary<00:05:30.560> services<00:05:31.280> tools<00:05:31.680> that 00:05:31.830 --> 00:05:31.840 align:start position:0% issues ancillary services tools that 00:05:31.840 --> 00:05:33.110 align:start position:0% issues ancillary services tools that we're<00:05:32.080> considering 00:05:33.110 --> 00:05:33.120 align:start position:0% we're considering 00:05:33.120 --> 00:05:35.510 align:start position:0% we're considering uh<00:05:33.440> deploying<00:05:34.160> will<00:05:34.320> have<00:05:34.560> costs<00:05:34.960> associated 00:05:35.510 --> 00:05:35.520 align:start position:0% uh deploying will have costs associated 00:05:35.520 --> 00:05:38.469 align:start position:0% uh deploying will have costs associated with<00:05:35.759> them<00:05:36.160> and<00:05:36.400> how<00:05:36.639> those<00:05:36.960> costs<00:05:37.440> are<00:05:38.160> uh 00:05:38.469 --> 00:05:38.479 align:start position:0% with them and how those costs are uh 00:05:38.479 --> 00:05:39.909 align:start position:0% with them and how those costs are uh allocated<00:05:39.199> but 00:05:39.909 --> 00:05:39.919 align:start position:0% allocated but 00:05:39.919 --> 00:05:42.710 align:start position:0% allocated but also<00:05:40.639> charged<00:05:40.960> to<00:05:41.120> the<00:05:41.520> to<00:05:41.680> the<00:05:41.759> market<00:05:42.160> on<00:05:42.320> a 00:05:42.710 --> 00:05:42.720 align:start position:0% also charged to the to the market on a 00:05:42.720 --> 00:05:46.390 align:start position:0% also charged to the to the market on a seasonal<00:05:43.199> basis<00:05:43.680> or<00:05:44.320> other<00:05:44.720> period<00:05:45.520> so 00:05:46.390 --> 00:05:46.400 align:start position:0% seasonal basis or other period so 00:05:46.400 --> 00:05:48.310 align:start position:0% seasonal basis or other period so in<00:05:46.479> the<00:05:46.639> interest<00:05:47.039> of<00:05:47.120> consistency<00:05:47.840> in<00:05:48.000> trying 00:05:48.310 --> 00:05:48.320 align:start position:0% in the interest of consistency in trying 00:05:48.320 --> 00:05:51.189 align:start position:0% in the interest of consistency in trying to<00:05:48.800> allow<00:05:49.199> consumers<00:05:49.759> to<00:05:50.080> hedge<00:05:50.479> and<00:05:50.639> expect 00:05:51.189 --> 00:05:51.199 align:start position:0% to allow consumers to hedge and expect 00:05:51.199 --> 00:05:54.070 align:start position:0% to allow consumers to hedge and expect on<00:05:51.440> a<00:05:51.680> seasonal<00:05:52.160> basis<00:05:52.720> rather<00:05:52.960> than<00:05:53.280> just<00:05:53.759> one 00:05:54.070 --> 00:05:54.080 align:start position:0% on a seasonal basis rather than just one 00:05:54.080 --> 00:05:57.670 align:start position:0% on a seasonal basis rather than just one lump<00:05:54.400> sum<00:05:55.199> it<00:05:55.360> may<00:05:55.600> afford<00:05:56.000> efficiencies 00:05:57.670 --> 00:05:57.680 align:start position:0% lump sum it may afford efficiencies 00:05:57.680 --> 00:05:59.749 align:start position:0% lump sum it may afford efficiencies and<00:05:58.080> cost<00:05:58.319> reductions<00:05:58.880> i<00:05:59.039> think<00:05:59.280> money<00:05:59.600> is 00:05:59.749 --> 00:05:59.759 align:start position:0% and cost reductions i think money is 00:05:59.759 --> 00:06:01.670 align:start position:0% and cost reductions i think money is going<00:05:59.919> to<00:06:00.080> flow<00:06:00.560> to<00:06:00.720> generators<00:06:01.199> one<00:06:01.440> way<00:06:01.600> or 00:06:01.670 --> 00:06:01.680 align:start position:0% going to flow to generators one way or 00:06:01.680 --> 00:06:03.510 align:start position:0% going to flow to generators one way or another<00:06:02.319> dispatchable<00:06:02.800> generators<00:06:03.199> one<00:06:03.360> way 00:06:03.510 --> 00:06:03.520 align:start position:0% another dispatchable generators one way 00:06:03.520 --> 00:06:05.430 align:start position:0% another dispatchable generators one way or<00:06:03.600> another<00:06:03.840> with<00:06:04.000> our<00:06:04.160> policy 00:06:05.430 --> 00:06:05.440 align:start position:0% or another with our policy 00:06:05.440 --> 00:06:07.670 align:start position:0% or another with our policy considerations<00:06:06.240> here<00:06:06.800> it's<00:06:06.960> just<00:06:07.199> a<00:06:07.280> question 00:06:07.670 --> 00:06:07.680 align:start position:0% considerations here it's just a question 00:06:07.680 --> 00:06:10.150 align:start position:0% considerations here it's just a question of<00:06:08.000> when<00:06:08.160> you<00:06:08.319> bake<00:06:08.639> the<00:06:08.800> whole<00:06:09.199> cake<00:06:09.919> what 00:06:10.150 --> 00:06:10.160 align:start position:0% of when you bake the whole cake what 00:06:10.160 --> 00:06:12.150 align:start position:0% of when you bake the whole cake what does<00:06:10.240> that<00:06:10.479> look<00:06:10.720> like<00:06:11.440> and<00:06:11.680> where<00:06:11.919> are<00:06:12.000> the 00:06:12.150 --> 00:06:12.160 align:start position:0% does that look like and where are the 00:06:12.160 --> 00:06:14.070 align:start position:0% does that look like and where are the efficiencies<00:06:12.720> that<00:06:12.880> we<00:06:12.960> can<00:06:13.120> find<00:06:13.840> so<00:06:14.000> you're 00:06:14.070 --> 00:06:14.080 align:start position:0% efficiencies that we can find so you're 00:06:14.080 --> 00:06:15.909 align:start position:0% efficiencies that we can find so you're thinking<00:06:14.400> about<00:06:14.560> it<00:06:14.639> from<00:06:14.880> a 00:06:15.909 --> 00:06:15.919 align:start position:0% thinking about it from a 00:06:15.919 --> 00:06:18.710 align:start position:0% thinking about it from a holistic<00:06:16.319> financial<00:06:17.199> consistency<00:06:18.319> yeah<00:06:18.560> yes 00:06:18.710 --> 00:06:18.720 align:start position:0% holistic financial consistency yeah yes 00:06:18.720 --> 00:06:21.510 align:start position:0% holistic financial consistency yeah yes sir<00:06:19.039> um<00:06:19.680> rather<00:06:19.919> than<00:06:20.080> the<00:06:20.319> operational 00:06:21.510 --> 00:06:21.520 align:start position:0% sir um rather than the operational 00:06:21.520 --> 00:06:22.710 align:start position:0% sir um rather than the operational heat<00:06:21.759> rate 00:06:22.710 --> 00:06:22.720 align:start position:0% heat rate 00:06:22.720 --> 00:06:24.550 align:start position:0% heat rate you<00:06:22.800> know<00:06:22.880> what<00:06:23.120> price<00:06:23.759> is<00:06:23.919> required<00:06:24.240> to<00:06:24.319> get<00:06:24.479> a 00:06:24.550 --> 00:06:24.560 align:start position:0% you know what price is required to get a 00:06:24.560 --> 00:06:26.309 align:start position:0% you know what price is required to get a certain<00:06:24.800> heat<00:06:25.039> rate 00:06:26.309 --> 00:06:26.319 align:start position:0% certain heat rate 00:06:26.319 --> 00:06:28.469 align:start position:0% certain heat rate economic<00:06:26.880> correct<00:06:27.199> well<00:06:27.440> and<00:06:27.680> and<00:06:27.919> those<00:06:28.240> uh 00:06:28.469 --> 00:06:28.479 align:start position:0% economic correct well and and those uh 00:06:28.479 --> 00:06:30.950 align:start position:0% economic correct well and and those uh ordc<00:06:29.199> curves<00:06:29.600> are<00:06:30.080> are<00:06:30.319> different<00:06:30.720> in<00:06:30.800> those 00:06:30.950 --> 00:06:30.960 align:start position:0% ordc curves are are different in those 00:06:30.960 --> 00:06:32.150 align:start position:0% ordc curves are are different in those shoulder<00:06:31.360> months<00:06:31.600> and<00:06:31.680> that<00:06:31.759> was<00:06:31.840> kind<00:06:32.000> of<00:06:32.080> the 00:06:32.150 --> 00:06:32.160 align:start position:0% shoulder months and that was kind of the 00:06:32.160 --> 00:06:33.909 align:start position:0% shoulder months and that was kind of the whole<00:06:32.400> point<00:06:32.800> you<00:06:32.880> know<00:06:33.039> when<00:06:33.199> you<00:06:33.600> when<00:06:33.759> you 00:06:33.909 --> 00:06:33.919 align:start position:0% whole point you know when you when you 00:06:33.919 --> 00:06:36.950 align:start position:0% whole point you know when you when you bake<00:06:34.160> it<00:06:34.319> in<00:06:34.880> with<00:06:35.039> the<00:06:35.199> peaks 00:06:36.950 --> 00:06:36.960 align:start position:0% bake it in with the peaks 00:06:36.960 --> 00:06:40.390 align:start position:0% bake it in with the peaks of<00:06:37.360> of<00:06:38.160> summer<00:06:38.880> you<00:06:39.039> know<00:06:39.280> and<00:06:39.440> and<00:06:39.840> even<00:06:40.160> still 00:06:40.390 --> 00:06:40.400 align:start position:0% of of summer you know and and even still 00:06:40.400 --> 00:06:43.990 align:start position:0% of of summer you know and and even still winter<00:06:41.120> but<00:06:41.280> not<00:06:41.440> with<00:06:41.680> a<00:06:42.000> a<00:06:42.240> spring<00:06:42.880> uh<00:06:43.360> fall 00:06:43.990 --> 00:06:44.000 align:start position:0% winter but not with a a spring uh fall 00:06:44.000 --> 00:06:46.230 align:start position:0% winter but not with a a spring uh fall um<00:06:44.560> curve<00:06:44.880> in<00:06:44.960> there<00:06:45.199> which<00:06:45.440> is 00:06:46.230 --> 00:06:46.240 align:start position:0% um curve in there which is 00:06:46.240 --> 00:06:47.909 align:start position:0% um curve in there which is it<00:06:46.400> reacts<00:06:46.800> different<00:06:47.120> it<00:06:47.199> plays<00:06:47.520> differently 00:06:47.909 --> 00:06:47.919 align:start position:0% it reacts different it plays differently 00:06:47.919 --> 00:06:49.510 align:start position:0% it reacts different it plays differently it's<00:06:48.080> my<00:06:48.240> understanding<00:06:49.039> what<00:06:49.199> would<00:06:49.360> that 00:06:49.510 --> 00:06:49.520 align:start position:0% it's my understanding what would that 00:06:49.520 --> 00:06:51.510 align:start position:0% it's my understanding what would that look<00:06:49.759> like<00:06:50.080> i<00:06:50.160> guess<00:06:50.400> in<00:06:50.560> practice 00:06:51.510 --> 00:06:51.520 align:start position:0% look like i guess in practice 00:06:51.520 --> 00:06:53.670 align:start position:0% look like i guess in practice we<00:06:51.680> can<00:06:51.759> get<00:06:51.919> more<00:06:52.080> comment<00:06:52.479> on<00:06:52.639> that<00:06:52.960> but<00:06:53.280> uh 00:06:53.670 --> 00:06:53.680 align:start position:0% we can get more comment on that but uh 00:06:53.680 --> 00:06:54.950 align:start position:0% we can get more comment on that but uh that<00:06:53.919> they<00:06:54.160> were 00:06:54.950 --> 00:06:54.960 align:start position:0% that they were 00:06:54.960 --> 00:06:57.510 align:start position:0% that they were um 00:06:57.510 --> 00:06:57.520 align:start position:0% 00:06:57.520 --> 00:06:59.029 align:start position:0% i'll<00:06:57.759> have<00:06:57.840> to<00:06:57.919> get<00:06:58.000> you<00:06:58.160> more<00:06:58.319> feedback<00:06:58.639> on 00:06:59.029 --> 00:06:59.039 align:start position:0% i'll have to get you more feedback on 00:06:59.039 --> 00:07:05.430 align:start position:0% i'll have to get you more feedback on what<00:06:59.199> it<00:06:59.280> looked<00:06:59.520> like<00:06:59.880> probably<00:07:00.880> versus 00:07:05.430 --> 00:07:05.440 align:start position:0% 00:07:05.440 --> 00:07:07.510 align:start position:0% spring<00:07:05.680> versus<00:07:06.080> summer<00:07:06.639> versus<00:07:07.039> seasonal 00:07:07.510 --> 00:07:07.520 align:start position:0% spring versus summer versus seasonal 00:07:07.520 --> 00:07:08.629 align:start position:0% spring versus summer versus seasonal curve 00:07:08.629 --> 00:07:08.639 align:start position:0% curve 00:07:08.639 --> 00:07:10.150 align:start position:0% curve um<00:07:08.960> i<00:07:09.199> don't<00:07:09.280> know<00:07:09.440> one<00:07:09.520> way<00:07:09.680> the<00:07:09.759> other<00:07:09.919> but 00:07:10.150 --> 00:07:10.160 align:start position:0% um i don't know one way the other but 00:07:10.160 --> 00:07:11.909 align:start position:0% um i don't know one way the other but it'd<00:07:10.319> be<00:07:10.479> helpful<00:07:10.800> to 00:07:11.909 --> 00:07:11.919 align:start position:0% it'd be helpful to 00:07:11.919 --> 00:07:14.710 align:start position:0% it'd be helpful to that's<00:07:12.160> right<00:07:12.400> now<00:07:12.639> i'll<00:07:12.880> uh<00:07:13.039> i'll<00:07:13.280> ask<00:07:13.520> sam<00:07:14.000> uh 00:07:14.710 --> 00:07:14.720 align:start position:0% that's right now i'll uh i'll ask sam uh 00:07:14.720 --> 00:07:16.469 align:start position:0% that's right now i'll uh i'll ask sam uh what<00:07:15.280> because<00:07:15.520> they've<00:07:15.759> watched<00:07:16.080> this 00:07:16.469 --> 00:07:16.479 align:start position:0% what because they've watched this 00:07:16.479 --> 00:07:17.510 align:start position:0% what because they've watched this picture 00:07:17.510 --> 00:07:17.520 align:start position:0% picture 00:07:17.520 --> 00:07:20.070 align:start position:0% picture i<00:07:17.599> know<00:07:17.840> me<00:07:18.000> too<00:07:18.639> and<00:07:19.199> that's<00:07:19.360> kind<00:07:19.520> of<00:07:19.599> why<00:07:19.919> i 00:07:20.070 --> 00:07:20.080 align:start position:0% i know me too and that's kind of why i 00:07:20.080 --> 00:07:22.469 align:start position:0% i know me too and that's kind of why i followed<00:07:20.319> that<00:07:20.479> memo<00:07:20.800> another<00:07:21.120> thing<00:07:21.360> on<00:07:21.599> ordc 00:07:22.469 --> 00:07:22.479 align:start position:0% followed that memo another thing on ordc 00:07:22.479 --> 00:07:23.589 align:start position:0% followed that memo another thing on ordc one<00:07:22.639> of<00:07:22.800> flag<00:07:23.039> as<00:07:23.120> a<00:07:23.199> part<00:07:23.360> of<00:07:23.440> this 00:07:23.589 --> 00:07:23.599 align:start position:0% one of flag as a part of this 00:07:23.599 --> 00:07:25.749 align:start position:0% one of flag as a part of this conversation<00:07:24.160> sir<00:07:24.479> um 00:07:25.749 --> 00:07:25.759 align:start position:0% conversation sir um 00:07:25.759 --> 00:07:28.469 align:start position:0% conversation sir um as<00:07:26.160> uh<00:07:26.720> brattle<00:07:27.280> is<00:07:27.440> looking<00:07:27.759> at<00:07:27.919> their<00:07:28.080> final 00:07:28.469 --> 00:07:28.479 align:start position:0% as uh brattle is looking at their final 00:07:28.479 --> 00:07:31.589 align:start position:0% as uh brattle is looking at their final analysis<00:07:28.960> and<00:07:29.120> feedback 00:07:31.589 --> 00:07:31.599 align:start position:0% analysis and feedback 00:07:31.599 --> 00:07:33.589 align:start position:0% analysis and feedback i<00:07:31.759> understand<00:07:32.240> that<00:07:32.400> they're 00:07:33.589 --> 00:07:33.599 align:start position:0% i understand that they're 00:07:33.599 --> 00:07:35.749 align:start position:0% i understand that they're they're<00:07:33.919> looking<00:07:34.319> forward<00:07:35.039> to<00:07:35.280> what<00:07:35.599> our 00:07:35.749 --> 00:07:35.759 align:start position:0% they're looking forward to what our 00:07:35.759 --> 00:07:36.950 align:start position:0% they're looking forward to what our expected 00:07:36.950 --> 00:07:36.960 align:start position:0% expected 00:07:36.960 --> 00:07:39.990 align:start position:0% expected resource<00:07:37.599> mix<00:07:38.080> will<00:07:38.319> be 00:07:39.990 --> 00:07:40.000 align:start position:0% resource mix will be 00:07:40.000 --> 00:07:43.350 align:start position:0% resource mix will be in<00:07:40.240> four<00:07:40.560> years<00:07:40.960> overlaid<00:07:42.080> onto 00:07:43.350 --> 00:07:43.360 align:start position:0% in four years overlaid onto 00:07:43.360 --> 00:07:46.710 align:start position:0% in four years overlaid onto 2019<00:07:44.240> weather<00:07:44.560> patterns<00:07:45.199> get<00:07:45.520> back<00:07:45.759> cast<00:07:46.319> onto 00:07:46.710 --> 00:07:46.720 align:start position:0% 2019 weather patterns get back cast onto 00:07:46.720 --> 00:07:48.070 align:start position:0% 2019 weather patterns get back cast onto 2019 00:07:48.070 --> 00:07:48.080 align:start position:0% 2019 00:07:48.080 --> 00:07:50.230 align:start position:0% 2019 and<00:07:48.240> that's<00:07:48.479> prudent<00:07:49.199> um 00:07:50.230 --> 00:07:50.240 align:start position:0% and that's prudent um 00:07:50.240 --> 00:07:52.150 align:start position:0% and that's prudent um i<00:07:50.319> want<00:07:50.479> to<00:07:50.560> stress<00:07:50.960> that 00:07:52.150 --> 00:07:52.160 align:start position:0% i want to stress that 00:07:52.160 --> 00:07:55.270 align:start position:0% i want to stress that the<00:07:52.560> resource<00:07:53.120> mix<00:07:53.759> will<00:07:54.080> change<00:07:54.720> i<00:07:54.879> believe 00:07:55.270 --> 00:07:55.280 align:start position:0% the resource mix will change i believe 00:07:55.280 --> 00:07:57.510 align:start position:0% the resource mix will change i believe significantly<00:07:56.000> as<00:07:56.240> per<00:07:56.479> my<00:07:56.639> memo<00:07:57.120> you<00:07:57.280> know 00:07:57.510 --> 00:07:57.520 align:start position:0% significantly as per my memo you know 00:07:57.520 --> 00:07:59.110 align:start position:0% significantly as per my memo you know filed 00:07:59.110 --> 00:07:59.120 align:start position:0% filed 00:07:59.120 --> 00:08:01.029 align:start position:0% filed and<00:07:59.520> if<00:07:59.680> we<00:07:59.840> ever<00:08:00.000> get<00:08:00.160> to<00:08:00.240> a<00:08:00.319> point<00:08:00.560> i'll<00:08:00.800> make 00:08:01.029 --> 00:08:01.039 align:start position:0% and if we ever get to a point i'll make 00:08:01.039 --> 00:08:03.350 align:start position:0% and if we ever get to a point i'll make a<00:08:01.120> little<00:08:01.280> speech<00:08:01.759> but<00:08:02.240> watching<00:08:02.639> the 00:08:03.350 --> 00:08:03.360 align:start position:0% a little speech but watching the 00:08:03.360 --> 00:08:05.189 align:start position:0% a little speech but watching the the<00:08:03.599> financial<00:08:04.160> discussions<00:08:04.639> over<00:08:04.879> the<00:08:04.960> last 00:08:05.189 --> 00:08:05.199 align:start position:0% the financial discussions over the last 00:08:05.199 --> 00:08:07.350 align:start position:0% the financial discussions over the last week<00:08:05.440> has<00:08:05.599> been<00:08:05.759> fascinating 00:08:07.350 --> 00:08:07.360 align:start position:0% week has been fascinating 00:08:07.360 --> 00:08:08.869 align:start position:0% week has been fascinating wall<00:08:07.599> street<00:08:07.840> journal<00:08:08.160> articles<00:08:08.479> all<00:08:08.720> over 00:08:08.869 --> 00:08:08.879 align:start position:0% wall street journal articles all over 00:08:08.879 --> 00:08:10.309 align:start position:0% wall street journal articles all over the<00:08:08.960> place<00:08:09.280> talking<00:08:09.520> about<00:08:09.599> how<00:08:09.759> much<00:08:10.000> money 00:08:10.309 --> 00:08:10.319 align:start position:0% the place talking about how much money 00:08:10.319 --> 00:08:12.150 align:start position:0% the place talking about how much money is<00:08:10.400> going<00:08:10.479> to<00:08:10.560> flow<00:08:10.879> in<00:08:10.960> certain<00:08:11.280> directions 00:08:12.150 --> 00:08:12.160 align:start position:0% is going to flow in certain directions 00:08:12.160 --> 00:08:14.150 align:start position:0% is going to flow in certain directions and<00:08:12.319> that's<00:08:12.560> going<00:08:12.639> to<00:08:12.800> impact<00:08:13.360> resource<00:08:13.919> mix 00:08:14.150 --> 00:08:14.160 align:start position:0% and that's going to impact resource mix 00:08:14.160 --> 00:08:15.749 align:start position:0% and that's going to impact resource mix in<00:08:14.319> texas 00:08:15.749 --> 00:08:15.759 align:start position:0% in texas 00:08:15.759 --> 00:08:19.029 align:start position:0% in texas just<00:08:15.919> because<00:08:16.400> of<00:08:16.479> the<00:08:16.639> way<00:08:17.360> ercot<00:08:18.080> operates 00:08:19.029 --> 00:08:19.039 align:start position:0% just because of the way ercot operates 00:08:19.039 --> 00:08:20.869 align:start position:0% just because of the way ercot operates and<00:08:19.280> and<00:08:19.520> why<00:08:19.759> we<00:08:19.919> are<00:08:20.080> different<00:08:20.479> and<00:08:20.560> why<00:08:20.720> we 00:08:20.869 --> 00:08:20.879 align:start position:0% and and why we are different and why we 00:08:20.879 --> 00:08:23.110 align:start position:0% and and why we are different and why we have<00:08:21.039> been<00:08:21.280> so 00:08:23.110 --> 00:08:23.120 align:start position:0% have been so 00:08:23.120 --> 00:08:25.510 align:start position:0% have been so bountiful<00:08:23.759> in<00:08:23.919> terms<00:08:24.319> of<00:08:24.639> renewable<00:08:25.120> resource 00:08:25.510 --> 00:08:25.520 align:start position:0% bountiful in terms of renewable resource 00:08:25.520 --> 00:08:28.390 align:start position:0% bountiful in terms of renewable resource penetration<00:08:26.240> but<00:08:26.400> also<00:08:27.199> in<00:08:27.280> the<00:08:27.440> early<00:08:27.759> days 00:08:28.390 --> 00:08:28.400 align:start position:0% penetration but also in the early days 00:08:28.400 --> 00:08:29.990 align:start position:0% penetration but also in the early days gas<00:08:28.800> generation<00:08:29.280> deployment<00:08:29.759> after 00:08:29.990 --> 00:08:30.000 align:start position:0% gas generation deployment after 00:08:30.000 --> 00:08:31.990 align:start position:0% gas generation deployment after deregulation<00:08:30.639> we're<00:08:30.800> innovative<00:08:31.599> and<00:08:31.759> we're 00:08:31.990 --> 00:08:32.000 align:start position:0% deregulation we're innovative and we're 00:08:32.000 --> 00:08:33.350 align:start position:0% deregulation we're innovative and we're easy<00:08:32.240> to<00:08:32.399> deploy 00:08:33.350 --> 00:08:33.360 align:start position:0% easy to deploy 00:08:33.360 --> 00:08:36.149 align:start position:0% easy to deploy and<00:08:33.599> so<00:08:34.000> when<00:08:34.159> we<00:08:34.240> consider<00:08:34.719> ordc<00:08:35.440> i<00:08:35.519> want<00:08:35.680> to 00:08:36.149 --> 00:08:36.159 align:start position:0% and so when we consider ordc i want to 00:08:36.159 --> 00:08:38.230 align:start position:0% and so when we consider ordc i want to make<00:08:36.320> sure<00:08:36.479> that<00:08:36.640> we<00:08:36.800> analyze<00:08:37.279> what<00:08:37.519> is<00:08:37.599> ordc 00:08:38.230 --> 00:08:38.240 align:start position:0% make sure that we analyze what is ordc 00:08:38.240 --> 00:08:39.670 align:start position:0% make sure that we analyze what is ordc going<00:08:38.399> to<00:08:38.479> look<00:08:38.719> like 00:08:39.670 --> 00:08:39.680 align:start position:0% going to look like 00:08:39.680 --> 00:08:41.829 align:start position:0% going to look like with<00:08:39.919> a<00:08:40.080> massive<00:08:40.479> amount<00:08:40.719> of<00:08:40.880> solar 00:08:41.829 --> 00:08:41.839 align:start position:0% with a massive amount of solar 00:08:41.839 --> 00:08:44.310 align:start position:0% with a massive amount of solar on<00:08:42.000> the<00:08:42.159> system<00:08:42.880> is<00:08:43.039> that<00:08:43.200> going<00:08:43.279> to<00:08:43.440> change<00:08:43.760> it 00:08:44.310 --> 00:08:44.320 align:start position:0% on the system is that going to change it 00:08:44.320 --> 00:08:46.230 align:start position:0% on the system is that going to change it because<00:08:44.640> i<00:08:44.720> want<00:08:44.880> to<00:08:45.040> be<00:08:45.200> able<00:08:45.440> to<00:08:45.760> adopt<00:08:46.160> a 00:08:46.230 --> 00:08:46.240 align:start position:0% because i want to be able to adopt a 00:08:46.240 --> 00:08:49.590 align:start position:0% because i want to be able to adopt a policy<00:08:47.200> that<00:08:47.440> one<00:08:48.000> adapts<00:08:48.880> to<00:08:49.040> the<00:08:49.200> changing 00:08:49.590 --> 00:08:49.600 align:start position:0% policy that one adapts to the changing 00:08:49.600 --> 00:08:51.590 align:start position:0% policy that one adapts to the changing landscape<00:08:50.480> so<00:08:50.640> that<00:08:50.800> we<00:08:50.959> don't<00:08:51.120> have<00:08:51.279> to<00:08:51.360> come 00:08:51.590 --> 00:08:51.600 align:start position:0% landscape so that we don't have to come 00:08:51.600 --> 00:08:54.470 align:start position:0% landscape so that we don't have to come back<00:08:51.839> in<00:08:52.000> mechanically<00:08:52.640> or<00:08:52.720> whoever<00:08:53.200> our 00:08:54.470 --> 00:08:54.480 align:start position:0% back in mechanically or whoever our 00:08:54.480 --> 00:08:57.430 align:start position:0% back in mechanically or whoever our you<00:08:54.640> know<00:08:54.959> ancestors<00:08:55.760> are<00:08:56.080> at<00:08:56.160> this<00:08:56.399> table<00:08:57.200> and 00:08:57.430 --> 00:08:57.440 align:start position:0% you know ancestors are at this table and 00:08:57.440 --> 00:08:58.630 align:start position:0% you know ancestors are at this table and and<00:08:57.600> have<00:08:57.839> to 00:08:58.630 --> 00:08:58.640 align:start position:0% and have to 00:08:58.640 --> 00:09:01.430 align:start position:0% and have to mechanically<00:08:59.200> modify<00:08:59.680> this 00:09:01.430 --> 00:09:01.440 align:start position:0% mechanically modify this 00:09:01.440 --> 00:09:03.110 align:start position:0% mechanically modify this look<00:09:01.600> forward<00:09:01.839> to<00:09:01.920> seeing<00:09:02.160> it 00:09:03.110 --> 00:09:03.120 align:start position:0% look forward to seeing it 00:09:03.120 --> 00:09:04.150 align:start position:0% look forward to seeing it yeah<00:09:03.279> me<00:09:03.440> too 00:09:04.150 --> 00:09:04.160 align:start position:0% yeah me too 00:09:04.160 --> 00:09:06.630 align:start position:0% yeah me too and<00:09:04.320> if<00:09:04.399> i<00:09:04.560> may<00:09:04.800> um<00:09:05.360> so<00:09:05.600> i<00:09:06.000> agree<00:09:06.240> with<00:09:06.320> you<00:09:06.560> i 00:09:06.630 --> 00:09:06.640 align:start position:0% and if i may um so i agree with you i 00:09:06.640 --> 00:09:08.470 align:start position:0% and if i may um so i agree with you i think<00:09:06.880> that<00:09:07.200> rattles<00:09:07.600> should<00:09:07.760> be<00:09:07.920> taking<00:09:08.240> into 00:09:08.470 --> 00:09:08.480 align:start position:0% think that rattles should be taking into 00:09:08.480 --> 00:09:09.910 align:start position:0% think that rattles should be taking into consideration 00:09:09.910 --> 00:09:09.920 align:start position:0% consideration 00:09:09.920 --> 00:09:11.269 align:start position:0% consideration what<00:09:10.080> what<00:09:10.240> the<00:09:10.399> future<00:09:10.640> may<00:09:10.800> look<00:09:10.959> like<00:09:11.200> in 00:09:11.269 --> 00:09:11.279 align:start position:0% what what the future may look like in 00:09:11.279 --> 00:09:13.430 align:start position:0% what what the future may look like in the<00:09:11.360> market<00:09:11.760> with<00:09:12.080> increased<00:09:12.959> renewable 00:09:13.430 --> 00:09:13.440 align:start position:0% the market with increased renewable 00:09:13.440 --> 00:09:16.150 align:start position:0% the market with increased renewable penetration<00:09:14.160> and<00:09:14.560> other<00:09:14.800> factors<00:09:15.360> that<00:09:15.600> that 00:09:16.150 --> 00:09:16.160 align:start position:0% penetration and other factors that that 00:09:16.160 --> 00:09:17.990 align:start position:0% penetration and other factors that that i<00:09:16.240> think<00:09:16.480> are<00:09:16.640> important<00:09:17.200> like 00:09:17.990 --> 00:09:18.000 align:start position:0% i think are important like 00:09:18.000 --> 00:09:20.550 align:start position:0% i think are important like ercot<00:09:18.480> carrying<00:09:18.959> 6<00:09:19.279> 500<00:09:19.839> megawatts<00:09:20.480> of 00:09:20.550 --> 00:09:20.560 align:start position:0% ercot carrying 6 500 megawatts of 00:09:20.560 --> 00:09:22.470 align:start position:0% ercot carrying 6 500 megawatts of reserves<00:09:21.360> i<00:09:21.519> think<00:09:21.680> that's<00:09:21.920> important<00:09:22.399> to 00:09:22.470 --> 00:09:22.480 align:start position:0% reserves i think that's important to 00:09:22.480 --> 00:09:24.310 align:start position:0% reserves i think that's important to bake<00:09:22.720> into<00:09:23.200> their<00:09:23.440> analysis<00:09:24.000> and<00:09:24.080> i<00:09:24.160> think 00:09:24.310 --> 00:09:24.320 align:start position:0% bake into their analysis and i think 00:09:24.320 --> 00:09:25.910 align:start position:0% bake into their analysis and i think they<00:09:24.560> are 00:09:25.910 --> 00:09:25.920 align:start position:0% they are 00:09:25.920 --> 00:09:27.910 align:start position:0% they are and<00:09:26.000> i<00:09:26.160> continue<00:09:26.720> to<00:09:26.880> stress<00:09:27.279> that<00:09:27.440> we<00:09:27.519> need<00:09:27.760> to 00:09:27.910 --> 00:09:27.920 align:start position:0% and i continue to stress that we need to 00:09:27.920 --> 00:09:29.750 align:start position:0% and i continue to stress that we need to see<00:09:28.160> what<00:09:28.320> the<00:09:28.480> cost<00:09:28.800> impacts<00:09:29.279> are<00:09:29.519> and<00:09:29.680> the 00:09:29.750 --> 00:09:29.760 align:start position:0% see what the cost impacts are and the 00:09:29.760 --> 00:09:31.670 align:start position:0% see what the cost impacts are and the revenue<00:09:30.240> impacts<00:09:30.640> to<00:09:30.800> the<00:09:30.880> market<00:09:31.360> are<00:09:31.519> going 00:09:31.670 --> 00:09:31.680 align:start position:0% revenue impacts to the market are going 00:09:31.680 --> 00:09:32.870 align:start position:0% revenue impacts to the market are going to<00:09:31.760> be 00:09:32.870 --> 00:09:32.880 align:start position:0% to be 00:09:32.880 --> 00:09:34.790 align:start position:0% to be i<00:09:32.959> just<00:09:33.120> want<00:09:33.279> to<00:09:33.360> be<00:09:33.519> really<00:09:33.760> clear<00:09:34.160> because 00:09:34.790 --> 00:09:34.800 align:start position:0% i just want to be really clear because 00:09:34.800 --> 00:09:36.550 align:start position:0% i just want to be really clear because you<00:09:34.880> know<00:09:35.040> as<00:09:35.120> we<00:09:35.279> await<00:09:35.519> for<00:09:35.760> brattle's 00:09:36.550 --> 00:09:36.560 align:start position:0% you know as we await for brattle's 00:09:36.560 --> 00:09:37.829 align:start position:0% you know as we await for brattle's analysis 00:09:37.829 --> 00:09:37.839 align:start position:0% analysis 00:09:37.839 --> 00:09:39.590 align:start position:0% analysis we<00:09:38.000> want<00:09:38.160> to<00:09:38.240> make<00:09:38.399> sure<00:09:38.800> when<00:09:38.959> we<00:09:39.120> get<00:09:39.279> it<00:09:39.440> it's 00:09:39.590 --> 00:09:39.600 align:start position:0% we want to make sure when we get it it's 00:09:39.600 --> 00:09:42.150 align:start position:0% we want to make sure when we get it it's robust<00:09:40.160> and<00:09:40.320> it<00:09:40.399> gives<00:09:40.640> us<00:09:40.800> a<00:09:40.880> clear<00:09:41.120> picture 00:09:42.150 --> 00:09:42.160 align:start position:0% robust and it gives us a clear picture 00:09:42.160 --> 00:09:45.110 align:start position:0% robust and it gives us a clear picture so<00:09:42.320> we<00:09:42.480> can<00:09:42.640> make<00:09:43.360> an<00:09:43.519> appropriate<00:09:44.000> decision 00:09:45.110 --> 00:09:45.120 align:start position:0% so we can make an appropriate decision 00:09:45.120 --> 00:09:46.790 align:start position:0% so we can make an appropriate decision and<00:09:45.279> i<00:09:45.440> still<00:09:45.680> want<00:09:45.839> to<00:09:45.920> stress<00:09:46.240> that<00:09:46.480> i<00:09:46.560> would 00:09:46.790 --> 00:09:46.800 align:start position:0% and i still want to stress that i would 00:09:46.800 --> 00:09:48.550 align:start position:0% and i still want to stress that i would really<00:09:47.040> like<00:09:47.200> to<00:09:47.279> take<00:09:47.519> action<00:09:48.160> to<00:09:48.320> have<00:09:48.480> the 00:09:48.550 --> 00:09:48.560 align:start position:0% really like to take action to have the 00:09:48.560 --> 00:09:51.350 align:start position:0% really like to take action to have the ordc<00:09:49.360> in<00:09:49.440> place<00:09:50.000> um<00:09:50.320> by<00:09:50.560> the<00:09:50.640> beginning<00:09:51.120> of 00:09:51.350 --> 00:09:51.360 align:start position:0% ordc in place um by the beginning of 00:09:51.360 --> 00:09:53.110 align:start position:0% ordc in place um by the beginning of january<00:09:52.000> i<00:09:52.160> think 00:09:53.110 --> 00:09:53.120 align:start position:0% january i think 00:09:53.120 --> 00:09:55.829 align:start position:0% january i think you<00:09:53.200> know<00:09:53.760> it's<00:09:53.920> prudent<00:09:54.560> to<00:09:54.720> do<00:09:54.880> so<00:09:55.360> to<00:09:55.600> to 00:09:55.829 --> 00:09:55.839 align:start position:0% you know it's prudent to do so to to 00:09:55.839 --> 00:09:58.230 align:start position:0% you know it's prudent to do so to to drive<00:09:56.160> resources<00:09:56.880> uh<00:09:57.360> reserves<00:09:57.839> online 00:09:58.230 --> 00:09:58.240 align:start position:0% drive resources uh reserves online 00:09:58.240 --> 00:10:01.030 align:start position:0% drive resources uh reserves online earlier<00:09:59.120> um<00:09:59.760> especially<00:10:00.240> as<00:10:00.399> i<00:10:00.480> think<00:10:00.720> you<00:10:00.800> see 00:10:01.030 --> 00:10:01.040 align:start position:0% earlier um especially as i think you see 00:10:01.040 --> 00:10:02.710 align:start position:0% earlier um especially as i think you see some<00:10:01.200> weather<00:10:01.440> reports<00:10:01.920> out<00:10:02.000> there<00:10:02.240> that<00:10:02.480> show 00:10:02.710 --> 00:10:02.720 align:start position:0% some weather reports out there that show 00:10:02.720 --> 00:10:04.389 align:start position:0% some weather reports out there that show that<00:10:03.360> even 00:10:04.389 --> 00:10:04.399 align:start position:0% that even 00:10:04.399 --> 00:10:07.030 align:start position:0% that even we<00:10:04.560> might<00:10:04.800> get<00:10:04.959> colder<00:10:05.279> weather<00:10:05.600> in<00:10:05.680> january 00:10:07.030 --> 00:10:07.040 align:start position:0% we might get colder weather in january 00:10:07.040 --> 00:10:10.069 align:start position:0% we might get colder weather in january versus<00:10:07.519> maybe<00:10:07.839> later<00:10:08.160> in<00:10:08.240> the<00:10:08.320> winter<00:10:08.800> so<00:10:09.279> i<00:10:09.760> i 00:10:10.069 --> 00:10:10.079 align:start position:0% versus maybe later in the winter so i i 00:10:10.079 --> 00:10:11.750 align:start position:0% versus maybe later in the winter so i i really<00:10:10.320> think<00:10:10.480> it's<00:10:10.720> prudent<00:10:11.040> to<00:10:11.120> take<00:10:11.360> action 00:10:11.750 --> 00:10:11.760 align:start position:0% really think it's prudent to take action 00:10:11.760 --> 00:10:12.949 align:start position:0% really think it's prudent to take action to<00:10:11.920> make<00:10:12.079> sure<00:10:12.240> we<00:10:12.399> have<00:10:12.560> it<00:10:12.640> fully 00:10:12.949 --> 00:10:12.959 align:start position:0% to make sure we have it fully 00:10:12.959 --> 00:10:14.870 align:start position:0% to make sure we have it fully implemented<00:10:13.519> ready<00:10:13.760> to<00:10:13.839> go<00:10:14.079> by<00:10:14.320> the<00:10:14.480> beginning 00:10:14.870 --> 00:10:14.880 align:start position:0% implemented ready to go by the beginning 00:10:14.880 --> 00:10:17.110 align:start position:0% implemented ready to go by the beginning of<00:10:14.959> january 00:10:17.110 --> 00:10:17.120 align:start position:0% of january 00:10:17.120 --> 00:10:18.630 align:start position:0% of january and<00:10:17.200> i<00:10:17.360> want<00:10:17.440> to<00:10:17.519> take<00:10:17.680> this<00:10:17.920> opportunity<00:10:18.480> to 00:10:18.630 --> 00:10:18.640 align:start position:0% and i want to take this opportunity to 00:10:18.640 --> 00:10:19.990 align:start position:0% and i want to take this opportunity to really<00:10:18.880> kind<00:10:19.040> of 00:10:19.990 --> 00:10:20.000 align:start position:0% really kind of 00:10:20.000 --> 00:10:21.990 align:start position:0% really kind of sort<00:10:20.320> of<00:10:20.880> um 00:10:21.990 --> 00:10:22.000 align:start position:0% sort of um 00:10:22.000 --> 00:10:23.829 align:start position:0% sort of um backtrack<00:10:22.480> a<00:10:22.560> little<00:10:22.720> bit<00:10:23.120> and 00:10:23.829 --> 00:10:23.839 align:start position:0% backtrack a little bit and 00:10:23.839 --> 00:10:25.190 align:start position:0% backtrack a little bit and and<00:10:24.320> you<00:10:24.399> know 00:10:25.190 --> 00:10:25.200 align:start position:0% and you know 00:10:25.200 --> 00:10:27.430 align:start position:0% and you know i<00:10:25.279> think<00:10:25.440> this<00:10:25.680> is<00:10:25.760> really<00:10:26.000> important<00:10:26.800> often 00:10:27.430 --> 00:10:27.440 align:start position:0% i think this is really important often 00:10:27.440 --> 00:10:28.949 align:start position:0% i think this is really important often all<00:10:27.600> these<00:10:27.839> items<00:10:28.160> that<00:10:28.240> we're<00:10:28.399> talking<00:10:28.640> about 00:10:28.949 --> 00:10:28.959 align:start position:0% all these items that we're talking about 00:10:28.959 --> 00:10:30.790 align:start position:0% all these items that we're talking about right<00:10:29.120> now<00:10:29.360> have<00:10:29.519> been<00:10:29.760> referred<00:10:30.160> to<00:10:30.399> as 00:10:30.790 --> 00:10:30.800 align:start position:0% right now have been referred to as 00:10:30.800 --> 00:10:33.509 align:start position:0% right now have been referred to as low-hanging<00:10:31.279> fruit<00:10:32.240> and<00:10:32.880> items<00:10:33.200> that<00:10:33.279> we<00:10:33.440> have 00:10:33.509 --> 00:10:33.519 align:start position:0% low-hanging fruit and items that we have 00:10:33.519 --> 00:10:36.630 align:start position:0% low-hanging fruit and items that we have consensus<00:10:34.240> on<00:10:34.480> and<00:10:35.040> and<00:10:35.200> i<00:10:35.279> don't<00:10:35.440> want<00:10:35.600> it 00:10:36.630 --> 00:10:36.640 align:start position:0% consensus on and and i don't want it 00:10:36.640 --> 00:10:37.910 align:start position:0% consensus on and and i don't want it and<00:10:36.720> really<00:10:37.040> i<00:10:37.120> think<00:10:37.279> it's<00:10:37.440> just<00:10:37.600> important 00:10:37.910 --> 00:10:37.920 align:start position:0% and really i think it's just important 00:10:37.920 --> 00:10:39.829 align:start position:0% and really i think it's just important for<00:10:38.079> the<00:10:38.240> public<00:10:38.560> to<00:10:38.720> know<00:10:39.040> and<00:10:39.600> and 00:10:39.829 --> 00:10:39.839 align:start position:0% for the public to know and and 00:10:39.839 --> 00:10:41.110 align:start position:0% for the public to know and and leadership<00:10:40.320> and<00:10:40.480> everybody<00:10:40.880> out<00:10:40.959> there 00:10:41.110 --> 00:10:41.120 align:start position:0% leadership and everybody out there 00:10:41.120 --> 00:10:43.430 align:start position:0% leadership and everybody out there that's<00:10:41.360> listening 00:10:43.430 --> 00:10:43.440 align:start position:0% that's listening 00:10:43.440 --> 00:10:44.870 align:start position:0% that's listening i<00:10:43.519> think<00:10:43.680> we<00:10:43.839> need<00:10:43.920> to<00:10:44.000> get<00:10:44.160> away<00:10:44.399> from<00:10:44.560> calling 00:10:44.870 --> 00:10:44.880 align:start position:0% i think we need to get away from calling 00:10:44.880 --> 00:10:46.470 align:start position:0% i think we need to get away from calling this<00:10:45.040> low-hanging<00:10:45.519> fruit<00:10:45.760> i<00:10:45.839> think<00:10:46.079> everybody 00:10:46.470 --> 00:10:46.480 align:start position:0% this low-hanging fruit i think everybody 00:10:46.480 --> 00:10:48.069 align:start position:0% this low-hanging fruit i think everybody in<00:10:46.560> this<00:10:46.720> room<00:10:47.040> knows<00:10:47.360> that 00:10:48.069 --> 00:10:48.079 align:start position:0% in this room knows that 00:10:48.079 --> 00:10:49.509 align:start position:0% in this room knows that under<00:10:48.320> certain<00:10:48.560> circumstances<00:10:49.279> we<00:10:49.360> would 00:10:49.509 --> 00:10:49.519 align:start position:0% under certain circumstances we would 00:10:49.519 --> 00:10:51.190 align:start position:0% under certain circumstances we would have<00:10:49.600> debated<00:10:50.079> this<00:10:50.320> and<00:10:50.480> bought<00:10:50.880> all<00:10:51.040> of 00:10:51.190 --> 00:10:51.200 align:start position:0% have debated this and bought all of 00:10:51.200 --> 00:10:53.509 align:start position:0% have debated this and bought all of these<00:10:51.440> issues<00:10:51.920> to<00:10:52.079> the<00:10:52.240> ground<00:10:53.120> including 00:10:53.509 --> 00:10:53.519 align:start position:0% these issues to the ground including 00:10:53.519 --> 00:10:55.269 align:start position:0% these issues to the ground including ordc 00:10:55.269 --> 00:10:55.279 align:start position:0% ordc 00:10:55.279 --> 00:10:56.550 align:start position:0% ordc and<00:10:55.760> there<00:10:55.920> would<00:10:56.000> have<00:10:56.079> been<00:10:56.240> a<00:10:56.320> lot<00:10:56.480> of 00:10:56.550 --> 00:10:56.560 align:start position:0% and there would have been a lot of 00:10:56.560 --> 00:10:58.949 align:start position:0% and there would have been a lot of controversial<00:10:57.279> debate<00:10:58.160> you<00:10:58.240> know<00:10:58.480> i<00:10:58.720> think 00:10:58.949 --> 00:10:58.959 align:start position:0% controversial debate you know i think 00:10:58.959 --> 00:11:01.030 align:start position:0% controversial debate you know i think these<00:10:59.440> actions<00:10:59.760> are<00:10:59.920> important<00:11:00.800> they're 00:11:01.030 --> 00:11:01.040 align:start position:0% these actions are important they're 00:11:01.040 --> 00:11:02.630 align:start position:0% these actions are important they're actions<00:11:01.440> that<00:11:01.519> move<00:11:01.760> urcat<00:11:02.160> away<00:11:02.399> from 00:11:02.630 --> 00:11:02.640 align:start position:0% actions that move urcat away from 00:11:02.640 --> 00:11:04.630 align:start position:0% actions that move urcat away from operating<00:11:03.040> the<00:11:03.200> grid<00:11:03.440> in<00:11:03.519> a<00:11:03.600> crisis-based 00:11:04.630 --> 00:11:04.640 align:start position:0% operating the grid in a crisis-based 00:11:04.640 --> 00:11:05.829 align:start position:0% operating the grid in a crisis-based manner 00:11:05.829 --> 00:11:05.839 align:start position:0% manner 00:11:05.839 --> 00:11:07.910 align:start position:0% manner and<00:11:06.160> provide<00:11:06.640> ercot<00:11:07.040> with<00:11:07.200> an<00:11:07.360> arsenal<00:11:07.839> of 00:11:07.910 --> 00:11:07.920 align:start position:0% and provide ercot with an arsenal of 00:11:07.920 --> 00:11:09.670 align:start position:0% and provide ercot with an arsenal of tools<00:11:08.240> to<00:11:08.320> address<00:11:08.800> issues<00:11:09.120> that<00:11:09.279> we<00:11:09.360> have<00:11:09.600> and 00:11:09.670 --> 00:11:09.680 align:start position:0% tools to address issues that we have and 00:11:09.680 --> 00:11:11.030 align:start position:0% tools to address issues that we have and will<00:11:09.920> continue<00:11:10.240> to<00:11:10.399> experience<00:11:10.800> in<00:11:10.880> the 00:11:11.030 --> 00:11:11.040 align:start position:0% will continue to experience in the 00:11:11.040 --> 00:11:13.110 align:start position:0% will continue to experience in the future<00:11:11.839> these<00:11:12.079> actions<00:11:12.399> are<00:11:12.480> strategic 00:11:13.110 --> 00:11:13.120 align:start position:0% future these actions are strategic 00:11:13.120 --> 00:11:14.389 align:start position:0% future these actions are strategic they're<00:11:13.279> targeted 00:11:14.389 --> 00:11:14.399 align:start position:0% they're targeted 00:11:14.399 --> 00:11:15.269 align:start position:0% they're targeted and 00:11:15.269 --> 00:11:15.279 align:start position:0% and 00:11:15.279 --> 00:11:17.269 align:start position:0% and they're<00:11:15.600> important<00:11:16.079> steps<00:11:16.480> towards<00:11:16.880> ensuring 00:11:17.269 --> 00:11:17.279 align:start position:0% they're important steps towards ensuring 00:11:17.279 --> 00:11:19.110 align:start position:0% they're important steps towards ensuring that<00:11:17.440> we<00:11:17.519> have<00:11:17.680> a<00:11:17.760> resilient<00:11:18.480> and<00:11:18.560> reliable 00:11:19.110 --> 00:11:19.120 align:start position:0% that we have a resilient and reliable 00:11:19.120 --> 00:11:21.190 align:start position:0% that we have a resilient and reliable grid<00:11:19.839> so<00:11:20.000> i<00:11:20.079> don't<00:11:20.240> want<00:11:20.399> to<00:11:20.480> minimize<00:11:20.959> these 00:11:21.190 --> 00:11:21.200 align:start position:0% grid so i don't want to minimize these 00:11:21.200 --> 00:11:22.550 align:start position:0% grid so i don't want to minimize these actions<00:11:21.600> i<00:11:21.680> don't<00:11:21.839> want<00:11:22.000> to<00:11:22.079> call<00:11:22.240> them<00:11:22.399> low 00:11:22.550 --> 00:11:22.560 align:start position:0% actions i don't want to call them low 00:11:22.560 --> 00:11:24.069 align:start position:0% actions i don't want to call them low hanging<00:11:22.880> fruit<00:11:23.120> anymore<00:11:23.600> even<00:11:23.839> though<00:11:24.000> they 00:11:24.069 --> 00:11:24.079 align:start position:0% hanging fruit anymore even though they 00:11:24.079 --> 00:11:25.910 align:start position:0% hanging fruit anymore even though they may<00:11:24.240> be<00:11:24.480> easy<00:11:24.720> to<00:11:24.880> implement<00:11:25.279> without<00:11:25.600> large 00:11:25.910 --> 00:11:25.920 align:start position:0% may be easy to implement without large 00:11:25.920 --> 00:11:27.269 align:start position:0% may be easy to implement without large system<00:11:26.320> changes 00:11:27.269 --> 00:11:27.279 align:start position:0% system changes 00:11:27.279 --> 00:11:28.790 align:start position:0% system changes and<00:11:27.440> with<00:11:27.760> and<00:11:28.000> and 00:11:28.790 --> 00:11:28.800 align:start position:0% and with and and 00:11:28.800 --> 00:11:30.470 align:start position:0% and with and and the<00:11:28.959> fact<00:11:29.200> that<00:11:29.279> we<00:11:29.440> have<00:11:29.600> consensus<00:11:30.240> on<00:11:30.399> them 00:11:30.470 --> 00:11:30.480 align:start position:0% the fact that we have consensus on them 00:11:30.480 --> 00:11:32.310 align:start position:0% the fact that we have consensus on them does<00:11:30.720> not<00:11:30.880> mean<00:11:31.200> that 00:11:32.310 --> 00:11:32.320 align:start position:0% does not mean that 00:11:32.320 --> 00:11:34.310 align:start position:0% does not mean that you<00:11:32.399> know<00:11:33.040> there's<00:11:33.440> been<00:11:33.680> not<00:11:33.839> been<00:11:34.000> a<00:11:34.079> lot<00:11:34.240> of 00:11:34.310 --> 00:11:34.320 align:start position:0% you know there's been not been a lot of 00:11:34.320 --> 00:11:35.990 align:start position:0% you know there's been not been a lot of hard<00:11:34.560> work<00:11:34.800> put<00:11:35.040> into<00:11:35.279> this<00:11:35.519> and<00:11:35.600> that<00:11:35.760> these 00:11:35.990 --> 00:11:36.000 align:start position:0% hard work put into this and that these 00:11:36.000 --> 00:11:37.829 align:start position:0% hard work put into this and that these actions<00:11:36.399> are<00:11:36.480> going<00:11:36.640> to<00:11:36.720> have<00:11:36.959> meaningful 00:11:37.829 --> 00:11:37.839 align:start position:0% actions are going to have meaningful 00:11:37.839 --> 00:11:39.829 align:start position:0% actions are going to have meaningful reliability<00:11:38.720> value 00:11:39.829 --> 00:11:39.839 align:start position:0% reliability value 00:11:39.839 --> 00:11:40.550 align:start position:0% reliability value for 00:11:40.550 --> 00:11:40.560 align:start position:0% for 00:11:40.560 --> 00:11:41.590 align:start position:0% for our<00:11:40.720> grid 00:11:41.590 --> 00:11:41.600 align:start position:0% our grid 00:11:41.600 --> 00:11:42.710 align:start position:0% our grid and<00:11:41.839> so 00:11:42.710 --> 00:11:42.720 align:start position:0% and so 00:11:42.720 --> 00:11:44.150 align:start position:0% and so i<00:11:42.800> just<00:11:42.959> kind<00:11:43.040> of<00:11:43.120> want<00:11:43.279> to<00:11:43.360> level<00:11:43.600> set<00:11:43.839> on<00:11:43.920> that 00:11:44.150 --> 00:11:44.160 align:start position:0% i just kind of want to level set on that 00:11:44.160 --> 00:11:45.269 align:start position:0% i just kind of want to level set on that that 00:11:45.269 --> 00:11:45.279 align:start position:0% that 00:11:45.279 --> 00:11:46.790 align:start position:0% that as<00:11:45.440> i<00:11:45.519> read<00:11:45.680> through<00:11:45.839> a<00:11:45.920> lot<00:11:46.079> of<00:11:46.160> the<00:11:46.320> comments 00:11:46.790 --> 00:11:46.800 align:start position:0% as i read through a lot of the comments 00:11:46.800 --> 00:11:47.910 align:start position:0% as i read through a lot of the comments a<00:11:46.880> lot<00:11:47.040> of<00:11:47.120> the<00:11:47.279> statements<00:11:47.600> that<00:11:47.680> have<00:11:47.760> been 00:11:47.910 --> 00:11:47.920 align:start position:0% a lot of the statements that have been 00:11:47.920 --> 00:11:48.790 align:start position:0% a lot of the statements that have been made 00:11:48.790 --> 00:11:48.800 align:start position:0% made 00:11:48.800 --> 00:11:50.150 align:start position:0% made um 00:11:50.150 --> 00:11:50.160 align:start position:0% um 00:11:50.160 --> 00:11:52.150 align:start position:0% um i<00:11:50.320> think<00:11:51.040> we<00:11:51.200> need<00:11:51.360> to<00:11:51.440> get<00:11:51.519> away<00:11:51.760> from<00:11:51.920> that 00:11:52.150 --> 00:11:52.160 align:start position:0% i think we need to get away from that 00:11:52.160 --> 00:11:53.590 align:start position:0% i think we need to get away from that all<00:11:52.480> of<00:11:52.560> these<00:11:52.720> actions<00:11:53.200> that<00:11:53.279> we're<00:11:53.440> going<00:11:53.519> to 00:11:53.590 --> 00:11:53.600 align:start position:0% all of these actions that we're going to 00:11:53.600 --> 00:11:55.350 align:start position:0% all of these actions that we're going to talk<00:11:53.839> about<00:11:54.079> this<00:11:54.320> this<00:11:54.560> first<00:11:54.800> set<00:11:54.959> of<00:11:55.200> this 00:11:55.350 --> 00:11:55.360 align:start position:0% talk about this this first set of this 00:11:55.360 --> 00:11:57.670 align:start position:0% talk about this this first set of this first<00:11:55.600> round<00:11:55.839> of<00:11:55.920> the<00:11:56.000> workshop<00:11:56.639> um 00:11:57.670 --> 00:11:57.680 align:start position:0% first round of the workshop um 00:11:57.680 --> 00:11:59.590 align:start position:0% first round of the workshop um are<00:11:57.839> very<00:11:58.160> important<00:11:59.040> and<00:11:59.200> come<00:11:59.440> with<00:11:59.519> a 00:11:59.590 --> 00:11:59.600 align:start position:0% are very important and come with a 00:11:59.600 --> 00:12:01.509 align:start position:0% are very important and come with a reliability<00:12:00.240> benefit<00:12:00.800> and<00:12:00.880> we<00:12:01.040> must<00:12:01.279> also 00:12:01.509 --> 00:12:01.519 align:start position:0% reliability benefit and we must also 00:12:01.519 --> 00:12:03.670 align:start position:0% reliability benefit and we must also balance<00:12:02.000> consumer<00:12:02.480> costs<00:12:02.800> with<00:12:02.959> them<00:12:03.120> so<00:12:03.600> i 00:12:03.670 --> 00:12:03.680 align:start position:0% balance consumer costs with them so i 00:12:03.680 --> 00:12:05.430 align:start position:0% balance consumer costs with them so i just<00:12:03.839> wanted<00:12:04.160> to<00:12:04.240> say<00:12:04.399> that<00:12:04.800> um<00:12:05.040> before<00:12:05.360> we 00:12:05.430 --> 00:12:05.440 align:start position:0% just wanted to say that um before we 00:12:05.440 --> 00:12:07.430 align:start position:0% just wanted to say that um before we went<00:12:05.600> too<00:12:05.760> far<00:12:06.000> along<00:12:06.399> down<00:12:06.560> the<00:12:06.639> list<00:12:07.200> well 00:12:07.430 --> 00:12:07.440 align:start position:0% went too far along down the list well 00:12:07.440 --> 00:12:08.470 align:start position:0% went too far along down the list well put 00:12:08.470 --> 00:12:08.480 align:start position:0% put 00:12:08.480 --> 00:12:11.910 align:start position:0% put okay<00:12:08.880> thoughts<00:12:09.120> on<00:12:09.279> rdc 00:12:11.910 --> 00:12:11.920 align:start position:0% 00:12:11.920 --> 00:12:13.350 align:start position:0% um 00:12:13.350 --> 00:12:13.360 align:start position:0% um 00:12:13.360 --> 00:12:16.230 align:start position:0% um thank<00:12:13.600> you<00:12:14.160> i<00:12:14.399> appreciate<00:12:14.880> it<00:12:15.360> i<00:12:15.600> appreciate 00:12:16.230 --> 00:12:16.240 align:start position:0% thank you i appreciate it i appreciate 00:12:16.240 --> 00:12:19.030 align:start position:0% thank you i appreciate it i appreciate the<00:12:16.399> other<00:12:16.560> comments<00:12:17.120> as<00:12:17.279> well<00:12:17.760> um 00:12:19.030 --> 00:12:19.040 align:start position:0% the other comments as well um 00:12:19.040 --> 00:12:23.590 align:start position:0% the other comments as well um so<00:12:19.680> to<00:12:19.839> me<00:12:20.399> um<00:12:21.200> the<00:12:21.440> ordc 00:12:23.590 --> 00:12:23.600 align:start position:0% so to me um the ordc 00:12:23.600 --> 00:12:25.350 align:start position:0% so to me um the ordc what<00:12:23.760> i've<00:12:23.839> been<00:12:24.000> struggling<00:12:24.399> with<00:12:24.720> is<00:12:24.880> that 00:12:25.350 --> 00:12:25.360 align:start position:0% what i've been struggling with is that 00:12:25.360 --> 00:12:26.710 align:start position:0% what i've been struggling with is that um 00:12:26.710 --> 00:12:26.720 align:start position:0% um 00:12:26.720 --> 00:12:29.190 align:start position:0% um what<00:12:26.880> are<00:12:26.959> we<00:12:27.200> using<00:12:27.440> the<00:12:27.600> ordc<00:12:28.240> to<00:12:28.399> solve 00:12:29.190 --> 00:12:29.200 align:start position:0% what are we using the ordc to solve 00:12:29.200 --> 00:12:31.590 align:start position:0% what are we using the ordc to solve right<00:12:29.920> very<00:12:30.160> good<00:12:30.320> question<00:12:30.800> are<00:12:30.959> we<00:12:31.200> so<00:12:31.440> are 00:12:31.590 --> 00:12:31.600 align:start position:0% right very good question are we so are 00:12:31.600 --> 00:12:34.629 align:start position:0% right very good question are we so are we<00:12:31.760> using<00:12:32.000> it<00:12:32.079> to<00:12:32.240> solve<00:12:32.480> a<00:12:32.560> capacity<00:12:33.200> problem 00:12:34.629 --> 00:12:34.639 align:start position:0% we using it to solve a capacity problem 00:12:34.639 --> 00:12:39.030 align:start position:0% we using it to solve a capacity problem um<00:12:35.360> if<00:12:35.519> that's<00:12:35.760> the<00:12:35.920> case<00:12:36.399> then 00:12:39.030 --> 00:12:39.040 align:start position:0% 00:12:39.040 --> 00:12:40.470 align:start position:0% one<00:12:39.200> thing<00:12:39.360> that<00:12:39.519> i<00:12:39.600> did<00:12:39.839> yesterday<00:12:40.240> was<00:12:40.399> i 00:12:40.470 --> 00:12:40.480 align:start position:0% one thing that i did yesterday was i 00:12:40.480 --> 00:12:41.990 align:start position:0% one thing that i did yesterday was i reached<00:12:40.800> out<00:12:40.880> to<00:12:41.040> a<00:12:41.040> lot<00:12:41.279> of<00:12:41.360> people<00:12:41.680> asking 00:12:41.990 --> 00:12:42.000 align:start position:0% reached out to a lot of people asking 00:12:42.000 --> 00:12:45.590 align:start position:0% reached out to a lot of people asking them<00:12:42.720> if<00:12:43.040> modifications<00:12:43.839> of<00:12:43.920> the<00:12:44.079> ordc 00:12:45.590 --> 00:12:45.600 align:start position:0% them if modifications of the ordc 00:12:45.600 --> 00:12:47.590 align:start position:0% them if modifications of the ordc since<00:12:45.839> its<00:12:46.000> inception<00:12:46.480> have<00:12:46.720> ever<00:12:46.880> incented 00:12:47.590 --> 00:12:47.600 align:start position:0% since its inception have ever incented 00:12:47.600 --> 00:12:49.430 align:start position:0% since its inception have ever incented new<00:12:47.760> generation<00:12:48.480> on<00:12:48.639> the<00:12:48.720> system<00:12:49.120> and<00:12:49.279> the 00:12:49.430 --> 00:12:49.440 align:start position:0% new generation on the system and the 00:12:49.440 --> 00:12:53.990 align:start position:0% new generation on the system and the answer<00:12:49.839> resoundingly<00:12:50.639> was<00:12:50.959> no<00:12:52.240> yeah<00:12:52.800> so 00:12:53.990 --> 00:12:54.000 align:start position:0% answer resoundingly was no yeah so 00:12:54.000 --> 00:12:55.350 align:start position:0% answer resoundingly was no yeah so we've<00:12:54.160> seen<00:12:54.399> this<00:12:54.560> show<00:12:54.800> if<00:12:54.959> you've<00:12:55.040> seen<00:12:55.200> this 00:12:55.350 --> 00:12:55.360 align:start position:0% we've seen this show if you've seen this 00:12:55.360 --> 00:12:57.670 align:start position:0% we've seen this show if you've seen this movie<00:12:55.760> yeah<00:12:56.000> so<00:12:56.480> what<00:12:56.639> i<00:12:56.720> want<00:12:56.880> to<00:12:57.040> do<00:12:57.279> is<00:12:57.360> just 00:12:57.670 --> 00:12:57.680 align:start position:0% movie yeah so what i want to do is just 00:12:57.680 --> 00:12:59.350 align:start position:0% movie yeah so what i want to do is just make<00:12:57.920> sure<00:12:58.320> that 00:12:59.350 --> 00:12:59.360 align:start position:0% make sure that 00:12:59.360 --> 00:13:01.509 align:start position:0% make sure that we're<00:12:59.600> not<00:12:59.839> going<00:13:00.160> into<00:13:00.560> that 00:13:01.509 --> 00:13:01.519 align:start position:0% we're not going into that 00:13:01.519 --> 00:13:04.550 align:start position:0% we're not going into that um<00:13:02.000> as<00:13:02.240> a<00:13:02.480> means<00:13:02.880> to 00:13:04.550 --> 00:13:04.560 align:start position:0% um as a means to 00:13:04.560 --> 00:13:05.910 align:start position:0% um as a means to we're<00:13:04.720> going<00:13:04.800> to<00:13:04.959> incent<00:13:05.200> new<00:13:05.440> generation 00:13:05.910 --> 00:13:05.920 align:start position:0% we're going to incent new generation 00:13:05.920 --> 00:13:08.150 align:start position:0% we're going to incent new generation here<00:13:06.240> because<00:13:06.639> i<00:13:06.959> think<00:13:07.200> history<00:13:07.600> has<00:13:07.839> proven 00:13:08.150 --> 00:13:08.160 align:start position:0% here because i think history has proven 00:13:08.160 --> 00:13:10.069 align:start position:0% here because i think history has proven that<00:13:08.320> it<00:13:08.560> that<00:13:08.800> it<00:13:08.880> doesn't 00:13:10.069 --> 00:13:10.079 align:start position:0% that it that it doesn't 00:13:10.079 --> 00:13:12.389 align:start position:0% that it that it doesn't so<00:13:10.320> so<00:13:10.480> that's<00:13:10.639> a<00:13:10.800> good<00:13:10.959> point<00:13:11.360> uh<00:13:11.680> correct<00:13:12.160> did 00:13:12.389 --> 00:13:12.399 align:start position:0% so so that's a good point uh correct did 00:13:12.399 --> 00:13:14.629 align:start position:0% so so that's a good point uh correct did i<00:13:12.480> like<00:13:12.639> to<00:13:12.720> have<00:13:12.959> an<00:13:13.120> exchange<00:13:13.519> on 00:13:14.629 --> 00:13:14.639 align:start position:0% i like to have an exchange on 00:13:14.639 --> 00:13:18.829 align:start position:0% i like to have an exchange on it<00:13:15.360> look<00:13:15.600> in<00:13:15.680> my<00:13:15.920> view<00:13:16.160> just<00:13:16.639> one<00:13:17.200> um 00:13:18.829 --> 00:13:18.839 align:start position:0% it look in my view just one um 00:13:18.839 --> 00:13:20.389 align:start position:0% it look in my view just one um ordc 00:13:20.389 --> 00:13:20.399 align:start position:0% ordc 00:13:20.399 --> 00:13:22.710 align:start position:0% ordc was<00:13:20.639> pitched<00:13:21.040> as<00:13:21.200> a<00:13:21.279> way<00:13:21.600> to<00:13:21.920> to<00:13:22.079> try<00:13:22.240> to<00:13:22.399> bridge 00:13:22.710 --> 00:13:22.720 align:start position:0% was pitched as a way to to try to bridge 00:13:22.720 --> 00:13:25.910 align:start position:0% was pitched as a way to to try to bridge the<00:13:22.800> divide<00:13:23.600> um<00:13:24.000> on<00:13:24.399> the<00:13:24.560> capacity<00:13:25.440> versus<00:13:25.760> the 00:13:25.910 --> 00:13:25.920 align:start position:0% the divide um on the capacity versus the 00:13:25.920 --> 00:13:28.949 align:start position:0% the divide um on the capacity versus the pure<00:13:26.240> energy<00:13:26.639> only<00:13:27.279> um<00:13:28.000> paradigms<00:13:28.639> that<00:13:28.800> were 00:13:28.949 --> 00:13:28.959 align:start position:0% pure energy only um paradigms that were 00:13:28.959 --> 00:13:31.430 align:start position:0% pure energy only um paradigms that were present<00:13:29.600> in<00:13:29.680> the<00:13:30.399> in<00:13:30.480> the<00:13:30.639> last<00:13:30.880> decade<00:13:31.360> the 00:13:31.430 --> 00:13:31.440 align:start position:0% present in the in the last decade the 00:13:31.440 --> 00:13:33.110 align:start position:0% present in the in the last decade the beginning<00:13:31.680> of<00:13:31.760> the<00:13:31.839> last<00:13:32.000> decade 00:13:33.110 --> 00:13:33.120 align:start position:0% beginning of the last decade 00:13:33.120 --> 00:13:34.790 align:start position:0% beginning of the last decade and 00:13:34.790 --> 00:13:34.800 align:start position:0% and 00:13:34.800 --> 00:13:37.670 align:start position:0% and but<00:13:35.120> ultimately<00:13:35.600> it<00:13:35.760> evolved<00:13:36.160> into<00:13:36.720> as<00:13:36.959> a<00:13:37.120> tool 00:13:37.670 --> 00:13:37.680 align:start position:0% but ultimately it evolved into as a tool 00:13:37.680 --> 00:13:40.150 align:start position:0% but ultimately it evolved into as a tool to<00:13:37.920> enhance<00:13:38.480> the<00:13:38.639> energy<00:13:39.040> only's 00:13:40.150 --> 00:13:40.160 align:start position:0% to enhance the energy only's 00:13:40.160 --> 00:13:42.470 align:start position:0% to enhance the energy only's single<00:13:40.720> most<00:13:40.959> important<00:13:41.440> function<00:13:42.160> which<00:13:42.399> is 00:13:42.470 --> 00:13:42.480 align:start position:0% single most important function which is 00:13:42.480 --> 00:13:45.350 align:start position:0% single most important function which is to<00:13:42.639> incent<00:13:43.040> price<00:13:43.360> responsive<00:13:44.000> behavior 00:13:45.350 --> 00:13:45.360 align:start position:0% to incent price responsive behavior 00:13:45.360 --> 00:13:47.350 align:start position:0% to incent price responsive behavior either<00:13:45.600> on<00:13:45.680> the<00:13:45.839> gen<00:13:46.160> side<00:13:46.720> and<00:13:47.120> on<00:13:47.199> the 00:13:47.350 --> 00:13:47.360 align:start position:0% either on the gen side and on the 00:13:47.360 --> 00:13:48.470 align:start position:0% either on the gen side and on the resource<00:13:47.760> side 00:13:48.470 --> 00:13:48.480 align:start position:0% resource side 00:13:48.480 --> 00:13:50.150 align:start position:0% resource side so<00:13:48.639> that<00:13:48.800> people<00:13:49.040> can<00:13:49.199> see<00:13:49.440> these<00:13:49.680> prices 00:13:50.150 --> 00:13:50.160 align:start position:0% so that people can see these prices 00:13:50.160 --> 00:13:52.230 align:start position:0% so that people can see these prices ticking<00:13:50.480> up<00:13:50.639> and<00:13:50.800> give<00:13:51.040> them<00:13:51.440> added<00:13:51.839> sense<00:13:52.079> of 00:13:52.230 --> 00:13:52.240 align:start position:0% ticking up and give them added sense of 00:13:52.240 --> 00:13:55.189 align:start position:0% ticking up and give them added sense of urgency<00:13:53.120> to<00:13:53.760> change<00:13:54.079> their<00:13:54.320> behavior<00:13:54.880> in<00:13:54.959> some 00:13:55.189 --> 00:13:55.199 align:start position:0% urgency to change their behavior in some 00:13:55.199 --> 00:13:59.110 align:start position:0% urgency to change their behavior in some way<00:13:55.440> that<00:13:55.600> positively<00:13:56.240> affects<00:13:56.560> the<00:13:56.720> grid 00:13:59.110 --> 00:13:59.120 align:start position:0% 00:13:59.120 --> 00:13:59.829 align:start position:0% and 00:13:59.829 --> 00:13:59.839 align:start position:0% and 00:13:59.839 --> 00:14:01.910 align:start position:0% and it<00:14:00.320> has<00:14:00.480> done<00:14:00.720> that<00:14:00.959> to<00:14:01.120> a<00:14:01.199> degree<00:14:01.519> and<00:14:01.680> that's 00:14:01.910 --> 00:14:01.920 align:start position:0% it has done that to a degree and that's 00:14:01.920 --> 00:14:03.910 align:start position:0% it has done that to a degree and that's why<00:14:02.079> 2019<00:14:02.720> was<00:14:02.880> so<00:14:03.040> important<00:14:03.440> and<00:14:03.519> that<00:14:03.680> was 00:14:03.910 --> 00:14:03.920 align:start position:0% why 2019 was so important and that was 00:14:03.920 --> 00:14:05.350 align:start position:0% why 2019 was so important and that was influencing<00:14:04.399> those<00:14:04.560> commission<00:14:04.959> decisions 00:14:05.350 --> 00:14:05.360 align:start position:0% influencing those commission decisions 00:14:05.360 --> 00:14:07.430 align:start position:0% influencing those commission decisions all<00:14:05.519> the<00:14:05.600> way<00:14:05.680> up<00:14:05.839> to<00:14:05.920> that<00:14:06.079> point<00:14:06.639> to<00:14:06.959> increase 00:14:07.430 --> 00:14:07.440 align:start position:0% all the way up to that point to increase 00:14:07.440 --> 00:14:09.910 align:start position:0% all the way up to that point to increase the<00:14:07.600> system-wide<00:14:08.160> offer<00:14:08.480> cap<00:14:09.199> from<00:14:09.519> what<00:14:09.680> was 00:14:09.910 --> 00:14:09.920 align:start position:0% the system-wide offer cap from what was 00:14:09.920 --> 00:14:11.110 align:start position:0% the system-wide offer cap from what was it 00:14:11.110 --> 00:14:11.120 align:start position:0% it 00:14:11.120 --> 00:14:14.550 align:start position:0% it 2000<00:14:11.839> somewhereabouts<00:14:13.040> to<00:14:13.519> 4500<00:14:14.320> and<00:14:14.399> then 00:14:14.550 --> 00:14:14.560 align:start position:0% 2000 somewhereabouts to 4500 and then 00:14:14.560 --> 00:14:16.710 align:start position:0% 2000 somewhereabouts to 4500 and then ultimately<00:14:15.040> to<00:14:15.440> 9<00:14:15.839> 000 00:14:16.710 --> 00:14:16.720 align:start position:0% ultimately to 9 000 00:14:16.720 --> 00:14:17.829 align:start position:0% ultimately to 9 000 over<00:14:17.040> that 00:14:17.829 --> 00:14:17.839 align:start position:0% over that 00:14:17.839 --> 00:14:20.550 align:start position:0% over that seven<00:14:18.079> year<00:14:18.320> period<00:14:18.880> so 00:14:20.550 --> 00:14:20.560 align:start position:0% seven year period so 00:14:20.560 --> 00:14:22.150 align:start position:0% seven year period so it<00:14:20.720> has<00:14:20.959> enhanced<00:14:21.440> price<00:14:21.680> responsive 00:14:22.150 --> 00:14:22.160 align:start position:0% it has enhanced price responsive 00:14:22.160 --> 00:14:24.870 align:start position:0% it has enhanced price responsive behavior<00:14:22.959> and<00:14:23.199> as<00:14:23.360> a<00:14:23.440> result<00:14:24.079> the<00:14:24.240> system<00:14:24.639> has 00:14:24.870 --> 00:14:24.880 align:start position:0% behavior and as a result the system has 00:14:24.880 --> 00:14:27.509 align:start position:0% behavior and as a result the system has been<00:14:25.040> able<00:14:25.199> to<00:14:25.360> cope<00:14:26.000> with<00:14:26.399> a<00:14:26.639> diametrically 00:14:27.509 --> 00:14:27.519 align:start position:0% been able to cope with a diametrically 00:14:27.519 --> 00:14:29.829 align:start position:0% been able to cope with a diametrically different<00:14:27.839> resource<00:14:28.399> mix<00:14:28.959> in<00:14:29.120> a<00:14:29.279> very<00:14:29.600> short 00:14:29.829 --> 00:14:29.839 align:start position:0% different resource mix in a very short 00:14:29.839 --> 00:14:31.110 align:start position:0% different resource mix in a very short amount<00:14:30.160> of<00:14:30.240> time 00:14:31.110 --> 00:14:31.120 align:start position:0% amount of time 00:14:31.120 --> 00:14:33.670 align:start position:0% amount of time and<00:14:31.360> that<00:14:31.600> resource<00:14:32.079> mix<00:14:32.480> has<00:14:32.800> become<00:14:33.199> more 00:14:33.670 --> 00:14:33.680 align:start position:0% and that resource mix has become more 00:14:33.680 --> 00:14:36.069 align:start position:0% and that resource mix has become more variable<00:14:34.560> which<00:14:34.800> you<00:14:35.040> point<00:14:35.279> out<00:14:35.440> and<00:14:35.680> ercod 00:14:36.069 --> 00:14:36.079 align:start position:0% variable which you point out and ercod 00:14:36.079 --> 00:14:37.910 align:start position:0% variable which you point out and ercod has<00:14:36.240> changed<00:14:36.480> their<00:14:36.639> procedures<00:14:37.519> added 00:14:37.910 --> 00:14:37.920 align:start position:0% has changed their procedures added 00:14:37.920 --> 00:14:39.910 align:start position:0% has changed their procedures added different<00:14:38.320> uh<00:14:38.800> functionaries<00:14:39.440> within<00:14:39.760> the 00:14:39.910 --> 00:14:39.920 align:start position:0% different uh functionaries within the 00:14:39.920 --> 00:14:41.590 align:start position:0% different uh functionaries within the ops<00:14:40.160> room<00:14:40.399> to<00:14:40.560> account<00:14:40.880> for<00:14:41.040> that<00:14:41.199> and<00:14:41.440> has 00:14:41.590 --> 00:14:41.600 align:start position:0% ops room to account for that and has 00:14:41.600 --> 00:14:44.069 align:start position:0% ops room to account for that and has done<00:14:41.760> a<00:14:42.160> an<00:14:42.399> able<00:14:42.639> job<00:14:42.959> of<00:14:43.040> it<00:14:43.199> you're<00:14:43.760> you're 00:14:44.069 --> 00:14:44.079 align:start position:0% done a an able job of it you're you're 00:14:44.079 --> 00:14:45.509 align:start position:0% done a an able job of it you're you're not<00:14:44.240> withstanding<00:14:44.720> that's<00:14:44.959> that<00:14:45.120> was 00:14:45.509 --> 00:14:45.519 align:start position:0% not withstanding that's that was 00:14:45.519 --> 00:14:47.590 align:start position:0% not withstanding that's that was 130-year<00:14:46.240> event<00:14:46.639> different 00:14:47.590 --> 00:14:47.600 align:start position:0% 130-year event different 00:14:47.600 --> 00:14:48.550 align:start position:0% 130-year event different um 00:14:48.550 --> 00:14:48.560 align:start position:0% um 00:14:48.560 --> 00:14:49.350 align:start position:0% um but 00:14:49.350 --> 00:14:49.360 align:start position:0% but 00:14:49.360 --> 00:14:51.750 align:start position:0% but we<00:14:49.519> have<00:14:49.760> adapted<00:14:50.480> uh<00:14:50.720> quite<00:14:50.959> well<00:14:51.199> and<00:14:51.519> ahead 00:14:51.750 --> 00:14:51.760 align:start position:0% we have adapted uh quite well and ahead 00:14:51.760 --> 00:14:54.150 align:start position:0% we have adapted uh quite well and ahead of<00:14:51.920> the<00:14:52.000> country<00:14:52.480> in<00:14:52.560> the<00:14:52.720> world<00:14:53.519> in<00:14:53.839> in<00:14:54.000> our 00:14:54.150 --> 00:14:54.160 align:start position:0% of the country in the world in in our 00:14:54.160 --> 00:14:56.310 align:start position:0% of the country in the world in in our ability<00:14:54.639> to<00:14:54.800> cope<00:14:55.600> we're<00:14:55.839> talking<00:14:56.079> about 00:14:56.310 --> 00:14:56.320 align:start position:0% ability to cope we're talking about 00:14:56.320 --> 00:14:57.910 align:start position:0% ability to cope we're talking about numbers<00:14:56.959> we're<00:14:57.120> not<00:14:57.279> that<00:14:57.440> far<00:14:57.680> behind 00:14:57.910 --> 00:14:57.920 align:start position:0% numbers we're not that far behind 00:14:57.920 --> 00:14:59.509 align:start position:0% numbers we're not that far behind california<00:14:58.399> and<00:14:58.480> california<00:14:58.959> is<00:14:59.040> a<00:14:59.120> burning 00:14:59.509 --> 00:14:59.519 align:start position:0% california and california is a burning 00:14:59.519 --> 00:15:01.670 align:start position:0% california and california is a burning wreck<00:14:59.760> right<00:15:00.000> now<00:15:00.480> um 00:15:01.670 --> 00:15:01.680 align:start position:0% wreck right now um 00:15:01.680 --> 00:15:03.430 align:start position:0% wreck right now um a<00:15:01.839> policy<00:15:02.399> fail 00:15:03.430 --> 00:15:03.440 align:start position:0% a policy fail 00:15:03.440 --> 00:15:05.910 align:start position:0% a policy fail and<00:15:03.920> um<00:15:04.560> and<00:15:04.880> and<00:15:04.959> then<00:15:05.279> europe<00:15:05.680> is 00:15:05.910 --> 00:15:05.920 align:start position:0% and um and and then europe is 00:15:05.920 --> 00:15:08.949 align:start position:0% and um and and then europe is experiencing<00:15:06.399> its<00:15:06.639> own<00:15:07.120> conditions<00:15:07.920> and<00:15:08.079> so 00:15:08.949 --> 00:15:08.959 align:start position:0% experiencing its own conditions and so 00:15:08.959 --> 00:15:13.110 align:start position:0% experiencing its own conditions and so that's<00:15:09.279> why<00:15:09.600> i<00:15:10.000> i<00:15:10.480> i<00:15:10.720> like<00:15:11.440> um<00:15:12.240> the<00:15:12.399> tool<00:15:12.880> that 00:15:13.110 --> 00:15:13.120 align:start position:0% that's why i i i like um the tool that 00:15:13.120 --> 00:15:15.110 align:start position:0% that's why i i i like um the tool that ordc<00:15:13.760> provides<00:15:14.320> us 00:15:15.110 --> 00:15:15.120 align:start position:0% ordc provides us 00:15:15.120 --> 00:15:17.509 align:start position:0% ordc provides us we<00:15:15.279> need<00:15:15.519> to<00:15:15.680> consider<00:15:16.560> that<00:15:16.800> tool<00:15:17.120> now<00:15:17.360> and 00:15:17.509 --> 00:15:17.519 align:start position:0% we need to consider that tool now and 00:15:17.519 --> 00:15:18.710 align:start position:0% we need to consider that tool now and the<00:15:17.600> refinements<00:15:18.079> that<00:15:18.160> we're<00:15:18.399> already 00:15:18.710 --> 00:15:18.720 align:start position:0% the refinements that we're already 00:15:18.720 --> 00:15:20.949 align:start position:0% the refinements that we're already moving<00:15:18.959> in<00:15:19.120> the<00:15:19.199> direction<00:15:19.600> of<00:15:20.320> should<00:15:20.639> help 00:15:20.949 --> 00:15:20.959 align:start position:0% moving in the direction of should help 00:15:20.959 --> 00:15:21.750 align:start position:0% moving in the direction of should help us 00:15:21.750 --> 00:15:21.760 align:start position:0% us 00:15:21.760 --> 00:15:24.230 align:start position:0% us given<00:15:22.480> the<00:15:22.639> report<00:15:23.040> that<00:15:23.519> i<00:15:23.680> filed<00:15:24.000> that<00:15:24.079> we 00:15:24.230 --> 00:15:24.240 align:start position:0% given the report that i filed that we 00:15:24.240 --> 00:15:25.670 align:start position:0% given the report that i filed that we have<00:15:24.399> all<00:15:24.560> seen<00:15:24.880> we 00:15:25.670 --> 00:15:25.680 align:start position:0% have all seen we 00:15:25.680 --> 00:15:28.870 align:start position:0% have all seen we we<00:15:25.920> all<00:15:26.240> agree<00:15:26.880> foundationally<00:15:27.760> that 00:15:28.870 --> 00:15:28.880 align:start position:0% we all agree foundationally that 00:15:28.880 --> 00:15:30.550 align:start position:0% we all agree foundationally that we<00:15:29.040> need<00:15:29.199> to<00:15:29.360> develop<00:15:29.759> tools<00:15:30.000> to<00:15:30.160> meet<00:15:30.320> that 00:15:30.550 --> 00:15:30.560 align:start position:0% we need to develop tools to meet that 00:15:30.560 --> 00:15:33.189 align:start position:0% we need to develop tools to meet that challenge<00:15:31.040> and<00:15:31.199> it<00:15:31.279> needs<00:15:31.519> to<00:15:31.600> be<00:15:31.839> soon<00:15:32.320> so<00:15:32.560> rdc 00:15:33.189 --> 00:15:33.199 align:start position:0% challenge and it needs to be soon so rdc 00:15:33.199 --> 00:15:34.949 align:start position:0% challenge and it needs to be soon so rdc theoretically<00:15:33.839> should<00:15:34.000> be<00:15:34.160> able<00:15:34.399> to<00:15:34.560> help 00:15:34.949 --> 00:15:34.959 align:start position:0% theoretically should be able to help 00:15:34.959 --> 00:15:36.629 align:start position:0% theoretically should be able to help smooth<00:15:35.360> that<00:15:35.600> out<00:15:35.839> because<00:15:36.160> people<00:15:36.320> will<00:15:36.480> see 00:15:36.629 --> 00:15:36.639 align:start position:0% smooth that out because people will see 00:15:36.639 --> 00:15:38.470 align:start position:0% smooth that out because people will see that<00:15:36.880> on<00:15:37.040> a<00:15:37.120> regular<00:15:37.519> basis 00:15:38.470 --> 00:15:38.480 align:start position:0% that on a regular basis 00:15:38.480 --> 00:15:39.749 align:start position:0% that on a regular basis and 00:15:39.749 --> 00:15:39.759 align:start position:0% and 00:15:39.759 --> 00:15:41.189 align:start position:0% and without<00:15:40.240> the 00:15:41.189 --> 00:15:41.199 align:start position:0% without the 00:15:41.199 --> 00:15:43.829 align:start position:0% without the administrative<00:15:42.480> out<00:15:42.639> of<00:15:42.720> market<00:15:43.120> action<00:15:43.600> that 00:15:43.829 --> 00:15:43.839 align:start position:0% administrative out of market action that 00:15:43.839 --> 00:15:45.749 align:start position:0% administrative out of market action that may<00:15:44.000> come<00:15:44.399> ahead<00:15:44.639> of<00:15:44.720> that 00:15:45.749 --> 00:15:45.759 align:start position:0% may come ahead of that 00:15:45.759 --> 00:15:47.509 align:start position:0% may come ahead of that it<00:15:45.920> will<00:15:46.079> incent<00:15:46.399> price<00:15:46.639> responsive<00:15:47.120> behavior 00:15:47.509 --> 00:15:47.519 align:start position:0% it will incent price responsive behavior 00:15:47.519 --> 00:15:49.269 align:start position:0% it will incent price responsive behavior on<00:15:47.600> a<00:15:47.680> regular<00:15:48.000> basis<00:15:48.480> when<00:15:48.639> you<00:15:48.800> say<00:15:49.040> price 00:15:49.269 --> 00:15:49.279 align:start position:0% on a regular basis when you say price 00:15:49.279 --> 00:15:51.990 align:start position:0% on a regular basis when you say price responsive<00:15:49.759> behavior<00:15:50.480> or<00:15:50.720> you 00:15:51.990 --> 00:15:52.000 align:start position:0% responsive behavior or you 00:15:52.000 --> 00:15:53.590 align:start position:0% responsive behavior or you change<00:15:52.320> behavior 00:15:53.590 --> 00:15:53.600 align:start position:0% change behavior 00:15:53.600 --> 00:15:55.350 align:start position:0% change behavior i<00:15:53.680> think<00:15:53.920> you're<00:15:54.079> talking<00:15:54.399> about 00:15:55.350 --> 00:15:55.360 align:start position:0% i think you're talking about 00:15:55.360 --> 00:15:57.189 align:start position:0% i think you're talking about demand<00:15:55.680> response 00:15:57.189 --> 00:15:57.199 align:start position:0% demand response 00:15:57.199 --> 00:15:58.870 align:start position:0% demand response and 00:15:58.870 --> 00:15:58.880 align:start position:0% and 00:15:58.880 --> 00:16:00.629 align:start position:0% and financial<00:15:59.440> economic<00:15:59.920> incentive<00:16:00.320> for<00:16:00.480> high 00:16:00.629 --> 00:16:00.639 align:start position:0% financial economic incentive for high 00:16:00.639 --> 00:16:02.550 align:start position:0% financial economic incentive for high heat<00:16:00.880> rate<00:16:01.120> units<00:16:01.440> to<00:16:01.519> come<00:16:01.759> on<00:16:02.160> sooner<00:16:02.399> than 00:16:02.550 --> 00:16:02.560 align:start position:0% heat rate units to come on sooner than 00:16:02.560 --> 00:16:04.150 align:start position:0% heat rate units to come on sooner than they<00:16:02.639> otherwise<00:16:02.959> would<00:16:03.120> have<00:16:03.360> yes<00:16:03.600> sir<00:16:03.839> and 00:16:04.150 --> 00:16:04.160 align:start position:0% they otherwise would have yes sir and 00:16:04.160 --> 00:16:06.310 align:start position:0% they otherwise would have yes sir and loading<00:16:04.720> and<00:16:04.880> load<00:16:05.120> resources<00:16:05.759> turning<00:16:06.079> off 00:16:06.310 --> 00:16:06.320 align:start position:0% loading and load resources turning off 00:16:06.320 --> 00:16:09.430 align:start position:0% loading and load resources turning off turning<00:16:06.639> down<00:16:07.279> throttling<00:16:07.839> down 00:16:09.430 --> 00:16:09.440 align:start position:0% turning down throttling down 00:16:09.440 --> 00:16:11.430 align:start position:0% turning down throttling down demand<00:16:09.680> response<00:16:10.240> yeah<00:16:10.480> and<00:16:10.880> not<00:16:11.040> just<00:16:11.199> but 00:16:11.430 --> 00:16:11.440 align:start position:0% demand response yeah and not just but 00:16:11.440 --> 00:16:12.870 align:start position:0% demand response yeah and not just but not<00:16:11.680> new<00:16:11.839> investment<00:16:12.320> you're<00:16:12.480> not<00:16:12.639> including 00:16:12.870 --> 00:16:12.880 align:start position:0% not new investment you're not including 00:16:12.880 --> 00:16:15.749 align:start position:0% not new investment you're not including new<00:16:13.040> investments<00:16:13.920> no<00:16:14.160> foundational<00:16:15.120> gossip 00:16:15.749 --> 00:16:15.759 align:start position:0% new investments no foundational gossip 00:16:15.759 --> 00:16:17.430 align:start position:0% new investments no foundational gossip no<00:16:16.160> just<00:16:16.399> just<00:16:16.639> trying<00:16:16.800> to<00:16:16.880> smooth<00:16:17.199> out<00:16:17.360> the 00:16:17.430 --> 00:16:17.440 align:start position:0% no just just trying to smooth out the 00:16:17.440 --> 00:16:19.590 align:start position:0% no just just trying to smooth out the immediate<00:16:17.920> near-term<00:16:18.720> uh<00:16:18.959> reliability 00:16:19.590 --> 00:16:19.600 align:start position:0% immediate near-term uh reliability 00:16:19.600 --> 00:16:22.550 align:start position:0% immediate near-term uh reliability impacts<00:16:20.079> but<00:16:20.560> ordc<00:16:21.199> is<00:16:21.279> a<00:16:21.360> great<00:16:21.600> tool<00:16:21.920> to 00:16:22.550 --> 00:16:22.560 align:start position:0% impacts but ordc is a great tool to 00:16:22.560 --> 00:16:23.990 align:start position:0% impacts but ordc is a great tool to translate<00:16:23.199> down 00:16:23.990 --> 00:16:24.000 align:start position:0% translate down 00:16:24.000 --> 00:16:24.710 align:start position:0% translate down to 00:16:24.710 --> 00:16:24.720 align:start position:0% to 00:16:24.720 --> 00:16:27.509 align:start position:0% to small<00:16:25.120> c<00:16:25.600> look<00:16:26.320> industrials<00:16:26.959> katie's<00:16:27.360> in<00:16:27.440> the 00:16:27.509 --> 00:16:27.519 align:start position:0% small c look industrials katie's in the 00:16:27.519 --> 00:16:28.870 align:start position:0% small c look industrials katie's in the room<00:16:27.759> her<00:16:28.000> crews<00:16:28.240> in<00:16:28.320> the<00:16:28.399> room<00:16:28.639> they're<00:16:28.800> going 00:16:28.870 --> 00:16:28.880 align:start position:0% room her crews in the room they're going 00:16:28.880 --> 00:16:29.990 align:start position:0% room her crews in the room they're going to<00:16:28.959> do<00:16:29.120> what<00:16:29.279> they're<00:16:29.440> going<00:16:29.600> to<00:16:29.680> do<00:16:29.920> and 00:16:29.990 --> 00:16:30.000 align:start position:0% to do what they're going to do and 00:16:30.000 --> 00:16:31.829 align:start position:0% to do what they're going to do and they're<00:16:30.160> going<00:16:30.240> to<00:16:30.320> do<00:16:30.480> it<00:16:30.560> in<00:16:30.639> a<00:16:30.720> big<00:16:30.959> way 00:16:31.829 --> 00:16:31.839 align:start position:0% they're going to do it in a big way 00:16:31.839 --> 00:16:32.710 align:start position:0% they're going to do it in a big way but 00:16:32.710 --> 00:16:32.720 align:start position:0% but 00:16:32.720 --> 00:16:35.030 align:start position:0% but we<00:16:32.959> need<00:16:33.199> the<00:16:33.360> buckies<00:16:33.839> of<00:16:34.000> the<00:16:34.079> world<00:16:34.480> we<00:16:34.720> need 00:16:35.030 --> 00:16:35.040 align:start position:0% we need the buckies of the world we need 00:16:35.040 --> 00:16:38.389 align:start position:0% we need the buckies of the world we need the the<00:16:35.680> hebs<00:16:36.399> of<00:16:36.560> the<00:16:36.639> world<00:16:37.120> we<00:16:37.360> need<00:16:37.680> those 00:16:38.389 --> 00:16:38.399 align:start position:0% the the hebs of the world we need those 00:16:38.399 --> 00:16:41.030 align:start position:0% the the hebs of the world we need those uh<00:16:38.639> mid-size<00:16:39.360> and<00:16:39.519> small<00:16:39.839> commercial<00:16:40.560> actors 00:16:41.030 --> 00:16:41.040 align:start position:0% uh mid-size and small commercial actors 00:16:41.040 --> 00:16:42.629 align:start position:0% uh mid-size and small commercial actors to<00:16:41.199> say<00:16:41.440> hey<00:16:41.759> i'm<00:16:41.839> going<00:16:42.000> to<00:16:42.079> manage<00:16:42.480> my 00:16:42.629 --> 00:16:42.639 align:start position:0% to say hey i'm going to manage my 00:16:42.639 --> 00:16:44.069 align:start position:0% to say hey i'm going to manage my freezers<00:16:43.199> better 00:16:44.069 --> 00:16:44.079 align:start position:0% freezers better 00:16:44.079 --> 00:16:46.550 align:start position:0% freezers better to<00:16:44.240> conserve<00:16:44.720> energy<00:16:45.279> specifically<00:16:46.000> from<00:16:46.240> 5 00:16:46.550 --> 00:16:46.560 align:start position:0% to conserve energy specifically from 5 00:16:46.560 --> 00:16:48.470 align:start position:0% to conserve energy specifically from 5 to<00:16:46.720> 7<00:16:46.959> pm<00:16:47.360> because<00:16:47.600> i'm<00:16:47.680> going<00:16:47.759> to<00:16:48.000> get<00:16:48.160> dinged 00:16:48.470 --> 00:16:48.480 align:start position:0% to 7 pm because i'm going to get dinged 00:16:48.480 --> 00:16:51.030 align:start position:0% to 7 pm because i'm going to get dinged with<00:16:48.639> a<00:16:48.720> lot<00:16:48.880> of<00:16:48.959> high<00:16:49.199> prices<00:16:50.160> ordc<00:16:50.880> is<00:16:50.959> a 00:16:51.030 --> 00:16:51.040 align:start position:0% with a lot of high prices ordc is a 00:16:51.040 --> 00:16:54.310 align:start position:0% with a lot of high prices ordc is a mechanism<00:16:51.920> that<00:16:52.079> will<00:16:52.160> help<00:16:52.399> incent<00:16:52.800> that 00:16:54.310 --> 00:16:54.320 align:start position:0% mechanism that will help incent that 00:16:54.320 --> 00:16:56.389 align:start position:0% mechanism that will help incent that sure<00:16:54.880> and<00:16:55.040> i<00:16:55.120> certainly<00:16:55.759> i<00:16:55.920> mean<00:16:56.079> i<00:16:56.160> agree<00:16:56.320> with 00:16:56.389 --> 00:16:56.399 align:start position:0% sure and i certainly i mean i agree with 00:16:56.399 --> 00:16:58.550 align:start position:0% sure and i certainly i mean i agree with you<00:16:56.560> jimmy<00:16:56.959> there's<00:16:57.519> zero<00:16:57.920> evidence<00:16:58.240> that<00:16:58.480> it 00:16:58.550 --> 00:16:58.560 align:start position:0% you jimmy there's zero evidence that it 00:16:58.560 --> 00:17:00.629 align:start position:0% you jimmy there's zero evidence that it drives<00:16:58.880> new<00:16:59.120> investment<00:16:59.759> and<00:17:00.160> like<00:17:00.399> i<00:17:00.480> said 00:17:00.629 --> 00:17:00.639 align:start position:0% drives new investment and like i said 00:17:00.639 --> 00:17:02.069 align:start position:0% drives new investment and like i said before<00:17:00.959> i<00:17:01.040> think<00:17:01.199> it's<00:17:01.360> a 00:17:02.069 --> 00:17:02.079 align:start position:0% before i think it's a 00:17:02.079 --> 00:17:04.630 align:start position:0% before i think it's a it<00:17:02.320> helps<00:17:02.839> retain 00:17:04.630 --> 00:17:04.640 align:start position:0% it helps retain 00:17:04.640 --> 00:17:06.789 align:start position:0% it helps retain existing<00:17:05.120> units 00:17:06.789 --> 00:17:06.799 align:start position:0% existing units 00:17:06.799 --> 00:17:08.309 align:start position:0% existing units and<00:17:07.039> justify 00:17:08.309 --> 00:17:08.319 align:start position:0% and justify 00:17:08.319 --> 00:17:09.990 align:start position:0% and justify delaying<00:17:08.799> retirements 00:17:09.990 --> 00:17:10.000 align:start position:0% delaying retirements 00:17:10.000 --> 00:17:12.150 align:start position:0% delaying retirements uh<00:17:10.240> but<00:17:10.480> it's<00:17:10.959> certainly 00:17:12.150 --> 00:17:12.160 align:start position:0% uh but it's certainly 00:17:12.160 --> 00:17:13.429 align:start position:0% uh but it's certainly apparent<00:17:12.480> that<00:17:12.640> it's<00:17:12.799> nothing<00:17:13.120> anybody's 00:17:13.429 --> 00:17:13.439 align:start position:0% apparent that it's nothing anybody's 00:17:13.439 --> 00:17:14.710 align:start position:0% apparent that it's nothing anybody's going<00:17:13.600> to<00:17:13.679> build<00:17:13.919> a 00:17:14.710 --> 00:17:14.720 align:start position:0% going to build a 00:17:14.720 --> 00:17:16.549 align:start position:0% going to build a business<00:17:15.039> model<00:17:15.360> on<00:17:15.520> or<00:17:15.600> a<00:17:15.679> new<00:17:16.400> new 00:17:16.549 --> 00:17:16.559 align:start position:0% business model on or a new new 00:17:16.559 --> 00:17:17.829 align:start position:0% business model on or a new new infrastructure<00:17:17.120> and<00:17:17.199> i<00:17:17.280> would<00:17:17.439> say<00:17:17.600> it's<00:17:17.679> not 00:17:17.829 --> 00:17:17.839 align:start position:0% infrastructure and i would say it's not 00:17:17.839 --> 00:17:19.990 align:start position:0% infrastructure and i would say it's not the<00:17:18.000> only<00:17:18.160> tool<00:17:18.480> in<00:17:18.559> the<00:17:18.640> toolbox<00:17:19.199> to 00:17:19.990 --> 00:17:20.000 align:start position:0% the only tool in the toolbox to 00:17:20.000 --> 00:17:22.949 align:start position:0% the only tool in the toolbox to uh<00:17:20.319> push<00:17:20.640> off<00:17:20.799> retirements<00:17:21.520> or<00:17:21.760> to<00:17:22.000> keep 00:17:22.949 --> 00:17:22.959 align:start position:0% uh push off retirements or to keep 00:17:22.959 --> 00:17:24.870 align:start position:0% uh push off retirements or to keep plants<00:17:23.280> on<00:17:23.360> the<00:17:23.520> system<00:17:24.079> older<00:17:24.400> plants<00:17:24.640> on<00:17:24.799> the 00:17:24.870 --> 00:17:24.880 align:start position:0% plants on the system older plants on the 00:17:24.880 --> 00:17:26.150 align:start position:0% plants on the system older plants on the system<00:17:25.439> so 00:17:26.150 --> 00:17:26.160 align:start position:0% system so 00:17:26.160 --> 00:17:27.829 align:start position:0% system so along<00:17:26.400> those<00:17:26.559> lines<00:17:26.799> are<00:17:26.880> you<00:17:26.959> thinking<00:17:27.280> which 00:17:27.829 --> 00:17:27.839 align:start position:0% along those lines are you thinking which 00:17:27.839 --> 00:17:29.350 align:start position:0% along those lines are you thinking which we<00:17:28.000> know<00:17:28.160> it<00:17:28.240> doesn't<00:17:28.559> drive<00:17:28.720> new<00:17:29.200> new 00:17:29.350 --> 00:17:29.360 align:start position:0% we know it doesn't drive new new 00:17:29.360 --> 00:17:31.270 align:start position:0% we know it doesn't drive new new investment<00:17:29.760> new<00:17:30.000> steel<00:17:30.160> in<00:17:30.240> the<00:17:30.320> ground 00:17:31.270 --> 00:17:31.280 align:start position:0% investment new steel in the ground 00:17:31.280 --> 00:17:33.590 align:start position:0% investment new steel in the ground is<00:17:31.440> it<00:17:31.919> does<00:17:32.160> that<00:17:32.240> mean<00:17:32.880> we<00:17:33.039> shouldn't<00:17:33.280> change 00:17:33.590 --> 00:17:33.600 align:start position:0% is it does that mean we shouldn't change 00:17:33.600 --> 00:17:35.590 align:start position:0% is it does that mean we shouldn't change it<00:17:33.840> or<00:17:34.320> it's<00:17:34.559> worth<00:17:34.799> changing<00:17:35.039> for<00:17:35.280> the<00:17:35.440> sake 00:17:35.590 --> 00:17:35.600 align:start position:0% it or it's worth changing for the sake 00:17:35.600 --> 00:17:37.590 align:start position:0% it or it's worth changing for the sake of<00:17:35.760> mitigating<00:17:36.240> retirements<00:17:36.799> no<00:17:37.280> well<00:17:37.520> i 00:17:37.590 --> 00:17:37.600 align:start position:0% of mitigating retirements no well i 00:17:37.600 --> 00:17:39.750 align:start position:0% of mitigating retirements no well i think<00:17:38.000> both<00:17:38.320> need<00:17:38.480> to<00:17:38.559> be<00:17:38.640> looked<00:17:38.880> at<00:17:39.120> and<00:17:39.520> and 00:17:39.750 --> 00:17:39.760 align:start position:0% think both need to be looked at and and 00:17:39.760 --> 00:17:41.430 align:start position:0% think both need to be looked at and and i<00:17:39.840> think<00:17:40.000> the<00:17:40.160> numbers<00:17:40.559> will<00:17:40.720> tell<00:17:40.880> the<00:17:41.039> story 00:17:41.430 --> 00:17:41.440 align:start position:0% i think the numbers will tell the story 00:17:41.440 --> 00:17:42.950 align:start position:0% i think the numbers will tell the story and<00:17:41.520> hopefully<00:17:42.240> they<00:17:42.400> will<00:17:42.559> drive<00:17:42.880> the 00:17:42.950 --> 00:17:42.960 align:start position:0% and hopefully they will drive the 00:17:42.960 --> 00:17:44.549 align:start position:0% and hopefully they will drive the decision-making 00:17:44.549 --> 00:17:44.559 align:start position:0% decision-making 00:17:44.559 --> 00:17:46.470 align:start position:0% decision-making obviously<00:17:45.120> outputs<00:17:45.440> are<00:17:45.520> driven<00:17:45.760> by<00:17:46.000> inputs 00:17:46.470 --> 00:17:46.480 align:start position:0% obviously outputs are driven by inputs 00:17:46.480 --> 00:17:49.029 align:start position:0% obviously outputs are driven by inputs but<00:17:46.960> um<00:17:47.440> we<00:17:47.600> have<00:17:47.760> a<00:17:47.840> lot<00:17:48.000> of 00:17:49.029 --> 00:17:49.039 align:start position:0% but um we have a lot of 00:17:49.039 --> 00:17:50.870 align:start position:0% but um we have a lot of we've<00:17:49.200> got<00:17:49.280> a<00:17:49.360> lot<00:17:49.520> of<00:17:49.600> expertise<00:17:50.160> in<00:17:50.240> the<00:17:50.400> room 00:17:50.870 --> 00:17:50.880 align:start position:0% we've got a lot of expertise in the room 00:17:50.880 --> 00:17:52.710 align:start position:0% we've got a lot of expertise in the room we<00:17:51.039> haven't<00:17:51.280> seen<00:17:51.520> brattle's 00:17:52.710 --> 00:17:52.720 align:start position:0% we haven't seen brattle's 00:17:52.720 --> 00:17:54.070 align:start position:0% we haven't seen brattle's responses 00:17:54.070 --> 00:17:54.080 align:start position:0% responses 00:17:54.080 --> 00:17:55.909 align:start position:0% responses i've<00:17:54.240> seen<00:17:54.480> some<00:17:54.720> responses 00:17:55.909 --> 00:17:55.919 align:start position:0% i've seen some responses 00:17:55.919 --> 00:17:58.830 align:start position:0% i've seen some responses to<00:17:56.160> a<00:17:56.240> couple<00:17:56.480> scenarios<00:17:57.120> that<00:17:57.280> i<00:17:57.440> asked 00:17:58.830 --> 00:17:58.840 align:start position:0% to a couple scenarios that i asked 00:17:58.840 --> 00:18:02.070 align:start position:0% to a couple scenarios that i asked um<00:17:59.840> potomac<00:18:00.400> to<00:18:00.559> do<00:18:01.200> um<00:18:01.600> and<00:18:01.679> they're<00:18:01.840> kind<00:18:02.000> of 00:18:02.070 --> 00:18:02.080 align:start position:0% um potomac to do um and they're kind of 00:18:02.080 --> 00:18:03.990 align:start position:0% um potomac to do um and they're kind of all<00:18:02.240> over<00:18:02.400> the<00:18:02.480> place<00:18:02.720> and<00:18:02.880> i<00:18:02.960> think<00:18:03.360> you<00:18:03.520> know 00:18:03.990 --> 00:18:04.000 align:start position:0% all over the place and i think you know 00:18:04.000 --> 00:18:06.390 align:start position:0% all over the place and i think you know it<00:18:04.160> behooves<00:18:04.720> us<00:18:04.880> to<00:18:05.280> to<00:18:05.440> take<00:18:05.679> a 00:18:06.390 --> 00:18:06.400 align:start position:0% it behooves us to to take a 00:18:06.400 --> 00:18:07.430 align:start position:0% it behooves us to to take a this 00:18:07.430 --> 00:18:07.440 align:start position:0% this 00:18:07.440 --> 00:18:10.789 align:start position:0% this um<00:18:08.240> you<00:18:08.320> know<00:18:08.559> all-encompassing<00:18:09.440> look<00:18:09.919> so<00:18:10.480> so 00:18:10.789 --> 00:18:10.799 align:start position:0% um you know all-encompassing look so so 00:18:10.799 --> 00:18:13.110 align:start position:0% um you know all-encompassing look so so what<00:18:11.039> i'm<00:18:11.200> saying<00:18:11.520> is<00:18:11.840> um<00:18:12.320> yes<00:18:12.640> i<00:18:12.799> you<00:18:12.880> know<00:18:13.039> i 00:18:13.110 --> 00:18:13.120 align:start position:0% what i'm saying is um yes i you know i 00:18:13.120 --> 00:18:14.630 align:start position:0% what i'm saying is um yes i you know i think<00:18:13.360> it<00:18:13.520> absolutely<00:18:14.000> is<00:18:14.160> a<00:18:14.240> tool<00:18:14.480> that<00:18:14.559> we 00:18:14.630 --> 00:18:14.640 align:start position:0% think it absolutely is a tool that we 00:18:14.640 --> 00:18:17.590 align:start position:0% think it absolutely is a tool that we should<00:18:14.799> work<00:18:15.039> on<00:18:15.600> it<00:18:15.919> can<00:18:16.160> be<00:18:16.320> improved<00:18:17.120> um<00:18:17.360> but 00:18:17.590 --> 00:18:17.600 align:start position:0% should work on it can be improved um but 00:18:17.600 --> 00:18:19.110 align:start position:0% should work on it can be improved um but let's<00:18:17.840> not<00:18:18.000> go<00:18:18.240> in<00:18:18.400> thinking<00:18:18.640> that<00:18:18.880> it's<00:18:19.039> going 00:18:19.110 --> 00:18:19.120 align:start position:0% let's not go in thinking that it's going 00:18:19.120 --> 00:18:21.110 align:start position:0% let's not go in thinking that it's going to<00:18:19.200> be<00:18:19.360> the<00:18:19.520> driver<00:18:19.919> for<00:18:20.480> new<00:18:20.720> steel<00:18:20.960> in<00:18:21.039> the 00:18:21.110 --> 00:18:21.120 align:start position:0% to be the driver for new steel in the 00:18:21.120 --> 00:18:22.870 align:start position:0% to be the driver for new steel in the ground<00:18:21.440> all<00:18:21.600> across<00:18:21.919> the<00:18:22.080> state<00:18:22.400> because<00:18:22.799> it's 00:18:22.870 --> 00:18:22.880 align:start position:0% ground all across the state because it's 00:18:22.880 --> 00:18:24.470 align:start position:0% ground all across the state because it's a<00:18:22.960> thing<00:18:23.280> you<00:18:23.360> know<00:18:23.679> history<00:18:24.080> shows<00:18:24.400> it 00:18:24.470 --> 00:18:24.480 align:start position:0% a thing you know history shows it 00:18:24.480 --> 00:18:25.750 align:start position:0% a thing you know history shows it doesn't 00:18:25.750 --> 00:18:25.760 align:start position:0% doesn't 00:18:25.760 --> 00:18:27.190 align:start position:0% doesn't i<00:18:26.080> agree<00:18:26.400> with<00:18:26.559> all<00:18:26.640> the<00:18:26.799> points<00:18:27.039> that<00:18:27.120> have 00:18:27.190 --> 00:18:27.200 align:start position:0% i agree with all the points that have 00:18:27.200 --> 00:18:29.990 align:start position:0% i agree with all the points that have been<00:18:27.360> made<00:18:27.600> i<00:18:27.919> think<00:18:28.480> ordc 00:18:29.990 --> 00:18:30.000 align:start position:0% been made i think ordc 00:18:30.000 --> 00:18:31.750 align:start position:0% been made i think ordc has<00:18:30.480> um 00:18:31.750 --> 00:18:31.760 align:start position:0% has um 00:18:31.760 --> 00:18:33.590 align:start position:0% has um you<00:18:31.840> know<00:18:32.000> it<00:18:32.400> is<00:18:32.480> a<00:18:32.559> tool<00:18:32.880> to<00:18:32.960> drive<00:18:33.280> demand 00:18:33.590 --> 00:18:33.600 align:start position:0% you know it is a tool to drive demand 00:18:33.600 --> 00:18:34.789 align:start position:0% you know it is a tool to drive demand response 00:18:34.789 --> 00:18:34.799 align:start position:0% response 00:18:34.799 --> 00:18:36.870 align:start position:0% response responsive<00:18:35.360> behavior<00:18:35.919> and<00:18:36.240> and<00:18:36.400> get<00:18:36.640> more 00:18:36.870 --> 00:18:36.880 align:start position:0% responsive behavior and and get more 00:18:36.880 --> 00:18:38.950 align:start position:0% responsive behavior and and get more generation<00:18:37.520> online 00:18:38.950 --> 00:18:38.960 align:start position:0% generation online 00:18:38.960 --> 00:18:41.270 align:start position:0% generation online and<00:18:39.120> it<00:18:39.679> it<00:18:40.080> will<00:18:40.240> continue<00:18:40.559> to<00:18:40.720> be<00:18:40.799> helpful<00:18:41.200> in 00:18:41.270 --> 00:18:41.280 align:start position:0% and it it will continue to be helpful in 00:18:41.280 --> 00:18:42.950 align:start position:0% and it it will continue to be helpful in that<00:18:41.440> respect 00:18:42.950 --> 00:18:42.960 align:start position:0% that respect 00:18:42.960 --> 00:18:44.710 align:start position:0% that respect i<00:18:43.280> think<00:18:43.520> that 00:18:44.710 --> 00:18:44.720 align:start position:0% i think that 00:18:44.720 --> 00:18:46.390 align:start position:0% i think that you<00:18:44.799> know<00:18:44.960> by<00:18:45.120> moving<00:18:45.360> it<00:18:45.520> out<00:18:45.600> of<00:18:45.679> scarcity 00:18:46.390 --> 00:18:46.400 align:start position:0% you know by moving it out of scarcity 00:18:46.400 --> 00:18:48.470 align:start position:0% you know by moving it out of scarcity it'll<00:18:46.559> be<00:18:46.720> an<00:18:46.960> even<00:18:47.200> more<00:18:47.520> valuable<00:18:48.000> tool<00:18:48.400> you 00:18:48.470 --> 00:18:48.480 align:start position:0% it'll be an even more valuable tool you 00:18:48.480 --> 00:18:51.430 align:start position:0% it'll be an even more valuable tool you know<00:18:48.640> to<00:18:48.799> even<00:18:49.039> arrive<00:18:49.440> at<00:18:49.520> the<00:18:49.600> 2000 00:18:51.430 --> 00:18:51.440 align:start position:0% know to even arrive at the 2000 00:18:51.440 --> 00:18:53.190 align:start position:0% know to even arrive at the 2000 minimum<00:18:51.760> contingency<00:18:52.400> level<00:18:52.880> was 00:18:53.190 --> 00:18:53.200 align:start position:0% minimum contingency level was 00:18:53.200 --> 00:18:55.510 align:start position:0% minimum contingency level was controversial<00:18:54.320> moving<00:18:54.640> it<00:18:54.799> all<00:18:54.880> the<00:18:54.960> way<00:18:55.360> out 00:18:55.510 --> 00:18:55.520 align:start position:0% controversial moving it all the way out 00:18:55.520 --> 00:18:57.990 align:start position:0% controversial moving it all the way out of<00:18:55.600> that<00:18:56.000> um<00:18:56.640> emergency<00:18:57.200> event<00:18:57.520> status<00:18:57.919> i 00:18:57.990 --> 00:18:58.000 align:start position:0% of that um emergency event status i 00:18:58.000 --> 00:18:59.590 align:start position:0% of that um emergency event status i think<00:18:58.160> will<00:18:58.320> provide 00:18:59.590 --> 00:18:59.600 align:start position:0% think will provide 00:18:59.600 --> 00:19:02.310 align:start position:0% think will provide more<00:18:59.840> reliability<00:19:00.559> benefits<00:19:01.280> in<00:19:01.440> the<00:19:01.520> future 00:19:02.310 --> 00:19:02.320 align:start position:0% more reliability benefits in the future 00:19:02.320 --> 00:19:03.190 align:start position:0% more reliability benefits in the future well<00:19:02.559> it 00:19:03.190 --> 00:19:03.200 align:start position:0% well it 00:19:03.200 --> 00:19:05.110 align:start position:0% well it whether<00:19:03.520> it<00:19:03.600> will<00:19:03.760> drive<00:19:04.400> new<00:19:04.640> still<00:19:04.880> in<00:19:05.039> the 00:19:05.110 --> 00:19:05.120 align:start position:0% whether it will drive new still in the 00:19:05.120 --> 00:19:07.029 align:start position:0% whether it will drive new still in the ground<00:19:05.360> that<00:19:05.520> that's<00:19:05.919> you<00:19:06.080> know 00:19:07.029 --> 00:19:07.039 align:start position:0% ground that that's you know 00:19:07.039 --> 00:19:08.789 align:start position:0% ground that that's you know the<00:19:07.200> past<00:19:07.520> hasn't<00:19:07.840> indicated<00:19:08.400> that<00:19:08.559> there's 00:19:08.789 --> 00:19:08.799 align:start position:0% the past hasn't indicated that there's 00:19:08.799 --> 00:19:11.350 align:start position:0% the past hasn't indicated that there's been<00:19:08.960> a<00:19:09.039> whole<00:19:09.200> lot<00:19:09.440> of<00:19:10.000> investment<00:19:10.559> made<00:19:11.120> as<00:19:11.280> a 00:19:11.350 --> 00:19:11.360 align:start position:0% been a whole lot of investment made as a 00:19:11.360 --> 00:19:13.590 align:start position:0% been a whole lot of investment made as a result<00:19:11.760> of<00:19:11.840> changes<00:19:12.160> to<00:19:12.320> the<00:19:12.480> ordc 00:19:13.590 --> 00:19:13.600 align:start position:0% result of changes to the ordc 00:19:13.600 --> 00:19:14.710 align:start position:0% result of changes to the ordc but 00:19:14.710 --> 00:19:14.720 align:start position:0% but 00:19:14.720 --> 00:19:16.390 align:start position:0% but chairman<00:19:15.039> you've<00:19:15.120> made<00:19:15.280> a<00:19:15.440> great<00:19:15.600> point<00:19:15.919> it<00:19:16.240> is 00:19:16.390 --> 00:19:16.400 align:start position:0% chairman you've made a great point it is 00:19:16.400 --> 00:19:18.950 align:start position:0% chairman you've made a great point it is important<00:19:16.799> to<00:19:16.960> continue<00:19:17.440> to<00:19:17.600> provide<00:19:18.480> revenue 00:19:18.950 --> 00:19:18.960 align:start position:0% important to continue to provide revenue 00:19:18.960 --> 00:19:21.270 align:start position:0% important to continue to provide revenue to<00:19:19.120> existing<00:19:19.600> generation<00:19:20.480> and 00:19:21.270 --> 00:19:21.280 align:start position:0% to existing generation and 00:19:21.280 --> 00:19:23.430 align:start position:0% to existing generation and demand<00:19:21.679> responsive 00:19:23.430 --> 00:19:23.440 align:start position:0% demand responsive 00:19:23.440 --> 00:19:26.390 align:start position:0% demand responsive investment<00:19:24.080> or<00:19:24.559> a<00:19:24.720> response<00:19:25.200> period 00:19:26.390 --> 00:19:26.400 align:start position:0% investment or a response period 00:19:26.400 --> 00:19:28.710 align:start position:0% investment or a response period and<00:19:26.640> i<00:19:26.960> think<00:19:27.120> we<00:19:27.440> we<00:19:27.679> have<00:19:27.840> to<00:19:28.400> make<00:19:28.559> some 00:19:28.710 --> 00:19:28.720 align:start position:0% and i think we we have to make some 00:19:28.720 --> 00:19:30.710 align:start position:0% and i think we we have to make some modifications<00:19:29.760> because<00:19:30.160> we<00:19:30.320> lowered<00:19:30.640> the 00:19:30.710 --> 00:19:30.720 align:start position:0% modifications because we lowered the 00:19:30.720 --> 00:19:32.150 align:start position:0% modifications because we lowered the price<00:19:30.960> cap<00:19:31.280> and<00:19:31.360> we<00:19:31.520> took<00:19:31.679> money<00:19:31.919> out<00:19:32.000> of<00:19:32.080> the 00:19:32.150 --> 00:19:32.160 align:start position:0% price cap and we took money out of the 00:19:32.160 --> 00:19:34.070 align:start position:0% price cap and we took money out of the market<00:19:32.559> so<00:19:32.720> we<00:19:32.799> need<00:19:33.039> to<00:19:33.200> we<00:19:33.360> need<00:19:33.520> to<00:19:33.840> bring 00:19:34.070 --> 00:19:34.080 align:start position:0% market so we need to we need to bring 00:19:34.080 --> 00:19:35.110 align:start position:0% market so we need to we need to bring that 00:19:35.110 --> 00:19:35.120 align:start position:0% that 00:19:35.120 --> 00:19:37.990 align:start position:0% that to<00:19:35.280> pair<00:19:36.000> and<00:19:36.160> i<00:19:36.240> continue<00:19:36.799> to<00:19:37.360> just<00:19:37.600> stress 00:19:37.990 --> 00:19:38.000 align:start position:0% to pair and i continue to just stress 00:19:38.000 --> 00:19:39.830 align:start position:0% to pair and i continue to just stress that<00:19:38.160> i<00:19:38.320> think<00:19:38.559> that<00:19:38.880> um<00:19:39.280> while<00:19:39.440> we<00:19:39.600> want<00:19:39.760> to 00:19:39.830 --> 00:19:39.840 align:start position:0% that i think that um while we want to 00:19:39.840 --> 00:19:41.669 align:start position:0% that i think that um while we want to take<00:19:40.000> a<00:19:40.080> very<00:19:40.640> deliberate<00:19:41.120> and<00:19:41.200> thoughtful 00:19:41.669 --> 00:19:41.679 align:start position:0% take a very deliberate and thoughtful 00:19:41.679 --> 00:19:44.549 align:start position:0% take a very deliberate and thoughtful approach<00:19:42.080> to<00:19:42.240> adjusting<00:19:42.640> the<00:19:42.799> ordc 00:19:44.549 --> 00:19:44.559 align:start position:0% approach to adjusting the ordc 00:19:44.559 --> 00:19:46.390 align:start position:0% approach to adjusting the ordc i<00:19:44.960> we<00:19:45.120> need<00:19:45.280> to<00:19:45.360> get<00:19:45.520> it<00:19:45.600> in<00:19:45.760> place<00:19:46.000> by<00:19:46.160> early 00:19:46.390 --> 00:19:46.400 align:start position:0% i we need to get it in place by early 00:19:46.400 --> 00:19:48.310 align:start position:0% i we need to get it in place by early january<00:19:46.960> i<00:19:47.039> think<00:19:47.200> that<00:19:47.440> that<00:19:47.679> is<00:19:47.760> one<00:19:48.000> tool 00:19:48.310 --> 00:19:48.320 align:start position:0% january i think that that is one tool 00:19:48.320 --> 00:19:49.909 align:start position:0% january i think that that is one tool that<00:19:48.480> we<00:19:48.640> need<00:19:48.799> to<00:19:48.880> add<00:19:49.039> to<00:19:49.200> our<00:19:49.360> arsenal<00:19:49.760> for 00:19:49.909 --> 00:19:49.919 align:start position:0% that we need to add to our arsenal for 00:19:49.919 --> 00:19:52.150 align:start position:0% that we need to add to our arsenal for this<00:19:50.160> winter<00:19:50.640> and<00:19:50.960> to<00:19:51.120> add<00:19:51.360> it<00:19:51.440> early<00:19:51.760> and<00:19:52.000> as 00:19:52.150 --> 00:19:52.160 align:start position:0% this winter and to add it early and as 00:19:52.160 --> 00:19:53.830 align:start position:0% this winter and to add it early and as early<00:19:52.400> in<00:19:52.480> the<00:19:52.559> winter<00:19:52.880> as<00:19:52.960> we<00:19:53.120> can 00:19:53.830 --> 00:19:53.840 align:start position:0% early in the winter as we can 00:19:53.840 --> 00:19:57.750 align:start position:0% early in the winter as we can okay<00:19:54.240> so<00:19:54.480> so<00:19:54.880> one<00:19:55.120> point<00:19:55.760> um<00:19:56.240> we<00:19:56.559> we<00:19:56.799> are<00:19:57.440> saying 00:19:57.750 --> 00:19:57.760 align:start position:0% okay so so one point um we we are saying 00:19:57.760 --> 00:20:00.789 align:start position:0% okay so so one point um we we are saying that<00:19:57.919> it<00:19:58.080> is<00:19:58.320> never<00:19:58.640> incented<00:19:59.280> generation 00:20:00.789 --> 00:20:00.799 align:start position:0% that it is never incented generation 00:20:00.799 --> 00:20:01.669 align:start position:0% that it is never incented generation um 00:20:01.669 --> 00:20:01.679 align:start position:0% um 00:20:01.679 --> 00:20:04.950 align:start position:0% um i<00:20:02.000> don't<00:20:02.240> see<00:20:02.720> wattbridge<00:20:03.600> on<00:20:03.760> the<00:20:03.919> list 00:20:04.950 --> 00:20:04.960 align:start position:0% i don't see wattbridge on the list 00:20:04.960 --> 00:20:06.950 align:start position:0% i don't see wattbridge on the list but<00:20:05.679> bill<00:20:05.919> i'm<00:20:06.080> kind<00:20:06.240> of<00:20:06.320> looking<00:20:06.559> at<00:20:06.720> you 00:20:06.950 --> 00:20:06.960 align:start position:0% but bill i'm kind of looking at you 00:20:06.960 --> 00:20:09.029 align:start position:0% but bill i'm kind of looking at you because<00:20:07.120> you<00:20:07.200> guys<00:20:07.440> are<00:20:07.600> eyeing<00:20:08.000> stuff 00:20:09.029 --> 00:20:09.039 align:start position:0% because you guys are eyeing stuff 00:20:09.039 --> 00:20:11.990 align:start position:0% because you guys are eyeing stuff but<00:20:09.600> but 00:20:11.990 --> 00:20:12.000 align:start position:0% 00:20:12.000 --> 00:20:14.070 align:start position:0% it<00:20:12.320> brings<00:20:12.640> up<00:20:12.799> the<00:20:12.960> question 00:20:14.070 --> 00:20:14.080 align:start position:0% it brings up the question 00:20:14.080 --> 00:20:17.110 align:start position:0% it brings up the question the<00:20:14.240> kind<00:20:14.480> of<00:20:14.640> generation<00:20:15.679> did<00:20:15.919> it<00:20:16.080> incense 00:20:17.110 --> 00:20:17.120 align:start position:0% the kind of generation did it incense 00:20:17.120 --> 00:20:18.630 align:start position:0% the kind of generation did it incense okay 00:20:18.630 --> 00:20:18.640 align:start position:0% okay 00:20:18.640 --> 00:20:21.669 align:start position:0% okay highly<00:20:19.039> rampable<00:20:20.000> uh<00:20:20.240> can<00:20:20.480> meet<00:20:20.799> those<00:20:21.280> uh 00:20:21.669 --> 00:20:21.679 align:start position:0% highly rampable uh can meet those uh 00:20:21.679 --> 00:20:24.630 align:start position:0% highly rampable uh can meet those uh those<00:20:22.000> adders<00:20:22.640> as<00:20:22.799> they're<00:20:22.960> ticking<00:20:23.360> up 00:20:24.630 --> 00:20:24.640 align:start position:0% those adders as they're ticking up 00:20:24.640 --> 00:20:25.830 align:start position:0% those adders as they're ticking up um 00:20:25.830 --> 00:20:25.840 align:start position:0% um 00:20:25.840 --> 00:20:27.669 align:start position:0% um and<00:20:26.240> that<00:20:26.559> in<00:20:26.720> conjunction<00:20:27.200> with<00:20:27.440> other 00:20:27.669 --> 00:20:27.679 align:start position:0% and that in conjunction with other 00:20:27.679 --> 00:20:29.590 align:start position:0% and that in conjunction with other things<00:20:28.000> things<00:20:28.240> that<00:20:28.320> are<00:20:28.400> on<00:20:28.559> our<00:20:28.720> list<00:20:29.280> uh 00:20:29.590 --> 00:20:29.600 align:start position:0% things things that are on our list uh 00:20:29.600 --> 00:20:31.270 align:start position:0% things things that are on our list uh menu<00:20:30.000> of<00:20:30.159> options 00:20:31.270 --> 00:20:31.280 align:start position:0% menu of options 00:20:31.280 --> 00:20:34.549 align:start position:0% menu of options that<00:20:31.600> tends<00:20:31.919> to<00:20:32.159> make<00:20:32.640> a<00:20:33.200> pretty<00:20:34.080> you<00:20:34.240> know 00:20:34.549 --> 00:20:34.559 align:start position:0% that tends to make a pretty you know 00:20:34.559 --> 00:20:35.430 align:start position:0% that tends to make a pretty you know sweet 00:20:35.430 --> 00:20:35.440 align:start position:0% sweet 00:20:35.440 --> 00:20:37.510 align:start position:0% sweet uh<00:20:36.000> financial<00:20:36.480> package 00:20:37.510 --> 00:20:37.520 align:start position:0% uh financial package 00:20:37.520 --> 00:20:39.430 align:start position:0% uh financial package for<00:20:37.840> a<00:20:38.080> type<00:20:38.320> of<00:20:38.400> generation<00:20:38.960> that<00:20:39.120> has<00:20:39.360> a 00:20:39.430 --> 00:20:39.440 align:start position:0% for a type of generation that has a 00:20:39.440 --> 00:20:41.669 align:start position:0% for a type of generation that has a particular<00:20:40.000> performance<00:20:40.559> value<00:20:41.200> and<00:20:41.360> if<00:20:41.440> we 00:20:41.669 --> 00:20:41.679 align:start position:0% particular performance value and if we 00:20:41.679 --> 00:20:42.950 align:start position:0% particular performance value and if we if<00:20:41.840> we<00:20:42.000> want<00:20:42.159> to<00:20:42.320> because<00:20:42.480> i<00:20:42.559> think<00:20:42.720> these<00:20:42.880> are 00:20:42.950 --> 00:20:42.960 align:start position:0% if we want to because i think these are 00:20:42.960 --> 00:20:44.230 align:start position:0% if we want to because i think these are important<00:20:43.280> questions<00:20:43.520> to<00:20:43.600> ask<00:20:43.760> and<00:20:43.919> maybe<00:20:44.080> we 00:20:44.230 --> 00:20:44.240 align:start position:0% important questions to ask and maybe we 00:20:44.240 --> 00:20:46.149 align:start position:0% important questions to ask and maybe we can<00:20:44.320> do<00:20:44.480> that<00:20:44.799> that<00:20:44.960> help<00:20:45.200> inform<00:20:45.679> brattle's 00:20:46.149 --> 00:20:46.159 align:start position:0% can do that that help inform brattle's 00:20:46.159 --> 00:20:47.190 align:start position:0% can do that that help inform brattle's final 00:20:47.190 --> 00:20:47.200 align:start position:0% final 00:20:47.200 --> 00:20:49.029 align:start position:0% final analysis<00:20:48.000> that<00:20:48.240> were<00:20:48.400> provided<00:20:48.799> would<00:20:48.960> you 00:20:49.029 --> 00:20:49.039 align:start position:0% analysis that were provided would you 00:20:49.039 --> 00:20:50.390 align:start position:0% analysis that were provided would you like<00:20:49.120> to<00:20:49.200> do<00:20:49.280> that<00:20:49.440> mr<00:20:49.600> chairman<00:20:49.840> or<00:20:50.000> i'll 00:20:50.390 --> 00:20:50.400 align:start position:0% like to do that mr chairman or i'll 00:20:50.400 --> 00:20:51.669 align:start position:0% like to do that mr chairman or i'll defer<00:20:50.720> to<00:20:50.799> you 00:20:51.669 --> 00:20:51.679 align:start position:0% defer to you 00:20:51.679 --> 00:20:53.029 align:start position:0% defer to you do<00:20:51.760> you<00:20:51.840> want<00:20:52.000> to<00:20:52.080> call<00:20:52.240> somebody<00:20:52.559> up<00:20:52.640> and<00:20:52.799> ask 00:20:53.029 --> 00:20:53.039 align:start position:0% do you want to call somebody up and ask 00:20:53.039 --> 00:20:54.710 align:start position:0% do you want to call somebody up and ask i'll<00:20:53.200> ask<00:20:53.360> barnes<00:20:53.919> if<00:20:54.000> i<00:20:54.080> could<00:20:54.480> are<00:20:54.640> you 00:20:54.710 --> 00:20:54.720 align:start position:0% i'll ask barnes if i could are you 00:20:54.720 --> 00:20:57.110 align:start position:0% i'll ask barnes if i could are you talking<00:20:54.880> about<00:20:55.039> people<00:20:55.840> yeah<00:20:56.320> okay 00:20:57.110 --> 00:20:57.120 align:start position:0% talking about people yeah okay 00:20:57.120 --> 00:20:58.870 align:start position:0% talking about people yeah okay i<00:20:57.200> think<00:20:57.360> we<00:20:57.520> should<00:20:57.679> get<00:20:57.919> ocra<00:20:58.400> to<00:20:58.559> talk<00:20:58.720> about 00:20:58.870 --> 00:20:58.880 align:start position:0% i think we should get ocra to talk about 00:20:58.880 --> 00:21:04.870 align:start position:0% i think we should get ocra to talk about that<00:20:59.039> too<00:20:59.280> cool 00:21:04.870 --> 00:21:04.880 align:start position:0% 00:21:04.880 --> 00:21:06.310 align:start position:0% glad<00:21:05.120> to<00:21:05.200> have<00:21:05.280> you<00:21:05.360> bill<00:21:05.600> bill<00:21:05.760> barnes 00:21:06.310 --> 00:21:06.320 align:start position:0% glad to have you bill bill barnes 00:21:06.320 --> 00:21:08.070 align:start position:0% glad to have you bill bill barnes representing<00:21:06.960> nrg 00:21:08.070 --> 00:21:08.080 align:start position:0% representing nrg 00:21:08.080 --> 00:21:08.789 align:start position:0% representing nrg i 00:21:08.789 --> 00:21:08.799 align:start position:0% i 00:21:08.799 --> 00:21:09.990 align:start position:0% i assume<00:21:09.039> this<00:21:09.200> is<00:21:09.200> called<00:21:09.360> the<00:21:09.440> hot<00:21:09.600> seat<00:21:09.919> i 00:21:09.990 --> 00:21:10.000 align:start position:0% assume this is called the hot seat i 00:21:10.000 --> 00:21:11.909 align:start position:0% assume this is called the hot seat i believe<00:21:10.240> so<00:21:10.400> okay 00:21:11.909 --> 00:21:11.919 align:start position:0% believe so okay 00:21:11.919 --> 00:21:13.990 align:start position:0% believe so okay i<00:21:12.080> know<00:21:12.240> mine's<00:21:12.559> warm 00:21:13.990 --> 00:21:14.000 align:start position:0% i know mine's warm 00:21:14.000 --> 00:21:17.510 align:start position:0% i know mine's warm and<00:21:14.240> so<00:21:14.880> um<00:21:15.760> you<00:21:15.919> were<00:21:16.080> talking<00:21:16.400> about 00:21:17.510 --> 00:21:17.520 align:start position:0% and so um you were talking about 00:21:17.520 --> 00:21:19.350 align:start position:0% and so um you were talking about the<00:21:17.679> rdc<00:21:18.320> and<00:21:18.480> its 00:21:19.350 --> 00:21:19.360 align:start position:0% the rdc and its 00:21:19.360 --> 00:21:20.549 align:start position:0% the rdc and its ability 00:21:20.549 --> 00:21:20.559 align:start position:0% ability 00:21:20.559 --> 00:21:22.470 align:start position:0% ability to<00:21:20.799> encourage<00:21:21.200> investment<00:21:21.679> and 00:21:22.470 --> 00:21:22.480 align:start position:0% to encourage investment and 00:21:22.480 --> 00:21:25.750 align:start position:0% to encourage investment and i<00:21:22.640> heard<00:21:23.440> almost<00:21:23.840> unanimous<00:21:24.880> consensus<00:21:25.520> that 00:21:25.750 --> 00:21:25.760 align:start position:0% i heard almost unanimous consensus that 00:21:25.760 --> 00:21:28.149 align:start position:0% i heard almost unanimous consensus that it<00:21:26.000> you<00:21:26.240> believe<00:21:26.480> that<00:21:26.640> it<00:21:27.039> provides<00:21:27.600> no 00:21:28.149 --> 00:21:28.159 align:start position:0% it you believe that it provides no 00:21:28.159 --> 00:21:30.549 align:start position:0% it you believe that it provides no incentive<00:21:29.039> for<00:21:29.280> investment<00:21:30.320> i<00:21:30.400> would 00:21:30.549 --> 00:21:30.559 align:start position:0% incentive for investment i would 00:21:30.559 --> 00:21:32.149 align:start position:0% incentive for investment i would disagree<00:21:31.039> with<00:21:31.200> that<00:21:31.520> i<00:21:31.600> think<00:21:31.840> it<00:21:31.919> does 00:21:32.149 --> 00:21:32.159 align:start position:0% disagree with that i think it does 00:21:32.159 --> 00:21:33.190 align:start position:0% disagree with that i think it does provide 00:21:33.190 --> 00:21:33.200 align:start position:0% provide 00:21:33.200 --> 00:21:35.029 align:start position:0% provide some<00:21:33.760> incentive 00:21:35.029 --> 00:21:35.039 align:start position:0% some incentive 00:21:35.039 --> 00:21:36.950 align:start position:0% some incentive um 00:21:36.950 --> 00:21:36.960 align:start position:0% um 00:21:36.960 --> 00:21:38.950 align:start position:0% um and<00:21:37.280> i<00:21:37.360> think<00:21:37.600> we've<00:21:37.840> seen<00:21:38.080> some<00:21:38.320> investment 00:21:38.950 --> 00:21:38.960 align:start position:0% and i think we've seen some investment 00:21:38.960 --> 00:21:41.430 align:start position:0% and i think we've seen some investment demand<00:21:39.360> response<00:21:39.840> capabilities<00:21:40.640> we've<00:21:40.880> seen 00:21:41.430 --> 00:21:41.440 align:start position:0% demand response capabilities we've seen 00:21:41.440 --> 00:21:42.950 align:start position:0% demand response capabilities we've seen batteries 00:21:42.950 --> 00:21:42.960 align:start position:0% batteries 00:21:42.960 --> 00:21:44.149 align:start position:0% batteries investment<00:21:43.360> and<00:21:43.440> demand<00:21:43.760> response 00:21:44.149 --> 00:21:44.159 align:start position:0% investment and demand response 00:21:44.159 --> 00:21:46.310 align:start position:0% investment and demand response capabilities<00:21:44.880> yeah<00:21:45.120> so<00:21:45.440> when<00:21:45.600> you<00:21:45.679> say<00:21:46.080> no 00:21:46.310 --> 00:21:46.320 align:start position:0% capabilities yeah so when you say no 00:21:46.320 --> 00:21:48.390 align:start position:0% capabilities yeah so when you say no investment<00:21:47.039> okay<00:21:47.280> so<00:21:47.520> i<00:21:47.679> just<00:21:47.760> want<00:21:47.919> to 00:21:48.390 --> 00:21:48.400 align:start position:0% investment okay so i just want to 00:21:48.400 --> 00:21:51.110 align:start position:0% investment okay so i just want to clarify<00:21:49.039> that<00:21:49.360> that<00:21:49.840> i<00:21:50.000> think<00:21:50.240> the<00:21:50.640> purpose<00:21:51.039> of 00:21:51.110 --> 00:21:51.120 align:start position:0% clarify that that i think the purpose of 00:21:51.120 --> 00:21:53.590 align:start position:0% clarify that that i think the purpose of that<00:21:51.280> mechanism<00:21:51.919> right<00:21:52.159> is<00:21:52.320> to 00:21:53.590 --> 00:21:53.600 align:start position:0% that mechanism right is to 00:21:53.600 --> 00:21:54.549 align:start position:0% that mechanism right is to signal 00:21:54.549 --> 00:21:54.559 align:start position:0% signal 00:21:54.559 --> 00:21:55.590 align:start position:0% signal when<00:21:54.720> we're 00:21:55.590 --> 00:21:55.600 align:start position:0% when we're 00:21:55.600 --> 00:21:57.350 align:start position:0% when we're expected<00:21:56.240> the<00:21:56.400> expected<00:21:56.720> number<00:21:56.880> of<00:21:57.039> hours<00:21:57.280> of 00:21:57.350 --> 00:21:57.360 align:start position:0% expected the expected number of hours of 00:21:57.360 --> 00:21:59.029 align:start position:0% expected the expected number of hours of scarcity<00:21:57.840> we're<00:21:58.000> going<00:21:58.159> to<00:21:58.320> see<00:21:58.880> in<00:21:58.960> the 00:21:59.029 --> 00:21:59.039 align:start position:0% scarcity we're going to see in the 00:21:59.039 --> 00:22:00.390 align:start position:0% scarcity we're going to see in the revenue<00:21:59.520> the<00:21:59.600> energy<00:21:59.840> revenues<00:22:00.240> that<00:22:00.320> would 00:22:00.390 --> 00:22:00.400 align:start position:0% revenue the energy revenues that would 00:22:00.400 --> 00:22:02.230 align:start position:0% revenue the energy revenues that would be<00:22:00.559> associated<00:22:01.039> with<00:22:01.200> that<00:22:01.760> and<00:22:01.919> folks<00:22:02.159> will 00:22:02.230 --> 00:22:02.240 align:start position:0% be associated with that and folks will 00:22:02.240 --> 00:22:03.510 align:start position:0% be associated with that and folks will try<00:22:02.400> to<00:22:02.480> project<00:22:02.799> that<00:22:02.960> forward<00:22:03.280> and<00:22:03.360> they 00:22:03.510 --> 00:22:03.520 align:start position:0% try to project that forward and they 00:22:03.520 --> 00:22:04.870 align:start position:0% try to project that forward and they will<00:22:03.679> make 00:22:04.870 --> 00:22:04.880 align:start position:0% will make 00:22:04.880 --> 00:22:06.390 align:start position:0% will make investments<00:22:05.440> that<00:22:05.600> they<00:22:05.760> think<00:22:06.000> are<00:22:06.159> in<00:22:06.320> the 00:22:06.390 --> 00:22:06.400 align:start position:0% investments that they think are in the 00:22:06.400 --> 00:22:08.549 align:start position:0% investments that they think are in the money<00:22:06.640> and<00:22:06.720> so<00:22:06.880> it's<00:22:07.200> there's<00:22:07.840> some<00:22:08.000> amount<00:22:08.400> of 00:22:08.549 --> 00:22:08.559 align:start position:0% money and so it's there's some amount of 00:22:08.559 --> 00:22:10.630 align:start position:0% money and so it's there's some amount of investment<00:22:08.960> that<00:22:09.120> will<00:22:09.520> occur<00:22:10.159> i<00:22:10.240> think<00:22:10.400> we've 00:22:10.630 --> 00:22:10.640 align:start position:0% investment that will occur i think we've 00:22:10.640 --> 00:22:13.270 align:start position:0% investment that will occur i think we've seen<00:22:10.960> some<00:22:12.080> i<00:22:12.159> think<00:22:12.320> the<00:22:12.480> challenge<00:22:12.880> with<00:22:13.120> the 00:22:13.270 --> 00:22:13.280 align:start position:0% seen some i think the challenge with the 00:22:13.280 --> 00:22:15.270 align:start position:0% seen some i think the challenge with the rdc<00:22:13.840> is<00:22:14.000> is<00:22:14.159> it<00:22:14.320> enough 00:22:15.270 --> 00:22:15.280 align:start position:0% rdc is is it enough 00:22:15.280 --> 00:22:17.750 align:start position:0% rdc is is it enough to<00:22:15.520> offset<00:22:16.080> load<00:22:16.400> growth<00:22:16.720> is<00:22:16.799> it<00:22:16.960> enough<00:22:17.520> to 00:22:17.750 --> 00:22:17.760 align:start position:0% to offset load growth is it enough to 00:22:17.760 --> 00:22:20.470 align:start position:0% to offset load growth is it enough to offset<00:22:18.480> retirements<00:22:19.360> which<00:22:19.600> will 00:22:20.470 --> 00:22:20.480 align:start position:0% offset retirements which will 00:22:20.480 --> 00:22:22.390 align:start position:0% offset retirements which will have<00:22:20.640> occurred<00:22:20.960> and<00:22:21.039> will<00:22:21.200> continue<00:22:21.520> to<00:22:21.679> occur 00:22:22.390 --> 00:22:22.400 align:start position:0% have occurred and will continue to occur 00:22:22.400 --> 00:22:25.029 align:start position:0% have occurred and will continue to occur and<00:22:22.559> i<00:22:22.640> think<00:22:22.799> that's<00:22:23.120> where 00:22:25.029 --> 00:22:25.039 align:start position:0% and i think that's where 00:22:25.039 --> 00:22:26.470 align:start position:0% and i think that's where i<00:22:25.120> would<00:22:25.200> agree<00:22:25.440> with<00:22:25.600> you<00:22:25.760> i<00:22:25.679> i<00:22:26.159> think<00:22:26.320> it's 00:22:26.470 --> 00:22:26.480 align:start position:0% i would agree with you i i think it's 00:22:26.480 --> 00:22:28.310 align:start position:0% i would agree with you i i think it's challenged<00:22:26.880> in<00:22:26.960> that<00:22:27.200> aspect<00:22:27.600> and<00:22:27.760> it<00:22:27.840> relies 00:22:28.310 --> 00:22:28.320 align:start position:0% challenged in that aspect and it relies 00:22:28.320 --> 00:22:29.190 align:start position:0% challenged in that aspect and it relies on 00:22:29.190 --> 00:22:29.200 align:start position:0% on 00:22:29.200 --> 00:22:31.990 align:start position:0% on scarcity<00:22:30.240> right<00:22:30.400> so<00:22:30.559> we<00:22:30.720> have<00:22:30.960> to<00:22:31.120> be<00:22:31.360> tight<00:22:31.919> in 00:22:31.990 --> 00:22:32.000 align:start position:0% scarcity right so we have to be tight in 00:22:32.000 --> 00:22:33.990 align:start position:0% scarcity right so we have to be tight in order<00:22:32.240> for<00:22:32.400> the<00:22:32.480> ordc<00:22:33.039> to<00:22:33.200> send<00:22:33.840> the 00:22:33.990 --> 00:22:34.000 align:start position:0% order for the ordc to send the 00:22:34.000 --> 00:22:36.149 align:start position:0% order for the ordc to send the investment<00:22:34.400> signals<00:22:34.720> and<00:22:34.799> i<00:22:34.880> think<00:22:35.039> we've 00:22:36.149 --> 00:22:36.159 align:start position:0% investment signals and i think we've 00:22:36.159 --> 00:22:37.430 align:start position:0% investment signals and i think we've that<00:22:36.320> mandate's<00:22:36.720> been<00:22:36.799> pretty<00:22:37.039> clear<00:22:37.200> to<00:22:37.280> us 00:22:37.430 --> 00:22:37.440 align:start position:0% that mandate's been pretty clear to us 00:22:37.440 --> 00:22:39.510 align:start position:0% that mandate's been pretty clear to us that<00:22:37.679> that's<00:22:38.000> not<00:22:38.159> really<00:22:38.720> we<00:22:38.799> don't<00:22:38.960> want<00:22:39.120> to 00:22:39.510 --> 00:22:39.520 align:start position:0% that that's not really we don't want to 00:22:39.520 --> 00:22:41.990 align:start position:0% that that's not really we don't want to continue<00:22:39.840> to<00:22:39.919> rely<00:22:40.240> on<00:22:40.480> crisis<00:22:41.039> to 00:22:41.990 --> 00:22:42.000 align:start position:0% continue to rely on crisis to 00:22:42.000 --> 00:22:43.990 align:start position:0% continue to rely on crisis to incentivize<00:22:42.559> exactly 00:22:43.990 --> 00:22:44.000 align:start position:0% incentivize exactly 00:22:44.000 --> 00:22:45.510 align:start position:0% incentivize exactly why<00:22:44.240> the<00:22:44.480> reforms<00:22:44.960> that<00:22:45.120> you<00:22:45.200> guys<00:22:45.360> are 00:22:45.510 --> 00:22:45.520 align:start position:0% why the reforms that you guys are 00:22:45.520 --> 00:22:47.830 align:start position:0% why the reforms that you guys are considering<00:22:46.159> are<00:22:46.400> the<00:22:46.559> right<00:22:46.799> step 00:22:47.830 --> 00:22:47.840 align:start position:0% considering are the right step 00:22:47.840 --> 00:22:48.710 align:start position:0% considering are the right step move 00:22:48.710 --> 00:22:48.720 align:start position:0% move 00:22:48.720 --> 00:22:51.190 align:start position:0% move move<00:22:48.960> the<00:22:49.039> goal<00:22:49.280> line<00:22:49.679> out<00:22:50.080> a<00:22:50.240> little<00:22:50.400> bit 00:22:51.190 --> 00:22:51.200 align:start position:0% move the goal line out a little bit 00:22:51.200 --> 00:22:53.029 align:start position:0% move the goal line out a little bit send<00:22:51.440> a<00:22:51.520> higher<00:22:51.760> price<00:22:52.000> signal<00:22:52.559> at<00:22:52.720> a<00:22:52.799> higher 00:22:53.029 --> 00:22:53.039 align:start position:0% send a higher price signal at a higher 00:22:53.039 --> 00:22:54.630 align:start position:0% send a higher price signal at a higher reserve<00:22:53.360> level<00:22:53.679> to<00:22:53.840> encourage<00:22:54.400> more 00:22:54.630 --> 00:22:54.640 align:start position:0% reserve level to encourage more 00:22:54.640 --> 00:22:55.909 align:start position:0% reserve level to encourage more commitment 00:22:55.909 --> 00:22:55.919 align:start position:0% commitment 00:22:55.919 --> 00:22:57.590 align:start position:0% commitment so<00:22:56.080> it's<00:22:56.240> solving<00:22:56.559> an<00:22:56.720> operational<00:22:57.200> problem 00:22:57.590 --> 00:22:57.600 align:start position:0% so it's solving an operational problem 00:22:57.600 --> 00:22:59.830 align:start position:0% so it's solving an operational problem which<00:22:57.919> i<00:22:58.400> agree<00:22:58.640> with<00:22:58.720> that<00:22:59.120> as<00:22:59.280> well<00:22:59.520> i<00:22:59.760> think 00:22:59.830 --> 00:22:59.840 align:start position:0% which i agree with that as well i think 00:22:59.840 --> 00:23:01.350 align:start position:0% which i agree with that as well i think that's<00:23:00.159> a<00:23:00.400> huge 00:23:01.350 --> 00:23:01.360 align:start position:0% that's a huge 00:23:01.360 --> 00:23:03.909 align:start position:0% that's a huge uh<00:23:01.600> benefit<00:23:02.000> of<00:23:02.080> the<00:23:02.240> reforms<00:23:02.799> is<00:23:02.880> to<00:23:03.520> push<00:23:03.760> us 00:23:03.909 --> 00:23:03.919 align:start position:0% uh benefit of the reforms is to push us 00:23:03.919 --> 00:23:04.950 align:start position:0% uh benefit of the reforms is to push us in<00:23:04.000> a<00:23:04.080> direction<00:23:04.320> where<00:23:04.480> the<00:23:04.559> market's 00:23:04.950 --> 00:23:04.960 align:start position:0% in a direction where the market's 00:23:04.960 --> 00:23:06.950 align:start position:0% in a direction where the market's responding<00:23:05.840> and<00:23:05.919> getting<00:23:06.159> more<00:23:06.559> reserves 00:23:06.950 --> 00:23:06.960 align:start position:0% responding and getting more reserves 00:23:06.960 --> 00:23:08.470 align:start position:0% responding and getting more reserves online<00:23:07.360> sooner<00:23:07.679> so<00:23:07.840> that<00:23:08.000> we<00:23:08.080> don't<00:23:08.240> have<00:23:08.400> to 00:23:08.470 --> 00:23:08.480 align:start position:0% online sooner so that we don't have to 00:23:08.480 --> 00:23:10.470 align:start position:0% online sooner so that we don't have to depend<00:23:08.799> on<00:23:08.960> out-of-market<00:23:09.600> actions<00:23:10.240> like<00:23:10.400> we 00:23:10.470 --> 00:23:10.480 align:start position:0% depend on out-of-market actions like we 00:23:10.480 --> 00:23:12.789 align:start position:0% depend on out-of-market actions like we have<00:23:10.720> and<00:23:11.120> i<00:23:11.280> will<00:23:11.440> say<00:23:11.679> i<00:23:12.000> i<00:23:12.320> do<00:23:12.480> agree<00:23:12.720> with 00:23:12.789 --> 00:23:12.799 align:start position:0% have and i will say i i do agree with 00:23:12.799 --> 00:23:15.190 align:start position:0% have and i will say i i do agree with you<00:23:12.960> to<00:23:13.039> an<00:23:13.120> extent<00:23:13.679> um<00:23:14.080> bill<00:23:14.400> i<00:23:14.720> think<00:23:14.960> it's 00:23:15.190 --> 00:23:15.200 align:start position:0% you to an extent um bill i think it's 00:23:15.200 --> 00:23:17.190 align:start position:0% you to an extent um bill i think it's it's<00:23:15.360> not<00:23:15.520> that<00:23:15.679> it<00:23:15.760> wholesale<00:23:16.240> hasn't<00:23:16.559> driven 00:23:17.190 --> 00:23:17.200 align:start position:0% it's not that it wholesale hasn't driven 00:23:17.200 --> 00:23:18.710 align:start position:0% it's not that it wholesale hasn't driven you<00:23:17.360> know<00:23:17.760> any 00:23:18.710 --> 00:23:18.720 align:start position:0% you know any 00:23:18.720 --> 00:23:20.310 align:start position:0% you know any investment<00:23:19.280> i<00:23:19.360> think<00:23:19.600> in<00:23:19.679> the<00:23:19.760> past<00:23:20.000> when<00:23:20.159> we 00:23:20.310 --> 00:23:20.320 align:start position:0% investment i think in the past when we 00:23:20.320 --> 00:23:21.750 align:start position:0% investment i think in the past when we adjusted<00:23:20.799> it<00:23:20.880> maybe<00:23:21.120> the<00:23:21.200> first<00:23:21.360> time<00:23:21.520> we<00:23:21.600> put 00:23:21.750 --> 00:23:21.760 align:start position:0% adjusted it maybe the first time we put 00:23:21.760 --> 00:23:23.510 align:start position:0% adjusted it maybe the first time we put it<00:23:21.919> in<00:23:22.080> place 00:23:23.510 --> 00:23:23.520 align:start position:0% it in place 00:23:23.520 --> 00:23:26.149 align:start position:0% it in place back<00:23:23.760> in<00:23:23.919> i<00:23:24.000> guess<00:23:24.280> 2013-14<00:23:25.520> there<00:23:25.679> was<00:23:25.840> some 00:23:26.149 --> 00:23:26.159 align:start position:0% back in i guess 2013-14 there was some 00:23:26.159 --> 00:23:28.390 align:start position:0% back in i guess 2013-14 there was some incremental<00:23:26.799> investment<00:23:27.280> that<00:23:27.440> was<00:23:27.679> made<00:23:28.240> is 00:23:28.390 --> 00:23:28.400 align:start position:0% incremental investment that was made is 00:23:28.400 --> 00:23:29.669 align:start position:0% incremental investment that was made is it<00:23:28.480> going<00:23:28.640> to<00:23:28.720> drive 00:23:29.669 --> 00:23:29.679 align:start position:0% it going to drive 00:23:29.679 --> 00:23:31.590 align:start position:0% it going to drive the<00:23:30.159> significant<00:23:30.640> amount<00:23:30.960> of<00:23:31.039> dispatchable 00:23:31.590 --> 00:23:31.600 align:start position:0% the significant amount of dispatchable 00:23:31.600 --> 00:23:34.950 align:start position:0% the significant amount of dispatchable generation<00:23:32.080> investment<00:23:32.720> it<00:23:32.880> might<00:23:33.440> you<00:23:33.600> know 00:23:34.950 --> 00:23:34.960 align:start position:0% generation investment it might you know 00:23:34.960 --> 00:23:37.110 align:start position:0% generation investment it might you know drive<00:23:35.280> some<00:23:35.600> incremental 00:23:37.110 --> 00:23:37.120 align:start position:0% drive some incremental 00:23:37.120 --> 00:23:38.310 align:start position:0% drive some incremental investment 00:23:38.310 --> 00:23:38.320 align:start position:0% investment 00:23:38.320 --> 00:23:40.230 align:start position:0% investment but<00:23:38.640> i<00:23:38.799> think<00:23:39.039> that<00:23:39.200> we<00:23:39.360> can<00:23:39.520> probably<00:23:39.919> all<00:23:40.080> say 00:23:40.230 --> 00:23:40.240 align:start position:0% but i think that we can probably all say 00:23:40.240 --> 00:23:41.669 align:start position:0% but i think that we can probably all say it's<00:23:40.320> not<00:23:40.480> go<00:23:40.799> depending<00:23:41.120> on<00:23:41.200> what<00:23:41.360> your<00:23:41.440> goal 00:23:41.669 --> 00:23:41.679 align:start position:0% it's not go depending on what your goal 00:23:41.679 --> 00:23:43.110 align:start position:0% it's not go depending on what your goal is<00:23:41.840> it's<00:23:42.080> not<00:23:42.240> going<00:23:42.320> to<00:23:42.400> get<00:23:42.559> you<00:23:42.720> the<00:23:42.880> full 00:23:43.110 --> 00:23:43.120 align:start position:0% is it's not going to get you the full 00:23:43.120 --> 00:23:44.390 align:start position:0% is it's not going to get you the full 100<00:23:43.520> percent 00:23:44.390 --> 00:23:44.400 align:start position:0% 100 percent 00:23:44.400 --> 00:23:46.310 align:start position:0% 100 percent you<00:23:44.480> know 00:23:46.310 --> 00:23:46.320 align:start position:0% you know 00:23:46.320 --> 00:23:48.870 align:start position:0% you know yeah<00:23:46.559> i<00:23:46.559> think<00:23:47.039> yeah<00:23:47.200> the<00:23:47.600> the 00:23:48.870 --> 00:23:48.880 align:start position:0% yeah i think yeah the the 00:23:48.880 --> 00:23:50.710 align:start position:0% yeah i think yeah the the unanimous 00:23:50.710 --> 00:23:50.720 align:start position:0% unanimous 00:23:50.720 --> 00:23:52.390 align:start position:0% unanimous opinions<00:23:51.200> you<00:23:51.520> just<00:23:51.760> heard<00:23:52.000> where<00:23:52.159> that 00:23:52.390 --> 00:23:52.400 align:start position:0% opinions you just heard where that 00:23:52.400 --> 00:23:55.269 align:start position:0% opinions you just heard where that doesn't<00:23:53.120> it<00:23:53.360> does<00:23:53.520> not<00:23:53.760> drive 00:23:55.269 --> 00:23:55.279 align:start position:0% doesn't it does not drive 00:23:55.279 --> 00:23:57.669 align:start position:0% doesn't it does not drive new<00:23:55.679> greenfield 00:23:57.669 --> 00:23:57.679 align:start position:0% new greenfield 00:23:57.679 --> 00:23:59.830 align:start position:0% new greenfield generation<00:23:58.320> steel<00:23:58.640> in<00:23:58.799> the<00:23:58.880> ground 00:23:59.830 --> 00:23:59.840 align:start position:0% generation steel in the ground 00:23:59.840 --> 00:24:01.110 align:start position:0% generation steel in the ground certainly 00:24:01.110 --> 00:24:01.120 align:start position:0% certainly 00:24:01.120 --> 00:24:03.190 align:start position:0% certainly incentivizes<00:24:01.919> investment<00:24:02.400> in<00:24:02.640> maintaining 00:24:03.190 --> 00:24:03.200 align:start position:0% incentivizes investment in maintaining 00:24:03.200 --> 00:24:04.870 align:start position:0% incentivizes investment in maintaining existing<00:24:03.600> assets<00:24:04.080> investment<00:24:04.480> and<00:24:04.559> demand 00:24:04.870 --> 00:24:04.880 align:start position:0% existing assets investment and demand 00:24:04.880 --> 00:24:06.230 align:start position:0% existing assets investment and demand response<00:24:05.440> i<00:24:05.520> think<00:24:05.679> everybody's<00:24:06.000> on<00:24:06.080> board 00:24:06.230 --> 00:24:06.240 align:start position:0% response i think everybody's on board 00:24:06.240 --> 00:24:07.029 align:start position:0% response i think everybody's on board with<00:24:06.320> that 00:24:07.029 --> 00:24:07.039 align:start position:0% with that 00:24:07.039 --> 00:24:08.390 align:start position:0% with that just<00:24:07.440> not 00:24:08.390 --> 00:24:08.400 align:start position:0% just not 00:24:08.400 --> 00:24:10.070 align:start position:0% just not greenfield<00:24:08.880> new<00:24:09.039> investment<00:24:09.600> which<00:24:09.919> and<00:24:10.000> i 00:24:10.070 --> 00:24:10.080 align:start position:0% greenfield new investment which and i 00:24:10.080 --> 00:24:13.430 align:start position:0% greenfield new investment which and i think<00:24:10.320> lori<00:24:10.640> makes<00:24:10.880> an<00:24:10.960> excellent<00:24:11.279> point<00:24:11.600> that 00:24:13.430 --> 00:24:13.440 align:start position:0% think lori makes an excellent point that 00:24:13.440 --> 00:24:15.510 align:start position:0% think lori makes an excellent point that if<00:24:13.600> we've<00:24:13.840> got<00:24:14.400> what<00:24:14.720> the 00:24:15.510 --> 00:24:15.520 align:start position:0% if we've got what the 00:24:15.520 --> 00:24:18.789 align:start position:0% if we've got what the problem<00:24:15.919> that<00:24:16.080> will's<00:24:16.400> gonna<00:24:16.960> articulate 00:24:18.789 --> 00:24:18.799 align:start position:0% problem that will's gonna articulate 00:24:18.799 --> 00:24:22.470 align:start position:0% problem that will's gonna articulate in<00:24:18.960> a<00:24:19.039> minute<00:24:19.600> when<00:24:19.760> we<00:24:20.000> get<00:24:20.159> to<00:24:20.240> ecrs<00:24:20.880> the<00:24:21.200> the 00:24:22.470 --> 00:24:22.480 align:start position:0% in a minute when we get to ecrs the the 00:24:22.480 --> 00:24:24.470 align:start position:0% in a minute when we get to ecrs the the when<00:24:22.640> we've<00:24:22.880> got<00:24:23.120> we've<00:24:23.360> got 00:24:24.470 --> 00:24:24.480 align:start position:0% when we've got we've got 00:24:24.480 --> 00:24:26.310 align:start position:0% when we've got we've got five<00:24:24.799> thousand<00:24:25.200> ten<00:24:25.440> thousand<00:24:25.840> fifteen 00:24:26.310 --> 00:24:26.320 align:start position:0% five thousand ten thousand fifteen 00:24:26.320 --> 00:24:29.110 align:start position:0% five thousand ten thousand fifteen thousand<00:24:27.120> megawatt<00:24:27.679> problems 00:24:29.110 --> 00:24:29.120 align:start position:0% thousand megawatt problems 00:24:29.120 --> 00:24:32.470 align:start position:0% thousand megawatt problems uh<00:24:29.679> both<00:24:29.919> in<00:24:30.159> ramping<00:24:30.799> and<00:24:31.039> in<00:24:31.840> just<00:24:32.240> load 00:24:32.470 --> 00:24:32.480 align:start position:0% uh both in ramping and in just load 00:24:32.480 --> 00:24:35.430 align:start position:0% uh both in ramping and in just load growth<00:24:33.360> and<00:24:33.600> offsetting<00:24:34.080> retirements 00:24:35.430 --> 00:24:35.440 align:start position:0% growth and offsetting retirements 00:24:35.440 --> 00:24:37.029 align:start position:0% growth and offsetting retirements it's<00:24:35.679> going<00:24:35.760> to<00:24:35.840> be<00:24:36.080> real<00:24:36.320> tough<00:24:36.559> to<00:24:36.640> get<00:24:36.799> there 00:24:37.029 --> 00:24:37.039 align:start position:0% it's going to be real tough to get there 00:24:37.039 --> 00:24:39.510 align:start position:0% it's going to be real tough to get there 100<00:24:37.440> megawatts<00:24:37.919> at<00:24:38.000> a<00:24:38.080> time 00:24:39.510 --> 00:24:39.520 align:start position:0% 100 megawatts at a time 00:24:39.520 --> 00:24:41.510 align:start position:0% 100 megawatts at a time and<00:24:40.159> i<00:24:40.320> think<00:24:40.559> some<00:24:40.720> of<00:24:40.799> the<00:24:40.960> existing 00:24:41.510 --> 00:24:41.520 align:start position:0% and i think some of the existing 00:24:41.520 --> 00:24:43.350 align:start position:0% and i think some of the existing investment<00:24:42.000> that's<00:24:42.240> been<00:24:42.400> made<00:24:42.720> have<00:24:42.880> been 00:24:43.350 --> 00:24:43.360 align:start position:0% investment that's been made have been 00:24:43.360 --> 00:24:45.590 align:start position:0% investment that's been made have been upgrades<00:24:44.240> or<00:24:44.720> up<00:24:44.880> rates<00:24:45.200> and<00:24:45.279> those<00:24:45.520> are 00:24:45.590 --> 00:24:45.600 align:start position:0% upgrades or up rates and those are 00:24:45.600 --> 00:24:47.430 align:start position:0% upgrades or up rates and those are important<00:24:46.080> too<00:24:46.320> because<00:24:46.799> those<00:24:46.960> are<00:24:47.120> real 00:24:47.430 --> 00:24:47.440 align:start position:0% important too because those are real 00:24:47.440 --> 00:24:50.789 align:start position:0% important too because those are real megawatts<00:24:48.159> and<00:24:48.880> every<00:24:49.200> bit<00:24:49.600> of<00:24:50.000> additional 00:24:50.789 --> 00:24:50.799 align:start position:0% megawatts and every bit of additional 00:24:50.799 --> 00:24:52.390 align:start position:0% megawatts and every bit of additional generation<00:24:51.279> we<00:24:51.440> can<00:24:51.520> get<00:24:51.679> from<00:24:51.840> dispatchable 00:24:52.390 --> 00:24:52.400 align:start position:0% generation we can get from dispatchable 00:24:52.400 --> 00:24:55.590 align:start position:0% generation we can get from dispatchable generation<00:24:53.440> is<00:24:53.679> important<00:24:54.559> so 00:24:55.590 --> 00:24:55.600 align:start position:0% generation is important so 00:24:55.600 --> 00:24:57.430 align:start position:0% generation is important so anyway<00:24:55.919> just<00:24:56.159> just<00:24:56.320> to<00:24:56.480> clarify<00:24:56.960> and<00:24:57.039> i<00:24:57.120> think 00:24:57.430 --> 00:24:57.440 align:start position:0% anyway just just to clarify and i think 00:24:57.440 --> 00:24:59.110 align:start position:0% anyway just just to clarify and i think we're<00:24:57.600> on<00:24:57.679> the<00:24:57.760> same<00:24:58.000> page<00:24:58.640> the<00:24:58.799> other<00:24:58.960> thing 00:24:59.110 --> 00:24:59.120 align:start position:0% we're on the same page the other thing 00:24:59.120 --> 00:25:01.430 align:start position:0% we're on the same page the other thing that<00:24:59.279> i<00:24:59.360> do<00:24:59.520> want<00:24:59.600> to<00:24:59.679> say<00:24:59.919> will<00:25:00.320> is<00:25:00.480> that 00:25:01.430 --> 00:25:01.440 align:start position:0% that i do want to say will is that 00:25:01.440 --> 00:25:04.310 align:start position:0% that i do want to say will is that from<00:25:01.679> an<00:25:01.840> operational<00:25:02.400> standpoint 00:25:04.310 --> 00:25:04.320 align:start position:0% from an operational standpoint 00:25:04.320 --> 00:25:06.950 align:start position:0% from an operational standpoint i<00:25:04.480> think<00:25:04.880> ordc<00:25:05.600> will<00:25:05.760> be<00:25:06.000> instrumental<00:25:06.799> in 00:25:06.950 --> 00:25:06.960 align:start position:0% i think ordc will be instrumental in 00:25:06.960 --> 00:25:10.230 align:start position:0% i think ordc will be instrumental in helping<00:25:07.360> us<00:25:07.600> address<00:25:07.919> the<00:25:08.080> duck<00:25:08.320> curve 00:25:10.230 --> 00:25:10.240 align:start position:0% helping us address the duck curve 00:25:10.240 --> 00:25:12.950 align:start position:0% helping us address the duck curve in<00:25:10.400> the<00:25:10.480> meantime<00:25:10.960> while<00:25:11.120> we<00:25:11.279> await<00:25:11.520> ecrs<00:25:12.720> so 00:25:12.950 --> 00:25:12.960 align:start position:0% in the meantime while we await ecrs so 00:25:12.960 --> 00:25:14.789 align:start position:0% in the meantime while we await ecrs so it's<00:25:13.120> important<00:25:13.520> we<00:25:13.919> we<00:25:14.080> get<00:25:14.240> that<00:25:14.480> right<00:25:14.720> as 00:25:14.789 --> 00:25:14.799 align:start position:0% it's important we we get that right as 00:25:14.799 --> 00:25:16.710 align:start position:0% it's important we we get that right as well<00:25:15.120> because<00:25:15.279> it's<00:25:15.520> another<00:25:15.840> tool<00:25:16.080> that<00:25:16.400> it 00:25:16.710 --> 00:25:16.720 align:start position:0% well because it's another tool that it 00:25:16.720 --> 00:25:18.710 align:start position:0% well because it's another tool that it is<00:25:16.799> an<00:25:16.960> existing<00:25:17.440> tool<00:25:17.679> that<00:25:17.840> ercot<00:25:18.159> will<00:25:18.320> rely 00:25:18.710 --> 00:25:18.720 align:start position:0% is an existing tool that ercot will rely 00:25:18.720 --> 00:25:21.430 align:start position:0% is an existing tool that ercot will rely on<00:25:19.440> um<00:25:19.679> in<00:25:19.840> the<00:25:19.919> interim<00:25:20.480> well<00:25:20.720> and<00:25:21.200> and 00:25:21.430 --> 00:25:21.440 align:start position:0% on um in the interim well and and 00:25:21.440 --> 00:25:24.230 align:start position:0% on um in the interim well and and logically<00:25:22.080> it<00:25:22.559> should<00:25:22.799> help<00:25:23.120> us<00:25:23.279> smooth<00:25:23.919> that 00:25:24.230 --> 00:25:24.240 align:start position:0% logically it should help us smooth that 00:25:24.240 --> 00:25:26.549 align:start position:0% logically it should help us smooth that curve<00:25:24.640> again<00:25:25.039> leading<00:25:25.440> into<00:25:25.760> it<00:25:25.919> that<00:25:26.159> time<00:25:26.400> of 00:25:26.549 --> 00:25:26.559 align:start position:0% curve again leading into it that time of 00:25:26.559 --> 00:25:27.430 align:start position:0% curve again leading into it that time of day 00:25:27.430 --> 00:25:27.440 align:start position:0% day 00:25:27.440 --> 00:25:30.950 align:start position:0% day you<00:25:27.760> so<00:25:28.240> yeah<00:25:28.799> um<00:25:29.360> and<00:25:29.440> so<00:25:29.679> i<00:25:29.840> i<00:25:30.080> asked 00:25:30.950 --> 00:25:30.960 align:start position:0% you so yeah um and so i i asked 00:25:30.960 --> 00:25:32.470 align:start position:0% you so yeah um and so i i asked randa<00:25:31.279> do<00:25:31.360> you<00:25:31.440> have<00:25:31.520> anything<00:25:31.919> else<00:25:32.159> to<00:25:32.320> add 00:25:32.470 --> 00:25:32.480 align:start position:0% randa do you have anything else to add 00:25:32.480 --> 00:25:34.230 align:start position:0% randa do you have anything else to add to<00:25:32.640> this 00:25:34.230 --> 00:25:34.240 align:start position:0% to this 00:25:34.240 --> 00:25:37.909 align:start position:0% to this okay 00:25:37.909 --> 00:25:37.919 align:start position:0% 00:25:37.919 --> 00:25:39.269 align:start position:0% you<00:25:38.000> should<00:25:38.240> learn<00:25:38.400> from<00:25:38.559> bill<00:25:38.799> not<00:25:38.960> to<00:25:39.039> sit<00:25:39.200> in 00:25:39.269 --> 00:25:39.279 align:start position:0% you should learn from bill not to sit in 00:25:39.279 --> 00:25:41.029 align:start position:0% you should learn from bill not to sit in the<00:25:39.440> scene 00:25:41.029 --> 00:25:41.039 align:start position:0% the scene 00:25:41.039 --> 00:25:42.149 align:start position:0% the scene she<00:25:41.200> really<00:25:41.360> wants<00:25:41.520> to<00:25:41.600> come<00:25:41.760> up<00:25:41.840> here<00:25:42.000> i<00:25:42.080> think 00:25:42.149 --> 00:25:42.159 align:start position:0% she really wants to come up here i think 00:25:42.159 --> 00:25:43.350 align:start position:0% she really wants to come up here i think we're<00:25:42.320> gonna<00:25:42.480> we're<00:25:42.640> gonna<00:25:42.799> have<00:25:42.880> to<00:25:42.960> add<00:25:43.120> two 00:25:43.350 --> 00:25:43.360 align:start position:0% we're gonna we're gonna have to add two 00:25:43.360 --> 00:25:45.909 align:start position:0% we're gonna we're gonna have to add two seats<00:25:44.159> so<00:25:44.320> we<00:25:44.400> can<00:25:44.559> make<00:25:44.640> this<00:25:44.880> efficient 00:25:45.909 --> 00:25:45.919 align:start position:0% seats so we can make this efficient 00:25:45.919 --> 00:25:49.909 align:start position:0% seats so we can make this efficient people<00:25:46.240> may<00:25:46.480> evacuate<00:25:46.960> if<00:25:47.120> we<00:25:47.200> do<00:25:47.360> that 00:25:49.909 --> 00:25:49.919 align:start position:0% 00:25:49.919 --> 00:25:52.470 align:start position:0% all<00:25:50.080> right<00:25:50.799> um<00:25:51.440> anymore<00:25:51.840> let<00:25:52.000> me<00:25:52.080> just<00:25:52.159> say<00:25:52.320> one 00:25:52.470 --> 00:25:52.480 align:start position:0% all right um anymore let me just say one 00:25:52.480 --> 00:25:54.230 align:start position:0% all right um anymore let me just say one thing<00:25:52.640> and<00:25:52.720> that<00:25:52.960> is<00:25:53.039> what<00:25:53.200> i<00:25:53.520> you<00:25:53.679> know<00:25:54.159> i 00:25:54.230 --> 00:25:54.240 align:start position:0% thing and that is what i you know i 00:25:54.240 --> 00:25:56.149 align:start position:0% thing and that is what i you know i wasn't<00:25:54.799> around<00:25:55.120> in<00:25:55.200> this<00:25:55.360> commission<00:25:55.840> in 00:25:56.149 --> 00:25:56.159 align:start position:0% wasn't around in this commission in 00:25:56.159 --> 00:26:00.070 align:start position:0% wasn't around in this commission in 2013.<00:25:57.600> um<00:25:58.000> but<00:25:58.159> when<00:25:58.400> ordc<00:25:59.039> was<00:25:59.440> created<00:25:59.919> and 00:26:00.070 --> 00:26:00.080 align:start position:0% 2013. um but when ordc was created and 00:26:00.080 --> 00:26:03.110 align:start position:0% 2013. um but when ordc was created and it<00:26:00.159> was<00:26:00.320> put<00:26:00.559> in<00:26:00.640> place<00:26:01.279> everybody<00:26:02.240> said<00:26:02.880> that 00:26:03.110 --> 00:26:03.120 align:start position:0% it was put in place everybody said that 00:26:03.120 --> 00:26:05.590 align:start position:0% it was put in place everybody said that it<00:26:03.279> wasn't<00:26:03.760> intended<00:26:04.159> to<00:26:04.240> act<00:26:04.480> alone 00:26:05.590 --> 00:26:05.600 align:start position:0% it wasn't intended to act alone 00:26:05.600 --> 00:26:08.870 align:start position:0% it wasn't intended to act alone so<00:26:06.159> it<00:26:06.400> is<00:26:06.640> a<00:26:06.880> tool<00:26:07.200> in<00:26:07.279> the<00:26:07.440> toolbox<00:26:08.320> it's<00:26:08.640> not 00:26:08.870 --> 00:26:08.880 align:start position:0% so it is a tool in the toolbox it's not 00:26:08.880 --> 00:26:10.789 align:start position:0% so it is a tool in the toolbox it's not intended<00:26:09.360> to<00:26:09.440> be<00:26:09.600> there<00:26:09.840> totally<00:26:10.159> by<00:26:10.400> itself 00:26:10.789 --> 00:26:10.799 align:start position:0% intended to be there totally by itself 00:26:10.799 --> 00:26:11.590 align:start position:0% intended to be there totally by itself so 00:26:11.590 --> 00:26:11.600 align:start position:0% so 00:26:11.600 --> 00:26:12.470 align:start position:0% so um 00:26:12.470 --> 00:26:12.480 align:start position:0% um 00:26:12.480 --> 00:26:13.990 align:start position:0% um looking<00:26:12.799> at<00:26:12.960> that<00:26:13.200> and<00:26:13.440> going<00:26:13.679> back<00:26:13.840> and 00:26:13.990 --> 00:26:14.000 align:start position:0% looking at that and going back and 00:26:14.000 --> 00:26:15.990 align:start position:0% looking at that and going back and thinking<00:26:14.240> about<00:26:14.559> that<00:26:15.039> you<00:26:15.120> know 00:26:15.990 --> 00:26:16.000 align:start position:0% thinking about that you know 00:26:16.000 --> 00:26:17.430 align:start position:0% thinking about that you know it's<00:26:16.240> a<00:26:16.400> sweet 00:26:17.430 --> 00:26:17.440 align:start position:0% it's a sweet 00:26:17.440 --> 00:26:19.510 align:start position:0% it's a sweet part<00:26:17.600> of<00:26:17.679> this<00:26:17.840> it's<00:26:18.000> a<00:26:18.080> scarcity<00:26:18.480> mechanism 00:26:19.510 --> 00:26:19.520 align:start position:0% part of this it's a scarcity mechanism 00:26:19.520 --> 00:26:21.510 align:start position:0% part of this it's a scarcity mechanism very<00:26:19.760> glass<00:26:20.080> in<00:26:20.159> case<00:26:20.400> of<00:26:20.480> emergency<00:26:21.360> not 00:26:21.510 --> 00:26:21.520 align:start position:0% very glass in case of emergency not 00:26:21.520 --> 00:26:23.190 align:start position:0% very glass in case of emergency not something<00:26:21.840> you<00:26:21.919> want<00:26:22.080> to<00:26:22.159> build<00:26:22.400> a<00:26:22.799> business 00:26:23.190 --> 00:26:23.200 align:start position:0% something you want to build a business 00:26:23.200 --> 00:26:25.269 align:start position:0% something you want to build a business model<00:26:23.520> on<00:26:23.679> for<00:26:23.840> a<00:26:24.240> billion<00:26:24.559> dollar<00:26:24.799> investment 00:26:25.269 --> 00:26:25.279 align:start position:0% model on for a billion dollar investment 00:26:25.279 --> 00:26:26.630 align:start position:0% model on for a billion dollar investment right 00:26:26.630 --> 00:26:26.640 align:start position:0% right 00:26:26.640 --> 00:26:28.789 align:start position:0% right anything<00:26:26.960> else<00:26:27.120> for<00:26:27.200> bill<00:26:27.840> no<00:26:28.000> sir<00:26:28.559> that<00:26:28.640> won't 00:26:28.789 --> 00:26:28.799 align:start position:0% anything else for bill no sir that won't 00:26:28.799 --> 00:26:31.269 align:start position:0% anything else for bill no sir that won't be<00:26:28.960> far 00:26:31.269 --> 00:26:31.279 align:start position:0% 00:26:31.279 --> 00:26:32.870 align:start position:0% thank<00:26:31.520> you<00:26:31.600> sir 00:26:32.870 --> 00:26:32.880 align:start position:0% thank you sir 00:26:32.880 --> 00:26:34.789 align:start position:0% thank you sir all<00:26:32.960> right<00:26:33.200> anything<00:26:33.520> else<00:26:33.679> on<00:26:33.840> ordc<00:26:34.480> i<00:26:34.559> know 00:26:34.789 --> 00:26:34.799 align:start position:0% all right anything else on ordc i know 00:26:34.799 --> 00:26:38.070 align:start position:0% all right anything else on ordc i know unfortunately<00:26:35.360> we've<00:26:35.600> got<00:26:35.760> a<00:26:36.400> big<00:26:36.880> tbd<00:26:37.440> there 00:26:38.070 --> 00:26:38.080 align:start position:0% unfortunately we've got a big tbd there 00:26:38.080 --> 00:26:40.630 align:start position:0% unfortunately we've got a big tbd there due<00:26:38.240> to<00:26:38.400> lack<00:26:38.640> of 00:26:40.630 --> 00:26:40.640 align:start position:0% due to lack of 00:26:40.640 --> 00:26:42.789 align:start position:0% due to lack of not<00:26:40.960> quite<00:26:41.120> up<00:26:41.200> to<00:26:41.360> speed<00:26:41.600> on<00:26:41.760> our<00:26:42.400> scenario 00:26:42.789 --> 00:26:42.799 align:start position:0% not quite up to speed on our scenario 00:26:42.799 --> 00:26:44.789 align:start position:0% not quite up to speed on our scenario analysis<00:26:43.440> uh 00:26:44.789 --> 00:26:44.799 align:start position:0% analysis uh 00:26:44.799 --> 00:26:47.669 align:start position:0% analysis uh that<00:26:44.960> will<00:26:45.120> bring<00:26:45.279> us<00:26:45.440> to<00:26:45.600> ecrs<00:26:46.559> uh<00:26:47.360> first<00:26:47.600> and 00:26:47.669 --> 00:26:47.679 align:start position:0% that will bring us to ecrs uh first and 00:26:47.679 --> 00:26:50.230 align:start position:0% that will bring us to ecrs uh first and foremost<00:26:48.640> i'll<00:26:49.279> want<00:26:49.440> to<00:26:49.520> say<00:26:49.840> thank<00:26:50.000> you 00:26:50.230 --> 00:26:50.240 align:start position:0% foremost i'll want to say thank you 00:26:50.240 --> 00:26:52.149 align:start position:0% foremost i'll want to say thank you commissioner<00:26:50.640> mcadams<00:26:51.120> for<00:26:51.440> posting<00:26:51.840> that 00:26:52.149 --> 00:26:52.159 align:start position:0% commissioner mcadams for posting that 00:26:52.159 --> 00:26:53.510 align:start position:0% commissioner mcadams for posting that memo 00:26:53.510 --> 00:26:53.520 align:start position:0% memo 00:26:53.520 --> 00:26:56.310 align:start position:0% memo and<00:26:53.600> the<00:26:53.760> accompanying<00:26:54.559> analysis<00:26:55.600> that's 00:26:56.310 --> 00:26:56.320 align:start position:0% and the accompanying analysis that's 00:26:56.320 --> 00:26:58.470 align:start position:0% and the accompanying analysis that's incredibly<00:26:56.960> important<00:26:57.600> maybe<00:26:58.000> maybe<00:26:58.240> one<00:26:58.400> of 00:26:58.470 --> 00:26:58.480 align:start position:0% incredibly important maybe maybe one of 00:26:58.480 --> 00:26:59.190 align:start position:0% incredibly important maybe maybe one of the 00:26:59.190 --> 00:26:59.200 align:start position:0% the 00:26:59.200 --> 00:27:01.269 align:start position:0% the top 00:27:01.269 --> 00:27:01.279 align:start position:0% top 00:27:01.279 --> 00:27:02.710 align:start position:0% top of<00:27:01.360> the<00:27:01.520> top<00:27:01.760> two<00:27:01.919> products<00:27:02.240> the<00:27:02.320> top<00:27:02.480> two 00:27:02.710 --> 00:27:02.720 align:start position:0% of the top two products the top two 00:27:02.720 --> 00:27:03.990 align:start position:0% of the top two products the top two problems<00:27:03.039> we're<00:27:03.200> facing<00:27:03.600> are<00:27:03.760> extreme 00:27:03.990 --> 00:27:04.000 align:start position:0% problems we're facing are extreme 00:27:04.000 --> 00:27:05.669 align:start position:0% problems we're facing are extreme weather<00:27:04.240> events<00:27:04.799> blue<00:27:05.039> sky<00:27:05.279> resource 00:27:05.669 --> 00:27:05.679 align:start position:0% weather events blue sky resource 00:27:05.679 --> 00:27:07.029 align:start position:0% weather events blue sky resource adequacy 00:27:07.029 --> 00:27:07.039 align:start position:0% adequacy 00:27:07.039 --> 00:27:08.549 align:start position:0% adequacy that's<00:27:07.279> got<00:27:07.440> to<00:27:07.520> be<00:27:07.600> number<00:27:07.840> three<00:27:08.080> and<00:27:08.240> it's<00:27:08.400> a 00:27:08.549 --> 00:27:08.559 align:start position:0% that's got to be number three and it's a 00:27:08.559 --> 00:27:11.590 align:start position:0% that's got to be number three and it's a close<00:27:08.880> three<00:27:09.600> i<00:27:09.919> appreciate<00:27:10.559> the<00:27:10.799> urcot<00:27:11.200> team 00:27:11.590 --> 00:27:11.600 align:start position:0% close three i appreciate the urcot team 00:27:11.600 --> 00:27:14.789 align:start position:0% close three i appreciate the urcot team for<00:27:12.159> putting<00:27:12.559> the<00:27:12.720> work<00:27:13.039> into<00:27:13.200> that<00:27:13.360> analysis 00:27:14.789 --> 00:27:14.799 align:start position:0% for putting the work into that analysis 00:27:14.799 --> 00:27:16.070 align:start position:0% for putting the work into that analysis i<00:27:14.960> know<00:27:15.120> you've<00:27:15.279> got<00:27:15.440> a<00:27:15.440> lot<00:27:15.600> of<00:27:15.679> thoughts<00:27:16.000> on 00:27:16.070 --> 00:27:16.080 align:start position:0% i know you've got a lot of thoughts on 00:27:16.080 --> 00:27:18.870 align:start position:0% i know you've got a lot of thoughts on that<00:27:16.240> so<00:27:16.720> i'll 00:27:18.870 --> 00:27:18.880 align:start position:0% that so i'll 00:27:18.880 --> 00:27:20.710 align:start position:0% that so i'll turn<00:27:19.120> the<00:27:19.440> floor<00:27:19.679> over<00:27:19.919> to<00:27:20.000> you 00:27:20.710 --> 00:27:20.720 align:start position:0% turn the floor over to you 00:27:20.720 --> 00:27:22.789 align:start position:0% turn the floor over to you well<00:27:21.120> thank<00:27:21.279> you<00:27:21.360> sir<00:27:21.840> um 00:27:22.789 --> 00:27:22.799 align:start position:0% well thank you sir um 00:27:22.799 --> 00:27:27.110 align:start position:0% well thank you sir um the<00:27:23.360> the<00:27:23.600> memo<00:27:24.240> uh<00:27:24.559> was<00:27:24.880> meant<00:27:25.279> to 00:27:27.110 --> 00:27:27.120 align:start position:0% the the memo uh was meant to 00:27:27.120 --> 00:27:28.950 align:start position:0% the the memo uh was meant to with<00:27:27.520> all<00:27:27.600> the<00:27:27.760> comments<00:27:28.240> and<00:27:28.399> the<00:27:28.480> workshops 00:27:28.950 --> 00:27:28.960 align:start position:0% with all the comments and the workshops 00:27:28.960 --> 00:27:30.710 align:start position:0% with all the comments and the workshops which<00:27:29.120> have<00:27:29.279> been<00:27:29.360> incredibly<00:27:29.840> valuable<00:27:30.399> i<00:27:30.559> i 00:27:30.710 --> 00:27:30.720 align:start position:0% which have been incredibly valuable i i 00:27:30.720 --> 00:27:33.029 align:start position:0% which have been incredibly valuable i i feel<00:27:30.960> like<00:27:31.120> i've<00:27:31.279> been<00:27:31.440> in<00:27:31.600> a<00:27:32.000> master's<00:27:32.559> course 00:27:33.029 --> 00:27:33.039 align:start position:0% feel like i've been in a master's course 00:27:33.039 --> 00:27:35.590 align:start position:0% feel like i've been in a master's course on<00:27:33.919> energy<00:27:34.320> only<00:27:34.640> versus<00:27:35.039> other<00:27:35.279> market 00:27:35.590 --> 00:27:35.600 align:start position:0% on energy only versus other market 00:27:35.600 --> 00:27:38.070 align:start position:0% on energy only versus other market designs<00:27:36.240> versus<00:27:36.880> reliability<00:27:37.679> and<00:27:37.760> all<00:27:37.919> these 00:27:38.070 --> 00:27:38.080 align:start position:0% designs versus reliability and all these 00:27:38.080 --> 00:27:39.669 align:start position:0% designs versus reliability and all these concepts 00:27:39.669 --> 00:27:39.679 align:start position:0% concepts 00:27:39.679 --> 00:27:41.830 align:start position:0% concepts the<00:27:39.840> analogy<00:27:40.480> of<00:27:40.640> couldn't<00:27:41.039> find<00:27:41.279> the<00:27:41.360> forest 00:27:41.830 --> 00:27:41.840 align:start position:0% the analogy of couldn't find the forest 00:27:41.840 --> 00:27:44.070 align:start position:0% the analogy of couldn't find the forest for<00:27:42.000> the<00:27:42.159> trees<00:27:43.039> was<00:27:43.200> the<00:27:43.279> best<00:27:43.520> that<00:27:43.679> came<00:27:43.840> to 00:27:44.070 --> 00:27:44.080 align:start position:0% for the trees was the best that came to 00:27:44.080 --> 00:27:46.310 align:start position:0% for the trees was the best that came to mind 00:27:46.310 --> 00:27:46.320 align:start position:0% mind 00:27:46.320 --> 00:27:48.549 align:start position:0% mind after<00:27:46.840> you 00:27:48.549 --> 00:27:48.559 align:start position:0% after you 00:27:48.559 --> 00:27:51.350 align:start position:0% after you sift<00:27:49.039> through<00:27:49.279> that<00:27:49.679> and<00:27:50.080> uh<00:27:50.559> and<00:27:50.799> look<00:27:51.120> at<00:27:51.200> the 00:27:51.350 --> 00:27:51.360 align:start position:0% sift through that and uh and look at the 00:27:51.360 --> 00:27:52.950 align:start position:0% sift through that and uh and look at the ercot<00:27:51.919> report 00:27:52.950 --> 00:27:52.960 align:start position:0% ercot report 00:27:52.960 --> 00:27:56.470 align:start position:0% ercot report um<00:27:53.600> again<00:27:54.240> in<00:27:54.559> three<00:27:54.880> years<00:27:55.520> uh<00:27:55.840> that<00:27:56.000> report 00:27:56.470 --> 00:27:56.480 align:start position:0% um again in three years uh that report 00:27:56.480 --> 00:27:59.029 align:start position:0% um again in three years uh that report is<00:27:56.559> based<00:27:56.880> on<00:27:57.120> a<00:27:57.200> reasonable<00:27:57.840> prediction 00:27:59.029 --> 00:27:59.039 align:start position:0% is based on a reasonable prediction 00:27:59.039 --> 00:28:03.110 align:start position:0% is based on a reasonable prediction of<00:27:59.840> the<00:28:00.000> resource<00:28:00.559> mix<00:28:01.039> and<00:28:01.200> our<00:28:01.360> cot<00:28:01.679> just 00:28:03.110 --> 00:28:03.120 align:start position:0% of the resource mix and our cot just 00:28:03.120 --> 00:28:05.269 align:start position:0% of the resource mix and our cot just changing 00:28:05.269 --> 00:28:05.279 align:start position:0% changing 00:28:05.279 --> 00:28:08.549 align:start position:0% changing and<00:28:05.840> changing<00:28:06.240> in<00:28:06.320> a<00:28:06.399> way<00:28:06.960> we<00:28:07.200> saw 00:28:08.549 --> 00:28:08.559 align:start position:0% and changing in a way we saw 00:28:08.559 --> 00:28:10.710 align:start position:0% and changing in a way we saw zero<00:28:09.039> cost<00:28:09.440> wind 00:28:10.710 --> 00:28:10.720 align:start position:0% zero cost wind 00:28:10.720 --> 00:28:12.950 align:start position:0% zero cost wind penetrate<00:28:11.279> our<00:28:11.440> market<00:28:12.159> from 00:28:12.950 --> 00:28:12.960 align:start position:0% penetrate our market from 00:28:12.960 --> 00:28:14.830 align:start position:0% penetrate our market from you<00:28:13.039> know<00:28:13.360> a<00:28:13.520> level 00:28:14.830 --> 00:28:14.840 align:start position:0% you know a level 00:28:14.840 --> 00:28:16.149 align:start position:0% you know a level of<00:28:15.039> um 00:28:16.149 --> 00:28:16.159 align:start position:0% of um 00:28:16.159 --> 00:28:20.230 align:start position:0% of um not<00:28:16.399> quite<00:28:16.799> five<00:28:17.039> thou<00:28:17.360> well<00:28:17.600> no<00:28:17.840> it<00:28:17.919> was<00:28:18.080> uh 00:28:20.230 --> 00:28:20.240 align:start position:0% not quite five thou well no it was uh 00:28:20.240 --> 00:28:22.710 align:start position:0% not quite five thou well no it was uh five<00:28:20.480> six<00:28:20.799> thousand<00:28:21.440> megawatts 00:28:22.710 --> 00:28:22.720 align:start position:0% five six thousand megawatts 00:28:22.720 --> 00:28:24.630 align:start position:0% five six thousand megawatts uh<00:28:23.039> ten<00:28:23.360> years<00:28:23.679> ago 00:28:24.630 --> 00:28:24.640 align:start position:0% uh ten years ago 00:28:24.640 --> 00:28:26.789 align:start position:0% uh ten years ago and<00:28:24.880> it<00:28:25.120> went<00:28:25.440> into<00:28:26.000> you<00:28:26.080> know<00:28:26.240> we're<00:28:26.399> now<00:28:26.640> at 00:28:26.789 --> 00:28:26.799 align:start position:0% and it went into you know we're now at 00:28:26.799 --> 00:28:28.310 align:start position:0% and it went into you know we're now at thirty<00:28:27.120> thousand 00:28:28.310 --> 00:28:28.320 align:start position:0% thirty thousand 00:28:28.320 --> 00:28:31.350 align:start position:0% thirty thousand or<00:28:28.559> twenty<00:28:28.799> five<00:28:29.120> 000<00:28:29.760> installed 00:28:31.350 --> 00:28:31.360 align:start position:0% or twenty five 000 installed 00:28:31.360 --> 00:28:32.470 align:start position:0% or twenty five 000 installed and<00:28:31.679> uh 00:28:32.470 --> 00:28:32.480 align:start position:0% and uh 00:28:32.480 --> 00:28:35.350 align:start position:0% and uh and<00:28:32.640> we<00:28:32.880> expect<00:28:33.200> to<00:28:33.360> see<00:28:33.600> still<00:28:33.919> more<00:28:34.399> wind<00:28:35.200> and 00:28:35.350 --> 00:28:35.360 align:start position:0% and we expect to see still more wind and 00:28:35.360 --> 00:28:37.430 align:start position:0% and we expect to see still more wind and that<00:28:35.520> has<00:28:35.760> been<00:28:36.080> a<00:28:36.320> good<00:28:36.559> thing<00:28:36.799> for<00:28:36.960> texas 00:28:37.430 --> 00:28:37.440 align:start position:0% that has been a good thing for texas 00:28:37.440 --> 00:28:40.389 align:start position:0% that has been a good thing for texas consumers<00:28:38.159> provides<00:28:38.799> good<00:28:39.360> clean 00:28:40.389 --> 00:28:40.399 align:start position:0% consumers provides good clean 00:28:40.399 --> 00:28:43.110 align:start position:0% consumers provides good clean uh<00:28:40.880> cheap<00:28:41.440> power 00:28:43.110 --> 00:28:43.120 align:start position:0% uh cheap power 00:28:43.120 --> 00:28:46.149 align:start position:0% uh cheap power now<00:28:43.440> we<00:28:43.600> will<00:28:43.840> see<00:28:44.320> in<00:28:44.559> a<00:28:44.720> three-year<00:28:45.200> period 00:28:46.149 --> 00:28:46.159 align:start position:0% now we will see in a three-year period 00:28:46.159 --> 00:28:47.029 align:start position:0% now we will see in a three-year period um 00:28:47.029 --> 00:28:47.039 align:start position:0% um 00:28:47.039 --> 00:28:50.070 align:start position:0% um potentially<00:28:47.760> up<00:28:48.000> to<00:28:48.559> uh<00:28:48.960> another 00:28:50.070 --> 00:28:50.080 align:start position:0% potentially up to uh another 00:28:50.080 --> 00:28:51.350 align:start position:0% potentially up to uh another 25 00:28:51.350 --> 00:28:51.360 align:start position:0% 25 00:28:51.360 --> 00:28:53.110 align:start position:0% 25 gigs<00:28:52.080> of 00:28:53.110 --> 00:28:53.120 align:start position:0% gigs of 00:28:53.120 --> 00:28:56.149 align:start position:0% gigs of solar<00:28:53.840> installed<00:28:54.720> again<00:28:55.360> that<00:28:55.520> will<00:28:55.760> be<00:28:55.919> good 00:28:56.149 --> 00:28:56.159 align:start position:0% solar installed again that will be good 00:28:56.159 --> 00:28:58.710 align:start position:0% solar installed again that will be good for<00:28:56.320> the<00:28:56.399> bottom<00:28:56.720> line<00:28:56.960> of<00:28:57.120> consumers<00:28:58.240> good 00:28:58.710 --> 00:28:58.720 align:start position:0% for the bottom line of consumers good 00:28:58.720 --> 00:28:59.990 align:start position:0% for the bottom line of consumers good clean 00:28:59.990 --> 00:29:00.000 align:start position:0% clean 00:29:00.000 --> 00:29:03.110 align:start position:0% clean cheap<00:29:00.559> power 00:29:03.110 --> 00:29:03.120 align:start position:0% 00:29:03.120 --> 00:29:05.430 align:start position:0% so<00:29:03.520> we're<00:29:03.840> talking<00:29:04.159> about 00:29:05.430 --> 00:29:05.440 align:start position:0% so we're talking about 00:29:05.440 --> 00:29:07.669 align:start position:0% so we're talking about you<00:29:05.600> know<00:29:05.760> even<00:29:06.399> reasonable<00:29:06.880> expectation<00:29:07.520> of 00:29:07.669 --> 00:29:07.679 align:start position:0% you know even reasonable expectation of 00:29:07.679 --> 00:29:09.669 align:start position:0% you know even reasonable expectation of load<00:29:07.919> growth<00:29:08.240> we're<00:29:08.399> talking<00:29:08.720> about 00:29:09.669 --> 00:29:09.679 align:start position:0% load growth we're talking about 00:29:09.679 --> 00:29:12.389 align:start position:0% load growth we're talking about over<00:29:10.080> 60<00:29:10.559> gigawatts<00:29:11.440> of 00:29:12.389 --> 00:29:12.399 align:start position:0% over 60 gigawatts of 00:29:12.399 --> 00:29:15.029 align:start position:0% over 60 gigawatts of variable<00:29:12.880> resources 00:29:15.029 --> 00:29:15.039 align:start position:0% variable resources 00:29:15.039 --> 00:29:16.310 align:start position:0% variable resources being<00:29:15.360> present 00:29:16.310 --> 00:29:16.320 align:start position:0% being present 00:29:16.320 --> 00:29:17.830 align:start position:0% being present on<00:29:16.480> the<00:29:16.640> grid 00:29:17.830 --> 00:29:17.840 align:start position:0% on the grid 00:29:17.840 --> 00:29:19.269 align:start position:0% on the grid maybe<00:29:18.080> not<00:29:18.240> producing<00:29:18.799> but<00:29:18.960> they'll<00:29:19.120> be 00:29:19.269 --> 00:29:19.279 align:start position:0% maybe not producing but they'll be 00:29:19.279 --> 00:29:20.630 align:start position:0% maybe not producing but they'll be present 00:29:20.630 --> 00:29:20.640 align:start position:0% present 00:29:20.640 --> 00:29:22.389 align:start position:0% present and<00:29:20.799> i<00:29:20.880> think<00:29:21.039> they'll<00:29:21.200> be<00:29:21.360> present<00:29:22.159> for<00:29:22.320> a 00:29:22.389 --> 00:29:22.399 align:start position:0% and i think they'll be present for a 00:29:22.399 --> 00:29:23.750 align:start position:0% and i think they'll be present for a number<00:29:22.640> of<00:29:22.720> reasons 00:29:23.750 --> 00:29:23.760 align:start position:0% number of reasons 00:29:23.760 --> 00:29:26.470 align:start position:0% number of reasons net<00:29:24.000> carbon<00:29:24.399> neutrality<00:29:25.120> and<00:29:25.279> energy<00:29:26.240> is<00:29:26.399> a 00:29:26.470 --> 00:29:26.480 align:start position:0% net carbon neutrality and energy is a 00:29:26.480 --> 00:29:29.590 align:start position:0% net carbon neutrality and energy is a concept<00:29:27.039> that<00:29:27.279> has<00:29:27.440> been<00:29:27.760> fully<00:29:28.080> embraced<00:29:29.039> by 00:29:29.590 --> 00:29:29.600 align:start position:0% concept that has been fully embraced by 00:29:29.600 --> 00:29:31.830 align:start position:0% concept that has been fully embraced by world<00:29:29.919> leaders 00:29:31.830 --> 00:29:31.840 align:start position:0% world leaders 00:29:31.840 --> 00:29:32.789 align:start position:0% world leaders of 00:29:32.789 --> 00:29:32.799 align:start position:0% of 00:29:32.799 --> 00:29:35.669 align:start position:0% of varying<00:29:33.279> fashions<00:29:34.080> and<00:29:34.480> that<00:29:35.039> i've<00:29:35.360> watched 00:29:35.669 --> 00:29:35.679 align:start position:0% varying fashions and that i've watched 00:29:35.679 --> 00:29:37.350 align:start position:0% varying fashions and that i've watched this<00:29:35.919> this<00:29:36.159> week<00:29:36.399> as<00:29:36.559> i'm<00:29:36.720> sure<00:29:36.880> some<00:29:37.039> of<00:29:37.200> you 00:29:37.350 --> 00:29:37.360 align:start position:0% this this week as i'm sure some of you 00:29:37.360 --> 00:29:38.230 align:start position:0% this this week as i'm sure some of you have 00:29:38.230 --> 00:29:38.240 align:start position:0% have 00:29:38.240 --> 00:29:41.350 align:start position:0% have of<00:29:38.480> the<00:29:39.039> conference<00:29:39.520> of<00:29:39.600> parties<00:29:40.080> the<00:29:40.159> cop<00:29:40.799> 26 00:29:41.350 --> 00:29:41.360 align:start position:0% of the conference of parties the cop 26 00:29:41.360 --> 00:29:43.990 align:start position:0% of the conference of parties the cop 26 conference<00:29:41.840> in<00:29:41.919> glasgow<00:29:42.480> scotland<00:29:43.520> which<00:29:43.760> is 00:29:43.990 --> 00:29:44.000 align:start position:0% conference in glasgow scotland which is 00:29:44.000 --> 00:29:46.149 align:start position:0% conference in glasgow scotland which is uh<00:29:44.320> still<00:29:44.640> ongoing 00:29:46.149 --> 00:29:46.159 align:start position:0% uh still ongoing 00:29:46.159 --> 00:29:47.669 align:start position:0% uh still ongoing where<00:29:46.399> world<00:29:46.640> leaders<00:29:47.039> are<00:29:47.120> discussing 00:29:47.669 --> 00:29:47.679 align:start position:0% where world leaders are discussing 00:29:47.679 --> 00:29:49.750 align:start position:0% where world leaders are discussing climate<00:29:48.080> change<00:29:48.480> but<00:29:48.720> policies<00:29:49.360> that<00:29:49.600> they 00:29:49.750 --> 00:29:49.760 align:start position:0% climate change but policies that they 00:29:49.760 --> 00:29:51.510 align:start position:0% climate change but policies that they will<00:29:50.080> impose 00:29:51.510 --> 00:29:51.520 align:start position:0% will impose 00:29:51.520 --> 00:29:52.950 align:start position:0% will impose to<00:29:51.760> address 00:29:52.950 --> 00:29:52.960 align:start position:0% to address 00:29:52.960 --> 00:29:55.190 align:start position:0% to address perceived<00:29:53.520> climate<00:29:53.919> change<00:29:54.240> and<00:29:54.480> i<00:29:54.640> am<00:29:54.799> not<00:29:55.039> as 00:29:55.190 --> 00:29:55.200 align:start position:0% perceived climate change and i am not as 00:29:55.200 --> 00:29:57.110 align:start position:0% perceived climate change and i am not as a<00:29:55.279> puc<00:29:55.760> commissioner<00:29:56.240> i'm<00:29:56.399> a<00:29:56.480> little<00:29:56.720> indian 00:29:57.110 --> 00:29:57.120 align:start position:0% a puc commissioner i'm a little indian 00:29:57.120 --> 00:29:59.029 align:start position:0% a puc commissioner i'm a little indian getting<00:29:57.440> in<00:29:57.760> into<00:29:58.080> that<00:29:58.240> debate<00:29:58.720> on<00:29:58.880> the 00:29:59.029 --> 00:29:59.039 align:start position:0% getting in into that debate on the 00:29:59.039 --> 00:30:01.909 align:start position:0% getting in into that debate on the science<00:29:59.360> or<00:29:59.520> anything<00:29:59.840> else<00:30:00.080> but<00:30:00.320> i<00:30:00.399> will<00:30:00.640> say 00:30:01.909 --> 00:30:01.919 align:start position:0% science or anything else but i will say 00:30:01.919 --> 00:30:03.909 align:start position:0% science or anything else but i will say that<00:30:02.159> the<00:30:02.320> headlines<00:30:02.799> from<00:30:02.960> the<00:30:03.039> conference 00:30:03.909 --> 00:30:03.919 align:start position:0% that the headlines from the conference 00:30:03.919 --> 00:30:06.870 align:start position:0% that the headlines from the conference are<00:30:04.399> uh<00:30:04.640> notable<00:30:05.360> and<00:30:05.679> and<00:30:05.919> bear<00:30:06.240> watching 00:30:06.870 --> 00:30:06.880 align:start position:0% are uh notable and and bear watching 00:30:06.880 --> 00:30:08.710 align:start position:0% are uh notable and and bear watching because 00:30:08.710 --> 00:30:08.720 align:start position:0% because 00:30:08.720 --> 00:30:10.389 align:start position:0% because you<00:30:08.880> know<00:30:09.200> one<00:30:09.440> headline<00:30:10.000> and<00:30:10.080> i'm<00:30:10.240> going<00:30:10.320> to 00:30:10.389 --> 00:30:10.399 align:start position:0% you know one headline and i'm going to 00:30:10.399 --> 00:30:11.350 align:start position:0% you know one headline and i'm going to roll<00:30:10.640> through<00:30:10.799> them<00:30:11.039> because<00:30:11.200> they're 00:30:11.350 --> 00:30:11.360 align:start position:0% roll through them because they're 00:30:11.360 --> 00:30:13.350 align:start position:0% roll through them because they're informative<00:30:12.080> the<00:30:12.240> financial<00:30:12.720> system<00:30:13.120> makes 00:30:13.350 --> 00:30:13.360 align:start position:0% informative the financial system makes 00:30:13.360 --> 00:30:15.590 align:start position:0% informative the financial system makes big<00:30:13.600> promises<00:30:14.080> on<00:30:14.240> climate<00:30:14.559> change<00:30:14.880> and<00:30:15.039> cop 00:30:15.590 --> 00:30:15.600 align:start position:0% big promises on climate change and cop 00:30:15.600 --> 00:30:19.029 align:start position:0% big promises on climate change and cop 26. 00:30:19.029 --> 00:30:19.039 align:start position:0% 00:30:19.039 --> 00:30:21.669 align:start position:0% large-scale<00:30:19.840> investors<00:30:20.480> and<00:30:21.039> the<00:30:21.200> financial 00:30:21.669 --> 00:30:21.679 align:start position:0% large-scale investors and the financial 00:30:21.679 --> 00:30:23.269 align:start position:0% large-scale investors and the financial system<00:30:22.080> has<00:30:22.240> committed 00:30:23.269 --> 00:30:23.279 align:start position:0% system has committed 00:30:23.279 --> 00:30:24.070 align:start position:0% system has committed that 00:30:24.070 --> 00:30:24.080 align:start position:0% that 00:30:24.080 --> 00:30:26.710 align:start position:0% that to<00:30:24.320> generate<00:30:24.720> 100<00:30:25.679> trillion<00:30:26.080> dollars<00:30:26.480> through 00:30:26.710 --> 00:30:26.720 align:start position:0% to generate 100 trillion dollars through 00:30:26.720 --> 00:30:29.750 align:start position:0% to generate 100 trillion dollars through 2050<00:30:27.760> to<00:30:27.919> fund<00:30:28.240> investments<00:30:29.039> and<00:30:29.200> esg 00:30:29.750 --> 00:30:29.760 align:start position:0% 2050 to fund investments and esg 00:30:29.760 --> 00:30:30.789 align:start position:0% 2050 to fund investments and esg positive 00:30:30.789 --> 00:30:30.799 align:start position:0% positive 00:30:30.799 --> 00:30:33.190 align:start position:0% positive programs<00:30:31.840> financial<00:30:32.320> regulators<00:30:32.880> including 00:30:33.190 --> 00:30:33.200 align:start position:0% programs financial regulators including 00:30:33.200 --> 00:30:34.870 align:start position:0% programs financial regulators including the<00:30:33.360> u.s<00:30:33.600> federal<00:30:33.919> reserve<00:30:34.320> and<00:30:34.399> the<00:30:34.480> bank<00:30:34.720> of 00:30:34.870 --> 00:30:34.880 align:start position:0% the u.s federal reserve and the bank of 00:30:34.880 --> 00:30:37.510 align:start position:0% the u.s federal reserve and the bank of england<00:30:35.360> plus<00:30:36.080> global<00:30:36.559> accounting<00:30:37.039> standards 00:30:37.510 --> 00:30:37.520 align:start position:0% england plus global accounting standards 00:30:37.520 --> 00:30:39.669 align:start position:0% england plus global accounting standards organization<00:30:38.640> which<00:30:38.799> that<00:30:39.039> sounds<00:30:39.360> important 00:30:39.669 --> 00:30:39.679 align:start position:0% organization which that sounds important 00:30:39.679 --> 00:30:42.870 align:start position:0% organization which that sounds important to<00:30:39.760> me<00:30:40.000> kind<00:30:40.080> of<00:30:40.159> like<00:30:40.320> the<00:30:40.480> global<00:30:40.880> fdic 00:30:42.870 --> 00:30:42.880 align:start position:0% to me kind of like the global fdic 00:30:42.880 --> 00:30:44.630 align:start position:0% to me kind of like the global fdic have<00:30:43.039> agreed<00:30:43.440> to<00:30:43.520> add<00:30:43.760> their<00:30:44.000> own<00:30:44.159> oversight 00:30:44.630 --> 00:30:44.640 align:start position:0% have agreed to add their own oversight 00:30:44.640 --> 00:30:45.990 align:start position:0% have agreed to add their own oversight to<00:30:44.799> the<00:30:44.880> system<00:30:45.279> through<00:30:45.440> reviews<00:30:45.919> and 00:30:45.990 --> 00:30:46.000 align:start position:0% to the system through reviews and 00:30:46.000 --> 00:30:48.470 align:start position:0% to the system through reviews and disclosure<00:30:46.640> standards 00:30:48.470 --> 00:30:48.480 align:start position:0% disclosure standards 00:30:48.480 --> 00:30:51.430 align:start position:0% disclosure standards go<00:30:48.720> on<00:30:48.880> to<00:30:48.960> read 00:30:51.430 --> 00:30:51.440 align:start position:0% go on to read 00:30:51.440 --> 00:30:53.190 align:start position:0% go on to read what's<00:30:51.679> his<00:30:51.840> name<00:30:52.240> bank<00:30:52.480> of<00:30:52.559> america<00:30:52.960> chief 00:30:53.190 --> 00:30:53.200 align:start position:0% what's his name bank of america chief 00:30:53.200 --> 00:30:55.430 align:start position:0% what's his name bank of america chief executive<00:30:53.600> brian<00:30:54.000> moynihan 00:30:55.430 --> 00:30:55.440 align:start position:0% executive brian moynihan 00:30:55.440 --> 00:30:56.789 align:start position:0% executive brian moynihan says<00:30:55.840> that 00:30:56.789 --> 00:30:56.799 align:start position:0% says that 00:30:56.799 --> 00:30:58.389 align:start position:0% says that government<00:30:57.279> does<00:30:57.440> not<00:30:57.600> have<00:30:57.760> the<00:30:57.919> money<00:30:58.320> it 00:30:58.389 --> 00:30:58.399 align:start position:0% government does not have the money it 00:30:58.399 --> 00:31:00.630 align:start position:0% government does not have the money it has<00:30:58.640> to<00:30:58.799> come<00:30:58.960> from<00:30:59.200> the<00:30:59.279> private<00:30:59.679> sector 00:31:00.630 --> 00:31:00.640 align:start position:0% has to come from the private sector 00:31:00.640 --> 00:31:03.509 align:start position:0% has to come from the private sector 100<00:31:01.120> trillion<00:31:01.440> it's<00:31:01.600> not<00:31:01.760> that<00:31:01.919> much<00:31:02.159> money 00:31:03.509 --> 00:31:03.519 align:start position:0% 100 trillion it's not that much money 00:31:03.519 --> 00:31:05.509 align:start position:0% 100 trillion it's not that much money so<00:31:03.679> they're<00:31:03.840> going<00:31:04.000> to<00:31:04.080> find<00:31:04.320> it 00:31:05.509 --> 00:31:05.519 align:start position:0% so they're going to find it 00:31:05.519 --> 00:31:08.950 align:start position:0% so they're going to find it the 00:31:08.950 --> 00:31:08.960 align:start position:0% 00:31:08.960 --> 00:31:10.710 align:start position:0% see<00:31:09.200> here 00:31:10.710 --> 00:31:10.720 align:start position:0% see here 00:31:10.720 --> 00:31:12.870 align:start position:0% see here big<00:31:10.960> change<00:31:11.360> in<00:31:11.440> the<00:31:11.519> last<00:31:11.840> five<00:31:12.159> years<00:31:12.480> is<00:31:12.640> net 00:31:12.870 --> 00:31:12.880 align:start position:0% big change in the last five years is net 00:31:12.880 --> 00:31:15.110 align:start position:0% big change in the last five years is net zero<00:31:13.200> commitments<00:31:13.760> which<00:31:14.240> create<00:31:14.640> demand 00:31:15.110 --> 00:31:15.120 align:start position:0% zero commitments which create demand 00:31:15.120 --> 00:31:17.430 align:start position:0% zero commitments which create demand around<00:31:15.360> the<00:31:15.440> private<00:31:15.760> sector<00:31:16.080> companies 00:31:17.430 --> 00:31:17.440 align:start position:0% around the private sector companies 00:31:17.440 --> 00:31:19.269 align:start position:0% around the private sector companies that<00:31:17.679> will<00:31:17.919> then<00:31:18.240> bring<00:31:18.480> money<00:31:18.880> that<00:31:19.120> is 00:31:19.269 --> 00:31:19.279 align:start position:0% that will then bring money that is 00:31:19.279 --> 00:31:22.470 align:start position:0% that will then bring money that is across<00:31:19.679> the<00:31:19.760> board<00:31:20.159> huge 00:31:22.470 --> 00:31:22.480 align:start position:0% across the board huge 00:31:22.480 --> 00:31:24.149 align:start position:0% across the board huge bank<00:31:22.720> of<00:31:22.880> america<00:31:23.279> is<00:31:23.360> willing<00:31:23.600> to<00:31:23.760> increase 00:31:24.149 --> 00:31:24.159 align:start position:0% bank of america is willing to increase 00:31:24.159 --> 00:31:26.470 align:start position:0% bank of america is willing to increase operating<00:31:24.559> costs<00:31:24.880> to<00:31:25.039> go<00:31:25.200> carbon<00:31:25.600> neutral<00:31:26.159> mr 00:31:26.470 --> 00:31:26.480 align:start position:0% operating costs to go carbon neutral mr 00:31:26.480 --> 00:31:28.789 align:start position:0% operating costs to go carbon neutral mr monaghan<00:31:26.960> says<00:31:27.360> it's<00:31:27.679> every<00:31:28.000> major<00:31:28.399> if<00:31:28.640> every 00:31:28.789 --> 00:31:28.799 align:start position:0% monaghan says it's every major if every 00:31:28.799 --> 00:31:30.389 align:start position:0% monaghan says it's every major if every major<00:31:29.120> company<00:31:29.440> did<00:31:29.600> the<00:31:29.679> same<00:31:29.919> the<00:31:30.000> resulting 00:31:30.389 --> 00:31:30.399 align:start position:0% major company did the same the resulting 00:31:30.399 --> 00:31:31.350 align:start position:0% major company did the same the resulting demand 00:31:31.350 --> 00:31:31.360 align:start position:0% demand 00:31:31.360 --> 00:31:33.590 align:start position:0% demand would<00:31:31.519> be<00:31:31.760> game<00:31:32.080> changing 00:31:33.590 --> 00:31:33.600 align:start position:0% would be game changing 00:31:33.600 --> 00:31:35.669 align:start position:0% would be game changing the<00:31:33.840> asia<00:31:34.159> development<00:31:34.640> bank<00:31:35.200> says<00:31:35.519> that 00:31:35.669 --> 00:31:35.679 align:start position:0% the asia development bank says that 00:31:35.679 --> 00:31:37.350 align:start position:0% the asia development bank says that without<00:31:36.000> an<00:31:36.159> active<00:31:36.399> intervention<00:31:37.039> to<00:31:37.200> get 00:31:37.350 --> 00:31:37.360 align:start position:0% without an active intervention to get 00:31:37.360 --> 00:31:39.110 align:start position:0% without an active intervention to get these<00:31:37.600> plants<00:31:38.080> out<00:31:38.240> of<00:31:38.320> our<00:31:38.480> power<00:31:38.799> system 00:31:39.110 --> 00:31:39.120 align:start position:0% these plants out of our power system 00:31:39.120 --> 00:31:40.389 align:start position:0% these plants out of our power system meaning<00:31:39.440> coal 00:31:40.389 --> 00:31:40.399 align:start position:0% meaning coal 00:31:40.399 --> 00:31:42.149 align:start position:0% meaning coal they<00:31:40.640> are<00:31:40.799> not<00:31:41.039> going<00:31:41.200> to<00:31:41.360> be<00:31:41.519> replaced<00:31:42.000> by 00:31:42.149 --> 00:31:42.159 align:start position:0% they are not going to be replaced by 00:31:42.159 --> 00:31:44.070 align:start position:0% they are not going to be replaced by renewables<00:31:42.720> until<00:31:43.039> they<00:31:43.200> reach<00:31:43.519> natural<00:31:43.919> end 00:31:44.070 --> 00:31:44.080 align:start position:0% renewables until they reach natural end 00:31:44.080 --> 00:31:47.190 align:start position:0% renewables until they reach natural end of<00:31:44.240> life<00:31:44.840> so<00:31:46.240> the 00:31:47.190 --> 00:31:47.200 align:start position:0% of life so the 00:31:47.200 --> 00:31:48.870 align:start position:0% of life so the asian<00:31:47.519> development<00:31:48.000> bank<00:31:48.240> says<00:31:48.480> there's<00:31:48.720> no 00:31:48.870 --> 00:31:48.880 align:start position:0% asian development bank says there's no 00:31:48.880 --> 00:31:50.310 align:start position:0% asian development bank says there's no shortage<00:31:49.360> of<00:31:49.440> capital<00:31:49.840> but<00:31:50.000> there's<00:31:50.240> a 00:31:50.310 --> 00:31:50.320 align:start position:0% shortage of capital but there's a 00:31:50.320 --> 00:31:52.789 align:start position:0% shortage of capital but there's a shortage<00:31:50.640> of<00:31:50.799> good<00:31:51.039> deals 00:31:52.789 --> 00:31:52.799 align:start position:0% shortage of good deals 00:31:52.799 --> 00:31:55.190 align:start position:0% shortage of good deals the<00:31:53.440> low<00:31:53.679> risk<00:31:54.000> nature<00:31:54.399> of<00:31:54.559> power<00:31:54.880> purchase 00:31:55.190 --> 00:31:55.200 align:start position:0% the low risk nature of power purchase 00:31:55.200 --> 00:31:56.549 align:start position:0% the low risk nature of power purchase agreements<00:31:55.760> can 00:31:56.549 --> 00:31:56.559 align:start position:0% agreements can 00:31:56.559 --> 00:31:58.870 align:start position:0% agreements can attract<00:31:57.039> very<00:31:57.279> competitive<00:31:57.919> private<00:31:58.240> sector 00:31:58.870 --> 00:31:58.880 align:start position:0% attract very competitive private sector 00:31:58.880 --> 00:32:01.669 align:start position:0% attract very competitive private sector capital<00:32:00.000> but<00:32:00.240> they<00:32:00.399> are<00:32:00.559> also<00:32:01.039> going<00:32:01.200> to<00:32:01.360> start 00:32:01.669 --> 00:32:01.679 align:start position:0% capital but they are also going to start 00:32:01.679 --> 00:32:03.990 align:start position:0% capital but they are also going to start investing<00:32:02.320> in<00:32:02.720> coal<00:32:02.960> plants 00:32:03.990 --> 00:32:04.000 align:start position:0% investing in coal plants 00:32:04.000 --> 00:32:06.549 align:start position:0% investing in coal plants in<00:32:04.240> the<00:32:04.720> pan<00:32:05.120> asian<00:32:05.519> rim 00:32:06.549 --> 00:32:06.559 align:start position:0% in the pan asian rim 00:32:06.559 --> 00:32:08.149 align:start position:0% in the pan asian rim and<00:32:06.880> retiring<00:32:07.360> them 00:32:08.149 --> 00:32:08.159 align:start position:0% and retiring them 00:32:08.159 --> 00:32:09.590 align:start position:0% and retiring them to<00:32:08.480> force 00:32:09.590 --> 00:32:09.600 align:start position:0% to force 00:32:09.600 --> 00:32:11.990 align:start position:0% to force consumption<00:32:10.320> of<00:32:10.640> renewables<00:32:11.519> now<00:32:11.679> they 00:32:11.990 --> 00:32:12.000 align:start position:0% consumption of renewables now they 00:32:12.000 --> 00:32:13.750 align:start position:0% consumption of renewables now they insist<00:32:12.480> that<00:32:12.559> they'll<00:32:12.799> do<00:32:12.960> this 00:32:13.750 --> 00:32:13.760 align:start position:0% insist that they'll do this 00:32:13.760 --> 00:32:16.230 align:start position:0% insist that they'll do this in<00:32:13.919> a<00:32:14.080> grid<00:32:14.399> reliable<00:32:15.039> way 00:32:16.230 --> 00:32:16.240 align:start position:0% in a grid reliable way 00:32:16.240 --> 00:32:19.029 align:start position:0% in a grid reliable way but 00:32:19.029 --> 00:32:19.039 align:start position:0% 00:32:19.039 --> 00:32:20.470 align:start position:0% my<00:32:19.279> point<00:32:19.600> is 00:32:20.470 --> 00:32:20.480 align:start position:0% my point is 00:32:20.480 --> 00:32:23.350 align:start position:0% my point is is<00:32:20.720> that 00:32:23.350 --> 00:32:23.360 align:start position:0% 00:32:23.360 --> 00:32:25.269 align:start position:0% the<00:32:23.519> paris<00:32:23.840> climate<00:32:24.159> accord<00:32:24.640> committed<00:32:25.120> to 00:32:25.269 --> 00:32:25.279 align:start position:0% the paris climate accord committed to 00:32:25.279 --> 00:32:27.110 align:start position:0% the paris climate accord committed to committing<00:32:25.760> globally<00:32:26.320> five<00:32:26.640> trillion 00:32:27.110 --> 00:32:27.120 align:start position:0% committing globally five trillion 00:32:27.120 --> 00:32:28.710 align:start position:0% committing globally five trillion dollars<00:32:27.760> all<00:32:28.000> in 00:32:28.710 --> 00:32:28.720 align:start position:0% dollars all in 00:32:28.720 --> 00:32:30.070 align:start position:0% dollars all in to<00:32:28.960> incenting 00:32:30.070 --> 00:32:30.080 align:start position:0% to incenting 00:32:30.080 --> 00:32:31.750 align:start position:0% to incenting renewable<00:32:30.480> resource<00:32:30.960> clean<00:32:31.279> carbon 00:32:31.750 --> 00:32:31.760 align:start position:0% renewable resource clean carbon 00:32:31.760 --> 00:32:33.590 align:start position:0% renewable resource clean carbon initiatives<00:32:32.399> globally 00:32:33.590 --> 00:32:33.600 align:start position:0% initiatives globally 00:32:33.600 --> 00:32:35.029 align:start position:0% initiatives globally we<00:32:33.760> just<00:32:33.919> heard<00:32:34.159> that<00:32:34.240> they're<00:32:34.480> committing<00:32:34.880> to 00:32:35.029 --> 00:32:35.039 align:start position:0% we just heard that they're committing to 00:32:35.039 --> 00:32:37.269 align:start position:0% we just heard that they're committing to spending<00:32:35.600> over<00:32:35.919> four<00:32:36.240> trillion<00:32:36.720> dollars<00:32:37.120> a 00:32:37.269 --> 00:32:37.279 align:start position:0% spending over four trillion dollars a 00:32:37.279 --> 00:32:39.830 align:start position:0% spending over four trillion dollars a year<00:32:38.000> globally<00:32:38.799> somehow 00:32:39.830 --> 00:32:39.840 align:start position:0% year globally somehow 00:32:39.840 --> 00:32:41.909 align:start position:0% year globally somehow now<00:32:40.000> how<00:32:40.240> firm<00:32:40.480> the<00:32:40.559> commitments<00:32:41.120> are<00:32:41.600> don't 00:32:41.909 --> 00:32:41.919 align:start position:0% now how firm the commitments are don't 00:32:41.919 --> 00:32:42.870 align:start position:0% now how firm the commitments are don't know 00:32:42.870 --> 00:32:42.880 align:start position:0% know 00:32:42.880 --> 00:32:45.110 align:start position:0% know but<00:32:43.279> just<00:32:43.600> on<00:32:43.760> an<00:32:43.919> aggregate 00:32:45.110 --> 00:32:45.120 align:start position:0% but just on an aggregate 00:32:45.120 --> 00:32:48.149 align:start position:0% but just on an aggregate texas<00:32:45.600> is<00:32:45.760> going<00:32:45.840> to<00:32:45.919> be<00:32:46.240> a 00:32:48.149 --> 00:32:48.159 align:start position:0% texas is going to be a 00:32:48.159 --> 00:32:50.630 align:start position:0% texas is going to be a very<00:32:48.480> enticing<00:32:49.039> destination<00:32:50.080> for<00:32:50.320> a<00:32:50.399> lot<00:32:50.559> of 00:32:50.630 --> 00:32:50.640 align:start position:0% very enticing destination for a lot of 00:32:50.640 --> 00:32:51.909 align:start position:0% very enticing destination for a lot of that<00:32:50.880> capital 00:32:51.909 --> 00:32:51.919 align:start position:0% that capital 00:32:51.919 --> 00:32:54.310 align:start position:0% that capital in<00:32:52.320> a<00:32:52.559> country<00:32:53.120> that<00:32:53.360> has<00:32:53.600> the<00:32:53.679> protections<00:32:54.240> of 00:32:54.310 --> 00:32:54.320 align:start position:0% in a country that has the protections of 00:32:54.320 --> 00:32:56.710 align:start position:0% in a country that has the protections of the<00:32:54.480> rule<00:32:54.720> of<00:32:54.799> law 00:32:56.710 --> 00:32:56.720 align:start position:0% the rule of law 00:32:56.720 --> 00:32:57.909 align:start position:0% the rule of law has 00:32:57.909 --> 00:32:57.919 align:start position:0% has 00:32:57.919 --> 00:32:59.830 align:start position:0% has friendly<00:32:58.320> policies<00:32:58.799> no<00:32:59.039> matter<00:32:59.360> what<00:32:59.600> because 00:32:59.830 --> 00:32:59.840 align:start position:0% friendly policies no matter what because 00:32:59.840 --> 00:33:02.389 align:start position:0% friendly policies no matter what because the<00:33:00.000> public<00:33:00.320> agrees<00:33:00.720> with<00:33:00.880> it 00:33:02.389 --> 00:33:02.399 align:start position:0% the public agrees with it 00:33:02.399 --> 00:33:04.230 align:start position:0% the public agrees with it texas<00:33:02.880> has<00:33:03.200> the<00:33:03.279> most<00:33:03.600> enticing 00:33:04.230 --> 00:33:04.240 align:start position:0% texas has the most enticing 00:33:04.240 --> 00:33:05.509 align:start position:0% texas has the most enticing interconnection 00:33:05.509 --> 00:33:05.519 align:start position:0% interconnection 00:33:05.519 --> 00:33:07.750 align:start position:0% interconnection queue<00:33:05.840> in<00:33:06.000> the<00:33:06.080> country<00:33:06.480> because<00:33:07.279> we<00:33:07.440> don't 00:33:07.750 --> 00:33:07.760 align:start position:0% queue in the country because we don't 00:33:07.760 --> 00:33:11.830 align:start position:0% queue in the country because we don't bog<00:33:08.159> generators<00:33:08.720> down<00:33:09.120> for<00:33:10.000> years<00:33:10.399> on<00:33:10.640> end 00:33:11.830 --> 00:33:11.840 align:start position:0% bog generators down for years on end 00:33:11.840 --> 00:33:14.950 align:start position:0% bog generators down for years on end with<00:33:12.080> our<00:33:12.320> regulatory<00:33:12.960> red<00:33:13.200> tape<00:33:13.519> and<00:33:13.679> studies 00:33:14.950 --> 00:33:14.960 align:start position:0% with our regulatory red tape and studies 00:33:14.960 --> 00:33:17.190 align:start position:0% with our regulatory red tape and studies they<00:33:15.120> can<00:33:15.279> get<00:33:15.519> up<00:33:15.600> and<00:33:15.760> running<00:33:16.240> in<00:33:16.480> 18<00:33:16.880> months 00:33:17.190 --> 00:33:17.200 align:start position:0% they can get up and running in 18 months 00:33:17.200 --> 00:33:19.509 align:start position:0% they can get up and running in 18 months if<00:33:17.279> they've<00:33:17.519> got<00:33:17.679> the<00:33:17.760> money 00:33:19.509 --> 00:33:19.519 align:start position:0% if they've got the money 00:33:19.519 --> 00:33:20.870 align:start position:0% if they've got the money so<00:33:19.840> i<00:33:20.000> believe 00:33:20.870 --> 00:33:20.880 align:start position:0% so i believe 00:33:20.880 --> 00:33:22.630 align:start position:0% so i believe that<00:33:21.039> the<00:33:21.200> solar<00:33:21.679> penetration<00:33:22.240> that<00:33:22.320> we<00:33:22.480> see 00:33:22.630 --> 00:33:22.640 align:start position:0% that the solar penetration that we see 00:33:22.640 --> 00:33:24.870 align:start position:0% that the solar penetration that we see in<00:33:22.720> that<00:33:22.960> report<00:33:23.679> is<00:33:23.919> absolutely<00:33:24.480> going<00:33:24.720> to 00:33:24.870 --> 00:33:24.880 align:start position:0% in that report is absolutely going to 00:33:24.880 --> 00:33:26.230 align:start position:0% in that report is absolutely going to happen 00:33:26.230 --> 00:33:26.240 align:start position:0% happen 00:33:26.240 --> 00:33:28.789 align:start position:0% happen and<00:33:26.640> that<00:33:26.960> defines<00:33:27.440> the<00:33:27.600> forest<00:33:28.320> within<00:33:28.640> the 00:33:28.789 --> 00:33:28.799 align:start position:0% and that defines the forest within the 00:33:28.799 --> 00:33:29.909 align:start position:0% and that defines the forest within the trees 00:33:29.909 --> 00:33:29.919 align:start position:0% trees 00:33:29.919 --> 00:33:31.909 align:start position:0% trees that<00:33:30.159> is<00:33:30.320> the<00:33:30.480> challenge<00:33:30.960> that<00:33:31.120> i<00:33:31.279> believe<00:33:31.679> we 00:33:31.909 --> 00:33:31.919 align:start position:0% that is the challenge that i believe we 00:33:31.919 --> 00:33:33.909 align:start position:0% that is the challenge that i believe we must<00:33:32.240> address<00:33:32.720> we<00:33:32.880> do<00:33:33.039> not<00:33:33.200> have<00:33:33.360> a<00:33:33.440> choice<00:33:33.760> is 00:33:33.909 --> 00:33:33.919 align:start position:0% must address we do not have a choice is 00:33:33.919 --> 00:33:36.230 align:start position:0% must address we do not have a choice is this<00:33:34.080> commission<00:33:34.640> it<00:33:34.799> is<00:33:34.960> our<00:33:35.120> duty 00:33:36.230 --> 00:33:36.240 align:start position:0% this commission it is our duty 00:33:36.240 --> 00:33:39.590 align:start position:0% this commission it is our duty to<00:33:36.399> the<00:33:36.559> state<00:33:36.799> of<00:33:36.880> texas<00:33:37.679> to<00:33:38.320> develop<00:33:38.799> tools 00:33:39.590 --> 00:33:39.600 align:start position:0% to the state of texas to develop tools 00:33:39.600 --> 00:33:42.149 align:start position:0% to the state of texas to develop tools that<00:33:39.840> meet<00:33:40.159> that<00:33:40.399> specific<00:33:40.880> scenario 00:33:42.149 --> 00:33:42.159 align:start position:0% that meet that specific scenario 00:33:42.159 --> 00:33:44.070 align:start position:0% that meet that specific scenario and<00:33:42.320> if<00:33:42.480> we<00:33:42.640> do<00:33:42.880> that<00:33:43.120> those<00:33:43.440> tools<00:33:43.760> can<00:33:43.919> be 00:33:44.070 --> 00:33:44.080 align:start position:0% and if we do that those tools can be 00:33:44.080 --> 00:33:46.389 align:start position:0% and if we do that those tools can be repurposed<00:33:44.799> at<00:33:44.960> other<00:33:45.120> times<00:33:45.760> to<00:33:45.919> serve<00:33:46.240> other 00:33:46.389 --> 00:33:46.399 align:start position:0% repurposed at other times to serve other 00:33:46.399 --> 00:33:49.029 align:start position:0% repurposed at other times to serve other reliability<00:33:47.120> needs<00:33:47.440> and<00:33:47.600> on<00:33:47.760> aggregate 00:33:49.029 --> 00:33:49.039 align:start position:0% reliability needs and on aggregate 00:33:49.039 --> 00:33:50.950 align:start position:0% reliability needs and on aggregate we<00:33:49.279> will<00:33:49.519> help<00:33:49.840> address 00:33:50.950 --> 00:33:50.960 align:start position:0% we will help address 00:33:50.960 --> 00:33:52.470 align:start position:0% we will help address both<00:33:51.120> the<00:33:51.279> yuri<00:33:51.600> scenario 00:33:52.470 --> 00:33:52.480 align:start position:0% both the yuri scenario 00:33:52.480 --> 00:33:54.310 align:start position:0% both the yuri scenario and<00:33:52.720> future<00:33:53.120> challenges<00:33:53.600> that<00:33:53.760> may<00:33:53.919> present 00:33:54.310 --> 00:33:54.320 align:start position:0% and future challenges that may present 00:33:54.320 --> 00:33:57.350 align:start position:0% and future challenges that may present themselves<00:33:55.360> in<00:33:55.519> a<00:33:55.679> scalable<00:33:56.240> way 00:33:57.350 --> 00:33:57.360 align:start position:0% themselves in a scalable way 00:33:57.360 --> 00:33:59.669 align:start position:0% themselves in a scalable way that<00:33:57.519> result<00:33:58.000> from<00:33:58.399> the<00:33:58.559> continuing 00:33:59.669 --> 00:33:59.679 align:start position:0% that result from the continuing 00:33:59.679 --> 00:34:01.590 align:start position:0% that result from the continuing change<00:34:00.000> in<00:34:00.080> resource<00:34:00.640> mix 00:34:01.590 --> 00:34:01.600 align:start position:0% change in resource mix 00:34:01.600 --> 00:34:03.509 align:start position:0% change in resource mix so<00:34:01.919> with<00:34:02.159> that 00:34:03.509 --> 00:34:03.519 align:start position:0% so with that 00:34:03.519 --> 00:34:05.590 align:start position:0% so with that that's<00:34:03.840> my<00:34:04.000> way<00:34:04.240> of<00:34:04.399> setting<00:34:04.720> the<00:34:04.799> table<00:34:05.519> on 00:34:05.590 --> 00:34:05.600 align:start position:0% that's my way of setting the table on 00:34:05.600 --> 00:34:07.430 align:start position:0% that's my way of setting the table on this<00:34:05.919> very<00:34:06.159> important<00:34:06.559> ancillary<00:34:07.039> service 00:34:07.430 --> 00:34:07.440 align:start position:0% this very important ancillary service 00:34:07.440 --> 00:34:09.349 align:start position:0% this very important ancillary service that<00:34:07.600> i<00:34:07.679> consider<00:34:08.240> absolutely<00:34:08.879> essential 00:34:09.349 --> 00:34:09.359 align:start position:0% that i consider absolutely essential 00:34:09.359 --> 00:34:11.109 align:start position:0% that i consider absolutely essential time<00:34:09.679> sensitive 00:34:11.109 --> 00:34:11.119 align:start position:0% time sensitive 00:34:11.119 --> 00:34:12.869 align:start position:0% time sensitive and<00:34:11.359> should 00:34:12.869 --> 00:34:12.879 align:start position:0% and should 00:34:12.879 --> 00:34:15.190 align:start position:0% and should warrant<00:34:13.440> prioritization<00:34:14.240> on<00:34:14.399> ercot's<00:34:14.879> part 00:34:15.190 --> 00:34:15.200 align:start position:0% warrant prioritization on ercot's part 00:34:15.200 --> 00:34:17.430 align:start position:0% warrant prioritization on ercot's part stakeholders<00:34:15.919> part<00:34:16.240> to<00:34:16.399> refine<00:34:16.800> the<00:34:16.960> details 00:34:17.430 --> 00:34:17.440 align:start position:0% stakeholders part to refine the details 00:34:17.440 --> 00:34:19.510 align:start position:0% stakeholders part to refine the details so<00:34:17.599> that<00:34:17.679> we<00:34:17.839> get<00:34:18.000> this<00:34:18.240> thing<00:34:18.560> up<00:34:18.720> and<00:34:18.800> running 00:34:19.510 --> 00:34:19.520 align:start position:0% so that we get this thing up and running 00:34:19.520 --> 00:34:21.270 align:start position:0% so that we get this thing up and running and<00:34:19.679> operational 00:34:21.270 --> 00:34:21.280 align:start position:0% and operational 00:34:21.280 --> 00:34:24.149 align:start position:0% and operational well<00:34:21.599> put 00:34:24.149 --> 00:34:24.159 align:start position:0% 00:34:24.159 --> 00:34:25.669 align:start position:0% although 00:34:25.669 --> 00:34:25.679 align:start position:0% although 00:34:25.679 --> 00:34:27.109 align:start position:0% although several<00:34:26.000> times 00:34:27.109 --> 00:34:27.119 align:start position:0% several times 00:34:27.119 --> 00:34:28.710 align:start position:0% several times through<00:34:27.280> your<00:34:27.440> comments<00:34:28.000> i<00:34:28.079> kept<00:34:28.320> thinking 00:34:28.710 --> 00:34:28.720 align:start position:0% through your comments i kept thinking 00:34:28.720 --> 00:34:31.030 align:start position:0% through your comments i kept thinking your<00:34:28.960> tax<00:34:29.200> dollars<00:34:29.520> at<00:34:29.599> work 00:34:31.030 --> 00:34:31.040 align:start position:0% your tax dollars at work 00:34:31.040 --> 00:34:32.950 align:start position:0% your tax dollars at work those<00:34:31.280> are<00:34:31.359> big<00:34:31.599> numbers<00:34:32.159> yes<00:34:32.399> sir<00:34:32.560> those<00:34:32.800> are 00:34:32.950 --> 00:34:32.960 align:start position:0% those are big numbers yes sir those are 00:34:32.960 --> 00:34:35.109 align:start position:0% those are big numbers yes sir those are really<00:34:33.119> big<00:34:33.359> numbers<00:34:33.919> and 00:34:35.109 --> 00:34:35.119 align:start position:0% really big numbers and 00:34:35.119 --> 00:34:38.230 align:start position:0% really big numbers and that<00:34:35.359> is<00:34:35.599> a 00:34:38.230 --> 00:34:38.240 align:start position:0% 00:34:38.240 --> 00:34:42.629 align:start position:0% good<00:34:38.720> articulation<00:34:39.760> of<00:34:40.399> the<00:34:41.119> financial<00:34:41.839> train 00:34:42.629 --> 00:34:42.639 align:start position:0% good articulation of the financial train 00:34:42.639 --> 00:34:44.550 align:start position:0% good articulation of the financial train that<00:34:42.879> is<00:34:43.040> rolling<00:34:43.359> downhill 00:34:44.550 --> 00:34:44.560 align:start position:0% that is rolling downhill 00:34:44.560 --> 00:34:46.790 align:start position:0% that is rolling downhill at<00:34:44.800> us<00:34:44.960> in<00:34:45.119> the<00:34:45.200> forms<00:34:45.520> of<00:34:46.079> subsidies<00:34:46.560> direct 00:34:46.790 --> 00:34:46.800 align:start position:0% at us in the forms of subsidies direct 00:34:46.800 --> 00:34:48.869 align:start position:0% at us in the forms of subsidies direct payments<00:34:47.200> etc<00:34:47.679> there's<00:34:47.919> nothing<00:34:48.159> we<00:34:48.240> can<00:34:48.399> do 00:34:48.869 --> 00:34:48.879 align:start position:0% payments etc there's nothing we can do 00:34:48.879 --> 00:34:50.950 align:start position:0% payments etc there's nothing we can do about<00:34:49.440> our<00:34:49.679> federal<00:34:50.000> partners 00:34:50.950 --> 00:34:50.960 align:start position:0% about our federal partners 00:34:50.960 --> 00:34:53.109 align:start position:0% about our federal partners i<00:34:51.119> will<00:34:51.679> note<00:34:51.919> that<00:34:52.159> and<00:34:52.399> to<00:34:52.560> build<00:34:52.800> on<00:34:52.960> your 00:34:53.109 --> 00:34:53.119 align:start position:0% i will note that and to build on your 00:34:53.119 --> 00:34:54.950 align:start position:0% i will note that and to build on your comments<00:34:53.520> about<00:34:53.919> the 00:34:54.950 --> 00:34:54.960 align:start position:0% comments about the 00:34:54.960 --> 00:34:57.030 align:start position:0% comments about the the<00:34:55.119> headlines<00:34:55.679> i<00:34:55.760> think<00:34:55.919> it's<00:34:56.560> coming<00:34:56.879> out<00:34:56.960> of 00:34:57.030 --> 00:34:57.040 align:start position:0% the headlines i think it's coming out of 00:34:57.040 --> 00:34:59.349 align:start position:0% the headlines i think it's coming out of glasgow<00:34:57.520> i<00:34:57.599> will<00:34:57.839> note<00:34:58.079> that<00:34:58.320> it's 00:34:59.349 --> 00:34:59.359 align:start position:0% glasgow i will note that it's 00:34:59.359 --> 00:35:01.589 align:start position:0% glasgow i will note that it's always<00:34:59.680> important<00:35:00.000> to<00:35:00.160> look<00:35:00.400> at<00:35:00.480> what<00:35:01.119> people 00:35:01.589 --> 00:35:01.599 align:start position:0% always important to look at what people 00:35:01.599 --> 00:35:04.390 align:start position:0% always important to look at what people actually<00:35:02.000> do<00:35:02.320> in<00:35:02.400> addition<00:35:02.720> to<00:35:02.800> what<00:35:02.960> they<00:35:03.200> say 00:35:04.390 --> 00:35:04.400 align:start position:0% actually do in addition to what they say 00:35:04.400 --> 00:35:06.150 align:start position:0% actually do in addition to what they say and<00:35:04.800> that 00:35:06.150 --> 00:35:06.160 align:start position:0% and that 00:35:06.160 --> 00:35:09.829 align:start position:0% and that the<00:35:06.320> host<00:35:06.640> country<00:35:07.040> of<00:35:07.200> the<00:35:07.440> summit<00:35:07.920> the<00:35:08.079> uk 00:35:09.829 --> 00:35:09.839 align:start position:0% the host country of the summit the uk 00:35:09.839 --> 00:35:10.950 align:start position:0% the host country of the summit the uk in 00:35:10.950 --> 00:35:10.960 align:start position:0% in 00:35:10.960 --> 00:35:12.069 align:start position:0% in dealing<00:35:11.280> with 00:35:12.069 --> 00:35:12.079 align:start position:0% dealing with 00:35:12.079 --> 00:35:14.470 align:start position:0% dealing with the<00:35:12.240> lack<00:35:12.480> of<00:35:12.640> wind<00:35:12.960> this<00:35:13.200> summer<00:35:13.920> that<00:35:14.160> also 00:35:14.470 --> 00:35:14.480 align:start position:0% the lack of wind this summer that also 00:35:14.480 --> 00:35:17.990 align:start position:0% the lack of wind this summer that also affected<00:35:14.880> france<00:35:15.280> and<00:35:15.359> germany 00:35:17.990 --> 00:35:18.000 align:start position:0% 00:35:18.000 --> 00:35:19.510 align:start position:0% are<00:35:18.240> making<00:35:18.560> lots<00:35:18.800> of 00:35:19.510 --> 00:35:19.520 align:start position:0% are making lots of 00:35:19.520 --> 00:35:21.510 align:start position:0% are making lots of headlines<00:35:20.160> at<00:35:20.240> the<00:35:20.400> summit<00:35:20.800> but<00:35:20.960> back<00:35:21.200> home 00:35:21.510 --> 00:35:21.520 align:start position:0% headlines at the summit but back home 00:35:21.520 --> 00:35:23.030 align:start position:0% headlines at the summit but back home both<00:35:21.760> of<00:35:21.839> those<00:35:22.079> countries<00:35:22.480> in<00:35:22.640> a<00:35:22.720> matter<00:35:22.960> of 00:35:23.030 --> 00:35:23.040 align:start position:0% both of those countries in a matter of 00:35:23.040 --> 00:35:24.310 align:start position:0% both of those countries in a matter of 60<00:35:23.440> days 00:35:24.310 --> 00:35:24.320 align:start position:0% 60 days 00:35:24.320 --> 00:35:26.310 align:start position:0% 60 days have<00:35:24.880> stepped<00:35:25.200> away<00:35:25.440> from<00:35:25.599> the<00:35:25.760> intermittency 00:35:26.310 --> 00:35:26.320 align:start position:0% have stepped away from the intermittency 00:35:26.320 --> 00:35:28.230 align:start position:0% have stepped away from the intermittency of<00:35:26.480> win<00:35:26.720> and<00:35:26.880> fully<00:35:27.200> embraced 00:35:28.230 --> 00:35:28.240 align:start position:0% of win and fully embraced 00:35:28.240 --> 00:35:30.870 align:start position:0% of win and fully embraced both<00:35:28.480> baseload<00:35:29.119> and<00:35:29.359> modular<00:35:29.839> nuclear 00:35:30.870 --> 00:35:30.880 align:start position:0% both baseload and modular nuclear 00:35:30.880 --> 00:35:32.870 align:start position:0% both baseload and modular nuclear uh<00:35:31.359> as<00:35:31.680> a 00:35:32.870 --> 00:35:32.880 align:start position:0% uh as a 00:35:32.880 --> 00:35:36.310 align:start position:0% uh as a as<00:35:33.119> the<00:35:33.280> only<00:35:33.599> zero<00:35:34.079> carbon<00:35:34.960> emission<00:35:35.359> way<00:35:36.000> to 00:35:36.310 --> 00:35:36.320 align:start position:0% as the only zero carbon emission way to 00:35:36.320 --> 00:35:38.069 align:start position:0% as the only zero carbon emission way to provide<00:35:36.720> reliable<00:35:37.200> power 00:35:38.069 --> 00:35:38.079 align:start position:0% provide reliable power 00:35:38.079 --> 00:35:40.230 align:start position:0% provide reliable power uh<00:35:38.400> so<00:35:38.800> i<00:35:39.200> appreciate<00:35:39.520> their<00:35:39.680> headlines<00:35:40.079> but 00:35:40.230 --> 00:35:40.240 align:start position:0% uh so i appreciate their headlines but 00:35:40.240 --> 00:35:41.430 align:start position:0% uh so i appreciate their headlines but it's<00:35:40.320> important<00:35:40.640> to<00:35:40.720> know<00:35:40.880> what<00:35:40.960> they<00:35:41.119> say<00:35:41.280> and 00:35:41.430 --> 00:35:41.440 align:start position:0% it's important to know what they say and 00:35:41.440 --> 00:35:44.310 align:start position:0% it's important to know what they say and i'll<00:35:41.599> also<00:35:41.920> note<00:35:42.160> that<00:35:42.320> last<00:35:42.560> week<00:35:42.800> japan<00:35:44.079> did 00:35:44.310 --> 00:35:44.320 align:start position:0% i'll also note that last week japan did 00:35:44.320 --> 00:35:45.750 align:start position:0% i'll also note that last week japan did the<00:35:44.400> same<00:35:44.720> thing 00:35:45.750 --> 00:35:45.760 align:start position:0% the same thing 00:35:45.760 --> 00:35:47.589 align:start position:0% the same thing so<00:35:46.320> we're<00:35:46.480> not<00:35:46.640> the<00:35:46.800> only<00:35:46.960> ones<00:35:47.200> in<00:35:47.280> the<00:35:47.359> world 00:35:47.589 --> 00:35:47.599 align:start position:0% so we're not the only ones in the world 00:35:47.599 --> 00:35:49.430 align:start position:0% so we're not the only ones in the world focused<00:35:47.920> on<00:35:48.079> reliability<00:35:48.800> just<00:35:48.960> one<00:35:49.200> last 00:35:49.430 --> 00:35:49.440 align:start position:0% focused on reliability just one last 00:35:49.440 --> 00:35:51.910 align:start position:0% focused on reliability just one last headline<00:35:50.160> to<00:35:50.240> speak<00:35:50.480> to<00:35:50.720> that<00:35:51.040> that 00:35:51.910 --> 00:35:51.920 align:start position:0% headline to speak to that that 00:35:51.920 --> 00:35:56.069 align:start position:0% headline to speak to that that does<00:35:52.320> come<00:35:52.560> to<00:35:52.720> your<00:35:52.880> point<00:35:53.280> mr<00:35:53.520> chairman 00:35:56.069 --> 00:35:56.079 align:start position:0% 00:35:56.079 --> 00:35:58.230 align:start position:0% separately<00:35:56.880> groups<00:35:57.200> including<00:35:57.599> the<00:35:57.760> u.s<00:35:58.160> the 00:35:58.230 --> 00:35:58.240 align:start position:0% separately groups including the u.s the 00:35:58.240 --> 00:36:00.069 align:start position:0% separately groups including the u.s the united<00:35:58.560> kingdom<00:35:58.880> and<00:35:59.040> canada<00:35:59.440> pledged<00:35:59.680> to<00:35:59.839> end 00:36:00.069 --> 00:36:00.079 align:start position:0% united kingdom and canada pledged to end 00:36:00.079 --> 00:36:02.870 align:start position:0% united kingdom and canada pledged to end public<00:36:00.480> funding<00:36:01.200> of<00:36:01.440> overseas<00:36:02.079> oil<00:36:02.320> and<00:36:02.480> gas 00:36:02.870 --> 00:36:02.880 align:start position:0% public funding of overseas oil and gas 00:36:02.880 --> 00:36:04.069 align:start position:0% public funding of overseas oil and gas developments 00:36:04.069 --> 00:36:04.079 align:start position:0% developments 00:36:04.079 --> 00:36:06.230 align:start position:0% developments in<00:36:04.240> that<00:36:04.400> deal<00:36:04.720> the<00:36:04.800> government<00:36:05.200> backed<00:36:05.520> banks 00:36:06.230 --> 00:36:06.240 align:start position:0% in that deal the government backed banks 00:36:06.240 --> 00:36:07.750 align:start position:0% in that deal the government backed banks keyword<00:36:06.720> government-backed<00:36:07.359> banks<00:36:07.680> i 00:36:07.750 --> 00:36:07.760 align:start position:0% keyword government-backed banks i 00:36:07.760 --> 00:36:09.349 align:start position:0% keyword government-backed banks i believe<00:36:08.160> all<00:36:08.320> of<00:36:08.480> our 00:36:09.349 --> 00:36:09.359 align:start position:0% believe all of our 00:36:09.359 --> 00:36:12.470 align:start position:0% believe all of our banks<00:36:09.760> are<00:36:10.000> government-backed<00:36:10.800> to<00:36:10.960> an<00:36:11.119> extent 00:36:12.470 --> 00:36:12.480 align:start position:0% banks are government-backed to an extent 00:36:12.480 --> 00:36:14.870 align:start position:0% banks are government-backed to an extent in<00:36:12.560> the<00:36:12.720> u.s<00:36:13.440> canada<00:36:13.920> and<00:36:14.079> the<00:36:14.160> united<00:36:14.480> kingdom 00:36:14.870 --> 00:36:14.880 align:start position:0% in the u.s canada and the united kingdom 00:36:14.880 --> 00:36:16.630 align:start position:0% in the u.s canada and the united kingdom said<00:36:15.040> that<00:36:15.200> they<00:36:15.359> would<00:36:15.599> stop<00:36:16.000> financing 00:36:16.630 --> 00:36:16.640 align:start position:0% said that they would stop financing 00:36:16.640 --> 00:36:17.670 align:start position:0% said that they would stop financing unabated 00:36:17.670 --> 00:36:17.680 align:start position:0% unabated 00:36:17.680 --> 00:36:20.310 align:start position:0% unabated coal<00:36:18.240> oil<00:36:18.640> natural<00:36:19.040> gas<00:36:19.359> projects<00:36:19.760> abroad<00:36:20.160> by 00:36:20.310 --> 00:36:20.320 align:start position:0% coal oil natural gas projects abroad by 00:36:20.320 --> 00:36:22.550 align:start position:0% coal oil natural gas projects abroad by the<00:36:20.480> end<00:36:20.640> of<00:36:20.880> next<00:36:21.200> year 00:36:22.550 --> 00:36:22.560 align:start position:0% the end of next year 00:36:22.560 --> 00:36:24.630 align:start position:0% the end of next year and<00:36:22.880> as<00:36:23.359> natural<00:36:23.680> gas<00:36:23.920> heads<00:36:24.160> to<00:36:24.320> seven 00:36:24.630 --> 00:36:24.640 align:start position:0% and as natural gas heads to seven 00:36:24.640 --> 00:36:26.470 align:start position:0% and as natural gas heads to seven dollars<00:36:24.960> here<00:36:25.200> and<00:36:25.280> forty<00:36:25.599> dollars<00:36:25.920> in<00:36:26.079> europe 00:36:26.470 --> 00:36:26.480 align:start position:0% dollars here and forty dollars in europe 00:36:26.480 --> 00:36:28.870 align:start position:0% dollars here and forty dollars in europe i'd<00:36:26.720> ask<00:36:26.960> folks<00:36:27.280> to<00:36:27.440> remember<00:36:27.839> that 00:36:28.870 --> 00:36:28.880 align:start position:0% i'd ask folks to remember that 00:36:28.880 --> 00:36:30.630 align:start position:0% i'd ask folks to remember that this<00:36:29.119> winter 00:36:30.630 --> 00:36:30.640 align:start position:0% this winter 00:36:30.640 --> 00:36:32.630 align:start position:0% this winter yeah<00:36:31.359> the<00:36:31.599> commissioner<00:36:31.920> mcadams<00:36:32.400> thank<00:36:32.560> you 00:36:32.630 --> 00:36:32.640 align:start position:0% yeah the commissioner mcadams thank you 00:36:32.640 --> 00:36:35.349 align:start position:0% yeah the commissioner mcadams thank you so<00:36:32.800> much<00:36:32.960> for<00:36:33.280> for<00:36:33.440> that<00:36:33.760> um<00:36:34.320> briefing 00:36:35.349 --> 00:36:35.359 align:start position:0% so much for for that um briefing 00:36:35.359 --> 00:36:37.430 align:start position:0% so much for for that um briefing i<00:36:35.440> think<00:36:35.599> it's<00:36:35.760> important<00:36:36.240> to<00:36:36.720> to 00:36:37.430 --> 00:36:37.440 align:start position:0% i think it's important to to 00:36:37.440 --> 00:36:39.430 align:start position:0% i think it's important to to for<00:36:37.680> us<00:36:37.839> to 00:36:39.430 --> 00:36:39.440 align:start position:0% for us to 00:36:39.440 --> 00:36:40.950 align:start position:0% for us to continue<00:36:39.839> to<00:36:39.920> be<00:36:40.079> apprised<00:36:40.480> of<00:36:40.560> what's<00:36:40.800> going 00:36:40.950 --> 00:36:40.960 align:start position:0% continue to be apprised of what's going 00:36:40.960 --> 00:36:43.910 align:start position:0% continue to be apprised of what's going on<00:36:41.119> globally<00:36:41.760> and<00:36:41.839> on<00:36:42.000> a<00:36:42.079> federal<00:36:42.480> level 00:36:43.910 --> 00:36:43.920 align:start position:0% on globally and on a federal level 00:36:43.920 --> 00:36:45.430 align:start position:0% on globally and on a federal level with<00:36:44.160> respect<00:36:44.640> to 00:36:45.430 --> 00:36:45.440 align:start position:0% with respect to 00:36:45.440 --> 00:36:46.870 align:start position:0% with respect to the<00:36:45.680> impacts<00:36:46.000> on<00:36:46.160> our<00:36:46.240> industry<00:36:46.560> here<00:36:46.800> in 00:36:46.870 --> 00:36:46.880 align:start position:0% the impacts on our industry here in 00:36:46.880 --> 00:36:50.390 align:start position:0% the impacts on our industry here in texas<00:36:47.760> we<00:36:47.920> must<00:36:48.160> be<00:36:48.320> proactive<00:36:49.280> on 00:36:50.390 --> 00:36:50.400 align:start position:0% texas we must be proactive on 00:36:50.400 --> 00:36:51.670 align:start position:0% texas we must be proactive on preparing 00:36:51.670 --> 00:36:51.680 align:start position:0% preparing 00:36:51.680 --> 00:36:54.630 align:start position:0% preparing to<00:36:52.160> address<00:36:52.560> those<00:36:52.880> issues<00:36:53.280> i<00:36:53.359> mean<00:36:54.000> ercot 00:36:54.630 --> 00:36:54.640 align:start position:0% to address those issues i mean ercot 00:36:54.640 --> 00:36:56.630 align:start position:0% to address those issues i mean ercot probably<00:36:55.040> briefed<00:36:55.359> us<00:36:55.520> all<00:36:55.760> on<00:36:55.920> this<00:36:56.400> duck 00:36:56.630 --> 00:36:56.640 align:start position:0% probably briefed us all on this duck 00:36:56.640 --> 00:36:59.430 align:start position:0% probably briefed us all on this duck curve<00:36:57.119> and<00:36:57.839> and<00:36:58.000> i<00:36:58.079> appreciate<00:36:58.560> you<00:36:59.119> bringing 00:36:59.430 --> 00:36:59.440 align:start position:0% curve and and i appreciate you bringing 00:36:59.440 --> 00:37:01.190 align:start position:0% curve and and i appreciate you bringing this<00:36:59.680> up<00:36:59.760> because<00:37:00.000> it's<00:37:00.160> it's<00:37:00.560> tremendously 00:37:01.190 --> 00:37:01.200 align:start position:0% this up because it's it's tremendously 00:37:01.200 --> 00:37:02.550 align:start position:0% this up because it's it's tremendously important 00:37:02.550 --> 00:37:02.560 align:start position:0% important 00:37:02.560 --> 00:37:04.790 align:start position:0% important i<00:37:02.720> would<00:37:02.960> encourage<00:37:03.280> your<00:37:03.520> cot<00:37:03.839> to<00:37:04.079> continue 00:37:04.790 --> 00:37:04.800 align:start position:0% i would encourage your cot to continue 00:37:04.800 --> 00:37:05.990 align:start position:0% i would encourage your cot to continue to 00:37:05.990 --> 00:37:06.000 align:start position:0% to 00:37:06.000 --> 00:37:08.790 align:start position:0% to drill<00:37:06.400> down<00:37:06.880> on<00:37:07.280> on<00:37:07.440> that<00:37:07.680> analysis<00:37:08.480> and<00:37:08.560> what 00:37:08.790 --> 00:37:08.800 align:start position:0% drill down on on that analysis and what 00:37:08.800 --> 00:37:11.349 align:start position:0% drill down on on that analysis and what i<00:37:08.880> mean<00:37:09.040> by<00:37:09.200> that<00:37:09.520> is<00:37:09.839> um 00:37:11.349 --> 00:37:11.359 align:start position:0% i mean by that is um 00:37:11.359 --> 00:37:12.470 align:start position:0% i mean by that is um to 00:37:12.470 --> 00:37:12.480 align:start position:0% to 00:37:12.480 --> 00:37:13.910 align:start position:0% to try<00:37:12.640> to<00:37:12.800> help<00:37:13.040> us<00:37:13.200> start<00:37:13.520> i<00:37:13.599> know<00:37:13.680> it's<00:37:13.839> a 00:37:13.910 --> 00:37:13.920 align:start position:0% try to help us start i know it's a 00:37:13.920 --> 00:37:15.430 align:start position:0% try to help us start i know it's a little<00:37:14.079> early<00:37:14.400> perhaps<00:37:14.800> but<00:37:14.960> to<00:37:15.119> start 00:37:15.430 --> 00:37:15.440 align:start position:0% little early perhaps but to start 00:37:15.440 --> 00:37:18.710 align:start position:0% little early perhaps but to start helping<00:37:15.760> the<00:37:15.920> size<00:37:16.320> how<00:37:16.560> big<00:37:16.800> ecrs<00:37:17.520> will<00:37:17.599> be 00:37:18.710 --> 00:37:18.720 align:start position:0% helping the size how big ecrs will be 00:37:18.720 --> 00:37:20.710 align:start position:0% helping the size how big ecrs will be so<00:37:18.880> that<00:37:18.960> we<00:37:19.119> can<00:37:19.359> see 00:37:20.710 --> 00:37:20.720 align:start position:0% so that we can see 00:37:20.720 --> 00:37:22.630 align:start position:0% so that we can see how<00:37:20.880> that<00:37:21.119> matches<00:37:21.520> up<00:37:21.680> with<00:37:22.079> with<00:37:22.240> the<00:37:22.400> duck 00:37:22.630 --> 00:37:22.640 align:start position:0% how that matches up with with the duck 00:37:22.640 --> 00:37:25.349 align:start position:0% how that matches up with with the duck curve<00:37:23.119> that<00:37:23.520> um<00:37:23.839> appears<00:37:24.160> to<00:37:24.320> be<00:37:24.400> coming 00:37:25.349 --> 00:37:25.359 align:start position:0% curve that um appears to be coming 00:37:25.359 --> 00:37:26.630 align:start position:0% curve that um appears to be coming um 00:37:26.630 --> 00:37:26.640 align:start position:0% um 00:37:26.640 --> 00:37:29.750 align:start position:0% um irrespective<00:37:27.760> of<00:37:28.560> any<00:37:28.800> state<00:37:29.040> regulatory 00:37:29.750 --> 00:37:29.760 align:start position:0% irrespective of any state regulatory 00:37:29.760 --> 00:37:30.790 align:start position:0% irrespective of any state regulatory action 00:37:30.790 --> 00:37:30.800 align:start position:0% action 00:37:30.800 --> 00:37:32.550 align:start position:0% action that<00:37:30.960> we<00:37:31.200> may<00:37:31.359> take<00:37:31.760> because<00:37:32.079> of<00:37:32.160> federal 00:37:32.550 --> 00:37:32.560 align:start position:0% that we may take because of federal 00:37:32.560 --> 00:37:33.589 align:start position:0% that we may take because of federal action 00:37:33.589 --> 00:37:33.599 align:start position:0% action 00:37:33.599 --> 00:37:36.630 align:start position:0% action and<00:37:33.920> that's<00:37:34.079> just<00:37:34.320> the<00:37:34.400> reality<00:37:34.800> of<00:37:34.960> it<00:37:35.280> and<00:37:35.440> so 00:37:36.630 --> 00:37:36.640 align:start position:0% and that's just the reality of it and so 00:37:36.640 --> 00:37:39.510 align:start position:0% and that's just the reality of it and so having<00:37:36.960> nercot<00:37:37.680> really<00:37:38.000> kind<00:37:38.160> of<00:37:38.800> fine<00:37:39.119> tune 00:37:39.510 --> 00:37:39.520 align:start position:0% having nercot really kind of fine tune 00:37:39.520 --> 00:37:41.750 align:start position:0% having nercot really kind of fine tune that<00:37:39.760> duck<00:37:40.000> curve<00:37:40.240> analysis<00:37:40.880> so<00:37:41.040> that<00:37:41.359> we<00:37:41.599> are 00:37:41.750 --> 00:37:41.760 align:start position:0% that duck curve analysis so that we are 00:37:41.760 --> 00:37:44.550 align:start position:0% that duck curve analysis so that we are accurately<00:37:42.320> planning<00:37:43.040> for<00:37:43.200> that<00:37:43.440> duct<00:37:43.680> curve 00:37:44.550 --> 00:37:44.560 align:start position:0% accurately planning for that duct curve 00:37:44.560 --> 00:37:47.589 align:start position:0% accurately planning for that duct curve and<00:37:44.800> accurately<00:37:45.359> sizing<00:37:46.079> the<00:37:46.240> ecrs 00:37:47.589 --> 00:37:47.599 align:start position:0% and accurately sizing the ecrs 00:37:47.599 --> 00:37:49.510 align:start position:0% and accurately sizing the ecrs because<00:37:47.839> we<00:37:47.920> don't<00:37:48.079> want<00:37:48.240> to<00:37:48.400> overbuild<00:37:48.960> ecrs 00:37:49.510 --> 00:37:49.520 align:start position:0% because we don't want to overbuild ecrs 00:37:49.520 --> 00:37:50.390 align:start position:0% because we don't want to overbuild ecrs and<00:37:49.680> we<00:37:49.760> don't<00:37:49.920> want<00:37:50.000> to<00:37:50.079> be<00:37:50.240> caught 00:37:50.390 --> 00:37:50.400 align:start position:0% and we don't want to be caught 00:37:50.400 --> 00:37:51.910 align:start position:0% and we don't want to be caught flat-footed 00:37:51.910 --> 00:37:51.920 align:start position:0% flat-footed 00:37:51.920 --> 00:37:53.190 align:start position:0% flat-footed i<00:37:52.079> would<00:37:52.240> venture<00:37:52.560> to<00:37:52.640> say<00:37:52.800> i've<00:37:53.119> had 00:37:53.190 --> 00:37:53.200 align:start position:0% i would venture to say i've had 00:37:53.200 --> 00:37:54.790 align:start position:0% i would venture to say i've had conversations<00:37:53.760> with<00:37:53.920> eric<00:37:54.240> about<00:37:54.480> how<00:37:54.640> we're 00:37:54.790 --> 00:37:54.800 align:start position:0% conversations with eric about how we're 00:37:54.800 --> 00:37:56.710 align:start position:0% conversations with eric about how we're going<00:37:54.880> to<00:37:54.960> handle<00:37:55.280> the<00:37:55.359> duck<00:37:55.599> curve<00:37:55.920> in 00:37:56.710 --> 00:37:56.720 align:start position:0% going to handle the duck curve in 00:37:56.720 --> 00:37:58.790 align:start position:0% going to handle the duck curve in in<00:37:56.800> the<00:37:56.960> interim<00:37:57.359> because 00:37:58.790 --> 00:37:58.800 align:start position:0% in the interim because 00:37:58.800 --> 00:38:00.550 align:start position:0% in the interim because as<00:37:59.040> we<00:37:59.119> know<00:37:59.280> we've<00:37:59.520> seen<00:37:59.680> a<00:37:59.760> little<00:38:00.000> bit<00:38:00.160> of<00:38:00.320> it 00:38:00.550 --> 00:38:00.560 align:start position:0% as we know we've seen a little bit of it 00:38:00.560 --> 00:38:03.670 align:start position:0% as we know we've seen a little bit of it and<00:38:00.800> and<00:38:01.040> it's<00:38:01.680> more<00:38:02.560> pronounced<00:38:03.280> it<00:38:03.359> will<00:38:03.520> be 00:38:03.670 --> 00:38:03.680 align:start position:0% and and it's more pronounced it will be 00:38:03.680 --> 00:38:05.349 align:start position:0% and and it's more pronounced it will be more<00:38:03.920> pronounced<00:38:04.320> in<00:38:04.400> the 00:38:05.349 --> 00:38:05.359 align:start position:0% more pronounced in the 00:38:05.359 --> 00:38:07.190 align:start position:0% more pronounced in the in<00:38:05.520> the<00:38:05.760> years<00:38:06.079> to<00:38:06.240> come<00:38:06.560> perhaps<00:38:06.960> in<00:38:07.119> the 00:38:07.190 --> 00:38:07.200 align:start position:0% in the years to come perhaps in the 00:38:07.200 --> 00:38:08.630 align:start position:0% in the years to come perhaps in the winter<00:38:07.520> in<00:38:07.599> the<00:38:07.760> spring 00:38:08.630 --> 00:38:08.640 align:start position:0% winter in the spring 00:38:08.640 --> 00:38:10.550 align:start position:0% winter in the spring and<00:38:08.800> so<00:38:08.960> what<00:38:09.119> do<00:38:09.200> we<00:38:09.280> do<00:38:09.599> from<00:38:09.839> now<00:38:10.160> until<00:38:10.480> the 00:38:10.550 --> 00:38:10.560 align:start position:0% and so what do we do from now until the 00:38:10.560 --> 00:38:12.390 align:start position:0% and so what do we do from now until the ecrs<00:38:11.040> is<00:38:11.119> put<00:38:11.280> in<00:38:11.440> place<00:38:11.680> and<00:38:11.839> and<00:38:12.000> so<00:38:12.240> what 00:38:12.390 --> 00:38:12.400 align:start position:0% ecrs is put in place and and so what 00:38:12.400 --> 00:38:14.630 align:start position:0% ecrs is put in place and and so what i've<00:38:12.560> gotten<00:38:12.880> feedback<00:38:13.359> is<00:38:13.599> you<00:38:13.760> know<00:38:13.920> ordc<00:38:14.480> is 00:38:14.630 --> 00:38:14.640 align:start position:0% i've gotten feedback is you know ordc is 00:38:14.640 --> 00:38:16.829 align:start position:0% i've gotten feedback is you know ordc is important<00:38:15.359> and<00:38:15.520> they'll<00:38:15.760> continue<00:38:16.160> to<00:38:16.240> use 00:38:16.829 --> 00:38:16.839 align:start position:0% important and they'll continue to use 00:38:16.839 --> 00:38:19.750 align:start position:0% important and they'll continue to use non-spin<00:38:18.079> as<00:38:18.320> the<00:38:18.480> tools<00:38:18.800> to<00:38:19.200> to<00:38:19.359> address<00:38:19.680> the 00:38:19.750 --> 00:38:19.760 align:start position:0% non-spin as the tools to to address the 00:38:19.760 --> 00:38:22.310 align:start position:0% non-spin as the tools to to address the duct<00:38:20.000> curve<00:38:20.240> in<00:38:20.320> the<00:38:20.400> future<00:38:20.800> it'll<00:38:20.960> be<00:38:21.200> ordc 00:38:22.310 --> 00:38:22.320 align:start position:0% duct curve in the future it'll be ordc 00:38:22.320 --> 00:38:24.710 align:start position:0% duct curve in the future it'll be ordc non-spin<00:38:22.960> and<00:38:23.040> ecrs 00:38:24.710 --> 00:38:24.720 align:start position:0% non-spin and ecrs 00:38:24.720 --> 00:38:26.069 align:start position:0% non-spin and ecrs and<00:38:24.960> so 00:38:26.069 --> 00:38:26.079 align:start position:0% and so 00:38:26.079 --> 00:38:28.310 align:start position:0% and so ercot<00:38:26.560> will<00:38:26.640> have<00:38:26.880> its<00:38:27.040> line<00:38:27.280> of<00:38:27.440> tools<00:38:28.160> to 00:38:28.310 --> 00:38:28.320 align:start position:0% ercot will have its line of tools to 00:38:28.320 --> 00:38:29.829 align:start position:0% ercot will have its line of tools to address<00:38:28.720> that 00:38:29.829 --> 00:38:29.839 align:start position:0% address that 00:38:29.839 --> 00:38:31.910 align:start position:0% address that but<00:38:30.000> i<00:38:30.320> do<00:38:30.480> want<00:38:30.640> to<00:38:30.720> say<00:38:30.960> that<00:38:31.440> at<00:38:31.520> the<00:38:31.599> back 00:38:31.910 --> 00:38:31.920 align:start position:0% but i do want to say that at the back 00:38:31.920 --> 00:38:34.470 align:start position:0% but i do want to say that at the back end<00:38:32.160> you<00:38:32.240> know<00:38:32.480> if<00:38:32.720> we<00:38:32.880> are<00:38:33.040> flooded<00:38:33.599> as<00:38:33.760> you 00:38:34.470 --> 00:38:34.480 align:start position:0% end you know if we are flooded as you 00:38:34.480 --> 00:38:37.349 align:start position:0% end you know if we are flooded as you you<00:38:34.880> um<00:38:35.280> are<00:38:35.680> uh<00:38:35.920> projecting 00:38:37.349 --> 00:38:37.359 align:start position:0% you um are uh projecting 00:38:37.359 --> 00:38:38.630 align:start position:0% you um are uh projecting you<00:38:37.440> know<00:38:37.599> we're<00:38:37.680> gonna<00:38:37.839> have<00:38:37.920> to<00:38:38.000> decide<00:38:38.560> if 00:38:38.630 --> 00:38:38.640 align:start position:0% you know we're gonna have to decide if 00:38:38.640 --> 00:38:40.950 align:start position:0% you know we're gonna have to decide if we're<00:38:38.800> just<00:38:38.960> gonna<00:38:39.119> rely<00:38:39.440> on<00:38:39.680> pure<00:38:39.920> ecrs<00:38:40.640> or 00:38:40.950 --> 00:38:40.960 align:start position:0% we're just gonna rely on pure ecrs or 00:38:40.960 --> 00:38:42.390 align:start position:0% we're just gonna rely on pure ecrs or we're<00:38:41.119> gonna<00:38:41.280> have<00:38:41.440> some<00:38:41.599> kind<00:38:41.760> of<00:38:41.920> strategic 00:38:42.390 --> 00:38:42.400 align:start position:0% we're gonna have some kind of strategic 00:38:42.400 --> 00:38:44.150 align:start position:0% we're gonna have some kind of strategic reliability<00:38:42.960> service<00:38:43.359> out<00:38:43.520> there<00:38:43.680> to<00:38:43.839> help<00:38:44.000> us 00:38:44.150 --> 00:38:44.160 align:start position:0% reliability service out there to help us 00:38:44.160 --> 00:38:46.390 align:start position:0% reliability service out there to help us if<00:38:44.320> we're<00:38:44.480> really<00:38:45.280> in<00:38:45.440> a<00:38:45.520> bind<00:38:45.839> with<00:38:46.000> that<00:38:46.160> much 00:38:46.390 --> 00:38:46.400 align:start position:0% if we're really in a bind with that much 00:38:46.400 --> 00:38:47.670 align:start position:0% if we're really in a bind with that much solder<00:38:46.720> on<00:38:46.800> the<00:38:46.880> system<00:38:47.200> so<00:38:47.280> i<00:38:47.359> just<00:38:47.520> want<00:38:47.599> to 00:38:47.670 --> 00:38:47.680 align:start position:0% solder on the system so i just want to 00:38:47.680 --> 00:38:49.190 align:start position:0% solder on the system so i just want to put<00:38:47.839> that<00:38:48.000> on<00:38:48.079> the<00:38:48.160> table 00:38:49.190 --> 00:38:49.200 align:start position:0% put that on the table 00:38:49.200 --> 00:38:51.510 align:start position:0% put that on the table as<00:38:49.440> a<00:38:49.680> as<00:38:49.839> a<00:38:49.920> placeholder 00:38:51.510 --> 00:38:51.520 align:start position:0% as a as a placeholder 00:38:51.520 --> 00:38:53.750 align:start position:0% as a as a placeholder just<00:38:51.920> to<00:38:52.079> kind<00:38:52.240> of<00:38:52.320> think<00:38:52.560> about<00:38:52.960> because<00:38:53.599> you 00:38:53.750 --> 00:38:53.760 align:start position:0% just to kind of think about because you 00:38:53.760 --> 00:38:56.230 align:start position:0% just to kind of think about because you know<00:38:53.920> as<00:38:54.000> you've<00:38:54.160> mentioned<00:38:54.560> sp3 00:38:56.230 --> 00:38:56.240 align:start position:0% know as you've mentioned sp3 00:38:56.240 --> 00:38:58.069 align:start position:0% know as you've mentioned sp3 sp3<00:38:56.800> does<00:38:56.960> a<00:38:57.040> lot<00:38:57.200> of<00:38:57.280> talking<00:38:57.680> about 00:38:58.069 --> 00:38:58.079 align:start position:0% sp3 does a lot of talking about 00:38:58.079 --> 00:38:59.829 align:start position:0% sp3 does a lot of talking about ancillary<00:38:58.640> services<00:38:59.119> and<00:38:59.200> reliability 00:38:59.829 --> 00:38:59.839 align:start position:0% ancillary services and reliability 00:38:59.839 --> 00:39:01.510 align:start position:0% ancillary services and reliability services<00:39:00.320> and<00:39:00.480> i<00:39:00.560> think<00:39:00.800> that 00:39:01.510 --> 00:39:01.520 align:start position:0% services and i think that 00:39:01.520 --> 00:39:04.230 align:start position:0% services and i think that um 00:39:04.230 --> 00:39:04.240 align:start position:0% 00:39:04.240 --> 00:39:05.589 align:start position:0% sp3<00:39:04.640> does<00:39:04.880> a<00:39:04.880> lot<00:39:05.040> of<00:39:05.119> talking<00:39:05.359> about 00:39:05.589 --> 00:39:05.599 align:start position:0% sp3 does a lot of talking about 00:39:05.599 --> 00:39:07.349 align:start position:0% sp3 does a lot of talking about reliability<00:39:06.320> services<00:39:06.720> and<00:39:06.880> ancillary 00:39:07.349 --> 00:39:07.359 align:start position:0% reliability services and ancillary 00:39:07.359 --> 00:39:09.990 align:start position:0% reliability services and ancillary services<00:39:07.760> so<00:39:07.920> we<00:39:08.079> have<00:39:08.640> full<00:39:09.359> authority<00:39:09.839> from 00:39:09.990 --> 00:39:10.000 align:start position:0% services so we have full authority from 00:39:10.000 --> 00:39:12.470 align:start position:0% services so we have full authority from the<00:39:10.160> legislature<00:39:11.280> to<00:39:11.440> utilize<00:39:12.079> those<00:39:12.240> two 00:39:12.470 --> 00:39:12.480 align:start position:0% the legislature to utilize those two 00:39:12.480 --> 00:39:14.470 align:start position:0% the legislature to utilize those two mechanisms<00:39:13.119> to<00:39:13.280> address<00:39:14.079> not<00:39:14.240> only 00:39:14.470 --> 00:39:14.480 align:start position:0% mechanisms to address not only 00:39:14.480 --> 00:39:16.630 align:start position:0% mechanisms to address not only operational<00:39:15.119> issues<00:39:15.440> but<00:39:15.839> um 00:39:16.630 --> 00:39:16.640 align:start position:0% operational issues but um 00:39:16.640 --> 00:39:19.109 align:start position:0% operational issues but um you<00:39:16.720> know<00:39:17.280> overall<00:39:17.680> reliability<00:39:18.400> and<00:39:18.800> supply 00:39:19.109 --> 00:39:19.119 align:start position:0% you know overall reliability and supply 00:39:19.119 --> 00:39:21.270 align:start position:0% you know overall reliability and supply adequacy<00:39:19.680> issues<00:39:19.920> so<00:39:20.079> i<00:39:20.160> just<00:39:20.320> want<00:39:20.480> to 00:39:21.270 --> 00:39:21.280 align:start position:0% adequacy issues so i just want to 00:39:21.280 --> 00:39:23.670 align:start position:0% adequacy issues so i just want to you<00:39:21.440> know<00:39:21.599> dovetail<00:39:22.079> that<00:39:22.240> into<00:39:22.480> your 00:39:23.670 --> 00:39:23.680 align:start position:0% you know dovetail that into your 00:39:23.680 --> 00:39:25.349 align:start position:0% you know dovetail that into your your<00:39:24.000> um 00:39:25.349 --> 00:39:25.359 align:start position:0% your um 00:39:25.359 --> 00:39:27.670 align:start position:0% your um your<00:39:25.520> briefing<00:39:25.920> thank<00:39:26.160> you 00:39:27.670 --> 00:39:27.680 align:start position:0% your briefing thank you 00:39:27.680 --> 00:39:30.230 align:start position:0% your briefing thank you very<00:39:28.000> important<00:39:28.320> question<00:39:28.640> lauren 00:39:30.230 --> 00:39:30.240 align:start position:0% very important question lauren 00:39:30.240 --> 00:39:31.190 align:start position:0% very important question lauren um 00:39:31.190 --> 00:39:31.200 align:start position:0% um 00:39:31.200 --> 00:39:32.710 align:start position:0% um thank<00:39:31.359> you<00:39:31.520> i<00:39:31.599> appreciate<00:39:32.000> you<00:39:32.240> putting<00:39:32.560> this 00:39:32.710 --> 00:39:32.720 align:start position:0% thank you i appreciate you putting this 00:39:32.720 --> 00:39:34.550 align:start position:0% thank you i appreciate you putting this in<00:39:32.800> the<00:39:32.880> record<00:39:33.280> and<00:39:33.599> letting<00:39:33.920> us<00:39:34.079> discuss 00:39:34.550 --> 00:39:34.560 align:start position:0% in the record and letting us discuss 00:39:34.560 --> 00:39:36.630 align:start position:0% in the record and letting us discuss this 00:39:36.630 --> 00:39:36.640 align:start position:0% this 00:39:36.640 --> 00:39:38.550 align:start position:0% this the<00:39:36.960> uh 00:39:38.550 --> 00:39:38.560 align:start position:0% the uh 00:39:38.560 --> 00:39:40.550 align:start position:0% the uh we<00:39:38.720> got<00:39:38.880> a<00:39:39.200> big<00:39:39.359> challenge<00:39:39.760> in<00:39:39.839> front<00:39:40.000> of<00:39:40.160> us<00:39:40.400> we 00:39:40.550 --> 00:39:40.560 align:start position:0% we got a big challenge in front of us we 00:39:40.560 --> 00:39:42.150 align:start position:0% we got a big challenge in front of us we got<00:39:40.640> to<00:39:40.720> learn<00:39:40.960> from<00:39:41.200> all<00:39:41.359> of<00:39:41.520> those<00:39:41.680> other 00:39:42.150 --> 00:39:42.160 align:start position:0% got to learn from all of those other 00:39:42.160 --> 00:39:45.430 align:start position:0% got to learn from all of those other places<00:39:42.640> that<00:39:42.880> have<00:39:43.440> a<00:39:43.599> massive<00:39:44.000> duck<00:39:44.320> curve 00:39:45.430 --> 00:39:45.440 align:start position:0% places that have a massive duck curve 00:39:45.440 --> 00:39:46.390 align:start position:0% places that have a massive duck curve um 00:39:46.390 --> 00:39:46.400 align:start position:0% um 00:39:46.400 --> 00:39:48.230 align:start position:0% um and 00:39:48.230 --> 00:39:48.240 align:start position:0% and 00:39:48.240 --> 00:39:49.670 align:start position:0% and i<00:39:48.320> don't<00:39:48.480> know<00:39:48.560> that<00:39:48.720> we're<00:39:49.119> totally<00:39:49.440> doing 00:39:49.670 --> 00:39:49.680 align:start position:0% i don't know that we're totally doing 00:39:49.680 --> 00:39:51.670 align:start position:0% i don't know that we're totally doing that<00:39:50.000> but<00:39:50.240> uh<00:39:50.560> we<00:39:50.720> are<00:39:50.880> texans<00:39:51.280> and<00:39:51.359> we<00:39:51.520> will 00:39:51.670 --> 00:39:51.680 align:start position:0% that but uh we are texans and we will 00:39:51.680 --> 00:39:53.829 align:start position:0% that but uh we are texans and we will kind<00:39:51.839> of<00:39:51.920> create<00:39:52.240> our<00:39:52.400> own<00:39:52.640> path<00:39:52.960> but 00:39:53.829 --> 00:39:53.839 align:start position:0% kind of create our own path but 00:39:53.839 --> 00:39:57.030 align:start position:0% kind of create our own path but um<00:39:54.480> the<00:39:54.720> one<00:39:54.880> thing<00:39:55.040> that<00:39:55.520> um<00:39:56.240> about<00:39:56.560> this 00:39:57.030 --> 00:39:57.040 align:start position:0% um the one thing that um about this 00:39:57.040 --> 00:39:58.230 align:start position:0% um the one thing that um about this curve 00:39:58.230 --> 00:39:58.240 align:start position:0% curve 00:39:58.240 --> 00:40:00.710 align:start position:0% curve that<00:39:58.640> i<00:39:58.880> think<00:39:59.280> is<00:39:59.760> um 00:40:00.710 --> 00:40:00.720 align:start position:0% that i think is um 00:40:00.720 --> 00:40:03.030 align:start position:0% that i think is um i<00:40:00.800> think<00:40:01.040> it's<00:40:01.200> an<00:40:01.440> incomplete<00:40:02.000> picture 00:40:03.030 --> 00:40:03.040 align:start position:0% i think it's an incomplete picture 00:40:03.040 --> 00:40:05.910 align:start position:0% i think it's an incomplete picture of<00:40:03.440> what's<00:40:03.680> going<00:40:03.760> to<00:40:03.920> happen<00:40:04.319> on<00:40:04.480> our<00:40:04.640> system 00:40:05.910 --> 00:40:05.920 align:start position:0% of what's going to happen on our system 00:40:05.920 --> 00:40:07.829 align:start position:0% of what's going to happen on our system this<00:40:06.240> is<00:40:06.640> a 00:40:07.829 --> 00:40:07.839 align:start position:0% this is a 00:40:07.839 --> 00:40:08.870 align:start position:0% this is a a 00:40:08.870 --> 00:40:08.880 align:start position:0% a 00:40:08.880 --> 00:40:10.550 align:start position:0% a net<00:40:09.280> load<00:40:09.599> profile 00:40:10.550 --> 00:40:10.560 align:start position:0% net load profile 00:40:10.560 --> 00:40:12.309 align:start position:0% net load profile and<00:40:10.720> it<00:40:10.800> doesn't<00:40:11.200> address<00:40:11.680> and<00:40:11.839> it<00:40:11.920> doesn't 00:40:12.309 --> 00:40:12.319 align:start position:0% and it doesn't address and it doesn't 00:40:12.319 --> 00:40:15.030 align:start position:0% and it doesn't address and it doesn't show<00:40:12.720> any<00:40:12.960> of<00:40:13.119> the<00:40:13.200> resources<00:40:14.160> that<00:40:14.400> are<00:40:14.560> used 00:40:15.030 --> 00:40:15.040 align:start position:0% show any of the resources that are used 00:40:15.040 --> 00:40:16.870 align:start position:0% show any of the resources that are used to<00:40:15.200> reduce<00:40:15.599> that<00:40:15.839> duct<00:40:16.079> curve<00:40:16.400> that<00:40:16.480> we<00:40:16.640> have 00:40:16.870 --> 00:40:16.880 align:start position:0% to reduce that duct curve that we have 00:40:16.880 --> 00:40:18.230 align:start position:0% to reduce that duct curve that we have today 00:40:18.230 --> 00:40:18.240 align:start position:0% today 00:40:18.240 --> 00:40:21.030 align:start position:0% today so<00:40:18.720> this<00:40:18.960> duct<00:40:19.280> curve<00:40:19.599> may<00:40:20.079> we<00:40:20.240> may<00:40:20.480> have<00:40:20.720> only 00:40:21.030 --> 00:40:21.040 align:start position:0% so this duct curve may we may have only 00:40:21.040 --> 00:40:23.190 align:start position:0% so this duct curve may we may have only 10<00:40:21.200> percent<00:40:21.520> of<00:40:21.599> that<00:40:22.000> that<00:40:22.079> we<00:40:22.240> have<00:40:22.400> to<00:40:22.560> solve 00:40:23.190 --> 00:40:23.200 align:start position:0% 10 percent of that that we have to solve 00:40:23.200 --> 00:40:25.349 align:start position:0% 10 percent of that that we have to solve we<00:40:23.359> may<00:40:23.520> have<00:40:23.760> 50<00:40:24.400> of<00:40:24.480> it<00:40:24.640> that<00:40:24.800> we<00:40:24.960> have<00:40:25.119> to 00:40:25.349 --> 00:40:25.359 align:start position:0% we may have 50 of it that we have to 00:40:25.359 --> 00:40:27.430 align:start position:0% we may have 50 of it that we have to solve<00:40:25.920> and<00:40:26.079> i<00:40:26.160> would<00:40:26.400> say<00:40:26.640> that<00:40:26.960> fill<00:40:27.119> in<00:40:27.280> those 00:40:27.430 --> 00:40:27.440 align:start position:0% solve and i would say that fill in those 00:40:27.440 --> 00:40:29.109 align:start position:0% solve and i would say that fill in those resources<00:40:28.000> for<00:40:28.160> us 00:40:29.109 --> 00:40:29.119 align:start position:0% resources for us 00:40:29.119 --> 00:40:31.430 align:start position:0% resources for us well<00:40:29.599> anything<00:40:30.079> that<00:40:30.319> is<00:40:30.480> used<00:40:30.960> that<00:40:31.119> can<00:40:31.280> be 00:40:31.430 --> 00:40:31.440 align:start position:0% well anything that is used that can be 00:40:31.440 --> 00:40:32.870 align:start position:0% well anything that is used that can be used<00:40:31.920> to 00:40:32.870 --> 00:40:32.880 align:start position:0% used to 00:40:32.880 --> 00:40:35.109 align:start position:0% used to minimize<00:40:33.520> this<00:40:33.839> ramp 00:40:35.109 --> 00:40:35.119 align:start position:0% minimize this ramp 00:40:35.119 --> 00:40:37.829 align:start position:0% minimize this ramp so<00:40:35.520> any<00:40:35.760> combined<00:40:36.240> cycle<00:40:36.720> any<00:40:36.960> simple<00:40:37.359> cycle 00:40:37.829 --> 00:40:37.839 align:start position:0% so any combined cycle any simple cycle 00:40:37.839 --> 00:40:41.109 align:start position:0% so any combined cycle any simple cycle any<00:40:38.079> battery<00:40:38.720> anything<00:40:39.280> any<00:40:39.520> demand<00:40:39.920> response 00:40:41.109 --> 00:40:41.119 align:start position:0% any battery anything any demand response 00:40:41.119 --> 00:40:43.670 align:start position:0% any battery anything any demand response any<00:40:41.680> you<00:40:41.839> know<00:40:42.400> spinning<00:40:42.800> reserve<00:40:43.280> that<00:40:43.440> can 00:40:43.670 --> 00:40:43.680 align:start position:0% any you know spinning reserve that can 00:40:43.680 --> 00:40:44.550 align:start position:0% any you know spinning reserve that can be 00:40:44.550 --> 00:40:44.560 align:start position:0% be 00:40:44.560 --> 00:40:45.349 align:start position:0% be um 00:40:45.349 --> 00:40:45.359 align:start position:0% um 00:40:45.359 --> 00:40:47.910 align:start position:0% um used<00:40:46.000> during<00:40:46.319> a<00:40:46.480> two<00:40:46.720> hour<00:40:46.960> window<00:40:47.280> to<00:40:47.440> solve<00:40:47.760> a 00:40:47.910 --> 00:40:47.920 align:start position:0% used during a two hour window to solve a 00:40:47.920 --> 00:40:51.190 align:start position:0% used during a two hour window to solve a ramp<00:40:48.720> is<00:40:49.040> not<00:40:49.359> in<00:40:49.839> it's<00:40:50.000> not<00:40:50.240> shown<00:40:50.560> here<00:40:51.040> so 00:40:51.190 --> 00:40:51.200 align:start position:0% ramp is not in it's not shown here so 00:40:51.200 --> 00:40:55.109 align:start position:0% ramp is not in it's not shown here so it's<00:40:51.359> only<00:40:51.599> half<00:40:51.920> the<00:40:52.079> story<00:40:53.040> so<00:40:53.359> to<00:40:53.520> me 00:40:55.109 --> 00:40:55.119 align:start position:0% it's only half the story so to me 00:40:55.119 --> 00:40:58.470 align:start position:0% it's only half the story so to me this<00:40:55.440> is<00:40:55.680> a<00:40:56.000> story<00:40:56.720> this<00:40:56.880> is<00:40:57.040> a<00:40:57.280> very<00:40:58.079> important 00:40:58.470 --> 00:40:58.480 align:start position:0% this is a story this is a very important 00:40:58.480 --> 00:41:01.670 align:start position:0% this is a story this is a very important story<00:40:58.800> to<00:40:58.960> tell<00:40:59.599> the<00:40:59.839> other<00:41:00.160> story<00:41:00.480> to<00:41:00.640> tell<00:41:01.119> is 00:41:01.670 --> 00:41:01.680 align:start position:0% story to tell the other story to tell is 00:41:01.680 --> 00:41:04.069 align:start position:0% story to tell the other story to tell is where<00:41:02.000> are<00:41:02.079> we<00:41:02.319> short 00:41:04.069 --> 00:41:04.079 align:start position:0% where are we short 00:41:04.079 --> 00:41:07.190 align:start position:0% where are we short and<00:41:04.319> this<00:41:04.560> doesn't<00:41:04.880> tell<00:41:05.119> that<00:41:05.359> story 00:41:07.190 --> 00:41:07.200 align:start position:0% and this doesn't tell that story 00:41:07.200 --> 00:41:09.349 align:start position:0% and this doesn't tell that story are<00:41:07.280> we<00:41:07.520> short<00:41:08.079> we<00:41:08.240> mean<00:41:08.400> short 00:41:09.349 --> 00:41:09.359 align:start position:0% are we short we mean short 00:41:09.359 --> 00:41:12.630 align:start position:0% are we short we mean short so<00:41:09.599> i<00:41:09.839> i<00:41:10.000> what<00:41:10.240> i<00:41:10.400> mean<00:41:10.800> is<00:41:11.119> this<00:41:11.520> doesn't<00:41:12.000> show 00:41:12.630 --> 00:41:12.640 align:start position:0% so i i what i mean is this doesn't show 00:41:12.640 --> 00:41:14.790 align:start position:0% so i i what i mean is this doesn't show the<00:41:12.880> resources<00:41:13.520> that<00:41:13.680> we<00:41:13.839> have<00:41:14.079> on<00:41:14.319> the<00:41:14.400> system 00:41:14.790 --> 00:41:14.800 align:start position:0% the resources that we have on the system 00:41:14.800 --> 00:41:18.870 align:start position:0% the resources that we have on the system today<00:41:15.599> that<00:41:16.000> solve<00:41:16.319> this<00:41:16.560> duck<00:41:16.800> curve<00:41:17.119> problem 00:41:18.870 --> 00:41:18.880 align:start position:0% today that solve this duck curve problem 00:41:18.880 --> 00:41:19.589 align:start position:0% today that solve this duck curve problem yeah 00:41:19.589 --> 00:41:19.599 align:start position:0% yeah 00:41:19.599 --> 00:41:23.430 align:start position:0% yeah so<00:41:20.160> so<00:41:20.400> if<00:41:20.640> we<00:41:21.280> what<00:41:21.440> we<00:41:22.079> what<00:41:22.720> would<00:41:22.880> be<00:41:23.040> useful 00:41:23.430 --> 00:41:23.440 align:start position:0% so so if we what we what would be useful 00:41:23.440 --> 00:41:24.470 align:start position:0% so so if we what we what would be useful to<00:41:23.599> me 00:41:24.470 --> 00:41:24.480 align:start position:0% to me 00:41:24.480 --> 00:41:27.510 align:start position:0% to me is<00:41:24.640> to<00:41:24.800> understand<00:41:25.599> you<00:41:25.680> know<00:41:25.920> you<00:41:26.319> overlay 00:41:27.510 --> 00:41:27.520 align:start position:0% is to understand you know you overlay 00:41:27.520 --> 00:41:31.670 align:start position:0% is to understand you know you overlay um<00:41:28.160> a<00:41:28.800> supply<00:41:29.440> side<00:41:30.000> component<00:41:30.480> to<00:41:30.640> this 00:41:31.670 --> 00:41:31.680 align:start position:0% um a supply side component to this 00:41:31.680 --> 00:41:33.349 align:start position:0% um a supply side component to this so<00:41:31.920> what<00:41:32.160> are<00:41:32.319> the<00:41:32.480> tools<00:41:32.800> that<00:41:32.880> we<00:41:33.040> have<00:41:33.280> and 00:41:33.349 --> 00:41:33.359 align:start position:0% so what are the tools that we have and 00:41:33.359 --> 00:41:35.910 align:start position:0% so what are the tools that we have and what<00:41:33.520> are<00:41:33.599> the<00:41:33.839> resources<00:41:34.640> that<00:41:34.880> we<00:41:35.119> have<00:41:35.760> the 00:41:35.910 --> 00:41:35.920 align:start position:0% what are the resources that we have the 00:41:35.920 --> 00:41:38.069 align:start position:0% what are the resources that we have the generation<00:41:36.720> the<00:41:36.800> demand<00:41:37.200> response<00:41:37.920> the 00:41:38.069 --> 00:41:38.079 align:start position:0% generation the demand response the 00:41:38.079 --> 00:41:40.230 align:start position:0% generation the demand response the batteries<00:41:38.880> that<00:41:39.200> help<00:41:39.520> solve<00:41:39.760> this<00:41:40.000> duct 00:41:40.230 --> 00:41:40.240 align:start position:0% batteries that help solve this duct 00:41:40.240 --> 00:41:43.109 align:start position:0% batteries that help solve this duct curve<00:41:40.800> problem<00:41:41.359> okay<00:41:42.079> and<00:41:42.240> then<00:41:42.480> what<00:41:42.640> we<00:41:42.880> do 00:41:43.109 --> 00:41:43.119 align:start position:0% curve problem okay and then what we do 00:41:43.119 --> 00:41:46.069 align:start position:0% curve problem okay and then what we do is<00:41:43.359> we<00:41:43.839> when<00:41:44.000> we<00:41:44.240> see<00:41:44.480> that<00:41:44.800> picture<00:41:45.599> what<00:41:45.839> i 00:41:46.069 --> 00:41:46.079 align:start position:0% is we when we see that picture what i 00:41:46.079 --> 00:41:49.030 align:start position:0% is we when we see that picture what i see<00:41:46.400> is<00:41:46.720> a<00:41:46.960> delta<00:41:47.280> between<00:41:47.599> what<00:41:47.760> we<00:41:48.000> have 00:41:49.030 --> 00:41:49.040 align:start position:0% see is a delta between what we have 00:41:49.040 --> 00:41:50.950 align:start position:0% see is a delta between what we have and<00:41:49.200> what<00:41:49.440> we<00:41:49.599> need 00:41:50.950 --> 00:41:50.960 align:start position:0% and what we need 00:41:50.960 --> 00:41:53.270 align:start position:0% and what we need and<00:41:51.119> then<00:41:51.280> we<00:41:51.520> create<00:41:51.839> products<00:41:52.240> to<00:41:52.400> solve 00:41:53.270 --> 00:41:53.280 align:start position:0% and then we create products to solve 00:41:53.280 --> 00:41:56.790 align:start position:0% and then we create products to solve that<00:41:53.839> not<00:41:54.240> an<00:41:54.400> entire<00:41:54.960> 20<00:41:55.359> 000<00:41:55.599> megawatt<00:41:56.480> duct 00:41:56.790 --> 00:41:56.800 align:start position:0% that not an entire 20 000 megawatt duct 00:41:56.800 --> 00:41:58.150 align:start position:0% that not an entire 20 000 megawatt duct curve<00:41:57.280> because 00:41:58.150 --> 00:41:58.160 align:start position:0% curve because 00:41:58.160 --> 00:42:00.390 align:start position:0% curve because while<00:41:58.400> that<00:41:58.720> is<00:41:59.440> the<00:41:59.680> problem<00:42:00.000> it's<00:42:00.240> not 00:42:00.390 --> 00:42:00.400 align:start position:0% while that is the problem it's not 00:42:00.400 --> 00:42:03.750 align:start position:0% while that is the problem it's not taking<00:42:00.720> into<00:42:00.880> consideration<00:42:02.240> any<00:42:02.640> cts 00:42:03.750 --> 00:42:03.760 align:start position:0% taking into consideration any cts 00:42:03.760 --> 00:42:04.630 align:start position:0% taking into consideration any cts any 00:42:04.630 --> 00:42:04.640 align:start position:0% any 00:42:04.640 --> 00:42:07.270 align:start position:0% any combined<00:42:05.040> cycle<00:42:05.440> plants<00:42:06.079> any<00:42:06.480> batteries<00:42:06.960> or 00:42:07.270 --> 00:42:07.280 align:start position:0% combined cycle plants any batteries or 00:42:07.280 --> 00:42:09.270 align:start position:0% combined cycle plants any batteries or anything<00:42:08.160> that<00:42:08.400> are<00:42:08.480> used<00:42:08.720> to<00:42:08.800> help<00:42:09.040> solve 00:42:09.270 --> 00:42:09.280 align:start position:0% anything that are used to help solve 00:42:09.280 --> 00:42:11.670 align:start position:0% anything that are used to help solve that<00:42:09.520> problem<00:42:10.000> so<00:42:10.319> what<00:42:10.560> i<00:42:10.720> hope<00:42:10.960> is<00:42:11.119> that<00:42:11.520> we 00:42:11.670 --> 00:42:11.680 align:start position:0% that problem so what i hope is that we 00:42:11.680 --> 00:42:13.430 align:start position:0% that problem so what i hope is that we could<00:42:11.839> get<00:42:12.000> from<00:42:12.240> our<00:42:12.319> cot<00:42:12.640> another<00:42:13.040> picture 00:42:13.430 --> 00:42:13.440 align:start position:0% could get from our cot another picture 00:42:13.440 --> 00:42:16.230 align:start position:0% could get from our cot another picture of<00:42:13.599> this<00:42:14.319> with<00:42:14.640> both<00:42:14.960> of<00:42:15.040> those<00:42:15.520> included<00:42:16.079> in 00:42:16.230 --> 00:42:16.240 align:start position:0% of this with both of those included in 00:42:16.240 --> 00:42:18.710 align:start position:0% of this with both of those included in there<00:42:16.640> so<00:42:16.960> i<00:42:17.119> could<00:42:17.359> quantify<00:42:17.839> in<00:42:18.000> my<00:42:18.160> head 00:42:18.710 --> 00:42:18.720 align:start position:0% there so i could quantify in my head 00:42:18.720 --> 00:42:21.430 align:start position:0% there so i could quantify in my head what<00:42:18.960> that<00:42:19.280> actual<00:42:19.760> problem<00:42:20.160> is<00:42:20.800> i'm<00:42:21.119> sure<00:42:21.280> we 00:42:21.430 --> 00:42:21.440 align:start position:0% what that actual problem is i'm sure we 00:42:21.440 --> 00:42:23.430 align:start position:0% what that actual problem is i'm sure we have<00:42:21.520> somebody<00:42:21.760> from<00:42:22.000> our<00:42:22.160> cot 00:42:23.430 --> 00:42:23.440 align:start position:0% have somebody from our cot 00:42:23.440 --> 00:42:25.109 align:start position:0% have somebody from our cot and<00:42:23.599> while<00:42:23.760> they<00:42:23.920> make<00:42:24.079> their<00:42:24.240> way<00:42:24.400> up<00:42:24.480> here<00:42:24.960> if 00:42:25.109 --> 00:42:25.119 align:start position:0% and while they make their way up here if 00:42:25.119 --> 00:42:26.790 align:start position:0% and while they make their way up here if they<00:42:25.280> are<00:42:25.839> um 00:42:26.790 --> 00:42:26.800 align:start position:0% they are um 00:42:26.800 --> 00:42:31.190 align:start position:0% they are um i<00:42:27.119> am<00:42:27.440> sorry<00:42:28.079> who's<00:42:28.319> the<00:42:28.720> sorry 00:42:31.190 --> 00:42:31.200 align:start position:0% 00:42:31.200 --> 00:42:32.550 align:start position:0% i<00:42:31.359> echo<00:42:31.599> what<00:42:31.760> jimmy's<00:42:32.000> saying<00:42:32.319> and<00:42:32.400> that's 00:42:32.550 --> 00:42:32.560 align:start position:0% i echo what jimmy's saying and that's 00:42:32.560 --> 00:42:33.910 align:start position:0% i echo what jimmy's saying and that's kind<00:42:32.640> of<00:42:32.720> what<00:42:32.880> i<00:42:32.960> mean<00:42:33.359> what<00:42:33.520> i<00:42:33.599> was<00:42:33.680> trying<00:42:33.839> to 00:42:33.910 --> 00:42:33.920 align:start position:0% kind of what i mean what i was trying to 00:42:33.920 --> 00:42:35.589 align:start position:0% kind of what i mean what i was trying to say<00:42:34.160> earlier<00:42:34.480> is<00:42:34.560> that<00:42:34.640> we<00:42:34.800> need<00:42:34.880> to<00:42:35.040> fine-tune 00:42:35.589 --> 00:42:35.599 align:start position:0% say earlier is that we need to fine-tune 00:42:35.599 --> 00:42:37.270 align:start position:0% say earlier is that we need to fine-tune it<00:42:35.760> to<00:42:35.920> see<00:42:36.400> you<00:42:36.560> know 00:42:37.270 --> 00:42:37.280 align:start position:0% it to see you know 00:42:37.280 --> 00:42:39.190 align:start position:0% it to see you know what<00:42:37.520> exactly<00:42:37.920> how<00:42:38.160> big<00:42:38.560> how<00:42:38.720> big<00:42:38.960> of<00:42:39.040> an 00:42:39.190 --> 00:42:39.200 align:start position:0% what exactly how big how big of an 00:42:39.200 --> 00:42:40.390 align:start position:0% what exactly how big how big of an operational 00:42:40.390 --> 00:42:40.400 align:start position:0% operational 00:42:40.400 --> 00:42:43.190 align:start position:0% operational um<00:42:40.880> issue<00:42:41.200> we're<00:42:41.359> trying<00:42:41.599> to<00:42:41.680> solve<00:42:42.000> for 00:42:43.190 --> 00:42:43.200 align:start position:0% um issue we're trying to solve for 00:42:43.200 --> 00:42:45.030 align:start position:0% um issue we're trying to solve for because<00:42:43.760> ercot<00:42:44.160> does<00:42:44.319> have<00:42:44.560> tools<00:42:44.800> in<00:42:44.880> its 00:42:45.030 --> 00:42:45.040 align:start position:0% because ercot does have tools in its 00:42:45.040 --> 00:42:46.630 align:start position:0% because ercot does have tools in its toolbox<00:42:45.599> like<00:42:45.920> you<00:42:46.079> know<00:42:46.240> we're<00:42:46.400> gonna<00:42:46.480> have 00:42:46.630 --> 00:42:46.640 align:start position:0% toolbox like you know we're gonna have 00:42:46.640 --> 00:42:48.470 align:start position:0% toolbox like you know we're gonna have the<00:42:46.720> ordc<00:42:47.520> that<00:42:47.680> hopefully<00:42:48.000> will<00:42:48.160> incent 00:42:48.470 --> 00:42:48.480 align:start position:0% the ordc that hopefully will incent 00:42:48.480 --> 00:42:50.069 align:start position:0% the ordc that hopefully will incent generation<00:42:48.960> online<00:42:49.280> to<00:42:49.440> chase<00:42:49.680> that<00:42:49.760> higher 00:42:50.069 --> 00:42:50.079 align:start position:0% generation online to chase that higher 00:42:50.079 --> 00:42:52.069 align:start position:0% generation online to chase that higher price<00:42:50.480> and<00:42:50.640> and<00:42:50.800> help<00:42:51.040> smooth<00:42:51.359> out<00:42:51.440> that<00:42:51.680> curve 00:42:52.069 --> 00:42:52.079 align:start position:0% price and and help smooth out that curve 00:42:52.079 --> 00:42:55.510 align:start position:0% price and and help smooth out that curve the<00:42:52.240> non-spin<00:42:53.200> in<00:42:53.359> between<00:42:54.000> now<00:42:54.319> and<00:42:54.400> the<00:42:54.480> ecrs 00:42:55.510 --> 00:42:55.520 align:start position:0% the non-spin in between now and the ecrs 00:42:55.520 --> 00:42:56.950 align:start position:0% the non-spin in between now and the ecrs but<00:42:55.680> it's<00:42:55.839> important<00:42:56.240> for<00:42:56.400> us<00:42:56.480> to<00:42:56.640> get<00:42:56.800> an 00:42:56.950 --> 00:42:56.960 align:start position:0% but it's important for us to get an 00:42:56.960 --> 00:43:00.069 align:start position:0% but it's important for us to get an accurate<00:42:57.280> picture<00:42:57.920> so<00:42:58.079> that<00:42:58.240> we're<00:42:58.480> not<00:42:58.880> um 00:43:00.069 --> 00:43:00.079 align:start position:0% accurate picture so that we're not um 00:43:00.079 --> 00:43:02.230 align:start position:0% accurate picture so that we're not um over<00:43:00.400> solving<00:43:01.200> and<00:43:01.359> we<00:43:01.520> can<00:43:01.680> start<00:43:02.000> right 00:43:02.230 --> 00:43:02.240 align:start position:0% over solving and we can start right 00:43:02.240 --> 00:43:04.710 align:start position:0% over solving and we can start right sizing<00:43:02.880> the<00:43:03.040> ecrs 00:43:04.710 --> 00:43:04.720 align:start position:0% sizing the ecrs 00:43:04.720 --> 00:43:07.510 align:start position:0% sizing the ecrs yeah<00:43:05.040> and<00:43:05.280> and<00:43:05.440> so<00:43:06.079> before<00:43:06.400> you<00:43:06.800> fire<00:43:07.040> away<00:43:07.280> at 00:43:07.510 --> 00:43:07.520 align:start position:0% yeah and and so before you fire away at 00:43:07.520 --> 00:43:09.670 align:start position:0% yeah and and so before you fire away at poor<00:43:07.760> woody<00:43:08.240> um 00:43:09.670 --> 00:43:09.680 align:start position:0% poor woody um 00:43:09.680 --> 00:43:11.990 align:start position:0% poor woody um and<00:43:09.839> that<00:43:10.079> gets<00:43:10.319> my<00:43:10.560> original<00:43:10.960> question<00:43:11.599> what 00:43:11.990 --> 00:43:12.000 align:start position:0% and that gets my original question what 00:43:12.000 --> 00:43:14.710 align:start position:0% and that gets my original question what type<00:43:12.319> of<00:43:12.560> generation<00:43:13.599> do<00:43:13.839> we<00:43:14.000> need<00:43:14.319> to<00:43:14.480> meet 00:43:14.710 --> 00:43:14.720 align:start position:0% type of generation do we need to meet 00:43:14.720 --> 00:43:17.270 align:start position:0% type of generation do we need to meet that<00:43:15.040> ramp<00:43:15.599> again<00:43:16.000> i<00:43:16.160> i<00:43:16.319> don't<00:43:16.560> want<00:43:16.720> a<00:43:16.880> poor 00:43:17.270 --> 00:43:17.280 align:start position:0% that ramp again i i don't want a poor 00:43:17.280 --> 00:43:19.910 align:start position:0% that ramp again i i don't want a poor coal<00:43:17.599> plant<00:43:18.000> to<00:43:18.160> bust<00:43:18.480> a<00:43:18.560> gut<00:43:18.880> and<00:43:19.200> you<00:43:19.359> know 00:43:19.910 --> 00:43:19.920 align:start position:0% coal plant to bust a gut and you know 00:43:19.920 --> 00:43:22.150 align:start position:0% coal plant to bust a gut and you know break<00:43:20.240> itself<00:43:21.040> trying<00:43:21.280> to<00:43:21.359> meet<00:43:21.599> that<00:43:21.760> steep 00:43:22.150 --> 00:43:22.160 align:start position:0% break itself trying to meet that steep 00:43:22.160 --> 00:43:25.109 align:start position:0% break itself trying to meet that steep ramp<00:43:22.960> so<00:43:23.119> we<00:43:23.200> have<00:43:23.359> to<00:43:23.520> determine<00:43:24.400> is<00:43:24.640> that<00:43:24.960> is 00:43:25.109 --> 00:43:25.119 align:start position:0% ramp so we have to determine is that is 00:43:25.119 --> 00:43:27.510 align:start position:0% ramp so we have to determine is that is that<00:43:25.359> base<00:43:25.680> load<00:43:25.920> fleet<00:43:26.400> there<00:43:26.800> to<00:43:26.960> sort<00:43:27.200> of 00:43:27.510 --> 00:43:27.520 align:start position:0% that base load fleet there to sort of 00:43:27.520 --> 00:43:29.270 align:start position:0% that base load fleet there to sort of meet<00:43:27.760> this<00:43:28.160> this<00:43:28.319> thing<00:43:28.560> that's<00:43:28.720> falling<00:43:29.119> off 00:43:29.270 --> 00:43:29.280 align:start position:0% meet this this thing that's falling off 00:43:29.280 --> 00:43:30.870 align:start position:0% meet this this thing that's falling off and<00:43:29.359> that's<00:43:29.520> why<00:43:29.680> i<00:43:29.760> use<00:43:30.000> the<00:43:30.079> yuri<00:43:30.400> analogy 00:43:30.870 --> 00:43:30.880 align:start position:0% and that's why i use the yuri analogy 00:43:30.880 --> 00:43:31.670 align:start position:0% and that's why i use the yuri analogy that's 00:43:31.670 --> 00:43:31.680 align:start position:0% that's 00:43:31.680 --> 00:43:33.910 align:start position:0% that's yuri<00:43:32.079> a<00:43:32.240> lot<00:43:32.400> of<00:43:32.480> stuff<00:43:32.720> was<00:43:32.880> happening<00:43:33.440> bad 00:43:33.910 --> 00:43:33.920 align:start position:0% yuri a lot of stuff was happening bad 00:43:33.920 --> 00:43:35.510 align:start position:0% yuri a lot of stuff was happening bad but<00:43:34.240> one<00:43:34.400> of<00:43:34.480> the<00:43:34.640> things<00:43:34.960> was<00:43:35.280> just 00:43:35.510 --> 00:43:35.520 align:start position:0% but one of the things was just 00:43:35.520 --> 00:43:36.710 align:start position:0% but one of the things was just generation 00:43:36.710 --> 00:43:36.720 align:start position:0% generation 00:43:36.720 --> 00:43:38.550 align:start position:0% generation was<00:43:36.960> falling<00:43:37.359> up<00:43:37.680> off 00:43:38.550 --> 00:43:38.560 align:start position:0% was falling up off 00:43:38.560 --> 00:43:41.430 align:start position:0% was falling up off with<00:43:39.200> to<00:43:39.440> a<00:43:39.839> such<00:43:40.079> a<00:43:40.160> magnitude 00:43:41.430 --> 00:43:41.440 align:start position:0% with to a such a magnitude 00:43:41.440 --> 00:43:43.829 align:start position:0% with to a such a magnitude that<00:43:41.760> it<00:43:41.920> it<00:43:42.079> was<00:43:42.240> hard<00:43:42.400> to<00:43:42.640> arrest<00:43:43.200> that<00:43:43.680> and 00:43:43.829 --> 00:43:43.839 align:start position:0% that it it was hard to arrest that and 00:43:43.839 --> 00:43:45.829 align:start position:0% that it it was hard to arrest that and so<00:43:44.079> that's<00:43:44.319> why<00:43:44.480> you<00:43:44.720> layer<00:43:45.040> in<00:43:45.200> and<00:43:45.599> i<00:43:45.680> get 00:43:45.829 --> 00:43:45.839 align:start position:0% so that's why you layer in and i get 00:43:45.839 --> 00:43:47.510 align:start position:0% so that's why you layer in and i get your<00:43:46.319> that's<00:43:46.560> what<00:43:46.720> i<00:43:46.800> would<00:43:46.960> like<00:43:47.119> to<00:43:47.200> know<00:43:47.359> is 00:43:47.510 --> 00:43:47.520 align:start position:0% your that's what i would like to know is 00:43:47.520 --> 00:43:50.390 align:start position:0% your that's what i would like to know is what<00:43:47.760> type<00:43:48.000> of<00:43:48.160> technologies<00:43:49.359> are<00:43:49.520> capable 00:43:50.390 --> 00:43:50.400 align:start position:0% what type of technologies are capable 00:43:50.400 --> 00:43:53.670 align:start position:0% what type of technologies are capable and<00:43:50.800> do<00:43:50.960> we<00:43:51.200> need<00:43:51.520> more<00:43:51.760> of<00:43:52.400> to<00:43:52.720> meet<00:43:53.040> the<00:43:53.200> ramp 00:43:53.670 --> 00:43:53.680 align:start position:0% and do we need more of to meet the ramp 00:43:53.680 --> 00:43:55.190 align:start position:0% and do we need more of to meet the ramp yeah<00:43:54.160> and<00:43:54.319> one<00:43:54.480> thing<00:43:54.640> that<00:43:54.800> i<00:43:54.880> would<00:43:54.960> add<00:43:55.119> to 00:43:55.190 --> 00:43:55.200 align:start position:0% yeah and one thing that i would add to 00:43:55.200 --> 00:43:58.230 align:start position:0% yeah and one thing that i would add to that<00:43:55.440> is<00:43:55.760> we<00:43:56.079> always<00:43:56.560> talk<00:43:56.720> about<00:43:57.040> batteries 00:43:58.230 --> 00:43:58.240 align:start position:0% that is we always talk about batteries 00:43:58.240 --> 00:44:00.550 align:start position:0% that is we always talk about batteries co-located<00:43:58.800> with<00:43:59.040> storage 00:44:00.550 --> 00:44:00.560 align:start position:0% co-located with storage 00:44:00.560 --> 00:44:02.470 align:start position:0% co-located with storage there<00:44:00.880> are<00:44:01.119> examples<00:44:01.599> in<00:44:01.760> places<00:44:02.079> around<00:44:02.400> the 00:44:02.470 --> 00:44:02.480 align:start position:0% there are examples in places around the 00:44:02.480 --> 00:44:03.910 align:start position:0% there are examples in places around the world<00:44:02.720> where<00:44:02.880> they<00:44:03.119> are<00:44:03.280> co-locating 00:44:03.910 --> 00:44:03.920 align:start position:0% world where they are co-locating 00:44:03.920 --> 00:44:06.470 align:start position:0% world where they are co-locating batteries<00:44:04.400> with<00:44:04.560> thermal<00:44:04.960> plants 00:44:06.470 --> 00:44:06.480 align:start position:0% batteries with thermal plants 00:44:06.480 --> 00:44:08.630 align:start position:0% batteries with thermal plants to<00:44:06.640> help<00:44:06.960> minimize<00:44:07.680> the 00:44:08.630 --> 00:44:08.640 align:start position:0% to help minimize the 00:44:08.640 --> 00:44:11.589 align:start position:0% to help minimize the uh<00:44:09.040> the<00:44:09.280> dispatch<00:44:09.839> lag 00:44:11.589 --> 00:44:11.599 align:start position:0% uh the dispatch lag 00:44:11.599 --> 00:44:14.150 align:start position:0% uh the dispatch lag to<00:44:11.760> help<00:44:12.000> them<00:44:12.240> in<00:44:12.400> ramping<00:44:12.880> so<00:44:13.119> if<00:44:13.200> you<00:44:13.359> have<00:44:13.760> a 00:44:14.150 --> 00:44:14.160 align:start position:0% to help them in ramping so if you have a 00:44:14.160 --> 00:44:15.990 align:start position:0% to help them in ramping so if you have a ct<00:44:14.560> that<00:44:14.720> takes<00:44:15.200> a<00:44:15.280> few<00:44:15.440> minutes<00:44:15.760> or<00:44:15.839> 10 00:44:15.990 --> 00:44:16.000 align:start position:0% ct that takes a few minutes or 10 00:44:16.000 --> 00:44:18.150 align:start position:0% ct that takes a few minutes or 10 minutes<00:44:16.319> to<00:44:16.560> get<00:44:16.720> up<00:44:16.880> and<00:44:16.960> running<00:44:17.760> batteries 00:44:18.150 --> 00:44:18.160 align:start position:0% minutes to get up and running batteries 00:44:18.160 --> 00:44:19.990 align:start position:0% minutes to get up and running batteries are<00:44:18.240> co-located<00:44:18.880> there<00:44:19.119> they<00:44:19.280> can<00:44:19.440> provide 00:44:19.990 --> 00:44:20.000 align:start position:0% are co-located there they can provide 00:44:20.000 --> 00:44:23.030 align:start position:0% are co-located there they can provide faster<00:44:20.400> reserve<00:44:20.880> or<00:44:21.040> faster<00:44:21.440> response 00:44:23.030 --> 00:44:23.040 align:start position:0% faster reserve or faster response 00:44:23.040 --> 00:44:25.109 align:start position:0% faster reserve or faster response while<00:44:23.280> their<00:44:23.440> ct<00:44:23.839> is<00:44:23.920> getting<00:44:24.240> up<00:44:24.400> and<00:44:24.480> running 00:44:25.109 --> 00:44:25.119 align:start position:0% while their ct is getting up and running 00:44:25.119 --> 00:44:26.710 align:start position:0% while their ct is getting up and running things<00:44:25.440> like<00:44:25.599> that<00:44:25.839> i<00:44:26.000> think<00:44:26.160> are<00:44:26.319> innovative 00:44:26.710 --> 00:44:26.720 align:start position:0% things like that i think are innovative 00:44:26.720 --> 00:44:29.030 align:start position:0% things like that i think are innovative that<00:44:26.880> the<00:44:26.960> market<00:44:27.359> will<00:44:27.599> come<00:44:27.920> help<00:44:28.160> solve<00:44:28.880> if 00:44:29.030 --> 00:44:29.040 align:start position:0% that the market will come help solve if 00:44:29.040 --> 00:44:30.950 align:start position:0% that the market will come help solve if we<00:44:29.359> shed<00:44:29.680> light<00:44:29.920> on<00:44:30.160> on<00:44:30.319> what<00:44:30.480> the<00:44:30.640> issue<00:44:30.800> is 00:44:30.950 --> 00:44:30.960 align:start position:0% we shed light on on what the issue is 00:44:30.960 --> 00:44:32.470 align:start position:0% we shed light on on what the issue is we've<00:44:31.119> got<00:44:31.359> the<00:44:31.440> resources<00:44:32.000> the<00:44:32.160> market's 00:44:32.470 --> 00:44:32.480 align:start position:0% we've got the resources the market's 00:44:32.480 --> 00:44:33.990 align:start position:0% we've got the resources the market's going<00:44:32.640> to<00:44:32.720> solve<00:44:32.960> it<00:44:33.119> we<00:44:33.200> can<00:44:33.359> save<00:44:33.599> a<00:44:33.680> lot<00:44:33.839> of 00:44:33.990 --> 00:44:34.000 align:start position:0% going to solve it we can save a lot of 00:44:34.000 --> 00:44:35.910 align:start position:0% going to solve it we can save a lot of time<00:44:34.240> and<00:44:34.319> effort<00:44:34.800> and<00:44:34.960> money<00:44:35.200> for<00:44:35.359> consumers 00:44:35.910 --> 00:44:35.920 align:start position:0% time and effort and money for consumers 00:44:35.920 --> 00:44:39.430 align:start position:0% time and effort and money for consumers and<00:44:36.079> just<00:44:36.400> skip<00:44:36.880> all<00:44:36.960> this 00:44:39.430 --> 00:44:39.440 align:start position:0% 00:44:39.440 --> 00:44:40.630 align:start position:0% woody 00:44:40.630 --> 00:44:40.640 align:start position:0% woody 00:44:40.640 --> 00:44:46.710 align:start position:0% woody so<00:44:40.880> what<00:44:41.119> what<00:44:41.359> what's<00:44:41.599> the<00:44:41.680> question 00:44:46.710 --> 00:44:46.720 align:start position:0% 00:44:46.720 --> 00:44:49.510 align:start position:0% given<00:44:47.200> the<00:44:47.359> profile<00:44:48.079> demonstrated<00:44:48.880> in<00:44:49.280> in<00:44:49.359> the 00:44:49.510 --> 00:44:49.520 align:start position:0% given the profile demonstrated in in the 00:44:49.520 --> 00:44:51.990 align:start position:0% given the profile demonstrated in in the study<00:44:50.319> again<00:44:50.720> here<00:44:50.960> let's<00:44:51.280> let's<00:44:51.520> pick<00:44:51.680> one 00:44:51.990 --> 00:44:52.000 align:start position:0% study again here let's let's pick one 00:44:52.000 --> 00:44:54.470 align:start position:0% study again here let's let's pick one let's<00:44:52.480> oh<00:44:52.720> i'm<00:44:52.800> sorry<00:44:53.200> well<00:44:53.599> let's<00:44:53.839> do<00:44:54.240> can<00:44:54.400> we 00:44:54.470 --> 00:44:54.480 align:start position:0% let's oh i'm sorry well let's do can we 00:44:54.480 --> 00:44:57.589 align:start position:0% let's oh i'm sorry well let's do can we do<00:44:54.640> march<00:44:54.960> 5th<00:44:55.440> yes<00:44:55.760> because<00:44:56.560> um 00:44:57.589 --> 00:44:57.599 align:start position:0% do march 5th yes because um 00:44:57.599 --> 00:45:00.069 align:start position:0% do march 5th yes because um that<00:44:57.839> profile<00:44:58.560> may<00:44:58.720> be<00:44:58.880> more<00:44:59.119> acute<00:44:59.520> because 00:45:00.069 --> 00:45:00.079 align:start position:0% that profile may be more acute because 00:45:00.079 --> 00:45:02.870 align:start position:0% that profile may be more acute because of<00:45:00.880> our<00:45:01.200> planned<00:45:01.599> outages<00:45:02.160> that<00:45:02.400> always<00:45:02.640> need 00:45:02.870 --> 00:45:02.880 align:start position:0% of our planned outages that always need 00:45:02.880 --> 00:45:05.589 align:start position:0% of our planned outages that always need to<00:45:03.040> occur<00:45:04.000> at<00:45:04.160> that<00:45:04.400> time<00:45:04.640> of<00:45:04.800> year 00:45:05.589 --> 00:45:05.599 align:start position:0% to occur at that time of year 00:45:05.599 --> 00:45:06.870 align:start position:0% to occur at that time of year yeah<00:45:05.760> i<00:45:05.839> think<00:45:06.000> that's<00:45:06.240> the<00:45:06.560> that's<00:45:06.800> the 00:45:06.870 --> 00:45:06.880 align:start position:0% yeah i think that's the that's the 00:45:06.880 --> 00:45:08.630 align:start position:0% yeah i think that's the that's the missing<00:45:07.280> one<00:45:07.520> of<00:45:07.599> the<00:45:07.680> missing<00:45:08.000> pieces<00:45:08.319> here 00:45:08.630 --> 00:45:08.640 align:start position:0% missing one of the missing pieces here 00:45:08.640 --> 00:45:10.150 align:start position:0% missing one of the missing pieces here is<00:45:08.800> that 00:45:10.150 --> 00:45:10.160 align:start position:0% is that 00:45:10.160 --> 00:45:13.030 align:start position:0% is that the<00:45:10.319> fleet<00:45:10.720> of<00:45:10.800> dispatch<00:45:11.280> regeneration 00:45:13.030 --> 00:45:13.040 align:start position:0% the fleet of dispatch regeneration 00:45:13.040 --> 00:45:14.630 align:start position:0% the fleet of dispatch regeneration is<00:45:13.200> gonna<00:45:13.440> be 00:45:14.630 --> 00:45:14.640 align:start position:0% is gonna be 00:45:14.640 --> 00:45:16.309 align:start position:0% is gonna be a<00:45:14.720> lot<00:45:14.880> of<00:45:14.960> that's<00:45:15.119> gonna<00:45:15.280> be<00:45:15.440> out<00:45:15.520> on<00:45:15.680> outage 00:45:16.309 --> 00:45:16.319 align:start position:0% a lot of that's gonna be out on outage 00:45:16.319 --> 00:45:17.750 align:start position:0% a lot of that's gonna be out on outage at<00:45:16.480> that<00:45:16.640> point 00:45:17.750 --> 00:45:17.760 align:start position:0% at that point 00:45:17.760 --> 00:45:19.990 align:start position:0% at that point and<00:45:18.000> so<00:45:18.319> you<00:45:18.480> have<00:45:18.640> to<00:45:18.800> give<00:45:19.040> those<00:45:19.200> guys<00:45:19.520> time 00:45:19.990 --> 00:45:20.000 align:start position:0% and so you have to give those guys time 00:45:20.000 --> 00:45:21.349 align:start position:0% and so you have to give those guys time to 00:45:21.349 --> 00:45:21.359 align:start position:0% to 00:45:21.359 --> 00:45:23.430 align:start position:0% to to<00:45:21.839> to<00:45:22.000> get<00:45:22.160> ready<00:45:22.480> for<00:45:22.720> winter<00:45:23.040> and<00:45:23.119> summer 00:45:23.430 --> 00:45:23.440 align:start position:0% to to get ready for winter and summer 00:45:23.440 --> 00:45:25.750 align:start position:0% to to get ready for winter and summer peaks<00:45:23.920> and<00:45:24.160> march<00:45:24.560> and<00:45:24.720> november 00:45:25.750 --> 00:45:25.760 align:start position:0% peaks and march and november 00:45:25.760 --> 00:45:27.589 align:start position:0% peaks and march and november the<00:45:25.920> times<00:45:26.319> we<00:45:26.400> have<00:45:26.560> the<00:45:26.720> most 00:45:27.589 --> 00:45:27.599 align:start position:0% the times we have the most 00:45:27.599 --> 00:45:30.309 align:start position:0% the times we have the most wind<00:45:27.920> and<00:45:28.000> solar<00:45:28.400> generation 00:45:30.309 --> 00:45:30.319 align:start position:0% wind and solar generation 00:45:30.319 --> 00:45:32.630 align:start position:0% wind and solar generation and<00:45:30.480> the<00:45:30.560> lowest<00:45:30.880> load<00:45:31.680> when<00:45:32.000> these<00:45:32.319> kinds<00:45:32.560> of 00:45:32.630 --> 00:45:32.640 align:start position:0% and the lowest load when these kinds of 00:45:32.640 --> 00:45:34.870 align:start position:0% and the lowest load when these kinds of graphs<00:45:32.960> look<00:45:33.119> the<00:45:33.280> scariest<00:45:34.319> or<00:45:34.560> the<00:45:34.640> times 00:45:34.870 --> 00:45:34.880 align:start position:0% graphs look the scariest or the times 00:45:34.880 --> 00:45:37.589 align:start position:0% graphs look the scariest or the times when<00:45:35.040> dispatchable<00:45:35.680> generation<00:45:36.319> is<00:45:36.560> being 00:45:37.589 --> 00:45:37.599 align:start position:0% when dispatchable generation is being 00:45:37.599 --> 00:45:40.230 align:start position:0% when dispatchable generation is being so<00:45:38.160> is<00:45:38.319> being<00:45:38.800> uh<00:45:39.040> repaired<00:45:39.760> getting<00:45:40.000> waiting 00:45:40.230 --> 00:45:40.240 align:start position:0% so is being uh repaired getting waiting 00:45:40.240 --> 00:45:41.430 align:start position:0% so is being uh repaired getting waiting for<00:45:40.400> the<00:45:40.480> other<00:45:40.720> so 00:45:41.430 --> 00:45:41.440 align:start position:0% for the other so 00:45:41.440 --> 00:45:43.670 align:start position:0% for the other so the<00:45:41.599> market<00:45:42.000> needs<00:45:42.319> to<00:45:42.800> provide<00:45:43.200> some<00:45:43.359> kind<00:45:43.520> of 00:45:43.670 --> 00:45:43.680 align:start position:0% the market needs to provide some kind of 00:45:43.680 --> 00:45:45.670 align:start position:0% the market needs to provide some kind of incentive 00:45:45.670 --> 00:45:45.680 align:start position:0% incentive 00:45:45.680 --> 00:45:47.510 align:start position:0% incentive for<00:45:46.160> exactly<00:45:46.640> the<00:45:46.720> kind<00:45:46.880> of<00:45:46.960> generation<00:45:47.359> you 00:45:47.510 --> 00:45:47.520 align:start position:0% for exactly the kind of generation you 00:45:47.520 --> 00:45:49.190 align:start position:0% for exactly the kind of generation you were<00:45:47.599> talking<00:45:47.839> about<00:45:48.480> and<00:45:48.800> what<00:45:48.960> kind<00:45:49.119> of 00:45:49.190 --> 00:45:49.200 align:start position:0% were talking about and what kind of 00:45:49.200 --> 00:45:52.230 align:start position:0% were talking about and what kind of generation<00:45:49.760> is<00:45:49.920> that<00:45:50.240> quick<00:45:50.640> responding<00:45:51.520> okay 00:45:52.230 --> 00:45:52.240 align:start position:0% generation is that quick responding okay 00:45:52.240 --> 00:45:54.390 align:start position:0% generation is that quick responding okay fast<00:45:52.560> ramping 00:45:54.390 --> 00:45:54.400 align:start position:0% fast ramping 00:45:54.400 --> 00:45:56.630 align:start position:0% fast ramping probably<00:45:54.800> smaller 00:45:56.630 --> 00:45:56.640 align:start position:0% probably smaller 00:45:56.640 --> 00:45:58.630 align:start position:0% probably smaller so<00:45:56.880> to<00:45:57.040> my<00:45:57.200> point<00:45:57.440> earlier<00:45:58.160> it<00:45:58.319> sounds<00:45:58.560> like 00:45:58.630 --> 00:45:58.640 align:start position:0% so to my point earlier it sounds like 00:45:58.640 --> 00:46:00.150 align:start position:0% so to my point earlier it sounds like there's<00:45:58.880> sort<00:45:59.119> of<00:45:59.200> a<00:45:59.280> disconnect<00:45:59.760> here<00:45:59.920> right 00:46:00.150 --> 00:46:00.160 align:start position:0% there's sort of a disconnect here right 00:46:00.160 --> 00:46:02.710 align:start position:0% there's sort of a disconnect here right so<00:46:00.720> especially<00:46:01.359> in<00:46:01.520> the<00:46:01.599> shoulder<00:46:01.920> month<00:46:02.319> of 00:46:02.710 --> 00:46:02.720 align:start position:0% so especially in the shoulder month of 00:46:02.720 --> 00:46:04.390 align:start position:0% so especially in the shoulder month of the<00:46:02.800> spring<00:46:03.359> the<00:46:03.440> shoulder<00:46:03.920> period<00:46:04.240> of<00:46:04.319> the 00:46:04.390 --> 00:46:04.400 align:start position:0% the spring the shoulder period of the 00:46:04.400 --> 00:46:06.230 align:start position:0% the spring the shoulder period of the spring 00:46:06.230 --> 00:46:06.240 align:start position:0% spring 00:46:06.240 --> 00:46:08.710 align:start position:0% spring um<00:46:06.560> where<00:46:06.880> a<00:46:06.960> lot<00:46:07.119> of<00:46:07.200> plants<00:46:07.520> will<00:46:07.599> be<00:46:07.760> down 00:46:08.710 --> 00:46:08.720 align:start position:0% um where a lot of plants will be down 00:46:08.720 --> 00:46:10.950 align:start position:0% um where a lot of plants will be down you<00:46:08.880> know<00:46:09.119> for<00:46:09.440> for<00:46:10.000> maintenance<00:46:10.400> they<00:46:10.800> have 00:46:10.950 --> 00:46:10.960 align:start position:0% you know for for maintenance they have 00:46:10.960 --> 00:46:14.550 align:start position:0% you know for for maintenance they have to<00:46:11.119> take<00:46:11.359> to<00:46:11.520> prepare<00:46:11.839> for<00:46:12.000> the<00:46:12.079> summer<00:46:12.640> and<00:46:12.880> so 00:46:14.550 --> 00:46:14.560 align:start position:0% to take to prepare for the summer and so 00:46:14.560 --> 00:46:15.910 align:start position:0% to take to prepare for the summer and so you<00:46:14.720> know<00:46:14.800> you<00:46:14.960> might<00:46:15.119> have<00:46:15.599> some<00:46:15.760> of<00:46:15.839> the 00:46:15.910 --> 00:46:15.920 align:start position:0% you know you might have some of the 00:46:15.920 --> 00:46:17.829 align:start position:0% you know you might have some of the plants<00:46:16.240> that<00:46:16.400> would<00:46:16.560> be<00:46:16.800> chasing<00:46:17.119> the<00:46:17.200> ordc 00:46:17.829 --> 00:46:17.839 align:start position:0% plants that would be chasing the ordc 00:46:17.839 --> 00:46:19.109 align:start position:0% plants that would be chasing the ordc price 00:46:19.109 --> 00:46:19.119 align:start position:0% price 00:46:19.119 --> 00:46:20.950 align:start position:0% price non-spin 00:46:20.950 --> 00:46:20.960 align:start position:0% non-spin 00:46:20.960 --> 00:46:22.470 align:start position:0% non-spin down<00:46:21.200> to<00:46:21.280> get<00:46:21.440> planned<00:46:21.760> maintenance<00:46:22.240> so<00:46:22.400> what 00:46:22.470 --> 00:46:22.480 align:start position:0% down to get planned maintenance so what 00:46:22.480 --> 00:46:23.990 align:start position:0% down to get planned maintenance so what do<00:46:22.560> we<00:46:22.640> have<00:46:22.880> in<00:46:22.960> between<00:46:23.440> those<00:46:23.599> are<00:46:23.760> only 00:46:23.990 --> 00:46:24.000 align:start position:0% do we have in between those are only 00:46:24.000 --> 00:46:26.630 align:start position:0% do we have in between those are only tools<00:46:24.319> for<00:46:24.400> the<00:46:24.480> next<00:46:24.720> few<00:46:24.880> years 00:46:26.630 --> 00:46:26.640 align:start position:0% tools for the next few years 00:46:26.640 --> 00:46:28.550 align:start position:0% tools for the next few years ultimately<00:46:27.119> we'll<00:46:27.280> hobby<00:46:27.520> crs<00:46:28.240> i<00:46:28.319> think<00:46:28.480> we've 00:46:28.550 --> 00:46:28.560 align:start position:0% ultimately we'll hobby crs i think we've 00:46:28.560 --> 00:46:31.510 align:start position:0% ultimately we'll hobby crs i think we've got<00:46:28.720> to<00:46:28.800> be<00:46:28.960> thinking<00:46:29.280> about<00:46:30.000> um 00:46:31.510 --> 00:46:31.520 align:start position:0% got to be thinking about um 00:46:31.520 --> 00:46:33.030 align:start position:0% got to be thinking about um some<00:46:31.680> kind<00:46:31.839> of<00:46:31.920> strategic<00:46:32.400> reliability 00:46:33.030 --> 00:46:33.040 align:start position:0% some kind of strategic reliability 00:46:33.040 --> 00:46:35.349 align:start position:0% some kind of strategic reliability service 00:46:35.349 --> 00:46:35.359 align:start position:0% service 00:46:35.359 --> 00:46:38.550 align:start position:0% service for<00:46:35.599> times<00:46:35.839> like<00:46:36.079> that<00:46:36.480> yeah<00:46:37.040> well<00:46:37.200> i<00:46:37.280> think 00:46:38.550 --> 00:46:38.560 align:start position:0% for times like that yeah well i think 00:46:38.560 --> 00:46:39.990 align:start position:0% for times like that yeah well i think the<00:46:38.720> fact<00:46:38.960> that<00:46:39.119> we've<00:46:39.280> had<00:46:39.440> to<00:46:39.599> use<00:46:39.839> our 00:46:39.990 --> 00:46:40.000 align:start position:0% the fact that we've had to use our 00:46:40.000 --> 00:46:42.309 align:start position:0% the fact that we've had to use our advanced<00:46:40.400> action<00:46:40.720> notice<00:46:41.440> three<00:46:41.680> times<00:46:42.000> is 00:46:42.309 --> 00:46:42.319 align:start position:0% advanced action notice three times is 00:46:42.319 --> 00:46:44.069 align:start position:0% advanced action notice three times is just 00:46:44.069 --> 00:46:44.079 align:start position:0% just 00:46:44.079 --> 00:46:45.109 align:start position:0% just uh 00:46:45.109 --> 00:46:45.119 align:start position:0% uh 00:46:45.119 --> 00:46:47.510 align:start position:0% uh recently<00:46:45.680> is<00:46:46.000> just<00:46:46.240> an<00:46:46.560> indication<00:46:47.119> of<00:46:47.280> of 00:46:47.510 --> 00:46:47.520 align:start position:0% recently is just an indication of of 00:46:47.520 --> 00:46:49.589 align:start position:0% recently is just an indication of of things<00:46:47.760> to<00:46:47.920> come<00:46:48.240> the<00:46:48.400> fact<00:46:48.640> that<00:46:49.280> that<00:46:49.440> that 00:46:49.589 --> 00:46:49.599 align:start position:0% things to come the fact that that that 00:46:49.599 --> 00:46:51.670 align:start position:0% things to come the fact that that that dispatchable<00:46:50.400> level<00:46:50.800> and 00:46:51.670 --> 00:46:51.680 align:start position:0% dispatchable level and 00:46:51.680 --> 00:46:52.870 align:start position:0% dispatchable level and and 00:46:52.870 --> 00:46:52.880 align:start position:0% and 00:46:52.880 --> 00:46:54.470 align:start position:0% and the<00:46:53.040> irr 00:46:54.470 --> 00:46:54.480 align:start position:0% the irr 00:46:54.480 --> 00:46:55.829 align:start position:0% the irr we're<00:46:54.720> starting<00:46:55.119> they're<00:46:55.280> starting<00:46:55.520> to<00:46:55.599> bump 00:46:55.829 --> 00:46:55.839 align:start position:0% we're starting they're starting to bump 00:46:55.839 --> 00:46:57.270 align:start position:0% we're starting they're starting to bump against<00:46:56.160> each<00:46:56.319> other<00:46:56.480> now<00:46:56.800> and<00:46:56.960> so<00:46:57.119> we're 00:46:57.270 --> 00:46:57.280 align:start position:0% against each other now and so we're 00:46:57.280 --> 00:46:59.670 align:start position:0% against each other now and so we're starting<00:46:57.520> to<00:46:57.680> see<00:46:57.920> the<00:46:58.400> the<00:46:58.560> forerunning<00:46:59.200> of 00:46:59.670 --> 00:46:59.680 align:start position:0% starting to see the the forerunning of 00:46:59.680 --> 00:47:01.589 align:start position:0% starting to see the the forerunning of some<00:46:59.839> more<00:47:00.079> problems<00:47:00.480> there 00:47:01.589 --> 00:47:01.599 align:start position:0% some more problems there 00:47:01.599 --> 00:47:04.790 align:start position:0% some more problems there i<00:47:01.760> would<00:47:02.000> call<00:47:02.160> those<00:47:02.720> giant<00:47:03.040> red<00:47:03.200> flags 00:47:04.790 --> 00:47:04.800 align:start position:0% i would call those giant red flags 00:47:04.800 --> 00:47:05.670 align:start position:0% i would call those giant red flags um 00:47:05.670 --> 00:47:05.680 align:start position:0% um 00:47:05.680 --> 00:47:07.030 align:start position:0% um you<00:47:05.839> have<00:47:05.920> a<00:47:06.000> question<00:47:06.240> about<00:47:06.400> how<00:47:06.640> i<00:47:06.720> was<00:47:06.800> just 00:47:07.030 --> 00:47:07.040 align:start position:0% you have a question about how i was just 00:47:07.040 --> 00:47:09.270 align:start position:0% you have a question about how i was just incorporate<00:47:07.599> demand<00:47:07.920> response<00:47:08.400> and 00:47:09.270 --> 00:47:09.280 align:start position:0% incorporate demand response and 00:47:09.280 --> 00:47:11.270 align:start position:0% incorporate demand response and everything<00:47:09.599> else<00:47:09.760> in<00:47:09.839> this<00:47:10.079> no<00:47:10.240> no<00:47:10.400> no<00:47:10.720> i<00:47:10.800> don't 00:47:11.270 --> 00:47:11.280 align:start position:0% everything else in this no no no i don't 00:47:11.280 --> 00:47:12.390 align:start position:0% everything else in this no no no i don't that<00:47:11.440> was<00:47:11.680> just 00:47:12.390 --> 00:47:12.400 align:start position:0% that was just 00:47:12.400 --> 00:47:14.150 align:start position:0% that was just i<00:47:12.560> believe<00:47:12.880> that<00:47:13.200> uh<00:47:13.440> that's<00:47:13.760> the<00:47:13.920> next 00:47:14.150 --> 00:47:14.160 align:start position:0% i believe that uh that's the next 00:47:14.160 --> 00:47:16.550 align:start position:0% i believe that uh that's the next analysis<00:47:14.720> that<00:47:15.200> that<00:47:15.359> has<00:47:15.520> to<00:47:15.599> happen 00:47:16.550 --> 00:47:16.560 align:start position:0% analysis that that has to happen 00:47:16.560 --> 00:47:20.150 align:start position:0% analysis that that has to happen what<00:47:17.040> what<00:47:17.200> about<00:47:17.359> the<00:47:17.440> world<00:47:18.000> i<00:47:18.079> mean<00:47:18.640> ask<00:47:18.960> him 00:47:20.150 --> 00:47:20.160 align:start position:0% what what about the world i mean ask him 00:47:20.160 --> 00:47:22.470 align:start position:0% what what about the world i mean ask him the<00:47:20.319> winter<00:47:20.800> period<00:47:21.280> it<00:47:21.520> you<00:47:21.680> know<00:47:22.079> sort<00:47:22.240> of<00:47:22.400> a 00:47:22.470 --> 00:47:22.480 align:start position:0% the winter period it you know sort of a 00:47:22.480 --> 00:47:23.670 align:start position:0% the winter period it you know sort of a different<00:47:22.720> construct<00:47:23.119> right<00:47:23.280> you<00:47:23.359> have<00:47:23.440> more 00:47:23.670 --> 00:47:23.680 align:start position:0% different construct right you have more 00:47:23.680 --> 00:47:25.190 align:start position:0% different construct right you have more generation<00:47:24.160> online<00:47:24.559> they're<00:47:24.720> not<00:47:24.880> down<00:47:25.040> for 00:47:25.190 --> 00:47:25.200 align:start position:0% generation online they're not down for 00:47:25.200 --> 00:47:27.030 align:start position:0% generation online they're not down for planned<00:47:25.440> maintenance<00:47:26.160> um 00:47:27.030 --> 00:47:27.040 align:start position:0% planned maintenance um 00:47:27.040 --> 00:47:28.549 align:start position:0% planned maintenance um i<00:47:27.280> think<00:47:27.520> continuing<00:47:28.000> to<00:47:28.079> refine<00:47:28.400> that 00:47:28.549 --> 00:47:28.559 align:start position:0% i think continuing to refine that 00:47:28.559 --> 00:47:30.150 align:start position:0% i think continuing to refine that scenario<00:47:29.119> too 00:47:30.150 --> 00:47:30.160 align:start position:0% scenario too 00:47:30.160 --> 00:47:31.829 align:start position:0% scenario too with<00:47:30.400> respect<00:47:30.800> to 00:47:31.829 --> 00:47:31.839 align:start position:0% with respect to 00:47:31.839 --> 00:47:33.750 align:start position:0% with respect to how<00:47:32.000> much<00:47:32.640> you<00:47:32.720> know<00:47:32.880> resources<00:47:33.440> we'll<00:47:33.599> have 00:47:33.750 --> 00:47:33.760 align:start position:0% how much you know resources we'll have 00:47:33.760 --> 00:47:35.990 align:start position:0% how much you know resources we'll have online<00:47:34.480> to<00:47:34.800> address<00:47:35.200> that<00:47:35.440> issue<00:47:35.760> in<00:47:35.839> the 00:47:35.990 --> 00:47:36.000 align:start position:0% online to address that issue in the 00:47:36.000 --> 00:47:38.150 align:start position:0% online to address that issue in the spring<00:47:36.640> i<00:47:36.720> mean<00:47:36.960> i'm<00:47:37.040> sorry<00:47:37.200> in<00:47:37.280> the<00:47:37.359> winter 00:47:38.150 --> 00:47:38.160 align:start position:0% spring i mean i'm sorry in the winter 00:47:38.160 --> 00:47:39.750 align:start position:0% spring i mean i'm sorry in the winter would<00:47:38.400> also<00:47:38.559> be<00:47:38.720> helpful<00:47:39.119> i<00:47:39.200> know<00:47:39.599> just 00:47:39.750 --> 00:47:39.760 align:start position:0% would also be helpful i know just 00:47:39.760 --> 00:47:41.829 align:start position:0% would also be helpful i know just continuing<00:47:40.240> to<00:47:40.319> fine-tune<00:47:41.119> um<00:47:41.359> with<00:47:41.520> that<00:47:41.760> we 00:47:41.829 --> 00:47:41.839 align:start position:0% continuing to fine-tune um with that we 00:47:41.839 --> 00:47:43.030 align:start position:0% continuing to fine-tune um with that we can<00:47:42.079> certainly 00:47:43.030 --> 00:47:43.040 align:start position:0% can certainly 00:47:43.040 --> 00:47:44.309 align:start position:0% can certainly uh 00:47:44.309 --> 00:47:44.319 align:start position:0% uh 00:47:44.319 --> 00:47:46.390 align:start position:0% uh fine-tune<00:47:44.880> these<00:47:45.280> this<00:47:45.520> analysis<00:47:46.079> more<00:47:46.319> this 00:47:46.390 --> 00:47:46.400 align:start position:0% fine-tune these this analysis more this 00:47:46.400 --> 00:47:48.150 align:start position:0% fine-tune these this analysis more this was<00:47:46.640> kind<00:47:46.800> of<00:47:46.880> the<00:47:46.960> first<00:47:47.280> run<00:47:47.520> at<00:47:47.680> it<00:47:47.760> but<00:47:48.000> we 00:47:48.150 --> 00:47:48.160 align:start position:0% was kind of the first run at it but we 00:47:48.160 --> 00:47:49.589 align:start position:0% was kind of the first run at it but we can<00:47:48.400> certainly<00:47:48.800> add<00:47:48.960> some<00:47:49.119> more<00:47:49.280> and<00:47:49.359> we've 00:47:49.589 --> 00:47:49.599 align:start position:0% can certainly add some more and we've 00:47:49.599 --> 00:47:51.109 align:start position:0% can certainly add some more and we've taken<00:47:49.920> some<00:47:50.079> notes<00:47:50.400> on<00:47:50.480> things<00:47:50.640> you've 00:47:51.109 --> 00:47:51.119 align:start position:0% taken some notes on things you've 00:47:51.119 --> 00:47:52.710 align:start position:0% taken some notes on things you've mentioned<00:47:51.440> this<00:47:51.599> morning<00:47:52.319> i<00:47:52.400> think<00:47:52.559> the 00:47:52.710 --> 00:47:52.720 align:start position:0% mentioned this morning i think the 00:47:52.720 --> 00:47:55.190 align:start position:0% mentioned this morning i think the winter<00:47:53.119> challenge<00:47:53.599> is<00:47:53.920> mainly<00:47:54.319> the<00:47:55.040> that 00:47:55.190 --> 00:47:55.200 align:start position:0% winter challenge is mainly the that 00:47:55.200 --> 00:47:56.630 align:start position:0% winter challenge is mainly the that morning<00:47:55.680> peak 00:47:56.630 --> 00:47:56.640 align:start position:0% morning peak 00:47:56.640 --> 00:47:58.230 align:start position:0% morning peak when<00:47:56.880> the<00:47:57.200> the<00:47:57.359> solar<00:47:57.680> is<00:47:57.760> just<00:47:57.920> not<00:47:58.079> going<00:47:58.160> to 00:47:58.230 --> 00:47:58.240 align:start position:0% when the the solar is just not going to 00:47:58.240 --> 00:48:00.230 align:start position:0% when the the solar is just not going to contribute<00:47:58.720> very<00:47:58.880> much<00:47:59.440> that's 00:48:00.230 --> 00:48:00.240 align:start position:0% contribute very much that's 00:48:00.240 --> 00:48:01.670 align:start position:0% contribute very much that's that's<00:48:00.480> a<00:48:00.559> little<00:48:00.720> bit<00:48:00.880> different<00:48:01.200> scenario 00:48:01.670 --> 00:48:01.680 align:start position:0% that's a little bit different scenario 00:48:01.680 --> 00:48:04.390 align:start position:0% that's a little bit different scenario than<00:48:01.839> you<00:48:02.000> see<00:48:02.240> in<00:48:02.480> i<00:48:02.559> mean<00:48:02.800> 20<00:48:03.119> 000 00:48:04.390 --> 00:48:04.400 align:start position:0% than you see in i mean 20 000 00:48:04.400 --> 00:48:07.670 align:start position:0% than you see in i mean 20 000 you<00:48:04.559> know<00:48:04.960> megawatts<00:48:05.599> of<00:48:06.079> solar 00:48:07.670 --> 00:48:07.680 align:start position:0% you know megawatts of solar 00:48:07.680 --> 00:48:10.630 align:start position:0% you know megawatts of solar on<00:48:07.839> a<00:48:08.000> february<00:48:08.480> morning<00:48:08.960> is<00:48:09.280> is<00:48:09.680> not<00:48:10.240> useful 00:48:10.630 --> 00:48:10.640 align:start position:0% on a february morning is is not useful 00:48:10.640 --> 00:48:12.549 align:start position:0% on a february morning is is not useful for<00:48:10.800> the<00:48:10.960> peak 00:48:12.549 --> 00:48:12.559 align:start position:0% for the peak 00:48:12.559 --> 00:48:15.030 align:start position:0% for the peak so<00:48:12.720> i'd<00:48:12.880> say<00:48:13.280> as<00:48:13.440> you<00:48:14.079> try<00:48:14.240> to<00:48:14.400> fine-tune<00:48:14.880> what 00:48:15.030 --> 00:48:15.040 align:start position:0% so i'd say as you try to fine-tune what 00:48:15.040 --> 00:48:16.630 align:start position:0% so i'd say as you try to fine-tune what this<00:48:15.200> picture<00:48:15.520> looks<00:48:15.760> like<00:48:16.240> it<00:48:16.400> would<00:48:16.559> be 00:48:16.630 --> 00:48:16.640 align:start position:0% this picture looks like it would be 00:48:16.640 --> 00:48:19.190 align:start position:0% this picture looks like it would be helpful<00:48:17.040> to<00:48:17.440> understand<00:48:18.000> you<00:48:18.079> know<00:48:18.240> how<00:48:18.319> much 00:48:19.190 --> 00:48:19.200 align:start position:0% helpful to understand you know how much 00:48:19.200 --> 00:48:21.030 align:start position:0% helpful to understand you know how much how<00:48:19.359> much<00:48:19.599> non-spin<00:48:20.079> our<00:48:20.240> cot<00:48:20.400> would<00:48:20.559> rely<00:48:20.880> on 00:48:21.030 --> 00:48:21.040 align:start position:0% how much non-spin our cot would rely on 00:48:21.040 --> 00:48:22.790 align:start position:0% how much non-spin our cot would rely on to<00:48:21.200> address<00:48:21.440> the<00:48:21.520> curve<00:48:21.760> how<00:48:21.920> much<00:48:22.079> ecrs<00:48:22.640> would 00:48:22.790 --> 00:48:22.800 align:start position:0% to address the curve how much ecrs would 00:48:22.800 --> 00:48:27.030 align:start position:0% to address the curve how much ecrs would be<00:48:22.960> needed<00:48:23.599> um<00:48:24.400> to<00:48:24.559> address<00:48:24.880> the<00:48:25.040> curve<00:48:25.599> and 00:48:27.030 --> 00:48:27.040 align:start position:0% be needed um to address the curve and 00:48:27.040 --> 00:48:28.230 align:start position:0% be needed um to address the curve and you<00:48:27.119> know<00:48:27.200> what<00:48:27.440> kind<00:48:27.599> of<00:48:27.680> load<00:48:27.920> what's<00:48:28.160> the 00:48:28.230 --> 00:48:28.240 align:start position:0% you know what kind of load what's the 00:48:28.240 --> 00:48:29.750 align:start position:0% you know what kind of load what's the estimate<00:48:28.640> behavior<00:48:29.040> we<00:48:29.200> have<00:48:29.520> you<00:48:29.599> all<00:48:29.680> have 00:48:29.750 --> 00:48:29.760 align:start position:0% estimate behavior we have you all have 00:48:29.760 --> 00:48:31.990 align:start position:0% estimate behavior we have you all have an<00:48:29.920> estimate<00:48:30.240> of<00:48:30.480> when<00:48:30.800> ecrs<00:48:31.359> opens<00:48:31.680> up<00:48:31.760> what's 00:48:31.990 --> 00:48:32.000 align:start position:0% an estimate of when ecrs opens up what's 00:48:32.000 --> 00:48:33.349 align:start position:0% an estimate of when ecrs opens up what's the<00:48:32.079> estimated<00:48:32.640> them<00:48:32.800> i<00:48:32.880> don't<00:48:33.040> have<00:48:33.200> that 00:48:33.349 --> 00:48:33.359 align:start position:0% the estimated them i don't have that 00:48:33.359 --> 00:48:35.510 align:start position:0% the estimated them i don't have that with<00:48:33.599> me<00:48:34.079> okay<00:48:34.400> last<00:48:34.640> i<00:48:34.720> got<00:48:34.880> was<00:48:35.040> five<00:48:35.359> to 00:48:35.510 --> 00:48:35.520 align:start position:0% with me okay last i got was five to 00:48:35.520 --> 00:48:36.630 align:start position:0% with me okay last i got was five to seven 00:48:36.630 --> 00:48:36.640 align:start position:0% seven 00:48:36.640 --> 00:48:38.069 align:start position:0% seven gigawatts 00:48:38.069 --> 00:48:38.079 align:start position:0% gigawatts 00:48:38.079 --> 00:48:40.309 align:start position:0% gigawatts big<00:48:38.559> big<00:48:38.880> estimate<00:48:39.359> on<00:48:39.520> that<00:48:39.680> one<00:48:39.920> so<00:48:40.079> i<00:48:40.240> think 00:48:40.309 --> 00:48:40.319 align:start position:0% big big estimate on that one so i think 00:48:40.319 --> 00:48:41.750 align:start position:0% big big estimate on that one so i think we<00:48:40.480> just<00:48:40.640> need 00:48:41.750 --> 00:48:41.760 align:start position:0% we just need 00:48:41.760 --> 00:48:44.549 align:start position:0% we just need a<00:48:41.920> vcrs<00:48:42.880> every<00:48:43.119> day<00:48:43.280> you<00:48:43.440> have<00:48:43.520> to<00:48:43.599> go<00:48:43.760> buy<00:48:44.160> 7 00:48:44.549 --> 00:48:44.559 align:start position:0% a vcrs every day you have to go buy 7 00:48:44.559 --> 00:48:46.950 align:start position:0% a vcrs every day you have to go buy 7 000<00:48:44.800> megawatts<00:48:45.280> of<00:48:45.359> ecrs<00:48:46.079> in<00:48:46.240> case<00:48:46.559> the<00:48:46.720> wind 00:48:46.950 --> 00:48:46.960 align:start position:0% 000 megawatts of ecrs in case the wind 00:48:46.960 --> 00:48:49.430 align:start position:0% 000 megawatts of ecrs in case the wind doesn't<00:48:47.280> pick<00:48:47.520> up<00:48:47.839> fast<00:48:48.160> enough<00:48:48.640> right 00:48:49.430 --> 00:48:49.440 align:start position:0% doesn't pick up fast enough right 00:48:49.440 --> 00:48:52.470 align:start position:0% doesn't pick up fast enough right um<00:48:50.000> and<00:48:50.079> that's<00:48:50.880> in<00:48:51.119> 18<00:48:51.520> months 00:48:52.470 --> 00:48:52.480 align:start position:0% um and that's in 18 months 00:48:52.480 --> 00:48:54.069 align:start position:0% um and that's in 18 months so 00:48:54.069 --> 00:48:54.079 align:start position:0% so 00:48:54.079 --> 00:48:56.549 align:start position:0% so 18<00:48:54.480> months<00:48:54.720> after<00:48:55.040> that<00:48:55.359> you<00:48:55.440> get<00:48:55.599> to<00:48:55.839> will's 00:48:56.549 --> 00:48:56.559 align:start position:0% 18 months after that you get to will's 00:48:56.559 --> 00:48:59.190 align:start position:0% 18 months after that you get to will's 30<00:48:56.880> gig 00:48:59.190 --> 00:48:59.200 align:start position:0% 00:48:59.200 --> 00:49:01.510 align:start position:0% problem<00:48:59.599> and<00:48:59.680> that<00:48:59.920> that<00:49:00.240> analysis<00:49:00.720> for<00:49:01.280> call 00:49:01.510 --> 00:49:01.520 align:start position:0% problem and that that analysis for call 00:49:01.520 --> 00:49:04.230 align:start position:0% problem and that that analysis for call it<00:49:01.680> six<00:49:02.240> six<00:49:02.480> thousand<00:49:02.800> megawatts 00:49:04.230 --> 00:49:04.240 align:start position:0% it six six thousand megawatts 00:49:04.240 --> 00:49:06.950 align:start position:0% it six six thousand megawatts uh<00:49:04.559> should<00:49:04.800> include<00:49:05.200> all<00:49:05.359> of<00:49:05.520> ercot's 00:49:06.950 --> 00:49:06.960 align:start position:0% uh should include all of ercot's 00:49:06.960 --> 00:49:07.910 align:start position:0% uh should include all of ercot's uh 00:49:07.910 --> 00:49:07.920 align:start position:0% uh 00:49:07.920 --> 00:49:10.069 align:start position:0% uh an<00:49:08.160> out<00:49:08.319> load<00:49:08.559> analysis<00:49:09.359> including<00:49:09.760> all<00:49:10.000> the 00:49:10.069 --> 00:49:10.079 align:start position:0% an out load analysis including all the 00:49:10.079 --> 00:49:11.510 align:start position:0% an out load analysis including all the resources<00:49:10.559> they<00:49:10.720> expect<00:49:11.040> to<00:49:11.119> have<00:49:11.280> in<00:49:11.359> their 00:49:11.510 --> 00:49:11.520 align:start position:0% resources they expect to have in their 00:49:11.520 --> 00:49:13.349 align:start position:0% resources they expect to have in their operating<00:49:11.839> plan<00:49:12.079> is<00:49:12.160> that<00:49:12.319> fair<00:49:12.480> woody<00:49:13.119> yeah<00:49:13.280> i 00:49:13.349 --> 00:49:13.359 align:start position:0% operating plan is that fair woody yeah i 00:49:13.359 --> 00:49:14.790 align:start position:0% operating plan is that fair woody yeah i mean<00:49:13.680> we're<00:49:13.839> not<00:49:14.000> gonna<00:49:14.160> get<00:49:14.240> to<00:49:14.400> that<00:49:14.480> blue 00:49:14.790 --> 00:49:14.800 align:start position:0% mean we're not gonna get to that blue 00:49:14.800 --> 00:49:15.589 align:start position:0% mean we're not gonna get to that blue line 00:49:15.589 --> 00:49:15.599 align:start position:0% line 00:49:15.599 --> 00:49:17.510 align:start position:0% line just<00:49:15.760> from<00:49:16.000> a<00:49:16.160> nursery<00:49:16.559> standpoint<00:49:17.119> that<00:49:17.359> that 00:49:17.510 --> 00:49:17.520 align:start position:0% just from a nursery standpoint that that 00:49:17.520 --> 00:49:19.109 align:start position:0% just from a nursery standpoint that that was<00:49:17.760> that's<00:49:18.000> a<00:49:18.079> very<00:49:18.400> important<00:49:18.720> thing<00:49:18.960> so 00:49:19.109 --> 00:49:19.119 align:start position:0% was that's a very important thing so 00:49:19.119 --> 00:49:19.910 align:start position:0% was that's a very important thing so let's<00:49:19.200> just 00:49:19.910 --> 00:49:19.920 align:start position:0% let's just 00:49:19.920 --> 00:49:21.510 align:start position:0% let's just talk<00:49:20.160> about<00:49:20.319> that<00:49:20.640> well 00:49:21.510 --> 00:49:21.520 align:start position:0% talk about that well 00:49:21.520 --> 00:49:22.950 align:start position:0% talk about that well there<00:49:21.760> is<00:49:21.920> a 00:49:22.950 --> 00:49:22.960 align:start position:0% there is a 00:49:22.960 --> 00:49:27.670 align:start position:0% there is a yeah<00:49:23.520> i<00:49:23.599> mean<00:49:23.839> 20<00:49:24.240> 000.<00:49:24.880> yeah<00:49:25.359> so<00:49:25.839> 28<00:49:26.319> 000<00:49:26.559> sorry 00:49:27.670 --> 00:49:27.680 align:start position:0% yeah i mean 20 000. yeah so 28 000 sorry 00:49:27.680 --> 00:49:30.069 align:start position:0% yeah i mean 20 000. yeah so 28 000 sorry with<00:49:28.240> technology<00:49:28.880> that<00:49:28.960> we<00:49:29.119> have<00:49:29.280> today<00:49:29.839> the 00:49:30.069 --> 00:49:30.079 align:start position:0% with technology that we have today the 00:49:30.079 --> 00:49:31.670 align:start position:0% with technology that we have today the fleet<00:49:30.319> that<00:49:30.400> we<00:49:30.480> have<00:49:30.640> today<00:49:30.960> we<00:49:31.119> will<00:49:31.280> have<00:49:31.440> to 00:49:31.670 --> 00:49:31.680 align:start position:0% fleet that we have today we will have to 00:49:31.680 --> 00:49:33.349 align:start position:0% fleet that we have today we will have to maintain<00:49:32.160> some<00:49:32.400> synchronous<00:49:32.800> units<00:49:33.119> on<00:49:33.200> the 00:49:33.349 --> 00:49:33.359 align:start position:0% maintain some synchronous units on the 00:49:33.359 --> 00:49:35.750 align:start position:0% maintain some synchronous units on the grid<00:49:33.599> to<00:49:33.760> maintain<00:49:34.160> inertia<00:49:34.800> and<00:49:34.960> so<00:49:35.520> that 00:49:35.750 --> 00:49:35.760 align:start position:0% grid to maintain inertia and so that 00:49:35.760 --> 00:49:37.829 align:start position:0% grid to maintain inertia and so that blue<00:49:36.000> line<00:49:36.480> won't<00:49:36.720> happen 00:49:37.829 --> 00:49:37.839 align:start position:0% blue line won't happen 00:49:37.839 --> 00:49:39.349 align:start position:0% blue line won't happen why<00:49:38.240> because 00:49:39.349 --> 00:49:39.359 align:start position:0% why because 00:49:39.359 --> 00:49:40.950 align:start position:0% why because we<00:49:39.440> would<00:49:39.599> just<00:49:39.760> have<00:49:39.920> to<00:49:40.000> turn<00:49:40.319> solar<00:49:40.640> off 00:49:40.950 --> 00:49:40.960 align:start position:0% we would just have to turn solar off 00:49:40.960 --> 00:49:41.990 align:start position:0% we would just have to turn solar off you're<00:49:41.119> going<00:49:41.200> to<00:49:41.280> curtail<00:49:41.599> them<00:49:41.760> we'll 00:49:41.990 --> 00:49:42.000 align:start position:0% you're going to curtail them we'll 00:49:42.000 --> 00:49:44.710 align:start position:0% you're going to curtail them we'll curtail<00:49:42.400> them<00:49:42.559> for<00:49:42.880> reliability 00:49:44.710 --> 00:49:44.720 align:start position:0% curtail them for reliability 00:49:44.720 --> 00:49:46.069 align:start position:0% curtail them for reliability grid<00:49:44.960> yes 00:49:46.069 --> 00:49:46.079 align:start position:0% grid yes 00:49:46.079 --> 00:49:48.150 align:start position:0% grid yes okay<00:49:46.319> what<00:49:46.559> number<00:49:46.800> is<00:49:46.960> that 00:49:48.150 --> 00:49:48.160 align:start position:0% okay what number is that 00:49:48.160 --> 00:49:50.710 align:start position:0% okay what number is that well<00:49:48.319> we<00:49:48.480> have<00:49:48.640> to<00:49:48.720> maintain<00:49:49.200> 109<00:49:50.160> gigawatt 00:49:50.710 --> 00:49:50.720 align:start position:0% well we have to maintain 109 gigawatt 00:49:50.720 --> 00:49:53.349 align:start position:0% well we have to maintain 109 gigawatt seconds<00:49:51.200> at<00:49:51.359> least<00:49:51.920> of<00:49:52.079> inertia 00:49:53.349 --> 00:49:53.359 align:start position:0% seconds at least of inertia 00:49:53.359 --> 00:49:54.630 align:start position:0% seconds at least of inertia which 00:49:54.630 --> 00:49:54.640 align:start position:0% which 00:49:54.640 --> 00:49:56.230 align:start position:0% which depending<00:49:54.960> on<00:49:55.040> what<00:49:55.280> units<00:49:55.599> are<00:49:55.760> running 00:49:56.230 --> 00:49:56.240 align:start position:0% depending on what units are running 00:49:56.240 --> 00:49:57.910 align:start position:0% depending on what units are running translates<00:49:56.720> to<00:49:56.880> a<00:49:56.960> certain<00:49:57.280> amount<00:49:57.520> of 00:49:57.910 --> 00:49:57.920 align:start position:0% translates to a certain amount of 00:49:57.920 --> 00:49:59.589 align:start position:0% translates to a certain amount of generation<00:49:58.480> and<00:49:58.559> we<00:49:58.640> can<00:49:59.040> i<00:49:59.119> can<00:49:59.200> give<00:49:59.359> you<00:49:59.440> an 00:49:59.589 --> 00:49:59.599 align:start position:0% generation and we can i can give you an 00:49:59.599 --> 00:50:01.430 align:start position:0% generation and we can i can give you an estimate<00:49:59.920> of<00:50:00.000> that<00:50:00.240> but<00:50:00.880> it's<00:50:01.119> different 00:50:01.430 --> 00:50:01.440 align:start position:0% estimate of that but it's different 00:50:01.440 --> 00:50:03.270 align:start position:0% estimate of that but it's different depending<00:50:01.760> on<00:50:01.839> what<00:50:02.000> generation<00:50:02.480> is<00:50:02.640> running 00:50:03.270 --> 00:50:03.280 align:start position:0% depending on what generation is running 00:50:03.280 --> 00:50:05.030 align:start position:0% depending on what generation is running sure<00:50:03.680> so<00:50:04.079> some<00:50:04.240> generators<00:50:04.720> have<00:50:04.880> more 00:50:05.030 --> 00:50:05.040 align:start position:0% sure so some generators have more 00:50:05.040 --> 00:50:06.470 align:start position:0% sure so some generators have more inertia<00:50:05.440> than<00:50:05.599> others 00:50:06.470 --> 00:50:06.480 align:start position:0% inertia than others 00:50:06.480 --> 00:50:08.470 align:start position:0% inertia than others at<00:50:06.640> some<00:50:06.880> point<00:50:07.200> is<00:50:07.359> this 00:50:08.470 --> 00:50:08.480 align:start position:0% at some point is this 00:50:08.480 --> 00:50:10.710 align:start position:0% at some point is this right<00:50:08.880> it'll<00:50:09.200> depend<00:50:09.599> hour<00:50:09.839> to<00:50:10.000> hour<00:50:10.480> right 00:50:10.710 --> 00:50:10.720 align:start position:0% right it'll depend hour to hour right 00:50:10.720 --> 00:50:12.870 align:start position:0% right it'll depend hour to hour right but<00:50:10.880> at<00:50:11.040> some<00:50:11.280> point<00:50:11.839> in<00:50:12.000> order<00:50:12.319> to<00:50:12.480> maintain 00:50:12.870 --> 00:50:12.880 align:start position:0% but at some point in order to maintain 00:50:12.880 --> 00:50:15.270 align:start position:0% but at some point in order to maintain stability<00:50:13.359> of<00:50:13.520> the<00:50:13.599> grid 00:50:15.270 --> 00:50:15.280 align:start position:0% stability of the grid 00:50:15.280 --> 00:50:17.270 align:start position:0% stability of the grid whether<00:50:15.599> it's<00:50:15.920> solar<00:50:16.319> or<00:50:16.400> wind<00:50:16.640> whether<00:50:16.960> the 00:50:17.270 --> 00:50:17.280 align:start position:0% whether it's solar or wind whether the 00:50:17.280 --> 00:50:18.950 align:start position:0% whether it's solar or wind whether the the<00:50:17.520> level<00:50:17.760> of<00:50:17.920> intermittence<00:50:18.480> has<00:50:18.640> to<00:50:18.800> be 00:50:18.950 --> 00:50:18.960 align:start position:0% the level of intermittence has to be 00:50:18.960 --> 00:50:20.150 align:start position:0% the level of intermittence has to be curtailed 00:50:20.150 --> 00:50:20.160 align:start position:0% curtailed 00:50:20.160 --> 00:50:21.990 align:start position:0% curtailed but<00:50:20.319> we<00:50:20.480> cannot<00:50:20.800> maintain<00:50:21.200> reliable<00:50:21.599> grid 00:50:21.990 --> 00:50:22.000 align:start position:0% but we cannot maintain reliable grid 00:50:22.000 --> 00:50:24.069 align:start position:0% but we cannot maintain reliable grid with<00:50:22.319> the<00:50:22.640> inverter<00:50:23.119> technologies<00:50:23.760> we<00:50:23.920> have 00:50:24.069 --> 00:50:24.079 align:start position:0% with the inverter technologies we have 00:50:24.079 --> 00:50:26.630 align:start position:0% with the inverter technologies we have today<00:50:24.319> that's<00:50:24.559> true<00:50:24.880> yes<00:50:25.760> okay<00:50:26.079> and<00:50:26.240> it's<00:50:26.480> not 00:50:26.630 --> 00:50:26.640 align:start position:0% today that's true yes okay and it's not 00:50:26.640 --> 00:50:28.549 align:start position:0% today that's true yes okay and it's not going<00:50:26.720> to<00:50:26.880> change<00:50:27.200> in<00:50:27.280> the<00:50:27.359> next<00:50:27.599> three<00:50:27.839> years 00:50:28.549 --> 00:50:28.559 align:start position:0% going to change in the next three years 00:50:28.559 --> 00:50:29.990 align:start position:0% going to change in the next three years and<00:50:28.720> what<00:50:28.880> level<00:50:29.119> would<00:50:29.280> that<00:50:29.440> be<00:50:29.680> like<00:50:29.839> from 00:50:29.990 --> 00:50:30.000 align:start position:0% and what level would that be like from 00:50:30.000 --> 00:50:30.950 align:start position:0% and what level would that be like from solar 00:50:30.950 --> 00:50:30.960 align:start position:0% solar 00:50:30.960 --> 00:50:32.630 align:start position:0% solar i<00:50:31.119> mean<00:50:31.280> how<00:50:31.440> much<00:50:31.599> solar<00:50:31.920> penetration<00:50:32.480> would 00:50:32.630 --> 00:50:32.640 align:start position:0% i mean how much solar penetration would 00:50:32.640 --> 00:50:34.309 align:start position:0% i mean how much solar penetration would you<00:50:32.720> have<00:50:32.880> to<00:50:32.960> see<00:50:33.200> to<00:50:33.520> to<00:50:34.000> pull<00:50:34.240> the 00:50:34.309 --> 00:50:34.319 align:start position:0% you have to see to to pull the 00:50:34.319 --> 00:50:35.910 align:start position:0% you have to see to to pull the curtailment<00:50:34.800> trigger<00:50:35.280> well<00:50:35.440> you<00:50:35.599> would<00:50:35.760> have 00:50:35.910 --> 00:50:35.920 align:start position:0% curtailment trigger well you would have 00:50:35.920 --> 00:50:37.510 align:start position:0% curtailment trigger well you would have to<00:50:36.000> maintain 00:50:37.510 --> 00:50:37.520 align:start position:0% to maintain 00:50:37.520 --> 00:50:40.309 align:start position:0% to maintain some<00:50:37.839> level<00:50:38.240> of<00:50:38.480> dispatchable<00:50:39.200> generation<00:50:40.160> so 00:50:40.309 --> 00:50:40.319 align:start position:0% some level of dispatchable generation so 00:50:40.319 --> 00:50:43.750 align:start position:0% some level of dispatchable generation so if<00:50:40.480> you<00:50:40.559> had<00:50:40.880> 40<00:50:41.280> 000<00:50:41.520> megawatts<00:50:42.160> of<00:50:42.400> load 00:50:43.750 --> 00:50:43.760 align:start position:0% if you had 40 000 megawatts of load 00:50:43.760 --> 00:50:45.910 align:start position:0% if you had 40 000 megawatts of load somewhere<00:50:44.319> i<00:50:44.480> don't<00:50:44.559> know<00:50:44.880> 20<00:50:45.200> 000<00:50:45.440> megawatts 00:50:45.910 --> 00:50:45.920 align:start position:0% somewhere i don't know 20 000 megawatts 00:50:45.920 --> 00:50:47.190 align:start position:0% somewhere i don't know 20 000 megawatts of<00:50:46.000> dispatchable<00:50:46.559> something<00:50:46.800> like<00:50:46.960> that<00:50:47.119> so 00:50:47.190 --> 00:50:47.200 align:start position:0% of dispatchable something like that so 00:50:47.200 --> 00:50:49.670 align:start position:0% of dispatchable something like that so that<00:50:47.359> leaves<00:50:47.680> 20<00:50:48.480> for<00:50:48.640> wind<00:50:48.880> and<00:50:49.040> solar 00:50:49.670 --> 00:50:49.680 align:start position:0% that leaves 20 for wind and solar 00:50:49.680 --> 00:50:51.750 align:start position:0% that leaves 20 for wind and solar something<00:50:50.079> like<00:50:50.319> that<00:50:51.040> so<00:50:51.200> you're<00:50:51.280> curtailing 00:50:51.750 --> 00:50:51.760 align:start position:0% something like that so you're curtailing 00:50:51.760 --> 00:50:56.470 align:start position:0% something like that so you're curtailing solar<00:50:52.079> at<00:50:52.240> 20 00:50:56.470 --> 00:50:56.480 align:start position:0% 00:50:56.480 --> 00:50:59.030 align:start position:0% so<00:50:56.720> i<00:50:56.800> think<00:50:57.040> you're<00:50:57.520> what<00:50:57.760> you<00:50:58.000> said 00:50:59.030 --> 00:50:59.040 align:start position:0% so i think you're what you said 00:50:59.040 --> 00:51:01.430 align:start position:0% so i think you're what you said it<00:50:59.200> makes<00:50:59.440> total<00:50:59.760> sense<00:51:00.000> to<00:51:00.079> me<00:51:00.240> and<00:51:00.559> it<00:51:00.880> makes 00:51:01.430 --> 00:51:01.440 align:start position:0% it makes total sense to me and it makes 00:51:01.440 --> 00:51:02.549 align:start position:0% it makes total sense to me and it makes my<00:51:01.599> point 00:51:02.549 --> 00:51:02.559 align:start position:0% my point 00:51:02.559 --> 00:51:04.630 align:start position:0% my point uh<00:51:02.960> it<00:51:03.119> sells<00:51:03.440> me<00:51:03.599> on<00:51:03.680> my<00:51:03.839> own<00:51:04.079> point<00:51:04.319> i<00:51:04.480> know 00:51:04.630 --> 00:51:04.640 align:start position:0% uh it sells me on my own point i know 00:51:04.640 --> 00:51:06.829 align:start position:0% uh it sells me on my own point i know that's<00:51:05.040> not<00:51:05.280> hard<00:51:05.440> to<00:51:05.520> do 00:51:06.829 --> 00:51:06.839 align:start position:0% that's not hard to do 00:51:06.839 --> 00:51:10.150 align:start position:0% that's not hard to do but<00:51:07.920> you<00:51:08.160> said<00:51:08.480> that<00:51:08.960> you're<00:51:09.200> not<00:51:09.680> we're<00:51:09.920> never 00:51:10.150 --> 00:51:10.160 align:start position:0% but you said that you're not we're never 00:51:10.160 --> 00:51:11.990 align:start position:0% but you said that you're not we're never going<00:51:10.319> to<00:51:10.400> get<00:51:10.559> to<00:51:10.640> the<00:51:10.720> blue<00:51:11.040> line 00:51:11.990 --> 00:51:12.000 align:start position:0% going to get to the blue line 00:51:12.000 --> 00:51:13.270 align:start position:0% going to get to the blue line because<00:51:12.319> we're<00:51:12.400> going<00:51:12.480> to<00:51:12.559> have<00:51:12.720> to<00:51:12.800> curtail 00:51:13.270 --> 00:51:13.280 align:start position:0% because we're going to have to curtail 00:51:13.280 --> 00:51:15.670 align:start position:0% because we're going to have to curtail some<00:51:13.440> solar<00:51:13.760> so<00:51:14.000> just<00:51:14.160> say<00:51:14.400> we<00:51:14.559> had 00:51:15.670 --> 00:51:15.680 align:start position:0% some solar so just say we had 00:51:15.680 --> 00:51:18.549 align:start position:0% some solar so just say we had 10<00:51:16.000> 000<00:51:16.319> megawatts 00:51:18.549 --> 00:51:18.559 align:start position:0% 10 000 megawatts 00:51:18.559 --> 00:51:20.870 align:start position:0% 10 000 megawatts let's<00:51:18.800> talk<00:51:19.040> about<00:51:19.200> this<00:51:19.359> one 00:51:20.870 --> 00:51:20.880 align:start position:0% let's talk about this one 00:51:20.880 --> 00:51:22.870 align:start position:0% let's talk about this one well<00:51:21.280> it's<00:51:21.599> the<00:51:21.760> same<00:51:22.000> thing<00:51:22.160> in<00:51:22.319> my<00:51:22.559> we're 00:51:22.870 --> 00:51:22.880 align:start position:0% well it's the same thing in my we're 00:51:22.880 --> 00:51:24.870 align:start position:0% well it's the same thing in my we're we're<00:51:23.119> trying<00:51:23.280> to<00:51:23.359> deal<00:51:23.520> with<00:51:23.680> this<00:51:23.839> ramp<00:51:24.640> okay 00:51:24.870 --> 00:51:24.880 align:start position:0% we're trying to deal with this ramp okay 00:51:24.880 --> 00:51:26.950 align:start position:0% we're trying to deal with this ramp okay so<00:51:25.119> you<00:51:25.200> cut<00:51:25.440> 10<00:51:25.680> off<00:51:25.920> the<00:51:26.000> top 00:51:26.950 --> 00:51:26.960 align:start position:0% so you cut 10 off the top 00:51:26.960 --> 00:51:28.790 align:start position:0% so you cut 10 off the top or<00:51:27.119> you<00:51:27.280> cut<00:51:27.440> 10<00:51:27.680> off<00:51:27.839> the<00:51:27.920> bottom<00:51:28.400> what<00:51:28.559> you're 00:51:28.790 --> 00:51:28.800 align:start position:0% or you cut 10 off the bottom what you're 00:51:28.800 --> 00:51:31.829 align:start position:0% or you cut 10 off the bottom what you're still<00:51:29.040> dealing<00:51:29.440> with<00:51:30.000> is<00:51:30.480> is<00:51:30.720> not<00:51:30.960> a<00:51:31.280> 20 00:51:31.829 --> 00:51:31.839 align:start position:0% still dealing with is is not a 20 00:51:31.839 --> 00:51:33.349 align:start position:0% still dealing with is is not a 20 something<00:51:32.240> megawatt<00:51:32.720> ramp<00:51:33.040> you're<00:51:33.119> dealing 00:51:33.349 --> 00:51:33.359 align:start position:0% something megawatt ramp you're dealing 00:51:33.359 --> 00:51:36.230 align:start position:0% something megawatt ramp you're dealing with<00:51:33.599> a<00:51:33.680> 10<00:51:34.319> gigawatt<00:51:34.880> ramp<00:51:35.599> because<00:51:35.920> you<00:51:36.079> have 00:51:36.230 --> 00:51:36.240 align:start position:0% with a 10 gigawatt ramp because you have 00:51:36.240 --> 00:51:39.430 align:start position:0% with a 10 gigawatt ramp because you have to<00:51:36.400> keep<00:51:36.640> some<00:51:36.800> of<00:51:36.960> your<00:51:37.520> your<00:51:38.079> thermals<00:51:38.640> on 00:51:39.430 --> 00:51:39.440 align:start position:0% to keep some of your your thermals on 00:51:39.440 --> 00:51:41.750 align:start position:0% to keep some of your your thermals on line<00:51:39.839> because<00:51:40.160> what<00:51:40.319> you're<00:51:40.480> doing<00:51:40.960> is<00:51:41.599> you've 00:51:41.750 --> 00:51:41.760 align:start position:0% line because what you're doing is you've 00:51:41.760 --> 00:51:44.069 align:start position:0% line because what you're doing is you've got<00:51:41.920> to<00:51:42.079> creep<00:51:42.319> the<00:51:42.720> keep<00:51:42.880> the<00:51:43.040> inertia<00:51:43.839> of<00:51:43.920> the 00:51:44.069 --> 00:51:44.079 align:start position:0% got to creep the keep the inertia of the 00:51:44.079 --> 00:51:46.470 align:start position:0% got to creep the keep the inertia of the system<00:51:44.559> going<00:51:45.440> now<00:51:45.680> i<00:51:45.839> do<00:51:46.079> know<00:51:46.240> that<00:51:46.400> there 00:51:46.470 --> 00:51:46.480 align:start position:0% system going now i do know that there 00:51:46.480 --> 00:51:48.150 align:start position:0% system going now i do know that there are<00:51:46.640> studies<00:51:47.040> out<00:51:47.119> there<00:51:47.280> that<00:51:47.520> say<00:51:47.839> the<00:51:48.000> more 00:51:48.150 --> 00:51:48.160 align:start position:0% are studies out there that say the more 00:51:48.160 --> 00:51:49.670 align:start position:0% are studies out there that say the more batteries<00:51:48.640> you<00:51:48.720> have<00:51:48.880> on<00:51:48.960> the<00:51:49.119> system<00:51:49.520> the 00:51:49.670 --> 00:51:49.680 align:start position:0% batteries you have on the system the 00:51:49.680 --> 00:51:51.589 align:start position:0% batteries you have on the system the less<00:51:49.920> inertia<00:51:50.319> you're<00:51:50.480> going<00:51:50.559> to<00:51:50.720> need 00:51:51.589 --> 00:51:51.599 align:start position:0% less inertia you're going to need 00:51:51.599 --> 00:51:53.910 align:start position:0% less inertia you're going to need right<00:51:51.839> and<00:51:52.000> i<00:51:52.160> think<00:51:52.559> that's<00:51:53.040> a<00:51:53.200> longer<00:51:53.599> term 00:51:53.910 --> 00:51:53.920 align:start position:0% right and i think that's a longer term 00:51:53.920 --> 00:51:55.270 align:start position:0% right and i think that's a longer term study<00:51:54.240> that<00:51:54.400> we're<00:51:54.559> going<00:51:54.640> to<00:51:54.720> have<00:51:54.880> to<00:51:54.960> get<00:51:55.119> to 00:51:55.270 --> 00:51:55.280 align:start position:0% study that we're going to have to get to 00:51:55.280 --> 00:51:57.589 align:start position:0% study that we're going to have to get to at<00:51:55.440> some<00:51:55.599> point<00:51:55.760> in<00:51:55.920> time<00:51:56.160> because<00:51:56.400> that's<00:51:56.640> a 00:51:57.589 --> 00:51:57.599 align:start position:0% at some point in time because that's a 00:51:57.599 --> 00:51:59.750 align:start position:0% at some point in time because that's a uh<00:51:58.000> that's<00:51:58.240> a<00:51:58.400> really<00:51:58.720> important<00:51:59.119> issue<00:51:59.520> but 00:51:59.750 --> 00:51:59.760 align:start position:0% uh that's a really important issue but 00:51:59.760 --> 00:52:01.990 align:start position:0% uh that's a really important issue but uh<00:52:00.480> while<00:52:00.720> we're<00:52:00.960> in<00:52:01.040> this<00:52:01.280> transition<00:52:01.839> we 00:52:01.990 --> 00:52:02.000 align:start position:0% uh while we're in this transition we 00:52:02.000 --> 00:52:04.790 align:start position:0% uh while we're in this transition we can't<00:52:02.319> just<00:52:02.880> eliminate<00:52:03.520> the 00:52:04.790 --> 00:52:04.800 align:start position:0% can't just eliminate the 00:52:04.800 --> 00:52:06.710 align:start position:0% can't just eliminate the grid-forming 00:52:06.710 --> 00:52:06.720 align:start position:0% grid-forming 00:52:06.720 --> 00:52:09.589 align:start position:0% grid-forming inertia<00:52:07.359> plants 00:52:09.589 --> 00:52:09.599 align:start position:0% inertia plants 00:52:09.599 --> 00:52:12.470 align:start position:0% inertia plants and<00:52:10.000> i<00:52:10.079> don't<00:52:10.240> think<00:52:10.400> you<00:52:10.480> ever<00:52:10.720> can 00:52:12.470 --> 00:52:12.480 align:start position:0% and i don't think you ever can 00:52:12.480 --> 00:52:14.150 align:start position:0% and i don't think you ever can well<00:52:12.720> i<00:52:12.800> think<00:52:12.960> with<00:52:13.119> today's<00:52:13.440> technology<00:52:14.000> we 00:52:14.150 --> 00:52:14.160 align:start position:0% well i think with today's technology we 00:52:14.160 --> 00:52:16.790 align:start position:0% well i think with today's technology we can't<00:52:14.400> but<00:52:14.800> but<00:52:15.040> i<00:52:15.119> don't<00:52:15.280> know<00:52:15.520> i<00:52:15.599> mean 00:52:16.790 --> 00:52:16.800 align:start position:0% can't but but i don't know i mean 00:52:16.800 --> 00:52:18.309 align:start position:0% can't but but i don't know i mean so<00:52:17.040> i<00:52:17.119> think<00:52:17.200> that's<00:52:17.440> the<00:52:17.520> point<00:52:17.760> i<00:52:17.839> think<00:52:18.160> your 00:52:18.309 --> 00:52:18.319 align:start position:0% so i think that's the point i think your 00:52:18.319 --> 00:52:20.069 align:start position:0% so i think that's the point i think your point's<00:52:18.640> well<00:52:18.880> taken<00:52:19.359> both<00:52:19.599> of<00:52:19.680> your<00:52:19.839> points 00:52:20.069 --> 00:52:20.079 align:start position:0% point's well taken both of your points 00:52:20.079 --> 00:52:21.349 align:start position:0% point's well taken both of your points were<00:52:20.319> well<00:52:20.480> taken<00:52:20.720> and<00:52:20.800> they<00:52:21.119> are<00:52:21.200> not 00:52:21.349 --> 00:52:21.359 align:start position:0% were well taken and they are not 00:52:21.359 --> 00:52:23.430 align:start position:0% were well taken and they are not mutually<00:52:21.760> exclusive<00:52:22.480> the<00:52:22.640> point<00:52:22.960> is<00:52:23.119> we<00:52:23.280> have 00:52:23.430 --> 00:52:23.440 align:start position:0% mutually exclusive the point is we have 00:52:23.440 --> 00:52:26.710 align:start position:0% mutually exclusive the point is we have to<00:52:23.520> build<00:52:23.760> a<00:52:23.839> tool<00:52:24.640> that<00:52:24.960> allows<00:52:25.599> the<00:52:25.920> cheap 00:52:26.710 --> 00:52:26.720 align:start position:0% to build a tool that allows the cheap 00:52:26.720 --> 00:52:29.030 align:start position:0% to build a tool that allows the cheap zero<00:52:27.200> carbon<00:52:27.920> solar<00:52:28.319> which<00:52:28.559> is<00:52:28.720> going<00:52:28.800> to<00:52:28.880> be 00:52:29.030 --> 00:52:29.040 align:start position:0% zero carbon solar which is going to be 00:52:29.040 --> 00:52:31.510 align:start position:0% zero carbon solar which is going to be on<00:52:29.119> there<00:52:29.280> no<00:52:29.440> matter<00:52:29.760> what<00:52:30.559> to<00:52:30.720> be<00:52:31.119> uh 00:52:31.510 --> 00:52:31.520 align:start position:0% on there no matter what to be uh 00:52:31.520 --> 00:52:33.430 align:start position:0% on there no matter what to be uh absorbed<00:52:32.240> and<00:52:32.480> incorporated<00:52:33.119> into<00:52:33.280> the 00:52:33.430 --> 00:52:33.440 align:start position:0% absorbed and incorporated into the 00:52:33.440 --> 00:52:34.870 align:start position:0% absorbed and incorporated into the system<00:52:33.760> right<00:52:34.000> because<00:52:34.160> that<00:52:34.400> ultimately 00:52:34.870 --> 00:52:34.880 align:start position:0% system right because that ultimately 00:52:34.880 --> 00:52:36.309 align:start position:0% system right because that ultimately benefits<00:52:35.280> consumers<00:52:35.760> so<00:52:35.920> we're<00:52:36.000> trying<00:52:36.240> to 00:52:36.309 --> 00:52:36.319 align:start position:0% benefits consumers so we're trying to 00:52:36.319 --> 00:52:38.069 align:start position:0% benefits consumers so we're trying to normalize<00:52:36.880> cost<00:52:37.280> well<00:52:37.520> if<00:52:37.599> we've<00:52:37.839> got<00:52:38.000> an 00:52:38.069 --> 00:52:38.079 align:start position:0% normalize cost well if we've got an 00:52:38.079 --> 00:52:39.670 align:start position:0% normalize cost well if we've got an upper<00:52:38.400> limit<00:52:38.880> on 00:52:39.670 --> 00:52:39.680 align:start position:0% upper limit on 00:52:39.680 --> 00:52:42.309 align:start position:0% upper limit on the<00:52:40.079> upper<00:52:40.319> limit<00:52:40.559> on<00:52:40.720> the<00:52:40.800> problem<00:52:41.280> yeah 00:52:42.309 --> 00:52:42.319 align:start position:0% the upper limit on the problem yeah 00:52:42.319 --> 00:52:43.910 align:start position:0% the upper limit on the problem yeah uh<00:52:42.880> you<00:52:43.040> know 00:52:43.910 --> 00:52:43.920 align:start position:0% uh you know 00:52:43.920 --> 00:52:45.270 align:start position:0% uh you know and 00:52:45.270 --> 00:52:45.280 align:start position:0% and 00:52:45.280 --> 00:52:47.589 align:start position:0% and you<00:52:45.440> know<00:52:45.599> you're<00:52:45.839> curtailing<00:52:46.480> curtailing 00:52:47.589 --> 00:52:47.599 align:start position:0% you know you're curtailing curtailing 00:52:47.599 --> 00:52:50.390 align:start position:0% you know you're curtailing curtailing inverter-based<00:52:48.240> resources<00:52:48.960> at<00:52:49.520> x 00:52:50.390 --> 00:52:50.400 align:start position:0% inverter-based resources at x 00:52:50.400 --> 00:52:51.589 align:start position:0% inverter-based resources at x right<00:52:50.640> so<00:52:50.800> you've<00:52:50.880> got<00:52:50.960> an<00:52:51.040> upper<00:52:51.280> limit<00:52:51.520> on 00:52:51.589 --> 00:52:51.599 align:start position:0% right so you've got an upper limit on 00:52:51.599 --> 00:52:52.950 align:start position:0% right so you've got an upper limit on the<00:52:51.760> problem 00:52:52.950 --> 00:52:52.960 align:start position:0% the problem 00:52:52.960 --> 00:52:54.870 align:start position:0% the problem and<00:52:53.520> it<00:52:53.760> sounds<00:52:54.079> you<00:52:54.160> know<00:52:54.319> it<00:52:54.400> sounds<00:52:54.640> like 00:52:54.870 --> 00:52:54.880 align:start position:0% and it sounds you know it sounds like 00:52:54.880 --> 00:52:56.870 align:start position:0% and it sounds you know it sounds like it's<00:52:55.040> going<00:52:55.119> to<00:52:55.200> be<00:52:55.359> about<00:52:56.079> 10 00:52:56.870 --> 00:52:56.880 align:start position:0% it's going to be about 10 00:52:56.880 --> 00:52:58.950 align:start position:0% it's going to be about 10 10<00:52:57.200> 000<00:52:57.359> megawatts<00:52:57.839> yeah<00:52:57.920> that<00:52:58.079> was 00:52:58.950 --> 00:52:58.960 align:start position:0% 10 000 megawatts yeah that was 00:52:58.960 --> 00:53:00.790 align:start position:0% 10 000 megawatts yeah that was just<00:52:59.200> a<00:52:59.520> rough<00:52:59.839> estimate<00:53:00.160> we've<00:53:00.319> never<00:53:00.559> gone 00:53:00.790 --> 00:53:00.800 align:start position:0% just a rough estimate we've never gone 00:53:00.800 --> 00:53:02.349 align:start position:0% just a rough estimate we've never gone below 00:53:02.349 --> 00:53:02.359 align:start position:0% below 00:53:02.359 --> 00:53:05.030 align:start position:0% below 110<00:53:03.599> gigawatt<00:53:04.079> seconds 00:53:05.030 --> 00:53:05.040 align:start position:0% 110 gigawatt seconds 00:53:05.040 --> 00:53:07.030 align:start position:0% 110 gigawatt seconds we<00:53:05.119> did<00:53:05.280> that<00:53:05.440> in<00:53:05.680> march<00:53:06.000> of<00:53:06.240> of<00:53:06.480> this<00:53:06.640> year<00:53:06.880> we 00:53:07.030 --> 00:53:07.040 align:start position:0% we did that in march of of this year we 00:53:07.040 --> 00:53:08.950 align:start position:0% we did that in march of of this year we got<00:53:07.200> dominant<00:53:07.599> low<00:53:08.000> this<00:53:08.240> may<00:53:08.400> be<00:53:08.559> a<00:53:08.640> silly 00:53:08.950 --> 00:53:08.960 align:start position:0% got dominant low this may be a silly 00:53:08.960 --> 00:53:10.870 align:start position:0% got dominant low this may be a silly question<00:53:09.359> but<00:53:09.920> at<00:53:10.079> some<00:53:10.319> point<00:53:10.480> do<00:53:10.640> we<00:53:10.800> just 00:53:10.870 --> 00:53:10.880 align:start position:0% question but at some point do we just 00:53:10.880 --> 00:53:12.150 align:start position:0% question but at some point do we just build<00:53:11.119> in<00:53:11.200> a<00:53:11.280> margin<00:53:11.599> of<00:53:11.680> safety<00:53:12.000> under 00:53:12.150 --> 00:53:12.160 align:start position:0% build in a margin of safety under 00:53:12.160 --> 00:53:14.390 align:start position:0% build in a margin of safety under kertamlin<00:53:12.720> and<00:53:12.880> move<00:53:13.200> non-spin<00:53:13.680> up<00:53:13.839> to<00:53:13.920> 10<00:53:14.160> 000 00:53:14.390 --> 00:53:14.400 align:start position:0% kertamlin and move non-spin up to 10 000 00:53:14.400 --> 00:53:19.670 align:start position:0% kertamlin and move non-spin up to 10 000 megawatts<00:53:14.960> and<00:53:15.520> call<00:53:15.680> it<00:53:15.839> a<00:53:15.920> day 00:53:19.670 --> 00:53:19.680 align:start position:0% 00:53:19.680 --> 00:53:22.950 align:start position:0% possibly<00:53:20.640> i<00:53:20.720> mean<00:53:20.880> that's 00:53:22.950 --> 00:53:22.960 align:start position:0% possibly i mean that's 00:53:22.960 --> 00:53:24.390 align:start position:0% possibly i mean that's i<00:53:23.200> just<00:53:23.359> think<00:53:23.520> we<00:53:23.680> need<00:53:23.839> a<00:53:23.920> real<00:53:24.079> clear 00:53:24.390 --> 00:53:24.400 align:start position:0% i just think we need a real clear 00:53:24.400 --> 00:53:25.990 align:start position:0% i just think we need a real clear picture<00:53:24.960> on<00:53:25.280> you<00:53:25.440> know<00:53:25.599> what<00:53:25.760> are<00:53:25.920> our 00:53:25.990 --> 00:53:26.000 align:start position:0% picture on you know what are our 00:53:26.000 --> 00:53:27.670 align:start position:0% picture on you know what are our existing<00:53:26.400> tools<00:53:26.720> what<00:53:26.880> are<00:53:27.040> our<00:53:27.119> future<00:53:27.440> tools 00:53:27.670 --> 00:53:27.680 align:start position:0% existing tools what are our future tools 00:53:27.680 --> 00:53:29.430 align:start position:0% existing tools what are our future tools okay<00:53:27.839> well<00:53:28.319> i<00:53:28.400> mean<00:53:28.559> the<00:53:28.720> most<00:53:28.960> important 00:53:29.430 --> 00:53:29.440 align:start position:0% okay well i mean the most important 00:53:29.440 --> 00:53:30.549 align:start position:0% okay well i mean the most important question 00:53:30.549 --> 00:53:30.559 align:start position:0% question 00:53:30.559 --> 00:53:31.910 align:start position:0% question so<00:53:30.800> far<00:53:31.040> is<00:53:31.119> what<00:53:31.280> you<00:53:31.440> asked<00:53:31.680> what<00:53:31.760> are<00:53:31.839> we 00:53:31.910 --> 00:53:31.920 align:start position:0% so far is what you asked what are we 00:53:31.920 --> 00:53:33.990 align:start position:0% so far is what you asked what are we doing<00:53:32.160> over<00:53:32.319> the<00:53:32.400> next<00:53:32.559> 18<00:53:32.880> months 00:53:33.990 --> 00:53:34.000 align:start position:0% doing over the next 18 months 00:53:34.000 --> 00:53:35.190 align:start position:0% doing over the next 18 months right<00:53:34.160> because<00:53:34.400> this<00:53:34.640> i<00:53:34.640> mean<00:53:34.800> this<00:53:34.960> is<00:53:35.119> a 00:53:35.190 --> 00:53:35.200 align:start position:0% right because this i mean this is a 00:53:35.200 --> 00:53:37.430 align:start position:0% right because this i mean this is a problem<00:53:35.599> today<00:53:36.319> ecr's<00:53:37.040> has<00:53:37.200> been<00:53:37.359> in 00:53:37.430 --> 00:53:37.440 align:start position:0% problem today ecr's has been in 00:53:37.440 --> 00:53:39.670 align:start position:0% problem today ecr's has been in development<00:53:38.079> for<00:53:38.720> 12 00:53:39.670 --> 00:53:39.680 align:start position:0% development for 12 00:53:39.680 --> 00:53:41.349 align:start position:0% development for 12 how<00:53:39.839> many<00:53:40.240> three<00:53:40.400> years<00:53:40.640> i<00:53:40.720> think<00:53:40.880> three<00:53:41.040> years 00:53:41.349 --> 00:53:41.359 align:start position:0% how many three years i think three years 00:53:41.359 --> 00:53:43.349 align:start position:0% how many three years i think three years it's<00:53:41.520> been<00:53:41.680> in<00:53:41.760> the<00:53:41.839> oven<00:53:42.079> for<00:53:42.240> a<00:53:42.319> while<00:53:42.720> yeah 00:53:43.349 --> 00:53:43.359 align:start position:0% it's been in the oven for a while yeah 00:53:43.359 --> 00:53:45.270 align:start position:0% it's been in the oven for a while yeah but<00:53:43.760> that's<00:53:44.240> your<00:53:44.400> question<00:53:44.720> what<00:53:44.880> do<00:53:44.960> we<00:53:45.040> do 00:53:45.270 --> 00:53:45.280 align:start position:0% but that's your question what do we do 00:53:45.280 --> 00:53:46.870 align:start position:0% but that's your question what do we do today<00:53:46.079> is 00:53:46.870 --> 00:53:46.880 align:start position:0% today is 00:53:46.880 --> 00:53:48.870 align:start position:0% today is incredibly<00:53:47.839> important 00:53:48.870 --> 00:53:48.880 align:start position:0% incredibly important 00:53:48.880 --> 00:53:50.309 align:start position:0% incredibly important well<00:53:49.119> today<00:53:49.440> we're<00:53:49.599> going<00:53:49.760> to<00:53:49.839> monitor 00:53:50.309 --> 00:53:50.319 align:start position:0% well today we're going to monitor 00:53:50.319 --> 00:53:51.910 align:start position:0% well today we're going to monitor inertia 00:53:51.910 --> 00:53:51.920 align:start position:0% inertia 00:53:51.920 --> 00:53:53.349 align:start position:0% inertia if<00:53:52.160> we<00:53:52.319> have<00:53:52.559> to 00:53:53.349 --> 00:53:53.359 align:start position:0% if we have to 00:53:53.359 --> 00:53:55.190 align:start position:0% if we have to rock<00:53:53.680> units<00:53:54.240> that<00:53:54.400> are<00:53:54.559> synchronous<00:53:54.960> to<00:53:55.119> the 00:53:55.190 --> 00:53:55.200 align:start position:0% rock units that are synchronous to the 00:53:55.200 --> 00:53:57.750 align:start position:0% rock units that are synchronous to the grid<00:53:56.319> to<00:53:56.480> maintain<00:53:56.800> that<00:53:56.960> inertia<00:53:57.359> we<00:53:57.520> can<00:53:57.599> do 00:53:57.750 --> 00:53:57.760 align:start position:0% grid to maintain that inertia we can do 00:53:57.760 --> 00:53:59.510 align:start position:0% grid to maintain that inertia we can do that<00:53:58.160> we<00:53:58.319> have<00:53:58.480> those<00:53:58.720> tools<00:53:59.119> we<00:53:59.280> have<00:53:59.440> the 00:53:59.510 --> 00:53:59.520 align:start position:0% that we have those tools we have the 00:53:59.520 --> 00:54:01.430 align:start position:0% that we have those tools we have the tools<00:53:59.839> to<00:53:59.920> monitor<00:54:00.240> the<00:54:00.400> inertia 00:54:01.430 --> 00:54:01.440 align:start position:0% tools to monitor the inertia 00:54:01.440 --> 00:54:02.230 align:start position:0% tools to monitor the inertia so 00:54:02.230 --> 00:54:02.240 align:start position:0% so 00:54:02.240 --> 00:54:03.750 align:start position:0% so uh<00:54:02.960> you<00:54:03.040> know 00:54:03.750 --> 00:54:03.760 align:start position:0% uh you know 00:54:03.760 --> 00:54:05.030 align:start position:0% uh you know going<00:54:04.000> into<00:54:04.160> the<00:54:04.240> future<00:54:04.559> we're<00:54:04.800> going<00:54:04.880> to 00:54:05.030 --> 00:54:05.040 align:start position:0% going into the future we're going to 00:54:05.040 --> 00:54:06.870 align:start position:0% going into the future we're going to continue<00:54:05.440> to<00:54:05.599> develop<00:54:06.079> our 00:54:06.870 --> 00:54:06.880 align:start position:0% continue to develop our 00:54:06.880 --> 00:54:08.950 align:start position:0% continue to develop our our<00:54:07.280> uh<00:54:07.680> our<00:54:07.839> forecasting<00:54:08.720> we're<00:54:08.800> going<00:54:08.880> to 00:54:08.950 --> 00:54:08.960 align:start position:0% our uh our forecasting we're going to 00:54:08.960 --> 00:54:11.109 align:start position:0% our uh our forecasting we're going to continue<00:54:09.280> to<00:54:09.359> develop<00:54:10.319> tools<00:54:10.640> that<00:54:10.800> look<00:54:11.040> at 00:54:11.109 --> 00:54:11.119 align:start position:0% continue to develop tools that look at 00:54:11.119 --> 00:54:12.870 align:start position:0% continue to develop tools that look at these<00:54:11.359> ramps<00:54:11.760> to<00:54:11.839> make<00:54:12.000> sure<00:54:12.160> we<00:54:12.319> have 00:54:12.870 --> 00:54:12.880 align:start position:0% these ramps to make sure we have 00:54:12.880 --> 00:54:15.430 align:start position:0% these ramps to make sure we have generation<00:54:13.440> online<00:54:14.240> and<00:54:14.480> capable<00:54:14.960> of<00:54:15.119> meeting 00:54:15.430 --> 00:54:15.440 align:start position:0% generation online and capable of meeting 00:54:15.440 --> 00:54:17.109 align:start position:0% generation online and capable of meeting those<00:54:15.680> ramps<00:54:16.240> so<00:54:16.400> those<00:54:16.559> are<00:54:16.720> all<00:54:16.800> things<00:54:17.040> that 00:54:17.109 --> 00:54:17.119 align:start position:0% those ramps so those are all things that 00:54:17.119 --> 00:54:19.349 align:start position:0% those ramps so those are all things that are<00:54:17.280> in<00:54:17.359> the<00:54:17.440> works<00:54:17.760> today<00:54:18.480> the<00:54:18.800> problem<00:54:19.119> gets 00:54:19.349 --> 00:54:19.359 align:start position:0% are in the works today the problem gets 00:54:19.359 --> 00:54:21.670 align:start position:0% are in the works today the problem gets more<00:54:19.520> and<00:54:19.680> more<00:54:19.920> difficult<00:54:20.400> though<00:54:20.960> the<00:54:21.119> more 00:54:21.670 --> 00:54:21.680 align:start position:0% more and more difficult though the more 00:54:21.680 --> 00:54:22.829 align:start position:0% more and more difficult though the more wind<00:54:21.920> and<00:54:22.000> solar 00:54:22.829 --> 00:54:22.839 align:start position:0% wind and solar 00:54:22.839 --> 00:54:25.430 align:start position:0% wind and solar is<00:54:23.040> in<00:54:23.119> the<00:54:23.200> system<00:54:23.760> so<00:54:24.240> do<00:54:24.319> you<00:54:24.480> all<00:54:24.640> have<00:54:24.800> any 00:54:25.430 --> 00:54:25.440 align:start position:0% is in the system so do you all have any 00:54:25.440 --> 00:54:27.510 align:start position:0% is in the system so do you all have any have<00:54:25.680> you<00:54:25.839> all<00:54:26.400> talked<00:54:26.720> with<00:54:26.960> the<00:54:27.119> market 00:54:27.510 --> 00:54:27.520 align:start position:0% have you all talked with the market 00:54:27.520 --> 00:54:28.390 align:start position:0% have you all talked with the market about 00:54:28.390 --> 00:54:28.400 align:start position:0% about 00:54:28.400 --> 00:54:31.109 align:start position:0% about where<00:54:28.720> you<00:54:28.960> might<00:54:29.280> need<00:54:30.000> additional 00:54:31.109 --> 00:54:31.119 align:start position:0% where you might need additional 00:54:31.119 --> 00:54:33.030 align:start position:0% where you might need additional inertia<00:54:31.680> facilities<00:54:32.319> or<00:54:32.559> synchronous 00:54:33.030 --> 00:54:33.040 align:start position:0% inertia facilities or synchronous 00:54:33.040 --> 00:54:34.710 align:start position:0% inertia facilities or synchronous condensers<00:54:33.520> or<00:54:33.599> whatever<00:54:34.079> they<00:54:34.240> may<00:54:34.480> be 00:54:34.710 --> 00:54:34.720 align:start position:0% condensers or whatever they may be 00:54:34.720 --> 00:54:37.030 align:start position:0% condensers or whatever they may be that's<00:54:35.040> not<00:54:35.280> just<00:54:35.920> a<00:54:36.079> spinning<00:54:36.400> power<00:54:36.720> plant 00:54:37.030 --> 00:54:37.040 align:start position:0% that's not just a spinning power plant 00:54:37.040 --> 00:54:39.510 align:start position:0% that's not just a spinning power plant that<00:54:37.200> the<00:54:37.359> market<00:54:37.680> might<00:54:38.000> provide<00:54:38.720> have<00:54:38.960> you 00:54:39.510 --> 00:54:39.520 align:start position:0% that the market might provide have you 00:54:39.520 --> 00:54:41.510 align:start position:0% that the market might provide have you given<00:54:39.839> the<00:54:39.920> market<00:54:40.400> any<00:54:40.640> ideas<00:54:41.040> of<00:54:41.200> where 00:54:41.510 --> 00:54:41.520 align:start position:0% given the market any ideas of where 00:54:41.520 --> 00:54:42.309 align:start position:0% given the market any ideas of where those 00:54:42.309 --> 00:54:42.319 align:start position:0% those 00:54:42.319 --> 00:54:44.470 align:start position:0% those areas<00:54:42.880> might<00:54:43.040> need<00:54:43.280> to<00:54:43.359> be 00:54:44.470 --> 00:54:44.480 align:start position:0% areas might need to be 00:54:44.480 --> 00:54:46.710 align:start position:0% areas might need to be addressed<00:54:45.200> the<00:54:45.359> inertia<00:54:45.839> problem<00:54:46.160> is<00:54:46.400> really 00:54:46.710 --> 00:54:46.720 align:start position:0% addressed the inertia problem is really 00:54:46.720 --> 00:54:49.670 align:start position:0% addressed the inertia problem is really not<00:54:46.880> a<00:54:46.960> locational<00:54:47.599> problem<00:54:48.000> okay 00:54:49.670 --> 00:54:49.680 align:start position:0% not a locational problem okay 00:54:49.680 --> 00:54:51.910 align:start position:0% not a locational problem okay so<00:54:50.240> where<00:54:50.799> isn't<00:54:51.200> hasn't<00:54:51.520> been<00:54:51.680> something 00:54:51.910 --> 00:54:51.920 align:start position:0% so where isn't hasn't been something 00:54:51.920 --> 00:54:54.230 align:start position:0% so where isn't hasn't been something we've<00:54:52.160> discussed<00:54:52.960> okay 00:54:54.230 --> 00:54:54.240 align:start position:0% we've discussed okay 00:54:54.240 --> 00:54:55.190 align:start position:0% we've discussed okay and<00:54:54.319> there's 00:54:55.190 --> 00:54:55.200 align:start position:0% and there's 00:54:55.200 --> 00:54:57.349 align:start position:0% and there's there's<00:54:55.440> two<00:54:55.680> parts<00:54:56.000> of<00:54:56.160> it<00:54:56.559> right<00:54:56.960> some<00:54:57.200> can 00:54:57.349 --> 00:54:57.359 align:start position:0% there's two parts of it right some can 00:54:57.359 --> 00:54:59.589 align:start position:0% there's two parts of it right some can be<00:54:57.440> solved<00:54:57.760> by<00:54:57.920> the<00:54:58.000> synchronous<00:54:58.480> condensers 00:54:59.589 --> 00:54:59.599 align:start position:0% be solved by the synchronous condensers 00:54:59.599 --> 00:55:01.510 align:start position:0% be solved by the synchronous condensers some<00:54:59.760> of<00:54:59.920> it<00:55:00.000> cannot<00:55:00.559> be<00:55:00.720> solved<00:55:01.040> by<00:55:01.200> anything 00:55:01.510 --> 00:55:01.520 align:start position:0% some of it cannot be solved by anything 00:55:01.520 --> 00:55:06.230 align:start position:0% some of it cannot be solved by anything other<00:55:01.680> than<00:55:01.839> rotating<00:55:02.240> mass<00:55:02.480> is<00:55:02.640> that<00:55:02.720> correct 00:55:06.230 --> 00:55:06.240 align:start position:0% 00:55:06.240 --> 00:55:07.990 align:start position:0% so<00:55:06.400> they<00:55:06.559> both<00:55:06.880> provide<00:55:07.280> inertia<00:55:07.839> that's 00:55:07.990 --> 00:55:08.000 align:start position:0% so they both provide inertia that's 00:55:08.000 --> 00:55:09.510 align:start position:0% so they both provide inertia that's right<00:55:08.319> synchronous<00:55:08.720> condensers<00:55:09.280> provide 00:55:09.510 --> 00:55:09.520 align:start position:0% right synchronous condensers provide 00:55:09.520 --> 00:55:12.309 align:start position:0% right synchronous condensers provide inertia<00:55:10.079> and<00:55:10.640> both<00:55:10.960> kinds 00:55:12.309 --> 00:55:12.319 align:start position:0% inertia and both kinds 00:55:12.319 --> 00:55:13.750 align:start position:0% inertia and both kinds or<00:55:12.480> i<00:55:12.559> mean<00:55:12.720> all<00:55:12.960> elements<00:55:13.280> of<00:55:13.440> voltage 00:55:13.750 --> 00:55:13.760 align:start position:0% or i mean all elements of voltage 00:55:13.760 --> 00:55:15.190 align:start position:0% or i mean all elements of voltage support<00:55:14.079> and<00:55:14.160> grid<00:55:14.400> forming<00:55:14.640> capabilities 00:55:15.190 --> 00:55:15.200 align:start position:0% support and grid forming capabilities 00:55:15.200 --> 00:55:16.309 align:start position:0% support and grid forming capabilities sorry 00:55:16.309 --> 00:55:16.319 align:start position:0% sorry 00:55:16.319 --> 00:55:18.789 align:start position:0% sorry yes<00:55:16.720> fault<00:55:16.960> current<00:55:17.280> and<00:55:17.440> inertia<00:55:17.920> yes<00:55:18.559> okay 00:55:18.789 --> 00:55:18.799 align:start position:0% yes fault current and inertia yes okay 00:55:18.799 --> 00:55:19.670 align:start position:0% yes fault current and inertia yes okay so 00:55:19.670 --> 00:55:19.680 align:start position:0% so 00:55:19.680 --> 00:55:21.589 align:start position:0% so we<00:55:19.839> can<00:55:19.920> get<00:55:20.160> everything<00:55:20.480> we<00:55:20.640> need<00:55:21.359> from 00:55:21.589 --> 00:55:21.599 align:start position:0% we can get everything we need from 00:55:21.599 --> 00:55:23.190 align:start position:0% we can get everything we need from synchronous<00:55:22.000> condensers<00:55:22.720> today<00:55:23.040> with 00:55:23.190 --> 00:55:23.200 align:start position:0% synchronous condensers today with 00:55:23.200 --> 00:55:25.670 align:start position:0% synchronous condensers today with existing<00:55:23.599> technology 00:55:25.670 --> 00:55:25.680 align:start position:0% existing technology 00:55:25.680 --> 00:55:27.510 align:start position:0% existing technology for<00:55:25.920> all<00:55:26.160> grid<00:55:26.319> forming<00:55:26.640> capabilities<00:55:27.280> so<00:55:27.359> now 00:55:27.510 --> 00:55:27.520 align:start position:0% for all grid forming capabilities so now 00:55:27.520 --> 00:55:29.589 align:start position:0% for all grid forming capabilities so now synchronous<00:55:28.000> condensers<00:55:28.960> actually<00:55:29.280> do<00:55:29.440> have 00:55:29.589 --> 00:55:29.599 align:start position:0% synchronous condensers actually do have 00:55:29.599 --> 00:55:31.990 align:start position:0% synchronous condensers actually do have a<00:55:29.680> locational<00:55:30.240> component<00:55:30.640> to<00:55:30.880> them 00:55:31.990 --> 00:55:32.000 align:start position:0% a locational component to them 00:55:32.000 --> 00:55:34.309 align:start position:0% a locational component to them because<00:55:32.720> uh<00:55:33.040> like<00:55:33.280> in<00:55:33.440> in<00:55:33.599> the<00:55:33.680> panhandle<00:55:34.160> we 00:55:34.309 --> 00:55:34.319 align:start position:0% because uh like in in the panhandle we 00:55:34.319 --> 00:55:36.390 align:start position:0% because uh like in in the panhandle we need<00:55:34.799> synchronous<00:55:35.200> candidates<00:55:35.599> are<00:55:35.760> there 00:55:36.390 --> 00:55:36.400 align:start position:0% need synchronous candidates are there 00:55:36.400 --> 00:55:38.230 align:start position:0% need synchronous candidates are there because<00:55:36.640> of<00:55:36.880> weak<00:55:37.119> grid 00:55:38.230 --> 00:55:38.240 align:start position:0% because of weak grid 00:55:38.240 --> 00:55:39.270 align:start position:0% because of weak grid issues 00:55:39.270 --> 00:55:39.280 align:start position:0% issues 00:55:39.280 --> 00:55:41.270 align:start position:0% issues and<00:55:39.359> so<00:55:39.520> that<00:55:39.760> aids<00:55:40.079> in<00:55:40.319> the<00:55:40.480> uh<00:55:41.119> the 00:55:41.270 --> 00:55:41.280 align:start position:0% and so that aids in the uh the 00:55:41.280 --> 00:55:43.030 align:start position:0% and so that aids in the uh the interconnection<00:55:41.839> of<00:55:41.920> more<00:55:42.160> wind<00:55:42.400> and<00:55:42.559> solar 00:55:43.030 --> 00:55:43.040 align:start position:0% interconnection of more wind and solar 00:55:43.040 --> 00:55:44.549 align:start position:0% interconnection of more wind and solar in<00:55:43.200> the<00:55:43.280> panhandle 00:55:44.549 --> 00:55:44.559 align:start position:0% in the panhandle 00:55:44.559 --> 00:55:45.430 align:start position:0% in the panhandle but 00:55:45.430 --> 00:55:45.440 align:start position:0% but 00:55:45.440 --> 00:55:48.069 align:start position:0% but the<00:55:45.599> inertia<00:55:46.160> problem<00:55:46.559> for<00:55:46.720> a<00:55:46.880> grid<00:55:47.599> is<00:55:47.839> not<00:55:48.000> a 00:55:48.069 --> 00:55:48.079 align:start position:0% the inertia problem for a grid is not a 00:55:48.079 --> 00:55:50.710 align:start position:0% the inertia problem for a grid is not a locational<00:55:48.720> problem 00:55:50.710 --> 00:55:50.720 align:start position:0% locational problem 00:55:50.720 --> 00:55:51.750 align:start position:0% locational problem okay 00:55:51.750 --> 00:55:51.760 align:start position:0% okay 00:55:51.760 --> 00:55:53.190 align:start position:0% okay grid<00:55:52.079> forming 00:55:53.190 --> 00:55:53.200 align:start position:0% grid forming 00:55:53.200 --> 00:55:55.910 align:start position:0% grid forming weak<00:55:53.440> grid<00:55:53.680> issues<00:55:54.319> and<00:55:54.640> inertia<00:55:55.280> are<00:55:55.680> really 00:55:55.910 --> 00:55:55.920 align:start position:0% weak grid issues and inertia are really 00:55:55.920 --> 00:55:59.270 align:start position:0% weak grid issues and inertia are really two<00:55:56.160> separate<00:55:56.559> things 00:55:59.270 --> 00:55:59.280 align:start position:0% 00:55:59.280 --> 00:56:00.390 align:start position:0% go<00:55:59.440> ahead<00:55:59.599> lori 00:56:00.390 --> 00:56:00.400 align:start position:0% go ahead lori 00:56:00.400 --> 00:56:01.109 align:start position:0% go ahead lori so 00:56:01.109 --> 00:56:01.119 align:start position:0% so 00:56:01.119 --> 00:56:04.069 align:start position:0% so okay<00:56:01.680> that<00:56:02.240> i<00:56:02.559> i<00:56:02.960> was<00:56:03.119> just<00:56:03.280> gonna 00:56:04.069 --> 00:56:04.079 align:start position:0% okay that i i was just gonna 00:56:04.079 --> 00:56:05.510 align:start position:0% okay that i i was just gonna i<00:56:04.240> think<00:56:04.319> you<00:56:04.400> hit<00:56:04.640> on<00:56:04.720> my<00:56:04.880> point<00:56:05.040> woody<00:56:05.359> the 00:56:05.510 --> 00:56:05.520 align:start position:0% i think you hit on my point woody the 00:56:05.520 --> 00:56:06.950 align:start position:0% i think you hit on my point woody the synchronous<00:56:06.000> condensers<00:56:06.559> are<00:56:06.640> for 00:56:06.950 --> 00:56:06.960 align:start position:0% synchronous condensers are for 00:56:06.960 --> 00:56:08.630 align:start position:0% synchronous condensers are for transmission<00:56:07.440> lines<00:56:07.760> that<00:56:07.839> are<00:56:08.319> you<00:56:08.480> know 00:56:08.630 --> 00:56:08.640 align:start position:0% transmission lines that are you know 00:56:08.640 --> 00:56:11.510 align:start position:0% transmission lines that are you know crossing<00:56:09.520> many<00:56:09.760> miles<00:56:10.079> across<00:56:10.400> the<00:56:10.559> state<00:56:10.960> um 00:56:11.510 --> 00:56:11.520 align:start position:0% crossing many miles across the state um 00:56:11.520 --> 00:56:13.349 align:start position:0% crossing many miles across the state um to<00:56:11.839> create<00:56:12.160> that<00:56:12.319> stability<00:56:12.960> like<00:56:13.119> from<00:56:13.280> the 00:56:13.349 --> 00:56:13.359 align:start position:0% to create that stability like from the 00:56:13.359 --> 00:56:15.430 align:start position:0% to create that stability like from the panhandle<00:56:13.839> maybe<00:56:14.160> down<00:56:14.319> in<00:56:14.400> the<00:56:14.480> valley 00:56:15.430 --> 00:56:15.440 align:start position:0% panhandle maybe down in the valley 00:56:15.440 --> 00:56:17.030 align:start position:0% panhandle maybe down in the valley i<00:56:15.599> see<00:56:15.760> that<00:56:15.920> as<00:56:16.000> a<00:56:16.079> separate<00:56:16.400> kind<00:56:16.559> of<00:56:16.720> issue 00:56:17.030 --> 00:56:17.040 align:start position:0% i see that as a separate kind of issue 00:56:17.040 --> 00:56:19.030 align:start position:0% i see that as a separate kind of issue and<00:56:17.599> actually<00:56:18.000> one<00:56:18.240> that 00:56:19.030 --> 00:56:19.040 align:start position:0% and actually one that 00:56:19.040 --> 00:56:20.549 align:start position:0% and actually one that results<00:56:19.440> in<00:56:19.599> problems<00:56:19.920> with<00:56:20.160> renewable 00:56:20.549 --> 00:56:20.559 align:start position:0% results in problems with renewable 00:56:20.559 --> 00:56:21.990 align:start position:0% results in problems with renewable generation 00:56:21.990 --> 00:56:22.000 align:start position:0% generation 00:56:22.000 --> 00:56:24.150 align:start position:0% generation the<00:56:22.160> interaction<00:56:22.640> potentially<00:56:23.760> so<00:56:23.920> that's 00:56:24.150 --> 00:56:24.160 align:start position:0% the interaction potentially so that's 00:56:24.160 --> 00:56:26.069 align:start position:0% the interaction potentially so that's kind<00:56:24.319> of<00:56:24.400> a<00:56:24.480> separate<00:56:24.880> issue<00:56:25.200> i<00:56:25.280> guess 00:56:26.069 --> 00:56:26.079 align:start position:0% kind of a separate issue i guess 00:56:26.079 --> 00:56:29.670 align:start position:0% kind of a separate issue i guess so<00:56:26.319> just<00:56:26.480> to<00:56:26.640> really<00:56:26.960> kind<00:56:27.200> of<00:56:27.680> focus<00:56:28.079> on 00:56:29.670 --> 00:56:29.680 align:start position:0% so just to really kind of focus on 00:56:29.680 --> 00:56:31.430 align:start position:0% so just to really kind of focus on i<00:56:29.760> think<00:56:30.000> what<00:56:30.160> you're<00:56:30.319> asking<00:56:30.799> is<00:56:30.880> what<00:56:31.280> where 00:56:31.430 --> 00:56:31.440 align:start position:0% i think what you're asking is what where 00:56:31.440 --> 00:56:33.109 align:start position:0% i think what you're asking is what where do<00:56:31.520> we<00:56:31.599> get<00:56:31.760> this<00:56:31.920> inertia<00:56:32.319> support<00:56:32.640> what<00:56:32.880> type 00:56:33.109 --> 00:56:33.119 align:start position:0% do we get this inertia support what type 00:56:33.119 --> 00:56:34.950 align:start position:0% do we get this inertia support what type of<00:56:33.520> what<00:56:33.680> type<00:56:33.920> of<00:56:34.079> units 00:56:34.950 --> 00:56:34.960 align:start position:0% of what type of units 00:56:34.960 --> 00:56:36.069 align:start position:0% of what type of units sources 00:56:36.069 --> 00:56:36.079 align:start position:0% sources 00:56:36.079 --> 00:56:38.950 align:start position:0% sources and<00:56:36.559> well<00:56:36.880> and<00:56:37.119> all<00:56:37.359> grid<00:56:37.680> forming<00:56:38.319> yeah<00:56:38.720> all 00:56:38.950 --> 00:56:38.960 align:start position:0% and well and all grid forming yeah all 00:56:38.960 --> 00:56:40.470 align:start position:0% and well and all grid forming yeah all elements<00:56:39.359> of<00:56:39.599> of<00:56:39.760> the<00:56:39.920> grid<00:56:40.160> forming 00:56:40.470 --> 00:56:40.480 align:start position:0% elements of of the grid forming 00:56:40.480 --> 00:56:42.069 align:start position:0% elements of of the grid forming capabilities<00:56:40.960> that<00:56:41.040> we<00:56:41.119> need<00:56:41.599> and<00:56:41.760> is<00:56:41.839> this 00:56:42.069 --> 00:56:42.079 align:start position:0% capabilities that we need and is this 00:56:42.079 --> 00:56:44.470 align:start position:0% capabilities that we need and is this that's<00:56:42.319> another<00:56:42.839> challenge<00:56:44.079> that<00:56:44.160> we're<00:56:44.319> kind 00:56:44.470 --> 00:56:44.480 align:start position:0% that's another challenge that we're kind 00:56:44.480 --> 00:56:45.750 align:start position:0% that's another challenge that we're kind of<00:56:44.559> thinking<00:56:44.880> of<00:56:45.040> you're<00:56:45.200> thinking<00:56:45.440> about<00:56:45.599> all 00:56:45.750 --> 00:56:45.760 align:start position:0% of thinking of you're thinking about all 00:56:45.760 --> 00:56:47.750 align:start position:0% of thinking of you're thinking about all of<00:56:45.839> them<00:56:46.000> i<00:56:46.079> mean<00:56:46.720> i'm<00:56:46.799> trying<00:56:47.040> to<00:56:47.200> i<00:56:47.280> mean 00:56:47.750 --> 00:56:47.760 align:start position:0% of them i mean i'm trying to i mean 00:56:47.760 --> 00:56:49.510 align:start position:0% of them i mean i'm trying to i mean you've<00:56:48.000> laid<00:56:48.240> out<00:56:48.480> a 00:56:49.510 --> 00:56:49.520 align:start position:0% you've laid out a 00:56:49.520 --> 00:56:51.829 align:start position:0% you've laid out a a<00:56:50.000> tremendous<00:56:50.559> problem<00:56:51.200> that<00:56:51.359> we've<00:56:51.599> got<00:56:51.760> to 00:56:51.829 --> 00:56:51.839 align:start position:0% a tremendous problem that we've got to 00:56:51.839 --> 00:56:53.270 align:start position:0% a tremendous problem that we've got to address<00:56:52.400> right 00:56:53.270 --> 00:56:53.280 align:start position:0% address right 00:56:53.280 --> 00:56:54.069 align:start position:0% address right it's 00:56:54.069 --> 00:56:54.079 align:start position:0% it's 00:56:54.079 --> 00:56:55.430 align:start position:0% it's incredibly<00:56:54.480> important<00:56:54.880> that<00:56:54.960> you<00:56:55.119> posted 00:56:55.430 --> 00:56:55.440 align:start position:0% incredibly important that you posted 00:56:55.440 --> 00:56:57.589 align:start position:0% incredibly important that you posted this<00:56:55.680> so<00:56:56.160> people 00:56:57.589 --> 00:56:57.599 align:start position:0% this so people 00:56:57.599 --> 00:56:59.030 align:start position:0% this so people that<00:56:57.839> the<00:56:58.000> public<00:56:58.319> knows<00:56:58.559> that<00:56:58.720> this<00:56:58.960> is 00:56:59.030 --> 00:56:59.040 align:start position:0% that the public knows that this is 00:56:59.040 --> 00:57:01.750 align:start position:0% that the public knows that this is coming<00:56:59.599> and<00:56:59.760> knows<00:57:00.000> that<00:57:00.160> ercot's 00:57:01.750 --> 00:57:01.760 align:start position:0% coming and knows that ercot's 00:57:01.760 --> 00:57:03.349 align:start position:0% coming and knows that ercot's doing<00:57:02.079> the<00:57:02.160> analysis<00:57:02.559> to<00:57:02.720> identify<00:57:03.200> and 00:57:03.349 --> 00:57:03.359 align:start position:0% doing the analysis to identify and 00:57:03.359 --> 00:57:04.470 align:start position:0% doing the analysis to identify and quantify<00:57:03.839> it 00:57:04.470 --> 00:57:04.480 align:start position:0% quantify it 00:57:04.480 --> 00:57:07.109 align:start position:0% quantify it which<00:57:04.720> can<00:57:04.880> be<00:57:04.960> enhanced 00:57:07.109 --> 00:57:07.119 align:start position:0% which can be enhanced 00:57:07.119 --> 00:57:09.190 align:start position:0% which can be enhanced but<00:57:07.359> i'm<00:57:07.920> at<00:57:08.079> the<00:57:08.240> end<00:57:08.319> of<00:57:08.400> the<00:57:08.559> day<00:57:08.799> i'm<00:57:08.960> trying 00:57:09.190 --> 00:57:09.200 align:start position:0% but i'm at the end of the day i'm trying 00:57:09.200 --> 00:57:10.390 align:start position:0% but i'm at the end of the day i'm trying to 00:57:10.390 --> 00:57:10.400 align:start position:0% to 00:57:10.400 --> 00:57:11.990 align:start position:0% to solve<00:57:10.640> it<00:57:10.960> we're<00:57:11.119> trying<00:57:11.280> to<00:57:11.359> keep<00:57:11.599> the<00:57:11.680> lights 00:57:11.990 --> 00:57:12.000 align:start position:0% solve it we're trying to keep the lights 00:57:12.000 --> 00:57:15.030 align:start position:0% solve it we're trying to keep the lights on<00:57:12.160> right<00:57:12.880> yeah<00:57:13.280> over<00:57:13.440> the<00:57:13.520> next<00:57:13.760> 18<00:57:14.160> months 00:57:15.030 --> 00:57:15.040 align:start position:0% on right yeah over the next 18 months 00:57:15.040 --> 00:57:16.549 align:start position:0% on right yeah over the next 18 months over<00:57:15.280> the<00:57:15.359> next<00:57:15.599> five<00:57:15.839> years<00:57:16.079> or<00:57:16.240> the<00:57:16.400> three 00:57:16.549 --> 00:57:16.559 align:start position:0% over the next five years or the three 00:57:16.559 --> 00:57:19.030 align:start position:0% over the next five years or the three years<00:57:16.880> that<00:57:16.960> you<00:57:17.119> laid<00:57:17.359> out<00:57:17.599> in<00:57:17.760> this<00:57:18.400> uh<00:57:18.880> the 00:57:19.030 --> 00:57:19.040 align:start position:0% years that you laid out in this uh the 00:57:19.040 --> 00:57:20.630 align:start position:0% years that you laid out in this uh the barrage<00:57:19.599> of<00:57:19.839> intermittence<00:57:20.319> that<00:57:20.480> are<00:57:20.559> going 00:57:20.630 --> 00:57:20.640 align:start position:0% barrage of intermittence that are going 00:57:20.640 --> 00:57:22.549 align:start position:0% barrage of intermittence that are going to<00:57:20.720> be<00:57:20.799> coming<00:57:21.119> with<00:57:21.280> the<00:57:21.359> financial 00:57:22.549 --> 00:57:22.559 align:start position:0% to be coming with the financial 00:57:22.559 --> 00:57:24.549 align:start position:0% to be coming with the financial avalanche<00:57:23.119> behind<00:57:23.440> them 00:57:24.549 --> 00:57:24.559 align:start position:0% avalanche behind them 00:57:24.559 --> 00:57:26.710 align:start position:0% avalanche behind them and<00:57:24.799> in<00:57:24.960> five<00:57:25.200> years<00:57:25.680> when<00:57:25.839> you<00:57:26.000> double<00:57:26.319> that 00:57:26.710 --> 00:57:26.720 align:start position:0% and in five years when you double that 00:57:26.720 --> 00:57:28.789 align:start position:0% and in five years when you double that amount<00:57:27.040> of<00:57:27.200> intermittent<00:57:27.599> resources 00:57:28.789 --> 00:57:28.799 align:start position:0% amount of intermittent resources 00:57:28.799 --> 00:57:30.549 align:start position:0% amount of intermittent resources uh<00:57:29.200> so<00:57:29.440> we've<00:57:29.599> got<00:57:29.760> to<00:57:29.839> solve<00:57:30.160> all<00:57:30.319> these 00:57:30.549 --> 00:57:30.559 align:start position:0% uh so we've got to solve all these 00:57:30.559 --> 00:57:31.510 align:start position:0% uh so we've got to solve all these problems 00:57:31.510 --> 00:57:31.520 align:start position:0% problems 00:57:31.520 --> 00:57:34.069 align:start position:0% problems and<00:57:31.680> so<00:57:32.319> i<00:57:32.400> mean<00:57:32.559> that's<00:57:32.960> i<00:57:33.119> mean<00:57:33.359> the 00:57:34.069 --> 00:57:34.079 align:start position:0% and so i mean that's i mean the 00:57:34.079 --> 00:57:35.589 align:start position:0% and so i mean that's i mean the uh<00:57:34.400> i<00:57:34.559> can't<00:57:34.720> remember<00:57:34.880> which<00:57:35.119> work<00:57:35.359> session 00:57:35.589 --> 00:57:35.599 align:start position:0% uh i can't remember which work session 00:57:35.599 --> 00:57:37.030 align:start position:0% uh i can't remember which work session it<00:57:35.680> was<00:57:35.839> but<00:57:36.160> the<00:57:36.240> whole<00:57:36.559> there's<00:57:36.720> a<00:57:36.799> whole 00:57:37.030 --> 00:57:37.040 align:start position:0% it was but the whole there's a whole 00:57:37.040 --> 00:57:38.710 align:start position:0% it was but the whole there's a whole universe<00:57:37.440> of<00:57:37.520> grid<00:57:37.760> forming 00:57:38.710 --> 00:57:38.720 align:start position:0% universe of grid forming 00:57:38.720 --> 00:57:41.030 align:start position:0% universe of grid forming support<00:57:39.200> needed<00:57:40.079> above<00:57:40.400> and<00:57:40.480> beyond<00:57:40.799> just 00:57:41.030 --> 00:57:41.040 align:start position:0% support needed above and beyond just 00:57:41.040 --> 00:57:44.309 align:start position:0% support needed above and beyond just inertia<00:57:42.000> which<00:57:42.640> we<00:57:42.799> can't<00:57:43.119> ignore 00:57:44.309 --> 00:57:44.319 align:start position:0% inertia which we can't ignore 00:57:44.319 --> 00:57:46.309 align:start position:0% inertia which we can't ignore um<00:57:45.040> so 00:57:46.309 --> 00:57:46.319 align:start position:0% um so 00:57:46.319 --> 00:57:47.670 align:start position:0% um so there's<00:57:46.559> obviously<00:57:46.960> tools<00:57:47.200> on<00:57:47.200> the<00:57:47.280> table<00:57:47.599> and 00:57:47.670 --> 00:57:47.680 align:start position:0% there's obviously tools on the table and 00:57:47.680 --> 00:57:49.990 align:start position:0% there's obviously tools on the table and demand<00:57:48.000> response<00:57:48.400> i<00:57:48.480> know<00:57:48.720> is<00:57:48.799> something<00:57:49.280> you 00:57:49.990 --> 00:57:50.000 align:start position:0% demand response i know is something you 00:57:50.000 --> 00:57:52.309 align:start position:0% demand response i know is something you you<00:57:50.160> don't<00:57:50.319> get<00:57:50.480> enough<00:57:50.720> credit<00:57:51.119> for 00:57:52.309 --> 00:57:52.319 align:start position:0% you don't get enough credit for 00:57:52.319 --> 00:57:54.630 align:start position:0% you don't get enough credit for well<00:57:52.880> for<00:57:53.200> bringing<00:57:53.920> bringing<00:57:54.160> the<00:57:54.240> demand 00:57:54.630 --> 00:57:54.640 align:start position:0% well for bringing bringing the demand 00:57:54.640 --> 00:57:56.150 align:start position:0% well for bringing bringing the demand side<00:57:54.880> up<00:57:55.119> consistently<00:57:55.599> there's<00:57:55.839> a<00:57:55.920> lot<00:57:56.079> of 00:57:56.150 --> 00:57:56.160 align:start position:0% side up consistently there's a lot of 00:57:56.160 --> 00:57:59.589 align:start position:0% side up consistently there's a lot of focus<00:57:56.559> on<00:57:56.640> new<00:57:56.880> investment<00:57:57.839> and<00:57:58.079> greenfield 00:57:59.589 --> 00:57:59.599 align:start position:0% focus on new investment and greenfield 00:57:59.599 --> 00:58:01.349 align:start position:0% focus on new investment and greenfield uh<00:57:59.920> new<00:58:00.079> generation 00:58:01.349 --> 00:58:01.359 align:start position:0% uh new generation 00:58:01.359 --> 00:58:03.190 align:start position:0% uh new generation uh<00:58:01.760> and<00:58:01.920> that's<00:58:02.160> the<00:58:02.319> demand<00:58:02.720> response<00:58:03.119> is 00:58:03.190 --> 00:58:03.200 align:start position:0% uh and that's the demand response is 00:58:03.200 --> 00:58:05.109 align:start position:0% uh and that's the demand response is something<00:58:03.520> that<00:58:03.920> can<00:58:04.079> get<00:58:04.240> lost<00:58:04.880> in<00:58:05.040> the 00:58:05.109 --> 00:58:05.119 align:start position:0% something that can get lost in the 00:58:05.119 --> 00:58:06.470 align:start position:0% something that can get lost in the conversation 00:58:06.470 --> 00:58:06.480 align:start position:0% conversation 00:58:06.480 --> 00:58:07.270 align:start position:0% conversation um 00:58:07.270 --> 00:58:07.280 align:start position:0% um 00:58:07.280 --> 00:58:09.109 align:start position:0% um and<00:58:07.520> so<00:58:08.000> and<00:58:08.319> in<00:58:08.480> a 00:58:09.109 --> 00:58:09.119 align:start position:0% and so and in a 00:58:09.119 --> 00:58:10.630 align:start position:0% and so and in a in<00:58:09.359> addition<00:58:09.760> to<00:58:09.839> the<00:58:09.920> analysis<00:58:10.400> you're 00:58:10.630 --> 00:58:10.640 align:start position:0% in addition to the analysis you're 00:58:10.640 --> 00:58:11.750 align:start position:0% in addition to the analysis you're talking<00:58:10.880> about 00:58:11.750 --> 00:58:11.760 align:start position:0% talking about 00:58:11.760 --> 00:58:14.230 align:start position:0% talking about as<00:58:12.000> these<00:58:12.240> numbers<00:58:12.640> get<00:58:12.799> bigger 00:58:14.230 --> 00:58:14.240 align:start position:0% as these numbers get bigger 00:58:14.240 --> 00:58:16.309 align:start position:0% as these numbers get bigger what<00:58:14.480> kind<00:58:14.640> of<00:58:15.280> what<00:58:15.440> kind<00:58:15.520> of<00:58:15.680> upper<00:58:15.920> limit<00:58:16.160> is 00:58:16.309 --> 00:58:16.319 align:start position:0% what kind of what kind of upper limit is 00:58:16.319 --> 00:58:18.710 align:start position:0% what kind of what kind of upper limit is their<00:58:16.480> own<00:58:16.559> demand<00:58:16.880> response 00:58:18.710 --> 00:58:18.720 align:start position:0% their own demand response 00:58:18.720 --> 00:58:21.030 align:start position:0% their own demand response like<00:58:19.040> turning<00:58:19.520> turning<00:58:19.839> your<00:58:19.920> heat<00:58:20.079> down<00:58:20.319> at 00:58:21.030 --> 00:58:21.040 align:start position:0% like turning turning your heat down at 00:58:21.040 --> 00:58:22.390 align:start position:0% like turning turning your heat down at six<00:58:21.280> o'clock 00:58:22.390 --> 00:58:22.400 align:start position:0% six o'clock 00:58:22.400 --> 00:58:25.270 align:start position:0% six o'clock in<00:58:22.559> january<00:58:23.119> because<00:58:23.359> it's<00:58:24.000> really<00:58:24.319> cold 00:58:25.270 --> 00:58:25.280 align:start position:0% in january because it's really cold 00:58:25.280 --> 00:58:27.990 align:start position:0% in january because it's really cold the<00:58:25.440> sun's<00:58:25.760> set<00:58:25.920> and<00:58:26.000> the<00:58:26.079> wind's<00:58:26.400> not<00:58:26.559> blowing 00:58:27.990 --> 00:58:28.000 align:start position:0% the sun's set and the wind's not blowing 00:58:28.000 --> 00:58:28.789 align:start position:0% the sun's set and the wind's not blowing you<00:58:28.160> know 00:58:28.789 --> 00:58:28.799 align:start position:0% you know 00:58:28.799 --> 00:58:30.789 align:start position:0% you know turning<00:58:29.119> the<00:58:29.359> thermostat<00:58:30.079> down<00:58:30.319> a<00:58:30.400> little<00:58:30.559> bit 00:58:30.789 --> 00:58:30.799 align:start position:0% turning the thermostat down a little bit 00:58:30.799 --> 00:58:32.870 align:start position:0% turning the thermostat down a little bit is<00:58:30.960> one<00:58:31.200> thing<00:58:31.839> it's<00:58:32.079> very<00:58:32.240> different<00:58:32.559> to<00:58:32.720> turn 00:58:32.870 --> 00:58:32.880 align:start position:0% is one thing it's very different to turn 00:58:32.880 --> 00:58:35.030 align:start position:0% is one thing it's very different to turn it<00:58:33.040> off 00:58:35.030 --> 00:58:35.040 align:start position:0% it off 00:58:35.040 --> 00:58:36.549 align:start position:0% it off i'm<00:58:35.200> happy<00:58:35.440> to<00:58:35.520> do<00:58:35.680> the<00:58:35.839> first<00:58:36.000> one<00:58:36.240> i<00:58:36.319> don't 00:58:36.549 --> 00:58:36.559 align:start position:0% i'm happy to do the first one i don't 00:58:36.559 --> 00:58:38.630 align:start position:0% i'm happy to do the first one i don't know<00:58:36.799> many<00:58:37.119> texans<00:58:37.520> are<00:58:37.680> willing<00:58:37.839> to<00:58:38.400> do<00:58:38.559> the 00:58:38.630 --> 00:58:38.640 align:start position:0% know many texans are willing to do the 00:58:38.640 --> 00:58:41.430 align:start position:0% know many texans are willing to do the second<00:58:38.960> one 00:58:41.430 --> 00:58:41.440 align:start position:0% 00:58:41.440 --> 00:58:42.150 align:start position:0% so 00:58:42.150 --> 00:58:42.160 align:start position:0% so 00:58:42.160 --> 00:58:43.589 align:start position:0% so at<00:58:42.319> the<00:58:42.400> end<00:58:42.480> of<00:58:42.559> the<00:58:42.559> day<00:58:42.880> we've<00:58:43.119> got<00:58:43.280> to<00:58:43.359> solve 00:58:43.589 --> 00:58:43.599 align:start position:0% at the end of the day we've got to solve 00:58:43.599 --> 00:58:45.430 align:start position:0% at the end of the day we've got to solve these<00:58:43.760> problems<00:58:44.240> in<00:58:44.559> in<00:58:44.720> the<00:58:44.880> most<00:58:45.119> cost 00:58:45.430 --> 00:58:45.440 align:start position:0% these problems in in the most cost 00:58:45.440 --> 00:58:47.109 align:start position:0% these problems in in the most cost effective 00:58:47.109 --> 00:58:47.119 align:start position:0% effective 00:58:47.119 --> 00:58:49.030 align:start position:0% effective manner 00:58:49.030 --> 00:58:49.040 align:start position:0% manner 00:58:49.040 --> 00:58:51.589 align:start position:0% manner but<00:58:49.520> and<00:58:49.839> so<00:58:50.240> ecrs<00:58:50.880> is<00:58:50.960> a<00:58:51.040> great<00:58:51.200> tool<00:58:51.359> to<00:58:51.440> do 00:58:51.589 --> 00:58:51.599 align:start position:0% but and so ecrs is a great tool to do 00:58:51.599 --> 00:58:54.470 align:start position:0% but and so ecrs is a great tool to do that<00:58:51.760> i<00:58:51.839> think<00:58:52.240> we're<00:58:52.640> it's<00:58:52.880> well<00:58:53.119> underway 00:58:54.470 --> 00:58:54.480 align:start position:0% that i think we're it's well underway 00:58:54.480 --> 00:58:55.990 align:start position:0% that i think we're it's well underway the<00:58:54.720> only 00:58:55.990 --> 00:58:56.000 align:start position:0% the only 00:58:56.000 --> 00:58:57.589 align:start position:0% the only i<00:58:56.079> mean<00:58:56.319> the<00:58:56.400> grid<00:58:56.640> forming<00:58:56.960> capability<00:58:57.520> is 00:58:57.589 --> 00:58:57.599 align:start position:0% i mean the grid forming capability is 00:58:57.599 --> 00:58:59.270 align:start position:0% i mean the grid forming capability is something<00:58:58.240> they're<00:58:58.480> all<00:58:58.640> of<00:58:58.720> those<00:58:58.960> elements 00:58:59.270 --> 00:58:59.280 align:start position:0% something they're all of those elements 00:58:59.280 --> 00:59:01.109 align:start position:0% something they're all of those elements the<00:58:59.440> curtailment<00:59:00.160> issue<00:59:00.480> is<00:59:00.559> something<00:59:00.880> that 00:59:01.109 --> 00:59:01.119 align:start position:0% the curtailment issue is something that 00:59:01.119 --> 00:59:03.109 align:start position:0% the curtailment issue is something that is<00:59:01.359> coming<00:59:01.680> at<00:59:01.839> us<00:59:02.240> just<00:59:02.480> as<00:59:02.640> fast<00:59:02.880> as<00:59:02.960> that 00:59:03.109 --> 00:59:03.119 align:start position:0% is coming at us just as fast as that 00:59:03.119 --> 00:59:04.390 align:start position:0% is coming at us just as fast as that avalanche<00:59:03.599> of 00:59:04.390 --> 00:59:04.400 align:start position:0% avalanche of 00:59:04.400 --> 00:59:05.990 align:start position:0% avalanche of intermittence 00:59:05.990 --> 00:59:06.000 align:start position:0% intermittence 00:59:06.000 --> 00:59:07.510 align:start position:0% intermittence so<00:59:06.160> we<00:59:06.480> need<00:59:06.640> to<00:59:06.720> be 00:59:07.510 --> 00:59:07.520 align:start position:0% so we need to be 00:59:07.520 --> 00:59:08.870 align:start position:0% so we need to be frank<00:59:07.760> and<00:59:07.920> up<00:59:08.000> front<00:59:08.240> about<00:59:08.400> that<00:59:08.640> what's 00:59:08.870 --> 00:59:08.880 align:start position:0% frank and up front about that what's 00:59:08.880 --> 00:59:09.910 align:start position:0% frank and up front about that what's that<00:59:08.960> going<00:59:09.119> to<00:59:09.200> look<00:59:09.359> like<00:59:09.520> when<00:59:09.760> are<00:59:09.839> we 00:59:09.910 --> 00:59:09.920 align:start position:0% that going to look like when are we 00:59:09.920 --> 00:59:12.069 align:start position:0% that going to look like when are we going<00:59:10.079> to<00:59:10.480> pull<00:59:10.720> the<00:59:10.799> trigger<00:59:11.200> on<00:59:11.359> it<00:59:11.680> and<00:59:11.839> how 00:59:12.069 --> 00:59:12.079 align:start position:0% going to pull the trigger on it and how 00:59:12.079 --> 00:59:13.829 align:start position:0% going to pull the trigger on it and how close<00:59:12.559> to 00:59:13.829 --> 00:59:13.839 align:start position:0% close to 00:59:13.839 --> 00:59:15.990 align:start position:0% close to the<00:59:14.000> limit<00:59:14.319> do<00:59:14.559> we<00:59:14.720> want<00:59:14.960> to<00:59:15.119> get 00:59:15.990 --> 00:59:16.000 align:start position:0% the limit do we want to get 00:59:16.000 --> 00:59:17.750 align:start position:0% the limit do we want to get how<00:59:16.160> big<00:59:16.400> a<00:59:16.480> margin<00:59:16.799> of<00:59:16.960> safety<00:59:17.280> do<00:59:17.440> we<00:59:17.520> want<00:59:17.680> to 00:59:17.750 --> 00:59:17.760 align:start position:0% how big a margin of safety do we want to 00:59:17.760 --> 00:59:19.190 align:start position:0% how big a margin of safety do we want to build<00:59:18.000> into<00:59:18.240> that<00:59:18.480> that's<00:59:18.799> it's<00:59:18.960> a<00:59:18.960> great 00:59:19.190 --> 00:59:19.200 align:start position:0% build into that that's it's a great 00:59:19.200 --> 00:59:21.030 align:start position:0% build into that that's it's a great segue<00:59:19.520> into<00:59:19.680> my<00:59:19.920> question 00:59:21.030 --> 00:59:21.040 align:start position:0% segue into my question 00:59:21.040 --> 00:59:23.349 align:start position:0% segue into my question for<00:59:21.200> the<00:59:21.280> purposes<00:59:21.760> of<00:59:21.920> individual<00:59:22.480> tools 00:59:23.349 --> 00:59:23.359 align:start position:0% for the purposes of individual tools 00:59:23.359 --> 00:59:25.030 align:start position:0% for the purposes of individual tools what<00:59:23.520> do<00:59:23.599> you<00:59:23.680> need<00:59:23.839> a<00:59:24.000> two<00:59:24.160> hour<00:59:24.400> tool<00:59:24.799> a<00:59:24.880> four 00:59:25.030 --> 00:59:25.040 align:start position:0% what do you need a two hour tool a four 00:59:25.040 --> 00:59:27.510 align:start position:0% what do you need a two hour tool a four hour<00:59:25.280> tool<00:59:25.599> a<00:59:25.680> six<00:59:25.920> hour<00:59:26.160> tool<00:59:26.480> right<00:59:26.720> now<00:59:26.880> ecrs 00:59:27.510 --> 00:59:27.520 align:start position:0% hour tool a six hour tool right now ecrs 00:59:27.520 --> 00:59:29.190 align:start position:0% hour tool a six hour tool right now ecrs has<00:59:27.599> been<00:59:27.760> discussed<00:59:28.160> at<00:59:28.319> six<00:59:28.640> hours<00:59:28.960> is<00:59:29.119> it 00:59:29.190 --> 00:59:29.200 align:start position:0% has been discussed at six hours is it 00:59:29.200 --> 00:59:30.630 align:start position:0% has been discussed at six hours is it two<00:59:29.440> hours<00:59:29.680> you<00:59:29.839> need 00:59:30.630 --> 00:59:30.640 align:start position:0% two hours you need 00:59:30.640 --> 00:59:31.510 align:start position:0% two hours you need yes 00:59:31.510 --> 00:59:31.520 align:start position:0% yes 00:59:31.520 --> 00:59:33.829 align:start position:0% yes to<00:59:31.680> all<00:59:31.839> of<00:59:31.920> those<00:59:32.319> okay<00:59:33.040> there<00:59:33.280> there<00:59:33.520> is<00:59:33.680> a 00:59:33.829 --> 00:59:33.839 align:start position:0% to all of those okay there there is a 00:59:33.839 --> 00:59:36.630 align:start position:0% to all of those okay there there is a place<00:59:34.079> for<00:59:34.240> all<00:59:34.480> of<00:59:34.559> those<00:59:35.280> okay 00:59:36.630 --> 00:59:36.640 align:start position:0% place for all of those okay 00:59:36.640 --> 00:59:38.789 align:start position:0% place for all of those okay so<00:59:36.880> but<00:59:37.040> isn't<00:59:37.280> there<00:59:37.440> a<00:59:37.920> six<00:59:38.160> hour<00:59:38.400> limit<00:59:38.640> on 00:59:38.789 --> 00:59:38.799 align:start position:0% so but isn't there a six hour limit on 00:59:38.799 --> 00:59:41.829 align:start position:0% so but isn't there a six hour limit on ecrs<00:59:39.440> right<00:59:39.599> now<00:59:40.160> yes<00:59:40.799> so<00:59:41.200> if<00:59:41.280> you<00:59:41.440> need<00:59:41.599> two 00:59:41.829 --> 00:59:41.839 align:start position:0% ecrs right now yes so if you need two 00:59:41.839 --> 00:59:43.430 align:start position:0% ecrs right now yes so if you need two four<00:59:42.079> and<00:59:42.240> six<00:59:42.480> why<00:59:42.640> would<00:59:42.799> you<00:59:42.960> have<00:59:43.119> a<00:59:43.200> limit 00:59:43.430 --> 00:59:43.440 align:start position:0% four and six why would you have a limit 00:59:43.440 --> 00:59:46.069 align:start position:0% four and six why would you have a limit different<00:59:43.680> ancillary<00:59:44.079> services<00:59:44.640> that<00:59:44.880> uh 00:59:46.069 --> 00:59:46.079 align:start position:0% different ancillary services that uh 00:59:46.079 --> 00:59:47.510 align:start position:0% different ancillary services that uh different<00:59:46.319> infrastructure<00:59:46.880> services<00:59:47.280> would 00:59:47.510 --> 00:59:47.520 align:start position:0% different infrastructure services would 00:59:47.520 --> 00:59:50.470 align:start position:0% different infrastructure services would have<00:59:47.680> different<00:59:47.920> time<00:59:48.079> limits<00:59:48.480> so<00:59:48.559> i'm 00:59:50.470 --> 00:59:50.480 align:start position:0% have different time limits so i'm 00:59:50.480 --> 00:59:52.150 align:start position:0% have different time limits so i'm your<00:59:50.720> question<00:59:51.040> was 00:59:52.150 --> 00:59:52.160 align:start position:0% your question was 00:59:52.160 --> 00:59:53.990 align:start position:0% your question was is<00:59:52.319> it<00:59:52.480> a<00:59:52.640> two<00:59:52.880> four<00:59:53.119> or<00:59:53.200> six<00:59:53.440> hour<00:59:53.680> i'm<00:59:53.760> saying 00:59:53.990 --> 00:59:54.000 align:start position:0% is it a two four or six hour i'm saying 00:59:54.000 --> 00:59:55.349 align:start position:0% is it a two four or six hour i'm saying that<00:59:54.079> there<00:59:54.319> is<00:59:54.400> an<00:59:54.559> ancillary<00:59:54.880> service 00:59:55.349 --> 00:59:55.359 align:start position:0% that there is an ancillary service 00:59:55.359 --> 00:59:57.910 align:start position:0% that there is an ancillary service product<00:59:55.680> that<00:59:56.160> they<00:59:56.319> have<00:59:56.559> different<00:59:57.280> limits 00:59:57.910 --> 00:59:57.920 align:start position:0% product that they have different limits 00:59:57.920 --> 00:59:58.870 align:start position:0% product that they have different limits yeah<00:59:58.160> no 00:59:58.870 --> 00:59:58.880 align:start position:0% yeah no 00:59:58.880 --> 01:00:01.190 align:start position:0% yeah no so<00:59:59.359> the<00:59:59.520> curve<00:59:59.760> is<00:59:59.920> going<01:00:00.079> to<01:00:00.480> maybe<01:00:00.880> start<01:00:01.119> at 01:00:01.190 --> 01:00:01.200 align:start position:0% so the curve is going to maybe start at 01:00:01.200 --> 01:00:03.270 align:start position:0% so the curve is going to maybe start at two<01:00:01.440> but<01:00:01.599> it<01:00:01.680> could<01:00:01.920> expand<01:00:02.559> as<01:00:02.720> you<01:00:02.880> have<01:00:03.040> more 01:00:03.270 --> 01:00:03.280 align:start position:0% two but it could expand as you have more 01:00:03.280 --> 01:00:05.270 align:start position:0% two but it could expand as you have more solar<01:00:03.680> on<01:00:03.760> the<01:00:03.920> system<01:00:04.319> but<01:00:04.960> what<01:00:05.200> i 01:00:05.270 --> 01:00:05.280 align:start position:0% solar on the system but what i 01:00:05.280 --> 01:00:06.870 align:start position:0% solar on the system but what i understand<01:00:05.680> i<01:00:05.760> think<01:00:05.920> is<01:00:06.079> an<01:00:06.319> important<01:00:06.640> point 01:00:06.870 --> 01:00:06.880 align:start position:0% understand i think is an important point 01:00:06.880 --> 01:00:08.470 align:start position:0% understand i think is an important point to<01:00:07.040> make<01:00:07.359> is<01:00:07.520> that 01:00:08.470 --> 01:00:08.480 align:start position:0% to make is that 01:00:08.480 --> 01:00:11.430 align:start position:0% to make is that for<01:00:08.720> the<01:00:08.799> public<01:00:09.440> um<01:00:10.000> is<01:00:10.160> that<01:00:10.640> well<01:00:10.960> this<01:00:11.200> is<01:00:11.359> a 01:00:11.430 --> 01:00:11.440 align:start position:0% for the public um is that well this is a 01:00:11.440 --> 01:00:13.349 align:start position:0% for the public um is that well this is a very<01:00:11.680> important<01:00:12.079> issue<01:00:12.400> we've<01:00:12.799> got<01:00:12.960> to<01:00:13.119> solve 01:00:13.349 --> 01:00:13.359 align:start position:0% very important issue we've got to solve 01:00:13.359 --> 01:00:14.549 align:start position:0% very important issue we've got to solve for<01:00:13.599> it 01:00:14.549 --> 01:00:14.559 align:start position:0% for it 01:00:14.559 --> 01:00:16.710 align:start position:0% for it ercot<01:00:14.960> does<01:00:15.200> have<01:00:15.359> tools<01:00:15.839> right<01:00:16.000> now<01:00:16.559> and 01:00:16.710 --> 01:00:16.720 align:start position:0% ercot does have tools right now and 01:00:16.720 --> 01:00:18.390 align:start position:0% ercot does have tools right now and we've<01:00:16.880> got<01:00:16.960> to<01:00:17.040> make<01:00:17.280> sure<01:00:17.760> that<01:00:17.920> those<01:00:18.160> tools 01:00:18.390 --> 01:00:18.400 align:start position:0% we've got to make sure that those tools 01:00:18.400 --> 01:00:20.470 align:start position:0% we've got to make sure that those tools are<01:00:18.559> enough<01:00:19.119> and<01:00:19.280> that<01:00:19.440> those<01:00:19.599> tools<01:00:20.000> are<01:00:20.400> you 01:00:20.470 --> 01:00:20.480 align:start position:0% are enough and that those tools are you 01:00:20.480 --> 01:00:21.270 align:start position:0% are enough and that those tools are you know 01:00:21.270 --> 01:00:21.280 align:start position:0% know 01:00:21.280 --> 01:00:22.789 align:start position:0% know having<01:00:21.599> generation<01:00:22.000> come<01:00:22.240> online<01:00:22.640> through 01:00:22.789 --> 01:00:22.799 align:start position:0% having generation come online through 01:00:22.799 --> 01:00:25.109 align:start position:0% having generation come online through the<01:00:22.880> ordc<01:00:23.599> and<01:00:23.760> through<01:00:24.000> non-spin 01:00:25.109 --> 01:00:25.119 align:start position:0% the ordc and through non-spin 01:00:25.119 --> 01:00:25.910 align:start position:0% the ordc and through non-spin and 01:00:25.910 --> 01:00:25.920 align:start position:0% and 01:00:25.920 --> 01:00:28.150 align:start position:0% and as<01:00:26.160> part<01:00:26.400> of<01:00:26.559> ercot's<01:00:27.040> ongoing<01:00:27.440> evaluation<01:00:28.000> of 01:00:28.150 --> 01:00:28.160 align:start position:0% as part of ercot's ongoing evaluation of 01:00:28.160 --> 01:00:29.589 align:start position:0% as part of ercot's ongoing evaluation of ancillary<01:00:28.559> services<01:00:29.040> to<01:00:29.119> make<01:00:29.280> sure<01:00:29.440> that 01:00:29.589 --> 01:00:29.599 align:start position:0% ancillary services to make sure that 01:00:29.599 --> 01:00:31.190 align:start position:0% ancillary services to make sure that those<01:00:29.760> are<01:00:29.920> enough<01:00:30.240> tools 01:00:31.190 --> 01:00:31.200 align:start position:0% those are enough tools 01:00:31.200 --> 01:00:34.390 align:start position:0% those are enough tools to<01:00:31.680> manage<01:00:32.000> the<01:00:32.160> ramp<01:00:32.640> until<01:00:32.880> we<01:00:32.960> get<01:00:33.119> ecrs 01:00:34.390 --> 01:00:34.400 align:start position:0% to manage the ramp until we get ecrs 01:00:34.400 --> 01:00:36.069 align:start position:0% to manage the ramp until we get ecrs and<01:00:34.960> one<01:00:35.119> thing<01:00:35.280> that<01:00:35.440> i<01:00:35.520> think<01:00:35.760> is<01:00:35.839> very 01:00:36.069 --> 01:00:36.079 align:start position:0% and one thing that i think is very 01:00:36.079 --> 01:00:38.710 align:start position:0% and one thing that i think is very important<01:00:36.559> as<01:00:36.640> part<01:00:36.799> of<01:00:36.880> that<01:00:37.040> analysis<01:00:37.760> and 01:00:38.710 --> 01:00:38.720 align:start position:0% important as part of that analysis and 01:00:38.720 --> 01:00:40.829 align:start position:0% important as part of that analysis and is<01:00:38.960> the<01:00:39.040> fact<01:00:39.280> that<01:00:39.520> you<01:00:39.599> know<01:00:39.760> sp3 01:00:40.829 --> 01:00:40.839 align:start position:0% is the fact that you know sp3 01:00:40.839 --> 01:00:43.190 align:start position:0% is the fact that you know sp3 requires<01:00:41.839> the<01:00:41.920> commission<01:00:42.319> to<01:00:42.480> require<01:00:42.880> ercot 01:00:43.190 --> 01:00:43.200 align:start position:0% requires the commission to require ercot 01:00:43.200 --> 01:00:45.349 align:start position:0% requires the commission to require ercot to<01:00:43.359> review<01:00:43.599> their<01:00:43.760> ancillary<01:00:44.240> services 01:00:45.349 --> 01:00:45.359 align:start position:0% to review their ancillary services 01:00:45.359 --> 01:00:47.510 align:start position:0% to review their ancillary services and<01:00:46.079> we<01:00:46.240> really<01:00:46.559> need 01:00:47.510 --> 01:00:47.520 align:start position:0% and we really need 01:00:47.520 --> 01:00:48.549 align:start position:0% and we really need to 01:00:48.549 --> 01:00:48.559 align:start position:0% to 01:00:48.559 --> 01:00:51.430 align:start position:0% to take<01:00:48.720> a<01:00:48.799> step<01:00:49.040> back<01:00:49.359> here<01:00:49.760> and<01:00:49.920> review 01:00:51.430 --> 01:00:51.440 align:start position:0% take a step back here and review 01:00:51.440 --> 01:00:52.549 align:start position:0% take a step back here and review you<01:00:51.520> know<01:00:51.599> what<01:00:51.839> what<01:00:52.000> are<01:00:52.160> some<01:00:52.319> of<01:00:52.400> the 01:00:52.549 --> 01:00:52.559 align:start position:0% you know what what are some of the 01:00:52.559 --> 01:00:54.950 align:start position:0% you know what what are some of the operational<01:00:53.359> issues<01:00:53.680> we're<01:00:53.920> facing<01:00:54.720> in<01:00:54.799> the 01:00:54.950 --> 01:00:54.960 align:start position:0% operational issues we're facing in the 01:00:54.960 --> 01:00:56.870 align:start position:0% operational issues we're facing in the near<01:00:55.200> future 01:00:56.870 --> 01:00:56.880 align:start position:0% near future 01:00:56.880 --> 01:00:58.390 align:start position:0% near future in<01:00:56.960> the<01:00:57.040> midterm<01:00:57.440> future<01:00:57.760> in<01:00:57.839> the<01:00:57.920> long<01:00:58.160> term 01:00:58.390 --> 01:00:58.400 align:start position:0% in the midterm future in the long term 01:00:58.400 --> 01:00:59.510 align:start position:0% in the midterm future in the long term future 01:00:59.510 --> 01:00:59.520 align:start position:0% future 01:00:59.520 --> 01:01:02.230 align:start position:0% future and 01:01:02.230 --> 01:01:02.240 align:start position:0% 01:01:02.240 --> 01:01:04.789 align:start position:0% look<01:01:02.480> at<01:01:02.559> our<01:01:02.720> existing<01:01:03.680> suite<01:01:04.000> of<01:01:04.079> tools<01:01:04.559> look 01:01:04.789 --> 01:01:04.799 align:start position:0% look at our existing suite of tools look 01:01:04.799 --> 01:01:06.549 align:start position:0% look at our existing suite of tools look at<01:01:05.119> you<01:01:05.200> know<01:01:05.359> the<01:01:05.520> upcoming 01:01:06.549 --> 01:01:06.559 align:start position:0% at you know the upcoming 01:01:06.559 --> 01:01:08.870 align:start position:0% at you know the upcoming ancillary<01:01:07.119> services<01:01:07.520> that<01:01:07.680> are<01:01:07.760> coming 01:01:08.870 --> 01:01:08.880 align:start position:0% ancillary services that are coming 01:01:08.880 --> 01:01:10.309 align:start position:0% ancillary services that are coming that<01:01:09.040> are<01:01:09.200> in<01:01:09.280> the<01:01:09.440> oven<01:01:09.680> we'll<01:01:09.839> be<01:01:09.920> ready<01:01:10.160> at 01:01:10.309 --> 01:01:10.319 align:start position:0% that are in the oven we'll be ready at 01:01:10.319 --> 01:01:11.589 align:start position:0% that are in the oven we'll be ready at some<01:01:10.480> point<01:01:10.640> in<01:01:10.720> the<01:01:10.799> next<01:01:11.040> you<01:01:11.119> know<01:01:11.280> year<01:01:11.520> or 01:01:11.589 --> 01:01:11.599 align:start position:0% some point in the next you know year or 01:01:11.599 --> 01:01:12.870 align:start position:0% some point in the next you know year or two 01:01:12.870 --> 01:01:12.880 align:start position:0% two 01:01:12.880 --> 01:01:14.549 align:start position:0% two and<01:01:13.040> make<01:01:13.280> sure<01:01:13.440> that<01:01:13.599> we're<01:01:13.839> right-sizing 01:01:14.549 --> 01:01:14.559 align:start position:0% and make sure that we're right-sizing 01:01:14.559 --> 01:01:17.510 align:start position:0% and make sure that we're right-sizing everything<01:01:14.960> and<01:01:15.280> we've<01:01:15.520> got<01:01:15.680> what<01:01:15.839> we<01:01:16.000> need<01:01:16.640> um 01:01:17.510 --> 01:01:17.520 align:start position:0% everything and we've got what we need um 01:01:17.520 --> 01:01:19.750 align:start position:0% everything and we've got what we need um with<01:01:17.760> the<01:01:17.839> duration<01:01:18.240> limits<01:01:18.720> that<01:01:18.880> we<01:01:19.040> need 01:01:19.750 --> 01:01:19.760 align:start position:0% with the duration limits that we need 01:01:19.760 --> 01:01:22.069 align:start position:0% with the duration limits that we need and<01:01:20.240> i<01:01:20.319> think<01:01:20.640> an<01:01:20.799> overall<01:01:21.200> ancillary<01:01:21.760> service 01:01:22.069 --> 01:01:22.079 align:start position:0% and i think an overall ancillary service 01:01:22.079 --> 01:01:24.150 align:start position:0% and i think an overall ancillary service study<01:01:22.400> that<01:01:22.559> is<01:01:22.720> required<01:01:23.040> by<01:01:23.280> sp3<01:01:23.839> needs<01:01:24.079> to 01:01:24.150 --> 01:01:24.160 align:start position:0% study that is required by sp3 needs to 01:01:24.160 --> 01:01:26.230 align:start position:0% study that is required by sp3 needs to be<01:01:24.319> conducted<01:01:24.799> so<01:01:24.960> we<01:01:25.119> can<01:01:25.280> make<01:01:25.520> sure 01:01:26.230 --> 01:01:26.240 align:start position:0% be conducted so we can make sure 01:01:26.240 --> 01:01:27.750 align:start position:0% be conducted so we can make sure that<01:01:26.480> we<01:01:26.720> are 01:01:27.750 --> 01:01:27.760 align:start position:0% that we are 01:01:27.760 --> 01:01:29.349 align:start position:0% that we are effectively 01:01:29.349 --> 01:01:29.359 align:start position:0% effectively 01:01:29.359 --> 01:01:31.589 align:start position:0% effectively sizing<01:01:29.839> our<01:01:30.000> ancillary<01:01:30.559> service<01:01:30.880> suite<01:01:31.440> with 01:01:31.589 --> 01:01:31.599 align:start position:0% sizing our ancillary service suite with 01:01:31.599 --> 01:01:33.270 align:start position:0% sizing our ancillary service suite with the<01:01:31.760> operational<01:01:32.240> characteristics<01:01:33.040> that<01:01:33.119> we 01:01:33.270 --> 01:01:33.280 align:start position:0% the operational characteristics that we 01:01:33.280 --> 01:01:35.270 align:start position:0% the operational characteristics that we need<01:01:33.599> sooner<01:01:33.920> rather<01:01:34.160> than<01:01:34.319> later<01:01:34.960> so<01:01:35.119> that 01:01:35.270 --> 01:01:35.280 align:start position:0% need sooner rather than later so that 01:01:35.280 --> 01:01:36.950 align:start position:0% need sooner rather than later so that we're<01:01:35.440> not<01:01:35.599> guessing<01:01:36.000> how<01:01:36.160> many<01:01:36.319> megawatts<01:01:36.880> we 01:01:36.950 --> 01:01:36.960 align:start position:0% we're not guessing how many megawatts we 01:01:36.960 --> 01:01:39.430 align:start position:0% we're not guessing how many megawatts we need<01:01:37.200> on<01:01:37.359> the<01:01:37.440> system<01:01:38.000> through<01:01:38.240> non-spin<01:01:38.880> or 01:01:39.430 --> 01:01:39.440 align:start position:0% need on the system through non-spin or 01:01:39.440 --> 01:01:41.270 align:start position:0% need on the system through non-spin or or<01:01:39.599> through<01:01:39.839> ecrs 01:01:41.270 --> 01:01:41.280 align:start position:0% or through ecrs 01:01:41.280 --> 01:01:42.789 align:start position:0% or through ecrs because 01:01:42.789 --> 01:01:42.799 align:start position:0% because 01:01:42.799 --> 01:01:46.789 align:start position:0% because not<01:01:43.040> only<01:01:43.359> is<01:01:43.520> it<01:01:43.839> an<01:01:44.079> operational<01:01:45.200> um 01:01:46.789 --> 01:01:46.799 align:start position:0% not only is it an operational um 01:01:46.799 --> 01:01:49.750 align:start position:0% not only is it an operational um issue<01:01:47.520> it's<01:01:47.760> also<01:01:48.079> a<01:01:48.160> consumer<01:01:48.640> cost<01:01:48.960> issue 01:01:49.750 --> 01:01:49.760 align:start position:0% issue it's also a consumer cost issue 01:01:49.760 --> 01:01:51.750 align:start position:0% issue it's also a consumer cost issue and<01:01:49.920> so<01:01:50.079> we<01:01:50.240> gotta<01:01:50.640> understand<01:01:51.280> what<01:01:51.599> what 01:01:51.750 --> 01:01:51.760 align:start position:0% and so we gotta understand what what 01:01:51.760 --> 01:01:53.430 align:start position:0% and so we gotta understand what what we're<01:01:51.920> going<01:01:52.000> to<01:01:52.160> be<01:01:52.319> paying<01:01:52.640> for 01:01:53.430 --> 01:01:53.440 align:start position:0% we're going to be paying for 01:01:53.440 --> 01:01:55.589 align:start position:0% we're going to be paying for and<01:01:53.839> if<01:01:54.079> all<01:01:54.240> of<01:01:54.319> those<01:01:54.640> tools<01:01:54.960> are<01:01:55.039> not<01:01:55.280> enough 01:01:55.589 --> 01:01:55.599 align:start position:0% and if all of those tools are not enough 01:01:55.599 --> 01:01:57.109 align:start position:0% and if all of those tools are not enough or<01:01:55.760> we<01:01:55.839> need<01:01:56.000> different<01:01:56.240> characteristics<01:01:56.960> and 01:01:57.109 --> 01:01:57.119 align:start position:0% or we need different characteristics and 01:01:57.119 --> 01:01:58.470 align:start position:0% or we need different characteristics and we<01:01:57.200> need<01:01:57.359> to<01:01:57.440> be<01:01:57.599> thinking<01:01:57.839> of<01:01:58.000> a<01:01:58.079> strategic 01:01:58.470 --> 01:01:58.480 align:start position:0% we need to be thinking of a strategic 01:01:58.480 --> 01:02:00.789 align:start position:0% we need to be thinking of a strategic reliability<01:01:59.119> service<01:01:59.520> to<01:01:59.680> fill<01:01:59.920> in<01:02:00.000> that<01:02:00.240> gap 01:02:00.789 --> 01:02:00.799 align:start position:0% reliability service to fill in that gap 01:02:00.799 --> 01:02:01.910 align:start position:0% reliability service to fill in that gap and<01:02:00.960> we're<01:02:01.119> not<01:02:01.280> going<01:02:01.359> to<01:02:01.440> get<01:02:01.599> there<01:02:01.760> we're 01:02:01.910 --> 01:02:01.920 align:start position:0% and we're not going to get there we're 01:02:01.920 --> 01:02:02.950 align:start position:0% and we're not going to get there we're not<01:02:02.000> going<01:02:02.079> to<01:02:02.160> have<01:02:02.319> that<01:02:02.400> full<01:02:02.640> picture 01:02:02.950 --> 01:02:02.960 align:start position:0% not going to have that full picture 01:02:02.960 --> 01:02:05.029 align:start position:0% not going to have that full picture until<01:02:03.280> we<01:02:03.440> actually<01:02:03.839> have<01:02:04.400> some<01:02:04.640> kind<01:02:04.799> of 01:02:05.029 --> 01:02:05.039 align:start position:0% until we actually have some kind of 01:02:05.039 --> 01:02:07.029 align:start position:0% until we actually have some kind of comprehensive<01:02:05.680> review<01:02:06.319> of<01:02:06.480> our<01:02:06.640> ancillary 01:02:07.029 --> 01:02:07.039 align:start position:0% comprehensive review of our ancillary 01:02:07.039 --> 01:02:08.950 align:start position:0% comprehensive review of our ancillary service<01:02:07.359> study<01:02:07.599> so<01:02:07.680> we<01:02:07.760> could<01:02:07.920> right<01:02:08.160> size 01:02:08.950 --> 01:02:08.960 align:start position:0% service study so we could right size 01:02:08.960 --> 01:02:10.390 align:start position:0% service study so we could right size well<01:02:09.200> i<01:02:09.200> think<01:02:09.359> we're<01:02:09.599> in<01:02:09.680> the<01:02:09.839> comprehensive 01:02:10.390 --> 01:02:10.400 align:start position:0% well i think we're in the comprehensive 01:02:10.400 --> 01:02:11.829 align:start position:0% well i think we're in the comprehensive review<01:02:10.640> of<01:02:10.799> our<01:02:10.880> ancillary<01:02:11.359> studies<01:02:11.680> right 01:02:11.829 --> 01:02:11.839 align:start position:0% review of our ancillary studies right 01:02:11.839 --> 01:02:15.109 align:start position:0% review of our ancillary studies right now<01:02:12.400> well<01:02:12.799> but<01:02:13.039> technical<01:02:13.520> review<01:02:14.240> from<01:02:14.480> ercot 01:02:15.109 --> 01:02:15.119 align:start position:0% now well but technical review from ercot 01:02:15.119 --> 01:02:17.190 align:start position:0% now well but technical review from ercot and<01:02:15.359> and<01:02:15.839> you<01:02:16.000> know<01:02:16.240> i 01:02:17.190 --> 01:02:17.200 align:start position:0% and and you know i 01:02:17.200 --> 01:02:18.710 align:start position:0% and and you know i you<01:02:17.359> know<01:02:17.520> get<01:02:17.680> getter<01:02:18.000> caught<01:02:18.240> to<01:02:18.400> comply 01:02:18.710 --> 01:02:18.720 align:start position:0% you know get getter caught to comply 01:02:18.720 --> 01:02:22.150 align:start position:0% you know get getter caught to comply with<01:02:18.880> sb3<01:02:19.440> and<01:02:19.599> give<01:02:19.760> us<01:02:19.920> an<01:02:20.160> as<01:02:20.480> study 01:02:22.150 --> 01:02:22.160 align:start position:0% with sb3 and give us an as study 01:02:22.160 --> 01:02:25.349 align:start position:0% with sb3 and give us an as study sb3<01:02:22.799> yes<01:02:23.200> requires<01:02:23.839> us<01:02:24.000> to<01:02:24.160> require<01:02:24.480> ercot<01:02:24.960> to 01:02:25.349 --> 01:02:25.359 align:start position:0% sb3 yes requires us to require ercot to 01:02:25.359 --> 01:02:29.190 align:start position:0% sb3 yes requires us to require ercot to review<01:02:25.680> their<01:02:25.839> ancillary<01:02:26.400> service 01:02:29.190 --> 01:02:29.200 align:start position:0% 01:02:29.200 --> 01:02:30.630 align:start position:0% and<01:02:29.440> i<01:02:29.520> know<01:02:29.680> brattle<01:02:30.000> is<01:02:30.160> looking<01:02:30.400> at<01:02:30.559> it 01:02:30.630 --> 01:02:30.640 align:start position:0% and i know brattle is looking at it 01:02:30.640 --> 01:02:32.230 align:start position:0% and i know brattle is looking at it right<01:02:30.799> now<01:02:30.960> yeah<01:02:31.119> i<01:02:31.200> mean<01:02:31.359> i<01:02:31.440> think<01:02:31.760> they<01:02:32.160> are 01:02:32.230 --> 01:02:32.240 align:start position:0% right now yeah i mean i think they are 01:02:32.240 --> 01:02:34.789 align:start position:0% right now yeah i mean i think they are doing<01:02:32.480> a<01:02:32.799> pretty<01:02:33.119> thorough<01:02:33.440> job<01:02:34.319> with<01:02:34.559> that 01:02:34.789 --> 01:02:34.799 align:start position:0% doing a pretty thorough job with that 01:02:34.799 --> 01:02:36.870 align:start position:0% doing a pretty thorough job with that and<01:02:35.039> brattle's<01:02:35.440> working<01:02:35.760> on<01:02:35.920> it<01:02:36.079> so<01:02:36.240> i<01:02:36.400> don't<01:02:36.720> i 01:02:36.870 --> 01:02:36.880 align:start position:0% and brattle's working on it so i don't i 01:02:36.880 --> 01:02:38.150 align:start position:0% and brattle's working on it so i don't i don't<01:02:36.960> want<01:02:37.119> to<01:02:37.200> say<01:02:37.359> we're<01:02:37.520> not<01:02:37.760> complying 01:02:38.150 --> 01:02:38.160 align:start position:0% don't want to say we're not complying 01:02:38.160 --> 01:02:39.910 align:start position:0% don't want to say we're not complying with<01:02:38.319> sb3<01:02:39.039> i'm<01:02:39.200> not<01:02:39.359> saying<01:02:39.599> we're<01:02:39.760> not 01:02:39.910 --> 01:02:39.920 align:start position:0% with sb3 i'm not saying we're not 01:02:39.920 --> 01:02:41.990 align:start position:0% with sb3 i'm not saying we're not complying<01:02:40.480> i<01:02:40.640> think<01:02:40.799> we<01:02:40.960> need<01:02:41.200> to<01:02:41.359> comply<01:02:41.760> more 01:02:41.990 --> 01:02:42.000 align:start position:0% complying i think we need to comply more 01:02:42.000 --> 01:02:43.910 align:start position:0% complying i think we need to comply more robustly<01:02:42.640> because<01:02:42.960> from<01:02:43.200> what<01:02:43.359> i<01:02:43.599> understand 01:02:43.910 --> 01:02:43.920 align:start position:0% robustly because from what i understand 01:02:43.920 --> 01:02:45.109 align:start position:0% robustly because from what i understand from<01:02:44.160> rattle 01:02:45.109 --> 01:02:45.119 align:start position:0% from rattle 01:02:45.119 --> 01:02:48.069 align:start position:0% from rattle is<01:02:45.359> they're<01:02:45.599> just<01:02:45.760> looking<01:02:46.319> at<01:02:46.480> certain<01:02:46.960> items 01:02:48.069 --> 01:02:48.079 align:start position:0% is they're just looking at certain items 01:02:48.079 --> 01:02:50.069 align:start position:0% is they're just looking at certain items but<01:02:48.640> i<01:02:48.799> think<01:02:48.960> we<01:02:49.119> need<01:02:49.280> a<01:02:49.359> little<01:02:49.520> bit<01:02:49.680> more<01:02:50.000> i 01:02:50.069 --> 01:02:50.079 align:start position:0% but i think we need a little bit more i 01:02:50.079 --> 01:02:51.990 align:start position:0% but i think we need a little bit more i think<01:02:50.240> this<01:02:50.480> discussion<01:02:51.359> proves<01:02:51.760> that<01:02:51.839> we 01:02:51.990 --> 01:02:52.000 align:start position:0% think this discussion proves that we 01:02:52.000 --> 01:02:54.630 align:start position:0% think this discussion proves that we need<01:02:52.160> to<01:02:52.319> understand<01:02:52.799> a<01:02:52.880> little<01:02:53.119> bit<01:02:53.280> more<01:02:53.680> of 01:02:54.630 --> 01:02:54.640 align:start position:0% need to understand a little bit more of 01:02:54.640 --> 01:02:56.470 align:start position:0% need to understand a little bit more of what<01:02:54.880> are<01:02:54.960> the<01:02:55.119> site<01:02:55.520> what<01:02:55.680> are<01:02:55.760> we<01:02:56.000> expecting 01:02:56.470 --> 01:02:56.480 align:start position:0% what are the site what are we expecting 01:02:56.480 --> 01:02:58.470 align:start position:0% what are the site what are we expecting in<01:02:56.559> the<01:02:56.640> future<01:02:56.960> with<01:02:57.119> respect<01:02:57.599> to 01:02:58.470 --> 01:02:58.480 align:start position:0% in the future with respect to 01:02:58.480 --> 01:02:59.430 align:start position:0% in the future with respect to or<01:02:58.559> what<01:02:58.720> are<01:02:58.799> we<01:02:58.880> going<01:02:59.039> to<01:02:59.119> need<01:02:59.280> in<01:02:59.359> the 01:02:59.430 --> 01:02:59.440 align:start position:0% or what are we going to need in the 01:02:59.440 --> 01:03:01.589 align:start position:0% or what are we going to need in the future<01:02:59.839> with<01:03:00.000> our<01:03:00.160> existing<01:03:00.559> suite 01:03:01.589 --> 01:03:01.599 align:start position:0% future with our existing suite 01:03:01.599 --> 01:03:04.470 align:start position:0% future with our existing suite and<01:03:01.760> ecrs<01:03:02.640> how<01:03:02.799> many<01:03:03.039> megawatts<01:03:04.000> you<01:03:04.079> know 01:03:04.470 --> 01:03:04.480 align:start position:0% and ecrs how many megawatts you know 01:03:04.480 --> 01:03:06.390 align:start position:0% and ecrs how many megawatts you know right<01:03:04.640> now<01:03:04.880> we're<01:03:05.039> just<01:03:05.280> kind<01:03:05.440> of 01:03:06.390 --> 01:03:06.400 align:start position:0% right now we're just kind of 01:03:06.400 --> 01:03:08.309 align:start position:0% right now we're just kind of i<01:03:06.480> mean<01:03:06.720> guessing<01:03:07.200> right<01:03:07.599> so 01:03:08.309 --> 01:03:08.319 align:start position:0% i mean guessing right so 01:03:08.319 --> 01:03:10.309 align:start position:0% i mean guessing right so no<01:03:08.960> to<01:03:09.119> some<01:03:09.359> degree 01:03:10.309 --> 01:03:10.319 align:start position:0% no to some degree 01:03:10.319 --> 01:03:12.309 align:start position:0% no to some degree we're<01:03:10.480> doing<01:03:10.720> a<01:03:10.799> pretty 01:03:12.309 --> 01:03:12.319 align:start position:0% we're doing a pretty 01:03:12.319 --> 01:03:15.349 align:start position:0% we're doing a pretty our<01:03:12.559> 2022<01:03:13.839> ancillary<01:03:14.240> service<01:03:14.559> methodology 01:03:15.349 --> 01:03:15.359 align:start position:0% our 2022 ancillary service methodology 01:03:15.359 --> 01:03:16.630 align:start position:0% our 2022 ancillary service methodology study<01:03:15.680> that's<01:03:15.839> working<01:03:16.079> its<01:03:16.240> way<01:03:16.400> through<01:03:16.559> the 01:03:16.630 --> 01:03:16.640 align:start position:0% study that's working its way through the 01:03:16.640 --> 01:03:18.230 align:start position:0% study that's working its way through the market<01:03:16.880> participant<01:03:17.440> and<01:03:17.839> it's<01:03:18.000> also 01:03:18.230 --> 01:03:18.240 align:start position:0% market participant and it's also 01:03:18.240 --> 01:03:19.589 align:start position:0% market participant and it's also associated<01:03:18.640> with<01:03:18.720> the<01:03:18.799> bridal<01:03:19.119> study<01:03:19.359> right 01:03:19.589 --> 01:03:19.599 align:start position:0% associated with the bridal study right 01:03:19.599 --> 01:03:21.109 align:start position:0% associated with the bridal study right now<01:03:19.920> is<01:03:20.079> a 01:03:21.109 --> 01:03:21.119 align:start position:0% now is a 01:03:21.119 --> 01:03:23.670 align:start position:0% now is a pretty<01:03:21.359> exhaustive<01:03:22.000> look<01:03:22.480> at<01:03:23.119> what<01:03:23.280> we<01:03:23.440> need 01:03:23.670 --> 01:03:23.680 align:start position:0% pretty exhaustive look at what we need 01:03:23.680 --> 01:03:28.150 align:start position:0% pretty exhaustive look at what we need in<01:03:23.760> 2022<01:03:25.039> where<01:03:25.280> it<01:03:25.520> maybe<01:03:25.839> falls<01:03:26.240> short<01:03:26.880> is 01:03:28.150 --> 01:03:28.160 align:start position:0% in 2022 where it maybe falls short is 01:03:28.160 --> 01:03:30.069 align:start position:0% in 2022 where it maybe falls short is it<01:03:28.240> doesn't<01:03:28.559> anticipate<01:03:29.039> what<01:03:29.200> new<01:03:29.599> ancillary 01:03:30.069 --> 01:03:30.079 align:start position:0% it doesn't anticipate what new ancillary 01:03:30.079 --> 01:03:32.470 align:start position:0% it doesn't anticipate what new ancillary services<01:03:30.480> might<01:03:30.720> get<01:03:31.280> put<01:03:31.520> into 01:03:32.470 --> 01:03:32.480 align:start position:0% services might get put into 01:03:32.480 --> 01:03:36.069 align:start position:0% services might get put into the<01:03:32.640> new<01:03:32.799> market<01:03:33.599> that's<01:03:33.920> the<01:03:34.079> piece<01:03:34.480> that<01:03:34.880> um 01:03:36.069 --> 01:03:36.079 align:start position:0% the new market that's the piece that um 01:03:36.079 --> 01:03:38.470 align:start position:0% the new market that's the piece that um that<01:03:36.559> is<01:03:36.799> maybe<01:03:37.119> missing<01:03:37.440> in<01:03:37.599> the<01:03:37.680> 2022 01:03:38.470 --> 01:03:38.480 align:start position:0% that is maybe missing in the 2022 01:03:38.480 --> 01:03:40.950 align:start position:0% that is maybe missing in the 2022 because<01:03:38.640> those<01:03:38.880> won't<01:03:39.039> be<01:03:39.200> there<01:03:39.359> in<01:03:39.440> 2022 01:03:40.950 --> 01:03:40.960 align:start position:0% because those won't be there in 2022 01:03:40.960 --> 01:03:43.109 align:start position:0% because those won't be there in 2022 and<01:03:41.119> so<01:03:41.839> given<01:03:42.079> the<01:03:42.160> tools<01:03:42.480> we<01:03:42.559> have<01:03:42.720> today 01:03:43.109 --> 01:03:43.119 align:start position:0% and so given the tools we have today 01:03:43.119 --> 01:03:45.430 align:start position:0% and so given the tools we have today it's<01:03:43.359> a<01:03:43.440> pretty<01:03:43.680> robust<01:03:44.160> study<01:03:44.640> of<01:03:45.039> what<01:03:45.280> we 01:03:45.430 --> 01:03:45.440 align:start position:0% it's a pretty robust study of what we 01:03:45.440 --> 01:03:46.309 align:start position:0% it's a pretty robust study of what we need 01:03:46.309 --> 01:03:46.319 align:start position:0% need 01:03:46.319 --> 01:03:49.270 align:start position:0% need and<01:03:46.799> how<01:03:46.960> it<01:03:47.039> will<01:03:47.200> be<01:03:47.359> used<01:03:47.680> in<01:03:47.839> 2022.<01:03:48.640> okay 01:03:49.270 --> 01:03:49.280 align:start position:0% and how it will be used in 2022. okay 01:03:49.280 --> 01:03:50.630 align:start position:0% and how it will be used in 2022. okay well<01:03:49.520> great<01:03:49.680> that's<01:03:49.920> great<01:03:50.079> to<01:03:50.240> know<01:03:50.400> i<01:03:50.480> mean 01:03:50.630 --> 01:03:50.640 align:start position:0% well great that's great to know i mean 01:03:50.640 --> 01:03:52.390 align:start position:0% well great that's great to know i mean that<01:03:51.280> i<01:03:51.440> just<01:03:51.599> want<01:03:51.680> to<01:03:51.760> make<01:03:52.000> sure<01:03:52.240> that 01:03:52.390 --> 01:03:52.400 align:start position:0% that i just want to make sure that 01:03:52.400 --> 01:03:54.390 align:start position:0% that i just want to make sure that something<01:03:52.799> is<01:03:52.960> being<01:03:53.200> looked<01:03:53.520> at<01:03:53.760> and<01:03:54.240> we've 01:03:54.390 --> 01:03:54.400 align:start position:0% something is being looked at and we've 01:03:54.400 --> 01:03:57.190 align:start position:0% something is being looked at and we've got<01:03:54.559> to<01:03:54.640> be<01:03:54.799> looking<01:03:55.200> beyond<01:03:55.599> 2022 01:03:57.190 --> 01:03:57.200 align:start position:0% got to be looking beyond 2022 01:03:57.200 --> 01:03:59.270 align:start position:0% got to be looking beyond 2022 because<01:03:57.599> i<01:03:57.760> want<01:03:57.920> to<01:03:58.000> get<01:03:58.160> a<01:03:58.240> clear<01:03:58.480> picture<01:03:59.119> of 01:03:59.270 --> 01:03:59.280 align:start position:0% because i want to get a clear picture of 01:03:59.280 --> 01:04:01.109 align:start position:0% because i want to get a clear picture of what<01:03:59.440> we're<01:03:59.680> facing<01:04:00.160> and<01:04:00.240> how<01:04:00.400> many<01:04:00.640> megawatts 01:04:01.109 --> 01:04:01.119 align:start position:0% what we're facing and how many megawatts 01:04:01.119 --> 01:04:03.349 align:start position:0% what we're facing and how many megawatts we're<01:04:01.200> going<01:04:01.280> to<01:04:01.359> need<01:04:01.520> of<01:04:01.599> non-spin<01:04:02.160> and<01:04:02.319> ecrs 01:04:03.349 --> 01:04:03.359 align:start position:0% we're going to need of non-spin and ecrs 01:04:03.359 --> 01:04:05.270 align:start position:0% we're going to need of non-spin and ecrs and<01:04:03.520> right<01:04:03.680> now<01:04:03.920> i<01:04:04.079> understand<01:04:04.559> you<01:04:04.640> know<01:04:04.799> it 01:04:05.270 --> 01:04:05.280 align:start position:0% and right now i understand you know it 01:04:05.280 --> 01:04:07.270 align:start position:0% and right now i understand you know it might<01:04:05.440> not<01:04:05.839> i<01:04:05.920> mean<01:04:06.160> the<01:04:06.319> five<01:04:06.480> to<01:04:06.640> seven<01:04:06.960> is<01:04:07.200> is 01:04:07.270 --> 01:04:07.280 align:start position:0% might not i mean the five to seven is is 01:04:07.280 --> 01:04:09.670 align:start position:0% might not i mean the five to seven is is a<01:04:07.359> very<01:04:07.599> big<01:04:07.839> guesstimate<01:04:08.799> but<01:04:09.280> i<01:04:09.359> don't<01:04:09.520> want 01:04:09.670 --> 01:04:09.680 align:start position:0% a very big guesstimate but i don't want 01:04:09.680 --> 01:04:11.029 align:start position:0% a very big guesstimate but i don't want to<01:04:09.839> think<01:04:10.000> that<01:04:10.160> we're<01:04:10.319> going<01:04:10.400> to<01:04:10.640> only<01:04:10.880> need 01:04:11.029 --> 01:04:11.039 align:start position:0% to think that we're going to only need 01:04:11.039 --> 01:04:13.190 align:start position:0% to think that we're going to only need five<01:04:11.200> to<01:04:11.359> seven<01:04:11.599> megawatts<01:04:12.480> six 01:04:13.190 --> 01:04:13.200 align:start position:0% five to seven megawatts six 01:04:13.200 --> 01:04:14.870 align:start position:0% five to seven megawatts six five<01:04:13.440> to<01:04:13.520> seven<01:04:13.760> thousand<01:04:14.079> megawatts<01:04:14.640> and 01:04:14.870 --> 01:04:14.880 align:start position:0% five to seven thousand megawatts and 01:04:14.880 --> 01:04:17.109 align:start position:0% five to seven thousand megawatts and ultimately<01:04:15.359> we<01:04:15.520> need<01:04:15.920> ten<01:04:16.160> thousand 01:04:17.109 --> 01:04:17.119 align:start position:0% ultimately we need ten thousand 01:04:17.119 --> 01:04:18.630 align:start position:0% ultimately we need ten thousand or<01:04:17.520> more 01:04:18.630 --> 01:04:18.640 align:start position:0% or more 01:04:18.640 --> 01:04:20.630 align:start position:0% or more footage<01:04:19.039> because<01:04:19.280> we<01:04:19.359> didn't<01:04:19.599> have<01:04:19.839> enough 01:04:20.630 --> 01:04:20.640 align:start position:0% footage because we didn't have enough 01:04:20.640 --> 01:04:22.950 align:start position:0% footage because we didn't have enough absolutely 01:04:22.950 --> 01:04:22.960 align:start position:0% absolutely 01:04:22.960 --> 01:04:24.870 align:start position:0% absolutely the<01:04:23.280> the<01:04:23.680> kind<01:04:23.839> of<01:04:24.000> above<01:04:24.240> and<01:04:24.319> beyond<01:04:24.720> the 01:04:24.870 --> 01:04:24.880 align:start position:0% the the kind of above and beyond the 01:04:24.880 --> 01:04:26.470 align:start position:0% the the kind of above and beyond the existing<01:04:25.680> suite<01:04:25.920> of<01:04:26.000> products<01:04:26.319> we're 01:04:26.470 --> 01:04:26.480 align:start position:0% existing suite of products we're 01:04:26.480 --> 01:04:28.069 align:start position:0% existing suite of products we're discussing<01:04:26.960> let's<01:04:27.119> say<01:04:27.359> for 01:04:28.069 --> 01:04:28.079 align:start position:0% discussing let's say for 01:04:28.079 --> 01:04:28.789 align:start position:0% discussing let's say for the 01:04:28.789 --> 01:04:28.799 align:start position:0% the 01:04:28.799 --> 01:04:30.309 align:start position:0% the the<01:04:28.960> second<01:04:29.280> part<01:04:29.440> of<01:04:29.599> our 01:04:30.309 --> 01:04:30.319 align:start position:0% the second part of our 01:04:30.319 --> 01:04:32.230 align:start position:0% the second part of our conversation 01:04:32.230 --> 01:04:32.240 align:start position:0% conversation 01:04:32.240 --> 01:04:35.750 align:start position:0% conversation anything<01:04:32.480> else<01:04:32.640> for<01:04:32.799> woody<01:04:33.520> a<01:04:33.920> question 01:04:35.750 --> 01:04:35.760 align:start position:0% anything else for woody a question 01:04:35.760 --> 01:04:39.349 align:start position:0% anything else for woody a question you<01:04:35.920> need<01:04:36.559> two<01:04:36.880> four<01:04:37.280> and<01:04:37.440> six<01:04:38.160> okay 01:04:39.349 --> 01:04:39.359 align:start position:0% you need two four and six okay 01:04:39.359 --> 01:04:40.630 align:start position:0% you need two four and six okay ecrs 01:04:40.630 --> 01:04:40.640 align:start position:0% ecrs 01:04:40.640 --> 01:04:42.230 align:start position:0% ecrs under<01:04:40.799> development<01:04:41.520> you've<01:04:41.760> been<01:04:41.920> working 01:04:42.230 --> 01:04:42.240 align:start position:0% under development you've been working 01:04:42.240 --> 01:04:44.710 align:start position:0% under development you've been working out<01:04:42.880> fine-tuning<01:04:43.680> uh 01:04:44.710 --> 01:04:44.720 align:start position:0% out fine-tuning uh 01:04:44.720 --> 01:04:46.789 align:start position:0% out fine-tuning uh procurement<01:04:45.440> auction<01:04:46.240> you've<01:04:46.400> been<01:04:46.559> thinking 01:04:46.789 --> 01:04:46.799 align:start position:0% procurement auction you've been thinking 01:04:46.799 --> 01:04:49.349 align:start position:0% procurement auction you've been thinking about<01:04:47.039> these<01:04:47.280> things<01:04:47.839> all<01:04:48.079> these<01:04:48.240> years 01:04:49.349 --> 01:04:49.359 align:start position:0% about these things all these years 01:04:49.359 --> 01:04:51.029 align:start position:0% about these things all these years i<01:04:49.520> can<01:04:49.680> say<01:04:49.920> all<01:04:50.079> these<01:04:50.319> years<01:04:50.559> now<01:04:50.799> after 01:04:51.029 --> 01:04:51.039 align:start position:0% i can say all these years now after 01:04:51.039 --> 01:04:52.309 align:start position:0% i can say all these years now after three 01:04:52.309 --> 01:04:52.319 align:start position:0% three 01:04:52.319 --> 01:04:55.349 align:start position:0% three and<01:04:52.480> so<01:04:52.880> if<01:04:53.200> if<01:04:53.280> we<01:04:53.440> get<01:04:53.599> this<01:04:53.760> done<01:04:54.079> by<01:04:54.400> 2020 01:04:55.349 --> 01:04:55.359 align:start position:0% and so if if we get this done by 2020 01:04:55.359 --> 01:04:58.309 align:start position:0% and so if if we get this done by 2020 the<01:04:55.440> winter<01:04:55.760> of<01:04:55.920> 2023<01:04:56.799> 2024<01:04:57.839> would<01:04:58.000> you<01:04:58.160> say 01:04:58.309 --> 01:04:58.319 align:start position:0% the winter of 2023 2024 would you say 01:04:58.319 --> 01:05:00.390 align:start position:0% the winter of 2023 2024 would you say that<01:04:58.559> is<01:04:58.640> a<01:04:58.720> manageable<01:04:59.280> expectation<01:05:00.240> to 01:05:00.390 --> 01:05:00.400 align:start position:0% that is a manageable expectation to 01:05:00.400 --> 01:05:04.150 align:start position:0% that is a manageable expectation to deploy<01:05:00.960> some<01:05:01.440> level<01:05:01.760> of<01:05:01.920> an<01:05:02.400> ecrs<01:05:03.200> tool 01:05:04.150 --> 01:05:04.160 align:start position:0% deploy some level of an ecrs tool 01:05:04.160 --> 01:05:08.150 align:start position:0% deploy some level of an ecrs tool yes<01:05:04.640> okay<01:05:05.200> good<01:05:05.440> answer<01:05:05.920> um 01:05:08.150 --> 01:05:08.160 align:start position:0% yes okay good answer um 01:05:08.160 --> 01:05:10.630 align:start position:0% yes okay good answer um within<01:05:08.559> that 01:05:10.630 --> 01:05:10.640 align:start position:0% within that 01:05:10.640 --> 01:05:11.670 align:start position:0% within that auction 01:05:11.670 --> 01:05:11.680 align:start position:0% auction 01:05:11.680 --> 01:05:13.589 align:start position:0% auction do<01:05:11.839> you<01:05:12.000> envision 01:05:13.589 --> 01:05:13.599 align:start position:0% do you envision 01:05:13.599 --> 01:05:14.950 align:start position:0% do you envision shooting<01:05:14.000> for 01:05:14.950 --> 01:05:14.960 align:start position:0% shooting for 01:05:14.960 --> 01:05:16.789 align:start position:0% shooting for subsets<01:05:15.839> of 01:05:16.789 --> 01:05:16.799 align:start position:0% subsets of 01:05:16.799 --> 01:05:20.390 align:start position:0% subsets of a<01:05:16.960> procurement<01:05:18.000> for<01:05:18.240> two<01:05:18.880> four<01:05:19.440> and<01:05:19.680> six<01:05:20.000> hours 01:05:20.390 --> 01:05:20.400 align:start position:0% a procurement for two four and six hours 01:05:20.400 --> 01:05:24.789 align:start position:0% a procurement for two four and six hours within<01:05:20.720> the<01:05:20.960> ecrs<01:05:22.079> ancillary<01:05:22.720> service<01:05:23.520> uh 01:05:24.789 --> 01:05:24.799 align:start position:0% within the ecrs ancillary service uh 01:05:24.799 --> 01:05:26.150 align:start position:0% within the ecrs ancillary service uh no<01:05:25.039> i<01:05:25.119> don't<01:05:25.200> think<01:05:25.359> it'll<01:05:25.520> be<01:05:25.680> two<01:05:25.839> four<01:05:26.000> and 01:05:26.150 --> 01:05:26.160 align:start position:0% no i don't think it'll be two four and 01:05:26.160 --> 01:05:29.589 align:start position:0% no i don't think it'll be two four and six<01:05:26.400> four<01:05:26.640> in<01:05:26.960> for<01:05:27.280> for<01:05:27.440> ecrs<01:05:28.160> okay<01:05:28.400> sure 01:05:29.589 --> 01:05:29.599 align:start position:0% six four in for for ecrs okay sure 01:05:29.599 --> 01:05:31.029 align:start position:0% six four in for for ecrs okay sure you<01:05:29.680> don't<01:05:29.839> need<01:05:30.160> a<01:05:30.240> single<01:05:30.480> duration<01:05:30.880> right 01:05:31.029 --> 01:05:31.039 align:start position:0% you don't need a single duration right 01:05:31.039 --> 01:05:33.589 align:start position:0% you don't need a single duration right it'll<01:05:31.200> be<01:05:31.280> a<01:05:31.440> single<01:05:31.760> direction<01:05:32.160> right<01:05:32.559> okay 01:05:33.589 --> 01:05:33.599 align:start position:0% it'll be a single direction right okay 01:05:33.599 --> 01:05:35.349 align:start position:0% it'll be a single direction right okay and<01:05:33.760> i<01:05:33.839> get<01:05:34.079> i<01:05:34.160> guess<01:05:34.319> slim 01:05:35.349 --> 01:05:35.359 align:start position:0% and i get i guess slim 01:05:35.359 --> 01:05:38.390 align:start position:0% and i get i guess slim go<01:05:35.599> what's<01:05:35.920> the<01:05:36.160> uh<01:05:36.880> ecrs<01:05:37.520> delivery 01:05:38.390 --> 01:05:38.400 align:start position:0% go what's the uh ecrs delivery 01:05:38.400 --> 01:05:39.109 align:start position:0% go what's the uh ecrs delivery two 01:05:39.109 --> 01:05:39.119 align:start position:0% two 01:05:39.119 --> 01:05:41.589 align:start position:0% two two<01:05:39.520> okay<01:05:39.920> but<01:05:40.079> what's<01:05:40.400> the 01:05:41.589 --> 01:05:41.599 align:start position:0% two okay but what's the 01:05:41.599 --> 01:05:46.069 align:start position:0% two okay but what's the the<01:05:41.839> delivery<01:05:42.319> right<01:05:42.480> now<01:05:42.720> vcrs<01:05:43.440> is<01:05:43.599> it<01:05:43.760> 2020 01:05:46.069 --> 01:05:46.079 align:start position:0% the delivery right now vcrs is it 2020 01:05:46.079 --> 01:05:47.829 align:start position:0% the delivery right now vcrs is it 2020 it's<01:05:46.240> still<01:05:46.559> planning<01:05:46.880> okay 01:05:47.829 --> 01:05:47.839 align:start position:0% it's still planning okay 01:05:47.839 --> 01:05:50.950 align:start position:0% it's still planning okay yeah<01:05:48.319> so<01:05:48.640> we<01:05:48.799> have<01:05:48.880> to<01:05:49.039> back<01:05:49.280> off<01:05:49.599> on<01:05:49.839> my<01:05:50.400> yes<01:05:50.799> no 01:05:50.950 --> 01:05:50.960 align:start position:0% yeah so we have to back off on my yes no 01:05:50.960 --> 01:05:52.630 align:start position:0% yeah so we have to back off on my yes no problem<01:05:51.359> the<01:05:51.440> commission<01:05:51.839> will<01:05:52.000> help<01:05:52.240> you<01:05:52.480> get 01:05:52.630 --> 01:05:52.640 align:start position:0% problem the commission will help you get 01:05:52.640 --> 01:05:55.349 align:start position:0% problem the commission will help you get that<01:05:52.880> i<01:05:52.960> could<01:05:53.200> feel<01:05:53.680> the<01:05:54.319> um<01:05:54.799> the<01:05:54.960> stairs 01:05:55.349 --> 01:05:55.359 align:start position:0% that i could feel the um the stairs 01:05:55.359 --> 01:05:59.349 align:start position:0% that i could feel the um the stairs coming<01:05:55.680> over<01:05:56.319> when<01:05:56.480> i<01:05:56.559> said<01:05:56.799> yes<01:05:57.200> there<01:05:57.520> so 01:05:59.349 --> 01:05:59.359 align:start position:0% coming over when i said yes there so 01:05:59.359 --> 01:06:01.109 align:start position:0% coming over when i said yes there so so<01:05:59.520> woody<01:05:59.839> and<01:06:00.079> that<01:06:00.559> i've<01:06:00.640> been<01:06:00.799> having<01:06:01.039> these 01:06:01.109 --> 01:06:01.119 align:start position:0% so woody and that i've been having these 01:06:01.119 --> 01:06:02.710 align:start position:0% so woody and that i've been having these conversations<01:06:01.680> with<01:06:01.760> their<01:06:01.920> cod<01:06:02.160> as<01:06:02.240> well<01:06:02.480> and 01:06:02.710 --> 01:06:02.720 align:start position:0% conversations with their cod as well and 01:06:02.720 --> 01:06:04.470 align:start position:0% conversations with their cod as well and and<01:06:02.880> for<01:06:03.039> what<01:06:03.119> i<01:06:03.280> understand<01:06:03.680> the<01:06:03.839> non-spin<01:06:04.400> i 01:06:04.470 --> 01:06:04.480 align:start position:0% and for what i understand the non-spin i 01:06:04.480 --> 01:06:05.990 align:start position:0% and for what i understand the non-spin i think<01:06:04.640> y'all<01:06:04.880> had<01:06:04.960> looked<01:06:05.200> at<01:06:05.280> four<01:06:05.520> hours<01:06:05.839> but 01:06:05.990 --> 01:06:06.000 align:start position:0% think y'all had looked at four hours but 01:06:06.000 --> 01:06:08.390 align:start position:0% think y'all had looked at four hours but maybe<01:06:06.319> stayed<01:06:06.559> at<01:06:06.720> six<01:06:07.280> and<01:06:07.599> ecrs<01:06:08.240> will 01:06:08.390 --> 01:06:08.400 align:start position:0% maybe stayed at six and ecrs will 01:06:08.400 --> 01:06:10.150 align:start position:0% maybe stayed at six and ecrs will ultimately<01:06:08.799> be<01:06:08.960> two<01:06:09.200> hours<01:06:09.680> is<01:06:09.839> what<01:06:10.000> y'all 01:06:10.150 --> 01:06:10.160 align:start position:0% ultimately be two hours is what y'all 01:06:10.160 --> 01:06:12.230 align:start position:0% ultimately be two hours is what y'all are<01:06:10.240> looking<01:06:10.480> at<01:06:10.880> i<01:06:11.039> think<01:06:11.200> we're<01:06:11.680> moving<01:06:12.000> the 01:06:12.230 --> 01:06:12.240 align:start position:0% are looking at i think we're moving the 01:06:12.240 --> 01:06:13.750 align:start position:0% are looking at i think we're moving the non-spin 01:06:13.750 --> 01:06:13.760 align:start position:0% non-spin 01:06:13.760 --> 01:06:17.430 align:start position:0% non-spin as<01:06:13.920> well<01:06:14.559> okay<01:06:14.880> to<01:06:15.039> maybe<01:06:15.359> four<01:06:15.680> yes<01:06:16.079> okay 01:06:17.430 --> 01:06:17.440 align:start position:0% as well okay to maybe four yes okay 01:06:17.440 --> 01:06:19.589 align:start position:0% as well okay to maybe four yes okay so<01:06:17.680> one<01:06:17.839> of<01:06:17.920> the<01:06:18.000> things<01:06:18.240> that<01:06:18.319> i<01:06:18.480> think<01:06:18.880> um<01:06:19.440> to 01:06:19.589 --> 01:06:19.599 align:start position:0% so one of the things that i think um to 01:06:19.599 --> 01:06:22.470 align:start position:0% so one of the things that i think um to me<01:06:20.240> gets<01:06:20.480> lost<01:06:20.799> in<01:06:20.960> a<01:06:21.039> little<01:06:21.200> bit<01:06:21.359> of<01:06:21.520> this<01:06:21.839> is 01:06:22.470 --> 01:06:22.480 align:start position:0% me gets lost in a little bit of this is 01:06:22.480 --> 01:06:25.349 align:start position:0% me gets lost in a little bit of this is this<01:06:22.799> dichotomy<01:06:23.520> between 01:06:25.349 --> 01:06:25.359 align:start position:0% this dichotomy between 01:06:25.359 --> 01:06:28.150 align:start position:0% this dichotomy between the<01:06:25.520> old<01:06:25.760> world<01:06:26.160> which<01:06:26.400> is<01:06:26.880> we<01:06:27.039> have<01:06:27.520> one<01:06:27.760> big 01:06:28.150 --> 01:06:28.160 align:start position:0% the old world which is we have one big 01:06:28.160 --> 01:06:29.990 align:start position:0% the old world which is we have one big thousand<01:06:28.480> megawatt<01:06:29.119> two<01:06:29.280> thousand<01:06:29.520> megawatt 01:06:29.990 --> 01:06:30.000 align:start position:0% thousand megawatt two thousand megawatt 01:06:30.000 --> 01:06:32.390 align:start position:0% thousand megawatt two thousand megawatt combined<01:06:30.400> cycle<01:06:30.799> plant<01:06:31.359> or<01:06:31.760> coal<01:06:32.079> plant 01:06:32.390 --> 01:06:32.400 align:start position:0% combined cycle plant or coal plant 01:06:32.400 --> 01:06:33.349 align:start position:0% combined cycle plant or coal plant that's 01:06:33.349 --> 01:06:33.359 align:start position:0% that's 01:06:33.359 --> 01:06:37.829 align:start position:0% that's providing<01:06:33.920> a<01:06:34.000> lot<01:06:34.160> of<01:06:34.240> these<01:06:34.480> grid<01:06:34.799> resources 01:06:37.829 --> 01:06:37.839 align:start position:0% 01:06:37.839 --> 01:06:39.190 align:start position:0% we<01:06:38.000> have 01:06:39.190 --> 01:06:39.200 align:start position:0% we have 01:06:39.200 --> 01:06:41.349 align:start position:0% we have and<01:06:39.440> what<01:06:39.680> the<01:06:39.760> new<01:06:40.000> world<01:06:40.319> is<01:06:40.559> is<01:06:40.720> not<01:06:41.119> one 01:06:41.349 --> 01:06:41.359 align:start position:0% and what the new world is is not one 01:06:41.359 --> 01:06:44.150 align:start position:0% and what the new world is is not one battery<01:06:41.839> trying<01:06:42.079> to<01:06:42.160> equal<01:06:42.559> that<01:06:43.200> we<01:06:43.359> have<01:06:43.920> a 01:06:44.150 --> 01:06:44.160 align:start position:0% battery trying to equal that we have a 01:06:44.160 --> 01:06:47.349 align:start position:0% battery trying to equal that we have a hundred<01:06:44.559> batteries<01:06:45.119> equaling<01:06:45.680> that 01:06:47.349 --> 01:06:47.359 align:start position:0% hundred batteries equaling that 01:06:47.359 --> 01:06:49.750 align:start position:0% hundred batteries equaling that so<01:06:47.599> the<01:06:47.760> question<01:06:48.160> is<01:06:48.720> how<01:06:48.880> do<01:06:49.039> we<01:06:49.280> create 01:06:49.750 --> 01:06:49.760 align:start position:0% so the question is how do we create 01:06:49.760 --> 01:06:51.910 align:start position:0% so the question is how do we create these<01:06:50.000> ancillary<01:06:50.480> services<01:06:51.039> and<01:06:51.200> resources 01:06:51.910 --> 01:06:51.920 align:start position:0% these ancillary services and resources 01:06:51.920 --> 01:06:55.109 align:start position:0% these ancillary services and resources to<01:06:52.160> allow<01:06:52.960> a<01:06:53.119> hundred<01:06:53.520> batteries<01:06:54.480> to<01:06:54.720> bid<01:06:54.960> into 01:06:55.109 --> 01:06:55.119 align:start position:0% to allow a hundred batteries to bid into 01:06:55.119 --> 01:06:57.109 align:start position:0% to allow a hundred batteries to bid into the<01:06:55.200> market<01:06:55.599> to<01:06:55.680> do<01:06:55.839> the<01:06:55.920> work<01:06:56.240> of<01:06:56.400> one<01:06:56.799> big 01:06:57.109 --> 01:06:57.119 align:start position:0% the market to do the work of one big 01:06:57.119 --> 01:06:58.069 align:start position:0% the market to do the work of one big plant 01:06:58.069 --> 01:06:58.079 align:start position:0% plant 01:06:58.079 --> 01:07:01.349 align:start position:0% plant as<01:06:58.400> this<01:06:58.799> ramping<01:06:59.200> happens<01:06:59.839> as<01:07:00.640> all<01:07:00.880> of<01:07:01.039> these 01:07:01.349 --> 01:07:01.359 align:start position:0% as this ramping happens as all of these 01:07:01.359 --> 01:07:02.630 align:start position:0% as this ramping happens as all of these small 01:07:02.630 --> 01:07:02.640 align:start position:0% small 01:07:02.640 --> 01:07:04.710 align:start position:0% small i<01:07:02.799> mean<01:07:02.960> obviously<01:07:03.359> loads<01:07:03.680> going<01:07:04.000> like<01:07:04.240> this 01:07:04.710 --> 01:07:04.720 align:start position:0% i mean obviously loads going like this 01:07:04.720 --> 01:07:05.910 align:start position:0% i mean obviously loads going like this and<01:07:04.960> i<01:07:05.119> think 01:07:05.910 --> 01:07:05.920 align:start position:0% and i think 01:07:05.920 --> 01:07:07.910 align:start position:0% and i think you<01:07:06.000> know<01:07:06.240> we<01:07:06.799> we<01:07:07.039> may<01:07:07.200> have<01:07:07.359> a<01:07:07.440> two<01:07:07.680> hour 01:07:07.910 --> 01:07:07.920 align:start position:0% you know we we may have a two hour 01:07:07.920 --> 01:07:10.710 align:start position:0% you know we we may have a two hour battery<01:07:08.240> that<01:07:08.400> runs<01:07:08.720> its<01:07:08.880> course<01:07:09.680> and<01:07:09.760> then<01:07:10.000> it 01:07:10.710 --> 01:07:10.720 align:start position:0% battery that runs its course and then it 01:07:10.720 --> 01:07:11.990 align:start position:0% battery that runs its course and then it it's<01:07:10.880> going<01:07:10.960> to<01:07:11.039> be<01:07:11.119> up<01:07:11.280> to<01:07:11.359> you<01:07:11.440> all<01:07:11.599> to<01:07:11.760> let<01:07:11.920> it 01:07:11.990 --> 01:07:12.000 align:start position:0% it's going to be up to you all to let it 01:07:12.000 --> 01:07:13.910 align:start position:0% it's going to be up to you all to let it run<01:07:12.240> its<01:07:12.400> course<01:07:13.119> and<01:07:13.200> then<01:07:13.359> you<01:07:13.520> got<01:07:13.680> to<01:07:13.760> bring 01:07:13.910 --> 01:07:13.920 align:start position:0% run its course and then you got to bring 01:07:13.920 --> 01:07:15.990 align:start position:0% run its course and then you got to bring another<01:07:14.240> one<01:07:14.480> up<01:07:15.039> and<01:07:15.200> the<01:07:15.359> question<01:07:15.680> that<01:07:15.839> i 01:07:15.990 --> 01:07:16.000 align:start position:0% another one up and the question that i 01:07:16.000 --> 01:07:17.109 align:start position:0% another one up and the question that i have<01:07:16.240> is<01:07:16.400> how 01:07:17.109 --> 01:07:17.119 align:start position:0% have is how 01:07:17.119 --> 01:07:18.630 align:start position:0% have is how is<01:07:17.280> that<01:07:17.520> something<01:07:17.839> that<01:07:17.920> you're<01:07:18.160> preparing 01:07:18.630 --> 01:07:18.640 align:start position:0% is that something that you're preparing 01:07:18.640 --> 01:07:21.430 align:start position:0% is that something that you're preparing for<01:07:18.880> or<01:07:19.039> is<01:07:19.200> that<01:07:19.359> something<01:07:19.680> that<01:07:19.839> you<01:07:20.160> are 01:07:21.430 --> 01:07:21.440 align:start position:0% for or is that something that you are 01:07:21.440 --> 01:07:23.589 align:start position:0% for or is that something that you are like<01:07:21.920> that's<01:07:22.319> that's<01:07:22.559> a<01:07:22.720> ways<01:07:23.119> off<01:07:23.359> we're 01:07:23.589 --> 01:07:23.599 align:start position:0% like that's that's a ways off we're 01:07:23.599 --> 01:07:25.029 align:start position:0% like that's that's a ways off we're still<01:07:23.839> just<01:07:24.000> kind<01:07:24.160> of<01:07:24.240> thinking<01:07:24.559> of<01:07:24.720> the<01:07:24.799> big 01:07:25.029 --> 01:07:25.039 align:start position:0% still just kind of thinking of the big 01:07:25.039 --> 01:07:27.589 align:start position:0% still just kind of thinking of the big thousand<01:07:25.280> megawatt<01:07:25.839> plant<01:07:26.400> well<01:07:26.559> i<01:07:26.640> think 01:07:27.589 --> 01:07:27.599 align:start position:0% thousand megawatt plant well i think 01:07:27.599 --> 01:07:28.390 align:start position:0% thousand megawatt plant well i think january 01:07:28.390 --> 01:07:28.400 align:start position:0% january 01:07:28.400 --> 01:07:32.309 align:start position:0% january 4th<01:07:28.720> we<01:07:28.960> open<01:07:29.280> up<01:07:29.599> the<01:07:30.079> dgr<01:07:30.799> moratorium 01:07:32.309 --> 01:07:32.319 align:start position:0% 4th we open up the dgr moratorium 01:07:32.319 --> 01:07:34.150 align:start position:0% 4th we open up the dgr moratorium so<01:07:32.480> that's<01:07:32.799> the<01:07:33.200> distributed<01:07:33.680> generation 01:07:34.150 --> 01:07:34.160 align:start position:0% so that's the distributed generation 01:07:34.160 --> 01:07:36.470 align:start position:0% so that's the distributed generation resource<01:07:34.640> so<01:07:34.720> that<01:07:34.960> opens<01:07:35.280> up<01:07:35.440> a<01:07:36.000> whole<01:07:36.240> new 01:07:36.470 --> 01:07:36.480 align:start position:0% resource so that opens up a whole new 01:07:36.480 --> 01:07:38.069 align:start position:0% resource so that opens up a whole new path<01:07:37.039> for 01:07:38.069 --> 01:07:38.079 align:start position:0% path for 01:07:38.079 --> 01:07:40.069 align:start position:0% path for for<01:07:38.400> investors<01:07:39.119> to<01:07:39.280> install<01:07:39.760> small 01:07:40.069 --> 01:07:40.079 align:start position:0% for investors to install small 01:07:40.079 --> 01:07:41.349 align:start position:0% for investors to install small generation 01:07:41.349 --> 01:07:41.359 align:start position:0% generation 01:07:41.359 --> 01:07:43.029 align:start position:0% generation at<01:07:41.520> the<01:07:41.599> distribution<01:07:42.240> level<01:07:42.559> a<01:07:42.559> lot<01:07:42.720> of<01:07:42.799> those 01:07:43.029 --> 01:07:43.039 align:start position:0% at the distribution level a lot of those 01:07:43.039 --> 01:07:45.270 align:start position:0% at the distribution level a lot of those will<01:07:43.280> be<01:07:43.440> batteries<01:07:44.319> right<01:07:44.799> i<01:07:44.960> think<01:07:45.039> there's 01:07:45.270 --> 01:07:45.280 align:start position:0% will be batteries right i think there's 01:07:45.280 --> 01:07:46.549 align:start position:0% will be batteries right i think there's going<01:07:45.440> to<01:07:45.520> be<01:07:45.680> a 01:07:46.549 --> 01:07:46.559 align:start position:0% going to be a 01:07:46.559 --> 01:07:48.789 align:start position:0% going to be a that<01:07:46.720> will<01:07:46.960> also<01:07:47.280> start<01:07:47.680> our<01:07:47.920> new<01:07:48.480> small 01:07:48.789 --> 01:07:48.799 align:start position:0% that will also start our new small 01:07:48.799 --> 01:07:50.630 align:start position:0% that will also start our new small generation<01:07:49.359> interconnection<01:07:50.000> process<01:07:50.400> which 01:07:50.630 --> 01:07:50.640 align:start position:0% generation interconnection process which 01:07:50.640 --> 01:07:52.630 align:start position:0% generation interconnection process which is<01:07:50.799> a<01:07:50.880> streamlined<01:07:51.599> process<01:07:52.079> for<01:07:52.400> for 01:07:52.630 --> 01:07:52.640 align:start position:0% is a streamlined process for for 01:07:52.640 --> 01:07:54.470 align:start position:0% is a streamlined process for for interconnecting<01:07:53.280> generation 01:07:54.470 --> 01:07:54.480 align:start position:0% interconnecting generation 01:07:54.480 --> 01:07:56.390 align:start position:0% interconnecting generation so<01:07:54.720> both<01:07:54.960> of<01:07:55.039> those<01:07:55.280> things<01:07:55.680> really<01:07:56.079> set<01:07:56.319> the 01:07:56.390 --> 01:07:56.400 align:start position:0% so both of those things really set the 01:07:56.400 --> 01:07:57.670 align:start position:0% so both of those things really set the stage 01:07:57.670 --> 01:07:57.680 align:start position:0% stage 01:07:57.680 --> 01:07:59.510 align:start position:0% stage for<01:07:58.240> exactly<01:07:58.640> what<01:07:58.720> you<01:07:58.880> were<01:07:58.960> talking<01:07:59.280> about 01:07:59.510 --> 01:07:59.520 align:start position:0% for exactly what you were talking about 01:07:59.520 --> 01:08:01.430 align:start position:0% for exactly what you were talking about and<01:07:59.599> enabling<01:08:00.079> a<01:08:00.160> lot<01:08:00.319> of<01:08:00.400> smaller<01:08:00.880> resources 01:08:01.430 --> 01:08:01.440 align:start position:0% and enabling a lot of smaller resources 01:08:01.440 --> 01:08:04.309 align:start position:0% and enabling a lot of smaller resources to<01:08:01.599> come<01:08:01.839> in<01:08:02.240> and<01:08:02.720> uh<01:08:03.280> in<01:08:03.440> aggregate<01:08:04.000> replace 01:08:04.309 --> 01:08:04.319 align:start position:0% to come in and uh in aggregate replace 01:08:04.319 --> 01:08:05.829 align:start position:0% to come in and uh in aggregate replace some<01:08:04.480> of<01:08:04.559> these<01:08:04.720> larger<01:08:05.039> ones 01:08:05.829 --> 01:08:05.839 align:start position:0% some of these larger ones 01:08:05.839 --> 01:08:06.470 align:start position:0% some of these larger ones and 01:08:06.470 --> 01:08:06.480 align:start position:0% and 01:08:06.480 --> 01:08:08.470 align:start position:0% and or<01:08:06.640> compete<01:08:06.960> with<01:08:07.119> art<01:08:07.359> or<01:08:07.440> what's<01:08:07.680> part<01:08:08.319> let 01:08:08.470 --> 01:08:08.480 align:start position:0% or compete with art or what's part let 01:08:08.480 --> 01:08:11.349 align:start position:0% or compete with art or what's part let me<01:08:08.720> follow<01:08:08.960> up<01:08:09.440> on<01:08:09.599> that<01:08:09.839> comment 01:08:11.349 --> 01:08:11.359 align:start position:0% me follow up on that comment 01:08:11.359 --> 01:08:15.270 align:start position:0% me follow up on that comment we<01:08:11.599> want<01:08:12.240> all<01:08:12.480> the<01:08:12.640> tools<01:08:12.960> in<01:08:13.039> the<01:08:13.119> toolbox 01:08:15.270 --> 01:08:15.280 align:start position:0% we want all the tools in the toolbox 01:08:15.280 --> 01:08:18.390 align:start position:0% we want all the tools in the toolbox and<01:08:15.680> don't<01:08:15.920> particularly<01:08:16.480> care<01:08:17.199> i<01:08:17.839> i<01:08:18.080> wouldn't 01:08:18.390 --> 01:08:18.400 align:start position:0% and don't particularly care i i wouldn't 01:08:18.400 --> 01:08:20.550 align:start position:0% and don't particularly care i i wouldn't mind<01:08:18.719> a<01:08:18.880> thousand<01:08:19.199> megawatt<01:08:19.839> combined<01:08:20.239> cycle 01:08:20.550 --> 01:08:20.560 align:start position:0% mind a thousand megawatt combined cycle 01:08:20.560 --> 01:08:22.309 align:start position:0% mind a thousand megawatt combined cycle clean<01:08:20.799> gas<01:08:21.120> that's<01:08:21.440> 70<01:08:21.759> percent<01:08:22.080> lower 01:08:22.309 --> 01:08:22.319 align:start position:0% clean gas that's 70 percent lower 01:08:22.319 --> 01:08:24.229 align:start position:0% clean gas that's 70 percent lower emissions<01:08:22.799> than<01:08:23.199> coal<01:08:23.520> i<01:08:23.600> wouldn't<01:08:23.839> mind<01:08:24.080> one 01:08:24.229 --> 01:08:24.239 align:start position:0% emissions than coal i wouldn't mind one 01:08:24.239 --> 01:08:25.669 align:start position:0% emissions than coal i wouldn't mind one of those<01:08:24.480> right<01:08:24.640> now<01:08:24.880> for<01:08:25.040> sure<01:08:25.279> you<01:08:25.359> know 01:08:25.669 --> 01:08:25.679 align:start position:0% of those right now for sure you know 01:08:25.679 --> 01:08:27.749 align:start position:0% of those right now for sure you know especially<01:08:26.159> would<01:08:26.319> have<01:08:26.400> liked<01:08:26.560> to<01:08:26.719> have<01:08:26.799> one 01:08:27.749 --> 01:08:27.759 align:start position:0% especially would have liked to have one 01:08:27.759 --> 01:08:30.149 align:start position:0% especially would have liked to have one in<01:08:27.920> late<01:08:28.159> october<01:08:29.040> right 01:08:30.149 --> 01:08:30.159 align:start position:0% in late october right 01:08:30.159 --> 01:08:31.430 align:start position:0% in late october right when<01:08:30.319> we<01:08:30.480> were 01:08:31.430 --> 01:08:31.440 align:start position:0% when we were 01:08:31.440 --> 01:08:32.950 align:start position:0% when we were scrambling<01:08:31.920> to<01:08:32.080> keep 01:08:32.950 --> 01:08:32.960 align:start position:0% scrambling to keep 01:08:32.960 --> 01:08:34.950 align:start position:0% scrambling to keep keep<01:08:33.199> things<01:08:33.440> going 01:08:34.950 --> 01:08:34.960 align:start position:0% keep things going 01:08:34.960 --> 01:08:37.990 align:start position:0% keep things going so<01:08:35.279> yes<01:08:35.600> all<01:08:35.759> tools<01:08:36.080> in<01:08:36.159> the<01:08:36.239> toolbox 01:08:37.990 --> 01:08:38.000 align:start position:0% so yes all tools in the toolbox 01:08:38.000 --> 01:08:39.349 align:start position:0% so yes all tools in the toolbox but 01:08:39.349 --> 01:08:39.359 align:start position:0% but 01:08:39.359 --> 01:08:41.349 align:start position:0% but i<01:08:39.759> want<01:08:39.920> to<01:08:40.080> make<01:08:40.239> sure 01:08:41.349 --> 01:08:41.359 align:start position:0% i want to make sure 01:08:41.359 --> 01:08:43.749 align:start position:0% i want to make sure that<01:08:42.000> all<01:08:42.239> of<01:08:42.319> our<01:08:42.400> market<01:08:42.640> participants 01:08:43.749 --> 01:08:43.759 align:start position:0% that all of our market participants 01:08:43.759 --> 01:08:46.229 align:start position:0% that all of our market participants understand<01:08:44.239> this<01:08:44.719> and<01:08:45.199> and<01:08:45.359> that<01:08:45.520> we<01:08:45.679> all<01:08:46.000> have 01:08:46.229 --> 01:08:46.239 align:start position:0% understand this and and that we all have 01:08:46.239 --> 01:08:48.630 align:start position:0% understand this and and that we all have a<01:08:46.319> sense<01:08:46.640> of<01:08:46.719> this 01:08:48.630 --> 01:08:48.640 align:start position:0% a sense of this 01:08:48.640 --> 01:08:51.669 align:start position:0% a sense of this it<01:08:48.799> is<01:08:49.279> not<01:08:49.600> our<01:08:49.920> job<01:08:50.319> to<01:08:50.560> fit<01:08:50.799> the<01:08:51.040> operational 01:08:51.669 --> 01:08:51.679 align:start position:0% it is not our job to fit the operational 01:08:51.679 --> 01:08:53.669 align:start position:0% it is not our job to fit the operational requirements<01:08:52.080> of<01:08:52.239> ercot<01:08:53.040> to<01:08:53.199> the<01:08:53.359> market 01:08:53.669 --> 01:08:53.679 align:start position:0% requirements of ercot to the market 01:08:53.679 --> 01:08:55.669 align:start position:0% requirements of ercot to the market participants<01:08:54.319> business<01:08:54.640> model<01:08:55.040> or<01:08:55.199> existing 01:08:55.669 --> 01:08:55.679 align:start position:0% participants business model or existing 01:08:55.679 --> 01:08:56.630 align:start position:0% participants business model or existing tools 01:08:56.630 --> 01:08:56.640 align:start position:0% tools 01:08:56.640 --> 01:08:59.269 align:start position:0% tools it<01:08:56.799> is<01:08:56.960> the<01:08:57.120> marketplace's<01:08:58.080> technology<01:08:59.040> to 01:08:59.269 --> 01:08:59.279 align:start position:0% it is the marketplace's technology to 01:08:59.279 --> 01:09:01.189 align:start position:0% it is the marketplace's technology to fit<01:08:59.520> the<01:08:59.600> technology<01:09:00.239> the<01:09:00.400> business<01:09:00.799> models 01:09:01.189 --> 01:09:01.199 align:start position:0% fit the technology the business models 01:09:01.199 --> 01:09:04.149 align:start position:0% fit the technology the business models to<01:09:01.359> the<01:09:01.520> operational<01:09:02.080> needs<01:09:02.799> of<01:09:02.960> ercot 01:09:04.149 --> 01:09:04.159 align:start position:0% to the operational needs of ercot 01:09:04.159 --> 01:09:05.669 align:start position:0% to the operational needs of ercot and<01:09:04.480> and<01:09:04.640> that's<01:09:04.880> what's<01:09:05.120> something<01:09:05.359> that 01:09:05.669 --> 01:09:05.679 align:start position:0% and and that's what's something that 01:09:05.679 --> 01:09:06.550 align:start position:0% and and that's what's something that really 01:09:06.550 --> 01:09:06.560 align:start position:0% really 01:09:06.560 --> 01:09:07.990 align:start position:0% really chapped<01:09:06.799> my<01:09:06.960> height<01:09:07.199> in<01:09:07.279> these<01:09:07.440> comments<01:09:07.839> is 01:09:07.990 --> 01:09:08.000 align:start position:0% chapped my height in these comments is 01:09:08.000 --> 01:09:09.590 align:start position:0% chapped my height in these comments is you've<01:09:08.159> got<01:09:08.319> to<01:09:08.400> change<01:09:08.719> woody's<01:09:09.120> ability<01:09:09.520> to 01:09:09.590 --> 01:09:09.600 align:start position:0% you've got to change woody's ability to 01:09:09.600 --> 01:09:12.870 align:start position:0% you've got to change woody's ability to respond<01:09:10.159> to<01:09:10.319> the<01:09:10.400> grid<01:09:11.279> just<01:09:11.520> so<01:09:11.679> you<01:09:11.839> can 01:09:12.870 --> 01:09:12.880 align:start position:0% respond to the grid just so you can 01:09:12.880 --> 01:09:15.669 align:start position:0% respond to the grid just so you can uh<01:09:13.600> get<01:09:13.759> your<01:09:14.000> accommodate<01:09:14.560> my<01:09:14.799> uh<01:09:15.040> pro<01:09:15.279> forma 01:09:15.669 --> 01:09:15.679 align:start position:0% uh get your accommodate my uh pro forma 01:09:15.679 --> 01:09:17.669 align:start position:0% uh get your accommodate my uh pro forma and<01:09:16.159> give<01:09:16.400> my<01:09:16.560> investors<01:09:17.040> the<01:09:17.199> returns<01:09:17.520> i 01:09:17.669 --> 01:09:17.679 align:start position:0% and give my investors the returns i 01:09:17.679 --> 01:09:20.070 align:start position:0% and give my investors the returns i expected<01:09:18.000> that<01:09:18.159> is<01:09:18.400> absolutely<01:09:18.960> unacceptable 01:09:20.070 --> 01:09:20.080 align:start position:0% expected that is absolutely unacceptable 01:09:20.080 --> 01:09:22.630 align:start position:0% expected that is absolutely unacceptable the<01:09:20.319> operational<01:09:20.799> needs<01:09:21.120> of<01:09:21.199> the<01:09:21.279> grid<01:09:22.159> uh 01:09:22.630 --> 01:09:22.640 align:start position:0% the operational needs of the grid uh 01:09:22.640 --> 01:09:24.870 align:start position:0% the operational needs of the grid uh come<01:09:22.880> first<01:09:23.440> the<01:09:23.600> market<01:09:23.920> needs<01:09:24.159> to<01:09:24.239> innovate 01:09:24.870 --> 01:09:24.880 align:start position:0% come first the market needs to innovate 01:09:24.880 --> 01:09:26.470 align:start position:0% come first the market needs to innovate both<01:09:25.120> technology<01:09:25.679> and<01:09:25.759> business<01:09:26.080> models<01:09:26.400> to 01:09:26.470 --> 01:09:26.480 align:start position:0% both technology and business models to 01:09:26.480 --> 01:09:28.630 align:start position:0% both technology and business models to match<01:09:26.719> the<01:09:26.880> operational<01:09:27.359> needs<01:09:27.679> that<01:09:27.839> we<01:09:28.000> have 01:09:28.630 --> 01:09:28.640 align:start position:0% match the operational needs that we have 01:09:28.640 --> 01:09:31.669 align:start position:0% match the operational needs that we have and<01:09:28.880> to<01:09:28.960> keep<01:09:29.120> the<01:09:29.279> lights<01:09:29.520> on<01:09:29.839> agreed<01:09:30.319> and<01:09:30.799> i<01:09:31.279> i 01:09:31.669 --> 01:09:31.679 align:start position:0% and to keep the lights on agreed and i i 01:09:31.679 --> 01:09:32.789 align:start position:0% and to keep the lights on agreed and i i agree<01:09:31.920> with<01:09:32.080> that 01:09:32.789 --> 01:09:32.799 align:start position:0% agree with that 01:09:32.799 --> 01:09:34.309 align:start position:0% agree with that i<01:09:32.880> just<01:09:33.120> think<01:09:33.279> that<01:09:33.440> the<01:09:33.600> operational<01:09:34.080> needs 01:09:34.309 --> 01:09:34.319 align:start position:0% i just think that the operational needs 01:09:34.319 --> 01:09:37.189 align:start position:0% i just think that the operational needs of<01:09:34.400> the<01:09:34.560> system<01:09:35.199> i<01:09:35.359> think<01:09:35.759> some<01:09:35.920> of<01:09:36.080> those<01:09:36.319> are 01:09:37.189 --> 01:09:37.199 align:start position:0% of the system i think some of those are 01:09:37.199 --> 01:09:39.910 align:start position:0% of the system i think some of those are are<01:09:37.520> uh<01:09:38.319> need<01:09:38.480> to<01:09:38.560> be<01:09:38.719> discussed<01:09:39.120> as<01:09:39.199> well 01:09:39.910 --> 01:09:39.920 align:start position:0% are uh need to be discussed as well 01:09:39.920 --> 01:09:40.789 align:start position:0% are uh need to be discussed as well mm-hmm 01:09:40.789 --> 01:09:40.799 align:start position:0% mm-hmm 01:09:40.799 --> 01:09:42.470 align:start position:0% mm-hmm so<01:09:41.199> we<01:09:41.279> need<01:09:41.359> to<01:09:41.520> figure<01:09:41.759> out<01:09:41.839> what<01:09:41.920> those<01:09:42.239> are 01:09:42.470 --> 01:09:42.480 align:start position:0% so we need to figure out what those are 01:09:42.480 --> 01:09:44.630 align:start position:0% so we need to figure out what those are yeah<01:09:42.880> speaking<01:09:43.279> of<01:09:43.440> operations 01:09:44.630 --> 01:09:44.640 align:start position:0% yeah speaking of operations 01:09:44.640 --> 01:09:48.550 align:start position:0% yeah speaking of operations um<01:09:45.359> when<01:09:45.600> when<01:09:45.759> you<01:09:46.000> envision<01:09:46.480> ecrs 01:09:48.550 --> 01:09:48.560 align:start position:0% um when when you envision ecrs 01:09:48.560 --> 01:09:50.870 align:start position:0% um when when you envision ecrs and<01:09:49.120> i'm<01:09:49.359> concerned<01:09:50.159> i<01:09:50.239> don't<01:09:50.319> want<01:09:50.480> to<01:09:50.560> step 01:09:50.870 --> 01:09:50.880 align:start position:0% and i'm concerned i don't want to step 01:09:50.880 --> 01:09:53.749 align:start position:0% and i'm concerned i don't want to step on<01:09:51.359> step<01:09:51.679> on<01:09:51.920> your<01:09:52.159> policy<01:09:52.960> with<01:09:53.120> policy<01:09:53.600> that 01:09:53.749 --> 01:09:53.759 align:start position:0% on step on your policy with policy that 01:09:53.759 --> 01:09:56.229 align:start position:0% on step on your policy with policy that we're<01:09:53.920> discussing<01:09:54.800> when<01:09:54.960> we're<01:09:55.520> formulating 01:09:56.229 --> 01:09:56.239 align:start position:0% we're discussing when we're formulating 01:09:56.239 --> 01:09:57.350 align:start position:0% we're discussing when we're formulating transmission<01:09:56.800> interconnection 01:09:57.350 --> 01:09:57.360 align:start position:0% transmission interconnection 01:09:57.360 --> 01:09:59.110 align:start position:0% transmission interconnection prioritization 01:09:59.110 --> 01:09:59.120 align:start position:0% prioritization 01:09:59.120 --> 01:10:01.430 align:start position:0% prioritization for<01:09:59.280> the<01:09:59.360> purposes<01:09:59.760> of<01:09:59.920> batteries 01:10:01.430 --> 01:10:01.440 align:start position:0% for the purposes of batteries 01:10:01.440 --> 01:10:03.189 align:start position:0% for the purposes of batteries and<01:10:01.600> ecrs 01:10:03.189 --> 01:10:03.199 align:start position:0% and ecrs 01:10:03.199 --> 01:10:04.709 align:start position:0% and ecrs when 01:10:04.709 --> 01:10:04.719 align:start position:0% when 01:10:04.719 --> 01:10:07.110 align:start position:0% when when<01:10:04.880> you<01:10:05.120> envision<01:10:05.520> their<01:10:05.679> participation 01:10:07.110 --> 01:10:07.120 align:start position:0% when you envision their participation 01:10:07.120 --> 01:10:08.149 align:start position:0% when you envision their participation can<01:10:07.360> a 01:10:08.149 --> 01:10:08.159 align:start position:0% can a 01:10:08.159 --> 01:10:11.350 align:start position:0% can a 100<01:10:08.800> megawatt<01:10:09.360> battery<01:10:10.159> that<01:10:10.400> lasts<01:10:10.800> for<01:10:11.120> one 01:10:11.350 --> 01:10:11.360 align:start position:0% 100 megawatt battery that lasts for one 01:10:11.360 --> 01:10:12.390 align:start position:0% 100 megawatt battery that lasts for one hour 01:10:12.390 --> 01:10:12.400 align:start position:0% hour 01:10:12.400 --> 01:10:14.229 align:start position:0% hour uh<01:10:12.719> d-rate<01:10:13.199> themselves 01:10:14.229 --> 01:10:14.239 align:start position:0% uh d-rate themselves 01:10:14.239 --> 01:10:17.430 align:start position:0% uh d-rate themselves to<01:10:14.480> 50<01:10:14.800> megawatts<01:10:15.520> and<01:10:15.760> last<01:10:16.080> for<01:10:16.320> two<01:10:16.560> hours 01:10:17.430 --> 01:10:17.440 align:start position:0% to 50 megawatts and last for two hours 01:10:17.440 --> 01:10:18.870 align:start position:0% to 50 megawatts and last for two hours under<01:10:17.760> your<01:10:18.000> model 01:10:18.870 --> 01:10:18.880 align:start position:0% under your model 01:10:18.880 --> 01:10:23.110 align:start position:0% under your model of<01:10:19.440> of<01:10:19.920> bidding<01:10:20.719> that<01:10:21.120> service 01:10:23.110 --> 01:10:23.120 align:start position:0% of of bidding that service 01:10:23.120 --> 01:10:24.950 align:start position:0% of of bidding that service so<01:10:23.600> i<01:10:23.760> think<01:10:23.920> there's<01:10:24.080> two<01:10:24.320> questions<01:10:24.640> there 01:10:24.950 --> 01:10:24.960 align:start position:0% so i think there's two questions there 01:10:24.960 --> 01:10:26.390 align:start position:0% so i think there's two questions there from<01:10:25.360> from 01:10:26.390 --> 01:10:26.400 align:start position:0% from from 01:10:26.400 --> 01:10:29.350 align:start position:0% from from our<01:10:26.560> standpoint<01:10:27.600> yes<01:10:28.239> okay<01:10:28.640> the<01:10:28.800> product<01:10:29.280> i 01:10:29.350 --> 01:10:29.360 align:start position:0% our standpoint yes okay the product i 01:10:29.360 --> 01:10:31.830 align:start position:0% our standpoint yes okay the product i mean<01:10:29.520> if<01:10:29.600> they<01:10:29.760> can<01:10:30.239> they<01:10:30.400> can<01:10:30.560> bid<01:10:30.800> in<01:10:31.360> for<01:10:31.600> two 01:10:31.830 --> 01:10:31.840 align:start position:0% mean if they can they can bid in for two 01:10:31.840 --> 01:10:32.950 align:start position:0% mean if they can they can bid in for two hours 01:10:32.950 --> 01:10:32.960 align:start position:0% hours 01:10:32.960 --> 01:10:34.229 align:start position:0% hours yes<01:10:33.440> okay 01:10:34.229 --> 01:10:34.239 align:start position:0% yes okay 01:10:34.239 --> 01:10:35.830 align:start position:0% yes okay now<01:10:34.480> from<01:10:34.880> the<01:10:34.960> other<01:10:35.120> side<01:10:35.280> of<01:10:35.360> that<01:10:35.520> question 01:10:35.830 --> 01:10:35.840 align:start position:0% now from the other side of that question 01:10:35.840 --> 01:10:37.270 align:start position:0% now from the other side of that question is<01:10:35.920> from<01:10:36.080> a<01:10:36.239> technology<01:10:36.719> standpoint<01:10:37.120> will 01:10:37.270 --> 01:10:37.280 align:start position:0% is from a technology standpoint will 01:10:37.280 --> 01:10:38.790 align:start position:0% is from a technology standpoint will they<01:10:37.440> be<01:10:37.600> able<01:10:37.840> to<01:10:38.159> and<01:10:38.239> that's<01:10:38.400> something 01:10:38.790 --> 01:10:38.800 align:start position:0% they be able to and that's something 01:10:38.800 --> 01:10:40.950 align:start position:0% they be able to and that's something that<01:10:38.960> the<01:10:39.040> developers<01:10:39.520> would<01:10:39.679> have<01:10:39.840> to 01:10:40.950 --> 01:10:40.960 align:start position:0% that the developers would have to 01:10:40.960 --> 01:10:42.390 align:start position:0% that the developers would have to you<01:10:41.040> know<01:10:41.199> if<01:10:41.520> that 01:10:42.390 --> 01:10:42.400 align:start position:0% you know if that 01:10:42.400 --> 01:10:43.750 align:start position:0% you know if that if<01:10:42.480> they<01:10:42.640> configure<01:10:43.040> their<01:10:43.199> unit<01:10:43.440> to<01:10:43.520> be<01:10:43.600> able 01:10:43.750 --> 01:10:43.760 align:start position:0% if they configure their unit to be able 01:10:43.760 --> 01:10:45.830 align:start position:0% if they configure their unit to be able to<01:10:43.840> do<01:10:44.000> that<01:10:44.159> or<01:10:44.320> not<01:10:44.719> right<01:10:45.280> maybe<01:10:45.520> the<01:10:45.600> more 01:10:45.830 --> 01:10:45.840 align:start position:0% to do that or not right maybe the more 01:10:45.840 --> 01:10:49.270 align:start position:0% to do that or not right maybe the more interesting<01:10:46.239> question<01:10:46.640> is<01:10:47.120> um 01:10:49.270 --> 01:10:49.280 align:start position:0% interesting question is um 01:10:49.280 --> 01:10:52.070 align:start position:0% interesting question is um a<01:10:49.440> two<01:10:49.679> hour<01:10:50.239> 50<01:10:50.480> megawatt<01:10:51.440> megawatt<01:10:51.840> hour 01:10:52.070 --> 01:10:52.080 align:start position:0% a two hour 50 megawatt megawatt hour 01:10:52.080 --> 01:10:55.430 align:start position:0% a two hour 50 megawatt megawatt hour battery 01:10:55.430 --> 01:10:55.440 align:start position:0% 01:10:55.440 --> 01:10:57.990 align:start position:0% will<01:10:55.679> it<01:10:55.760> be<01:10:55.920> able<01:10:56.159> to<01:10:56.320> produce<01:10:56.719> a<01:10:56.880> hundred<01:10:57.840> in 01:10:57.990 --> 01:10:58.000 align:start position:0% will it be able to produce a hundred in 01:10:58.000 --> 01:10:59.110 align:start position:0% will it be able to produce a hundred in one<01:10:58.239> hour 01:10:59.110 --> 01:10:59.120 align:start position:0% one hour 01:10:59.120 --> 01:11:00.229 align:start position:0% one hour and<01:10:59.280> that<01:10:59.440> will<01:10:59.600> have<01:10:59.760> to<01:10:59.920> do<01:11:00.000> with<01:11:00.080> the 01:11:00.229 --> 01:11:00.239 align:start position:0% and that will have to do with the 01:11:00.239 --> 01:11:01.990 align:start position:0% and that will have to do with the inverter<01:11:00.640> size<01:11:01.040> and<01:11:01.120> whether<01:11:01.520> the<01:11:01.679> how<01:11:01.840> they 01:11:01.990 --> 01:11:02.000 align:start position:0% inverter size and whether the how they 01:11:02.000 --> 01:11:03.590 align:start position:0% inverter size and whether the how they size<01:11:02.320> their<01:11:02.560> inverter 01:11:03.590 --> 01:11:03.600 align:start position:0% size their inverter 01:11:03.600 --> 01:11:05.350 align:start position:0% size their inverter so<01:11:03.840> stretching<01:11:04.239> them<01:11:04.480> stretching<01:11:04.800> one<01:11:04.960> out<01:11:05.199> is 01:11:05.350 --> 01:11:05.360 align:start position:0% so stretching them stretching one out is 01:11:05.360 --> 01:11:07.430 align:start position:0% so stretching them stretching one out is probably<01:11:05.600> not<01:11:05.760> as<01:11:05.840> big<01:11:06.000> a<01:11:06.080> deal<01:11:06.400> as 01:11:07.430 --> 01:11:07.440 align:start position:0% probably not as big a deal as 01:11:07.440 --> 01:11:09.510 align:start position:0% probably not as big a deal as bringing<01:11:08.239> twice<01:11:08.560> the<01:11:08.719> amount<01:11:09.040> in<01:11:09.120> a<01:11:09.199> shorter 01:11:09.510 --> 01:11:09.520 align:start position:0% bringing twice the amount in a shorter 01:11:09.520 --> 01:11:11.590 align:start position:0% bringing twice the amount in a shorter amount<01:11:09.679> of<01:11:09.840> time<01:11:10.159> and<01:11:10.320> so<01:11:10.719> that's<01:11:10.960> the 01:11:11.590 --> 01:11:11.600 align:start position:0% amount of time and so that's the 01:11:11.600 --> 01:11:14.070 align:start position:0% amount of time and so that's the so<01:11:11.760> how<01:11:11.920> we<01:11:12.080> design<01:11:12.400> these<01:11:12.560> services<01:11:13.199> may 01:11:14.070 --> 01:11:14.080 align:start position:0% so how we design these services may 01:11:14.080 --> 01:11:16.870 align:start position:0% so how we design these services may incent<01:11:14.640> larger<01:11:14.960> inverters 01:11:16.870 --> 01:11:16.880 align:start position:0% incent larger inverters 01:11:16.880 --> 01:11:18.070 align:start position:0% incent larger inverters is<01:11:16.960> that<01:11:17.120> a<01:11:17.199> good<01:11:17.360> thing 01:11:18.070 --> 01:11:18.080 align:start position:0% is that a good thing 01:11:18.080 --> 01:11:20.070 align:start position:0% is that a good thing we<01:11:18.239> would<01:11:18.560> want<01:11:18.960> larger<01:11:19.280> convert<01:11:19.679> the<01:11:19.760> larger 01:11:20.070 --> 01:11:20.080 align:start position:0% we would want larger convert the larger 01:11:20.080 --> 01:11:22.149 align:start position:0% we would want larger convert the larger environment<01:11:20.719> that's<01:11:21.040> added<01:11:21.360> flexibility 01:11:22.149 --> 01:11:22.159 align:start position:0% environment that's added flexibility 01:11:22.159 --> 01:11:23.990 align:start position:0% environment that's added flexibility okay 01:11:23.990 --> 01:11:24.000 align:start position:0% okay 01:11:24.000 --> 01:11:25.110 align:start position:0% okay all<01:11:24.159> right 01:11:25.110 --> 01:11:25.120 align:start position:0% all right 01:11:25.120 --> 01:11:27.669 align:start position:0% all right um<01:11:25.760> we've<01:11:25.920> got<01:11:26.159> i<01:11:26.239> think<01:11:26.400> the<01:11:26.560> next<01:11:27.120> hot<01:11:27.360> topic 01:11:27.669 --> 01:11:27.679 align:start position:0% um we've got i think the next hot topic 01:11:27.679 --> 01:11:30.709 align:start position:0% um we've got i think the next hot topic on<01:11:27.840> this<01:11:28.000> one<01:11:28.239> is<01:11:28.880> cost<01:11:29.199> allocation<01:11:30.239> oh<01:11:30.480> god 01:11:30.709 --> 01:11:30.719 align:start position:0% on this one is cost allocation oh god 01:11:30.719 --> 01:11:32.390 align:start position:0% on this one is cost allocation oh god we're<01:11:30.880> going<01:11:31.120> there<01:11:31.280> okay<01:11:31.679> sir<01:11:32.080> we<01:11:32.159> got<01:11:32.320> to 01:11:32.390 --> 01:11:32.400 align:start position:0% we're going there okay sir we got to 01:11:32.400 --> 01:11:34.550 align:start position:0% we're going there okay sir we got to start<01:11:32.880> talking<01:11:33.679> we<01:11:33.840> got<01:11:34.000> to<01:11:34.080> start<01:11:34.320> knocking 01:11:34.550 --> 01:11:34.560 align:start position:0% start talking we got to start knocking 01:11:34.560 --> 01:11:37.990 align:start position:0% start talking we got to start knocking some<01:11:34.719> of<01:11:34.800> these<01:11:35.040> down<01:11:35.679> um<01:11:36.320> thank<01:11:36.480> you<01:11:36.640> woody 01:11:37.990 --> 01:11:38.000 align:start position:0% some of these down um thank you woody 01:11:38.000 --> 01:11:40.470 align:start position:0% some of these down um thank you woody um<01:11:38.880> again<01:11:39.199> no<01:11:39.520> no<01:11:39.760> don't<01:11:40.000> expect<01:11:40.239> any 01:11:40.470 --> 01:11:40.480 align:start position:0% um again no no don't expect any 01:11:40.480 --> 01:11:41.830 align:start position:0% um again no no don't expect any decisions<01:11:40.880> today 01:11:41.830 --> 01:11:41.840 align:start position:0% decisions today 01:11:41.840 --> 01:11:43.590 align:start position:0% decisions today but<01:11:42.480> um 01:11:43.590 --> 01:11:43.600 align:start position:0% but um 01:11:43.600 --> 01:11:46.870 align:start position:0% but um sp<01:11:44.320> sb3<01:11:44.880> required<01:11:45.199> a<01:11:45.360> lot<01:11:45.520> of<01:11:45.600> things<01:11:46.159> uh<01:11:46.640> first 01:11:46.870 --> 01:11:46.880 align:start position:0% sp sb3 required a lot of things uh first 01:11:46.880 --> 01:11:49.189 align:start position:0% sp sb3 required a lot of things uh first and<01:11:47.040> foremost<01:11:47.520> was<01:11:48.000> action 01:11:49.189 --> 01:11:49.199 align:start position:0% and foremost was action 01:11:49.199 --> 01:11:50.149 align:start position:0% and foremost was action so 01:11:50.149 --> 01:11:50.159 align:start position:0% so 01:11:50.159 --> 01:11:53.189 align:start position:0% so i'll<01:11:50.880> i'll 01:11:53.189 --> 01:11:53.199 align:start position:0% 01:11:53.199 --> 01:11:56.390 align:start position:0% open<01:11:53.440> that<01:11:53.679> conversation<01:11:54.400> quickly<01:11:54.960> with 01:11:56.390 --> 01:11:56.400 align:start position:0% open that conversation quickly with 01:11:56.400 --> 01:11:59.590 align:start position:0% open that conversation quickly with uh<01:11:57.120> my<01:11:57.600> thought<01:11:57.840> that<01:11:58.080> right<01:11:58.320> now 01:11:59.590 --> 01:11:59.600 align:start position:0% uh my thought that right now 01:11:59.600 --> 01:12:02.310 align:start position:0% uh my thought that right now the<01:11:59.920> cost<01:12:00.239> allocation<01:12:00.800> for<01:12:00.960> ecrs<01:12:01.920> should<01:12:02.159> be 01:12:02.310 --> 01:12:02.320 align:start position:0% the cost allocation for ecrs should be 01:12:02.320 --> 01:12:04.550 align:start position:0% the cost allocation for ecrs should be allocated<01:12:02.960> to 01:12:04.550 --> 01:12:04.560 align:start position:0% allocated to 01:12:04.560 --> 01:12:06.149 align:start position:0% allocated to the<01:12:04.719> intermittent<01:12:05.199> resources<01:12:05.760> that<01:12:05.920> we're 01:12:06.149 --> 01:12:06.159 align:start position:0% the intermittent resources that we're 01:12:06.159 --> 01:12:09.910 align:start position:0% the intermittent resources that we're trying<01:12:06.320> to<01:12:06.400> catch<01:12:06.719> up<01:12:06.880> with 01:12:09.910 --> 01:12:09.920 align:start position:0% 01:12:09.920 --> 01:12:10.870 align:start position:0% that 01:12:10.870 --> 01:12:10.880 align:start position:0% that 01:12:10.880 --> 01:12:11.750 align:start position:0% that i<01:12:10.960> mean 01:12:11.750 --> 01:12:11.760 align:start position:0% i mean 01:12:11.760 --> 01:12:14.070 align:start position:0% i mean we've<01:12:12.000> never<01:12:12.400> had<01:12:12.719> 95 01:12:14.070 --> 01:12:14.080 align:start position:0% we've never had 95 01:12:14.080 --> 01:12:16.070 align:start position:0% we've never had 95 percent<01:12:14.640> of<01:12:14.960> our<01:12:15.199> thermal<01:12:15.520> dispatchable 01:12:16.070 --> 01:12:16.080 align:start position:0% percent of our thermal dispatchable 01:12:16.080 --> 01:12:19.030 align:start position:0% percent of our thermal dispatchable fleet<01:12:16.320> go<01:12:16.560> off<01:12:16.960> in<01:12:17.040> a<01:12:17.120> matter<01:12:17.360> of<01:12:17.520> hours 01:12:19.030 --> 01:12:19.040 align:start position:0% fleet go off in a matter of hours 01:12:19.040 --> 01:12:22.070 align:start position:0% fleet go off in a matter of hours we<01:12:19.360> you<01:12:19.520> know<01:12:19.679> the<01:12:19.840> bad<01:12:20.159> days<01:12:20.400> were<01:12:20.840> down<01:12:21.920> you 01:12:22.070 --> 01:12:22.080 align:start position:0% we you know the bad days were down you 01:12:22.080 --> 01:12:22.950 align:start position:0% we you know the bad days were down you know 01:12:22.950 --> 01:12:22.960 align:start position:0% know 01:12:22.960 --> 01:12:25.270 align:start position:0% know we<01:12:23.120> lose<01:12:23.440> 15<01:12:23.920> percent<01:12:24.560> through<01:12:24.800> forced<01:12:25.120> or 01:12:25.270 --> 01:12:25.280 align:start position:0% we lose 15 percent through forced or 01:12:25.280 --> 01:12:27.750 align:start position:0% we lose 15 percent through forced or planned<01:12:25.600> outages<01:12:26.000> maybe<01:12:26.320> 20<01:12:26.560> percent<01:12:27.199> uh<01:12:27.600> in 01:12:27.750 --> 01:12:27.760 align:start position:0% planned outages maybe 20 percent uh in 01:12:27.760 --> 01:12:28.950 align:start position:0% planned outages maybe 20 percent uh in the 01:12:28.950 --> 01:12:28.960 align:start position:0% the 01:12:28.960 --> 01:12:30.310 align:start position:0% the in<01:12:29.120> the<01:12:29.199> shoulder<01:12:29.520> months<01:12:29.760> when<01:12:29.920> we're<01:12:30.159> when 01:12:30.310 --> 01:12:30.320 align:start position:0% in the shoulder months when we're when 01:12:30.320 --> 01:12:31.910 align:start position:0% in the shoulder months when we're when we're<01:12:30.480> doing<01:12:30.719> maintenance 01:12:31.910 --> 01:12:31.920 align:start position:0% we're doing maintenance 01:12:31.920 --> 01:12:33.030 align:start position:0% we're doing maintenance um 01:12:33.030 --> 01:12:33.040 align:start position:0% um 01:12:33.040 --> 01:12:35.189 align:start position:0% um so<01:12:33.440> it<01:12:34.000> only<01:12:34.239> makes<01:12:34.480> sense<01:12:34.719> to<01:12:34.800> me<01:12:34.960> that<01:12:35.040> we're 01:12:35.189 --> 01:12:35.199 align:start position:0% so it only makes sense to me that we're 01:12:35.199 --> 01:12:38.470 align:start position:0% so it only makes sense to me that we're spending<01:12:35.840> like<01:12:36.080> the<01:12:36.320> cost<01:12:36.880> of<01:12:37.520> the<01:12:37.920> so-called 01:12:38.470 --> 01:12:38.480 align:start position:0% spending like the cost of the so-called 01:12:38.480 --> 01:12:39.910 align:start position:0% spending like the cost of the so-called free 01:12:39.910 --> 01:12:39.920 align:start position:0% free 01:12:39.920 --> 01:12:42.390 align:start position:0% free low<01:12:40.239> zero<01:12:40.560> marginal<01:12:40.960> cost<01:12:41.280> intermittence<01:12:42.239> is 01:12:42.390 --> 01:12:42.400 align:start position:0% low zero marginal cost intermittence is 01:12:42.400 --> 01:12:43.590 align:start position:0% low zero marginal cost intermittence is ecrs 01:12:43.590 --> 01:12:43.600 align:start position:0% ecrs 01:12:43.600 --> 01:12:45.350 align:start position:0% ecrs that<01:12:43.760> is<01:12:43.920> the<01:12:44.080> cost 01:12:45.350 --> 01:12:45.360 align:start position:0% that is the cost 01:12:45.360 --> 01:12:46.870 align:start position:0% that is the cost so<01:12:45.600> it<01:12:45.760> only<01:12:45.920> makes<01:12:46.080> sense<01:12:46.320> to<01:12:46.400> me<01:12:46.560> that<01:12:46.719> we 01:12:46.870 --> 01:12:46.880 align:start position:0% so it only makes sense to me that we 01:12:46.880 --> 01:12:49.510 align:start position:0% so it only makes sense to me that we allocate<01:12:47.280> those<01:12:47.840> those<01:12:48.080> costs<01:12:48.400> there 01:12:49.510 --> 01:12:49.520 align:start position:0% allocate those those costs there 01:12:49.520 --> 01:12:52.310 align:start position:0% allocate those those costs there i'll<01:12:50.000> open<01:12:50.159> it<01:12:50.320> up<01:12:50.880> after<01:12:51.199> that<01:12:51.920> and<01:12:52.080> i'm<01:12:52.159> not 01:12:52.310 --> 01:12:52.320 align:start position:0% i'll open it up after that and i'm not 01:12:52.320 --> 01:12:53.910 align:start position:0% i'll open it up after that and i'm not going<01:12:52.400> to<01:12:52.480> say<01:12:52.719> much<01:12:53.040> but<01:12:53.360> i<01:12:53.440> think<01:12:53.600> it<01:12:53.679> would 01:12:53.910 --> 01:12:53.920 align:start position:0% going to say much but i think it would 01:12:53.920 --> 01:12:54.790 align:start position:0% going to say much but i think it would help 01:12:54.790 --> 01:12:54.800 align:start position:0% help 01:12:54.800 --> 01:12:58.470 align:start position:0% help you<01:12:54.880> know<01:12:55.040> me<01:12:55.280> like<01:12:55.600> set<01:12:55.920> the<01:12:56.080> table 01:12:58.470 --> 01:12:58.480 align:start position:0% 01:12:58.480 --> 01:13:01.350 align:start position:0% reading<01:12:58.880> from<01:12:59.520> the<01:12:59.679> recently<01:13:00.159> passed<01:13:00.480> statute 01:13:01.350 --> 01:13:01.360 align:start position:0% reading from the recently passed statute 01:13:01.360 --> 01:13:02.350 align:start position:0% reading from the recently passed statute section 01:13:02.350 --> 01:13:02.360 align:start position:0% section 01:13:02.360 --> 01:13:05.189 align:start position:0% section 35.004<01:13:03.440> of<01:13:03.600> the<01:13:03.679> utilities<01:13:04.239> code<01:13:04.640> subsection 01:13:05.189 --> 01:13:05.199 align:start position:0% 35.004 of the utilities code subsection 01:13:05.199 --> 01:13:06.149 align:start position:0% 35.004 of the utilities code subsection g 01:13:06.149 --> 01:13:06.159 align:start position:0% g 01:13:06.159 --> 01:13:07.910 align:start position:0% g the<01:13:06.320> commission<01:13:06.800> shall<01:13:07.120> review<01:13:07.440> the<01:13:07.600> type 01:13:07.910 --> 01:13:07.920 align:start position:0% the commission shall review the type 01:13:07.920 --> 01:13:09.990 align:start position:0% the commission shall review the type volume<01:13:08.400> and<01:13:08.480> cost<01:13:08.800> of<01:13:08.960> ancillary<01:13:09.360> services<01:13:09.920> to 01:13:09.990 --> 01:13:10.000 align:start position:0% volume and cost of ancillary services to 01:13:10.000 --> 01:13:11.590 align:start position:0% volume and cost of ancillary services to determine<01:13:10.480> whether<01:13:10.719> those<01:13:10.960> services<01:13:11.440> will 01:13:11.590 --> 01:13:11.600 align:start position:0% determine whether those services will 01:13:11.600 --> 01:13:13.110 align:start position:0% determine whether those services will continue<01:13:12.080> to<01:13:12.239> meet<01:13:12.480> the<01:13:12.560> needs<01:13:12.880> of<01:13:12.960> the 01:13:13.110 --> 01:13:13.120 align:start position:0% continue to meet the needs of the 01:13:13.120 --> 01:13:15.030 align:start position:0% continue to meet the needs of the electricity<01:13:13.760> market<01:13:14.080> in<01:13:14.159> the<01:13:14.320> ercot<01:13:14.719> power 01:13:15.030 --> 01:13:15.040 align:start position:0% electricity market in the ercot power 01:13:15.040 --> 01:13:15.910 align:start position:0% electricity market in the ercot power region 01:13:15.910 --> 01:13:15.920 align:start position:0% region 01:13:15.920 --> 01:13:17.910 align:start position:0% region and<01:13:16.159> two<01:13:16.480> evaluate<01:13:17.040> whether<01:13:17.440> additional 01:13:17.910 --> 01:13:17.920 align:start position:0% and two evaluate whether additional 01:13:17.920 --> 01:13:19.910 align:start position:0% and two evaluate whether additional services<01:13:18.400> are<01:13:18.560> needed<01:13:18.880> for<01:13:19.120> reliability<01:13:19.760> in 01:13:19.910 --> 01:13:19.920 align:start position:0% services are needed for reliability in 01:13:19.920 --> 01:13:22.310 align:start position:0% services are needed for reliability in the<01:13:20.000> ercot<01:13:20.400> power<01:13:20.719> region<01:13:21.520> while<01:13:21.760> providing 01:13:22.310 --> 01:13:22.320 align:start position:0% the ercot power region while providing 01:13:22.320 --> 01:13:24.070 align:start position:0% the ercot power region while providing adequate<01:13:22.800> incentives<01:13:23.280> for<01:13:23.440> dispatchable 01:13:24.070 --> 01:13:24.080 align:start position:0% adequate incentives for dispatchable 01:13:24.080 --> 01:13:25.590 align:start position:0% adequate incentives for dispatchable generation 01:13:25.590 --> 01:13:25.600 align:start position:0% generation 01:13:25.600 --> 01:13:27.510 align:start position:0% generation h<01:13:26.080> the<01:13:26.239> commission<01:13:26.719> shall<01:13:27.040> require<01:13:27.360> the 01:13:27.510 --> 01:13:27.520 align:start position:0% h the commission shall require the 01:13:27.520 --> 01:13:29.550 align:start position:0% h the commission shall require the independent<01:13:28.000> organization<01:13:28.560> certified<01:13:29.120> under 01:13:29.550 --> 01:13:29.560 align:start position:0% independent organization certified under 01:13:29.560 --> 01:13:32.390 align:start position:0% independent organization certified under 39151<01:13:30.640> for<01:13:30.800> the<01:13:30.880> urcot<01:13:31.280> power<01:13:31.520> region 01:13:32.390 --> 01:13:32.400 align:start position:0% 39151 for the urcot power region 01:13:32.400 --> 01:13:35.110 align:start position:0% 39151 for the urcot power region to<01:13:32.560> modify<01:13:33.120> the<01:13:33.360> design<01:13:34.080> procurement<01:13:34.880> and 01:13:35.110 --> 01:13:35.120 align:start position:0% to modify the design procurement and 01:13:35.120 --> 01:13:37.830 align:start position:0% to modify the design procurement and cost<01:13:35.520> allocation<01:13:36.159> of<01:13:36.320> ancillary<01:13:36.880> services 01:13:37.830 --> 01:13:37.840 align:start position:0% cost allocation of ancillary services 01:13:37.840 --> 01:13:39.910 align:start position:0% cost allocation of ancillary services for<01:13:38.000> the<01:13:38.159> region<01:13:38.640> in<01:13:38.800> a<01:13:38.960> manner<01:13:39.360> consistent 01:13:39.910 --> 01:13:39.920 align:start position:0% for the region in a manner consistent 01:13:39.920 --> 01:13:42.470 align:start position:0% for the region in a manner consistent with<01:13:40.239> cost<01:13:40.560> causation<01:13:41.280> principles 01:13:42.470 --> 01:13:42.480 align:start position:0% with cost causation principles 01:13:42.480 --> 01:13:46.470 align:start position:0% with cost causation principles on<01:13:42.800> a<01:13:43.080> non-discriminatory<01:13:44.080> basis 01:13:46.470 --> 01:13:46.480 align:start position:0% on a non-discriminatory basis 01:13:46.480 --> 01:13:49.350 align:start position:0% on a non-discriminatory basis table<01:13:46.880> set 01:13:49.350 --> 01:13:49.360 align:start position:0% 01:13:49.360 --> 01:13:51.910 align:start position:0% don't<01:13:49.600> stop<01:13:49.840> there 01:13:51.910 --> 01:13:51.920 align:start position:0% don't stop there 01:13:51.920 --> 01:13:53.430 align:start position:0% don't stop there so<01:13:52.560> uh 01:13:53.430 --> 01:13:53.440 align:start position:0% so uh 01:13:53.440 --> 01:13:55.110 align:start position:0% so uh as<01:13:53.679> per 01:13:55.110 --> 01:13:55.120 align:start position:0% as per 01:13:55.120 --> 01:13:57.669 align:start position:0% as per as<01:13:55.360> per<01:13:55.600> the<01:13:55.760> report 01:13:57.669 --> 01:13:57.679 align:start position:0% as per the report 01:13:57.679 --> 01:14:00.390 align:start position:0% as per the report look<01:13:58.400> cost<01:13:58.719> causation<01:13:59.280> in<01:13:59.360> my<01:13:59.600> view 01:14:00.390 --> 01:14:00.400 align:start position:0% look cost causation in my view 01:14:00.400 --> 01:14:04.070 align:start position:0% look cost causation in my view and<01:14:00.880> that<01:14:01.280> as<01:14:01.520> it<01:14:01.679> is<01:14:02.239> litigated<01:14:02.960> in<01:14:03.120> other 01:14:04.070 --> 01:14:04.080 align:start position:0% and that as it is litigated in other 01:14:04.080 --> 01:14:06.390 align:start position:0% and that as it is litigated in other rtos 01:14:06.390 --> 01:14:06.400 align:start position:0% rtos 01:14:06.400 --> 01:14:07.830 align:start position:0% rtos has<01:14:06.640> to<01:14:06.800> be 01:14:07.830 --> 01:14:07.840 align:start position:0% has to be 01:14:07.840 --> 01:14:11.110 align:start position:0% has to be founded<01:14:08.480> on<01:14:08.800> technical<01:14:09.360> analysis 01:14:11.110 --> 01:14:11.120 align:start position:0% founded on technical analysis 01:14:11.120 --> 01:14:12.709 align:start position:0% founded on technical analysis studies<01:14:11.600> like<01:14:11.840> this 01:14:12.709 --> 01:14:12.719 align:start position:0% studies like this 01:14:12.719 --> 01:14:15.030 align:start position:0% studies like this are<01:14:12.960> rooted<01:14:13.440> in<01:14:13.600> technical<01:14:14.080> analysis<01:14:14.800> and 01:14:15.030 --> 01:14:15.040 align:start position:0% are rooted in technical analysis and 01:14:15.040 --> 01:14:17.430 align:start position:0% are rooted in technical analysis and show<01:14:15.679> a<01:14:15.840> direct<01:14:16.480> tie 01:14:17.430 --> 01:14:17.440 align:start position:0% show a direct tie 01:14:17.440 --> 01:14:19.910 align:start position:0% show a direct tie between<01:14:18.159> technical<01:14:18.719> phenomena 01:14:19.910 --> 01:14:19.920 align:start position:0% between technical phenomena 01:14:19.920 --> 01:14:22.790 align:start position:0% between technical phenomena and<01:14:20.400> certain<01:14:20.800> resources<01:14:21.920> so<01:14:22.159> again<01:14:22.480> they<01:14:22.640> are 01:14:22.790 --> 01:14:22.800 align:start position:0% and certain resources so again they are 01:14:22.800 --> 01:14:24.950 align:start position:0% and certain resources so again they are rooted<01:14:23.280> in<01:14:23.520> science<01:14:24.080> not<01:14:24.239> arbitrary<01:14:24.880> and 01:14:24.950 --> 01:14:24.960 align:start position:0% rooted in science not arbitrary and 01:14:24.960 --> 01:14:26.149 align:start position:0% rooted in science not arbitrary and capricious 01:14:26.149 --> 01:14:26.159 align:start position:0% capricious 01:14:26.159 --> 01:14:29.430 align:start position:0% capricious not<01:14:26.560> you<01:14:26.719> know<01:14:27.120> uh<01:14:28.239> picking<01:14:28.640> one<01:14:28.880> resource 01:14:29.430 --> 01:14:29.440 align:start position:0% not you know uh picking one resource 01:14:29.440 --> 01:14:31.910 align:start position:0% not you know uh picking one resource over<01:14:29.600> another<01:14:30.000> it's<01:14:30.159> just<01:14:30.320> like<01:14:30.560> can<01:14:30.800> you 01:14:31.910 --> 01:14:31.920 align:start position:0% over another it's just like can you 01:14:31.920 --> 01:14:34.630 align:start position:0% over another it's just like can you can<01:14:32.080> you<01:14:32.640> solve<01:14:32.960> for<01:14:33.199> this<01:14:33.920> and<01:14:34.080> if<01:14:34.239> not<01:14:34.400> we've 01:14:34.630 --> 01:14:34.640 align:start position:0% can you solve for this and if not we've 01:14:34.640 --> 01:14:36.149 align:start position:0% can you solve for this and if not we've got<01:14:34.719> to<01:14:34.880> pay<01:14:35.120> for<01:14:35.360> it<01:14:35.600> and<01:14:35.760> we've<01:14:35.920> got<01:14:36.000> to 01:14:36.149 --> 01:14:36.159 align:start position:0% got to pay for it and we've got to 01:14:36.159 --> 01:14:38.550 align:start position:0% got to pay for it and we've got to assign<01:14:36.560> costs<01:14:36.880> accordingly<01:14:37.520> but<01:14:37.679> everybody's 01:14:38.550 --> 01:14:38.560 align:start position:0% assign costs accordingly but everybody's 01:14:38.560 --> 01:14:40.149 align:start position:0% assign costs accordingly but everybody's you<01:14:38.719> know<01:14:38.880> on<01:14:38.960> a<01:14:39.040> cost<01:14:39.280> causation<01:14:39.679> basis 01:14:40.149 --> 01:14:40.159 align:start position:0% you know on a cost causation basis 01:14:40.159 --> 01:14:41.750 align:start position:0% you know on a cost causation basis everybody<01:14:40.640> takes<01:14:40.880> a<01:14:40.960> bite 01:14:41.750 --> 01:14:41.760 align:start position:0% everybody takes a bite 01:14:41.760 --> 01:14:44.390 align:start position:0% everybody takes a bite of<01:14:41.920> cost<01:14:42.719> it's<01:14:42.880> just<01:14:43.280> how<01:14:43.520> are<01:14:43.679> those<01:14:43.920> ratios 01:14:44.390 --> 01:14:44.400 align:start position:0% of cost it's just how are those ratios 01:14:44.400 --> 01:14:46.950 align:start position:0% of cost it's just how are those ratios assigned<01:14:45.199> i<01:14:45.360> believe<01:14:46.000> in<01:14:46.159> the<01:14:46.480> in<01:14:46.640> the<01:14:46.719> event 01:14:46.950 --> 01:14:46.960 align:start position:0% assigned i believe in the in the event 01:14:46.960 --> 01:14:48.390 align:start position:0% assigned i believe in the in the event of<01:14:47.120> ecrs 01:14:48.390 --> 01:14:48.400 align:start position:0% of ecrs 01:14:48.400 --> 01:14:50.790 align:start position:0% of ecrs it<01:14:48.640> directly<01:14:49.199> ties<01:14:49.520> to<01:14:49.679> the<01:14:49.760> statute<01:14:50.480> i<01:14:50.560> mean 01:14:50.790 --> 01:14:50.800 align:start position:0% it directly ties to the statute i mean 01:14:50.800 --> 01:14:52.950 align:start position:0% it directly ties to the statute i mean it<01:14:50.960> fits 01:14:52.950 --> 01:14:52.960 align:start position:0% it fits 01:14:52.960 --> 01:14:54.229 align:start position:0% it fits it's<01:14:53.280> it's 01:14:54.229 --> 01:14:54.239 align:start position:0% it's it's 01:14:54.239 --> 01:14:57.510 align:start position:0% it's it's tied<01:14:54.480> to<01:14:54.560> the<01:14:54.719> statute<01:14:55.440> agreed 01:14:57.510 --> 01:14:57.520 align:start position:0% tied to the statute agreed 01:14:57.520 --> 01:14:59.270 align:start position:0% tied to the statute agreed are<01:14:57.760> the<01:14:57.840> thoughts 01:14:59.270 --> 01:14:59.280 align:start position:0% are the thoughts 01:14:59.280 --> 01:15:01.030 align:start position:0% are the thoughts i<01:14:59.360> disagree<01:14:59.840> with<01:14:59.840> statute<01:15:00.400> all<01:15:00.480> right<01:15:00.880> what 01:15:01.030 --> 01:15:01.040 align:start position:0% i disagree with statute all right what 01:15:01.040 --> 01:15:03.270 align:start position:0% i disagree with statute all right what do<01:15:01.120> you<01:15:01.199> mean<01:15:01.360> by<01:15:01.520> tied<01:15:01.679> to<01:15:01.840> the<01:15:01.920> statute 01:15:03.270 --> 01:15:03.280 align:start position:0% do you mean by tied to the statute 01:15:03.280 --> 01:15:04.149 align:start position:0% do you mean by tied to the statute um 01:15:04.149 --> 01:15:04.159 align:start position:0% um 01:15:04.159 --> 01:15:06.709 align:start position:0% um it<01:15:04.320> is<01:15:04.640> it<01:15:04.880> is<01:15:05.360> one<01:15:05.600> we<01:15:05.920> are<01:15:06.080> reviewing<01:15:06.640> and 01:15:06.709 --> 01:15:06.719 align:start position:0% it is it is one we are reviewing and 01:15:06.719 --> 01:15:09.430 align:start position:0% it is it is one we are reviewing and developing<01:15:07.280> ancillary<01:15:07.760> services<01:15:08.719> to<01:15:09.040> ensure 01:15:09.430 --> 01:15:09.440 align:start position:0% developing ancillary services to ensure 01:15:09.440 --> 01:15:12.070 align:start position:0% developing ancillary services to ensure enough<01:15:09.760> dispatch<01:15:10.239> ability<01:15:10.640> on<01:15:10.719> the<01:15:10.880> system 01:15:12.070 --> 01:15:12.080 align:start position:0% enough dispatch ability on the system 01:15:12.080 --> 01:15:15.110 align:start position:0% enough dispatch ability on the system to<01:15:12.320> ensure<01:15:12.640> reliability<01:15:13.840> okay 01:15:15.110 --> 01:15:15.120 align:start position:0% to ensure reliability okay 01:15:15.120 --> 01:15:17.110 align:start position:0% to ensure reliability okay tied<01:15:15.280> to<01:15:15.520> study 01:15:17.110 --> 01:15:17.120 align:start position:0% tied to study 01:15:17.120 --> 01:15:19.669 align:start position:0% tied to study and<01:15:17.280> then<01:15:17.679> we<01:15:18.000> are<01:15:18.400> assigning<01:15:19.040> costs<01:15:19.520> for 01:15:19.669 --> 01:15:19.679 align:start position:0% and then we are assigning costs for 01:15:19.679 --> 01:15:21.750 align:start position:0% and then we are assigning costs for those<01:15:19.920> ancillary<01:15:20.400> services<01:15:21.199> on<01:15:21.360> a<01:15:21.520> cost 01:15:21.750 --> 01:15:21.760 align:start position:0% those ancillary services on a cost 01:15:21.760 --> 01:15:23.910 align:start position:0% those ancillary services on a cost causation<01:15:22.400> considering<01:15:23.440> assigning 01:15:23.910 --> 01:15:23.920 align:start position:0% causation considering assigning 01:15:23.920 --> 01:15:25.910 align:start position:0% causation considering assigning ancillary<01:15:24.320> service 01:15:25.910 --> 01:15:25.920 align:start position:0% ancillary service 01:15:25.920 --> 01:15:29.669 align:start position:0% ancillary service costs<01:15:26.719> on<01:15:26.880> a<01:15:26.960> cost<01:15:27.199> causation<01:15:27.760> basis 01:15:29.669 --> 01:15:29.679 align:start position:0% costs on a cost causation basis 01:15:29.679 --> 01:15:31.030 align:start position:0% costs on a cost causation basis and<01:15:29.840> a<01:15:29.920> non-discriminatory<01:15:30.719> base<01:15:30.960> a 01:15:31.030 --> 01:15:31.040 align:start position:0% and a non-discriminatory base a 01:15:31.040 --> 01:15:33.189 align:start position:0% and a non-discriminatory base a non-discriminatory<01:15:31.760> basis<01:15:32.159> but<01:15:32.640> technically 01:15:33.189 --> 01:15:33.199 align:start position:0% non-discriminatory basis but technically 01:15:33.199 --> 01:15:35.270 align:start position:0% non-discriminatory basis but technically non-discriminatory<01:15:34.159> if<01:15:34.239> they<01:15:34.400> can't 01:15:35.270 --> 01:15:35.280 align:start position:0% non-discriminatory if they can't 01:15:35.280 --> 01:15:37.830 align:start position:0% non-discriminatory if they can't provide<01:15:36.000> inertial<01:15:36.400> support<01:15:36.800> voltage<01:15:37.120> support 01:15:37.830 --> 01:15:37.840 align:start position:0% provide inertial support voltage support 01:15:37.840 --> 01:15:40.310 align:start position:0% provide inertial support voltage support and<01:15:38.000> they<01:15:38.159> provide<01:15:38.719> a<01:15:38.960> wave<01:15:39.440> of<01:15:40.000> falling 01:15:40.310 --> 01:15:40.320 align:start position:0% and they provide a wave of falling 01:15:40.320 --> 01:15:42.470 align:start position:0% and they provide a wave of falling voltage<01:15:40.880> at<01:15:41.199> uh<01:15:41.520> dependable<01:15:42.000> times<01:15:42.320> of<01:15:42.400> the 01:15:42.470 --> 01:15:42.480 align:start position:0% voltage at uh dependable times of the 01:15:42.480 --> 01:15:45.270 align:start position:0% voltage at uh dependable times of the day<01:15:43.199> that<01:15:43.520> is<01:15:43.760> a<01:15:43.920> reliability<01:15:44.640> constraint 01:15:45.270 --> 01:15:45.280 align:start position:0% day that is a reliability constraint 01:15:45.280 --> 01:15:47.189 align:start position:0% day that is a reliability constraint that<01:15:45.520> state<01:15:46.080> statute<01:15:46.560> requires<01:15:46.960> us<01:15:47.040> to 01:15:47.189 --> 01:15:47.199 align:start position:0% that state statute requires us to 01:15:47.199 --> 01:15:49.990 align:start position:0% that state statute requires us to address<01:15:47.520> on<01:15:47.600> a<01:15:47.679> cost<01:15:47.920> causation<01:15:48.400> basis 01:15:49.990 --> 01:15:50.000 align:start position:0% address on a cost causation basis 01:15:50.000 --> 01:15:52.390 align:start position:0% address on a cost causation basis so<01:15:50.239> i<01:15:50.400> i<01:15:50.960> somewhat<01:15:51.280> disagree<01:15:51.679> but<01:15:51.920> i<01:15:52.080> think<01:15:52.320> we 01:15:52.390 --> 01:15:52.400 align:start position:0% so i i somewhat disagree but i think we 01:15:52.400 --> 01:15:54.950 align:start position:0% so i i somewhat disagree but i think we need<01:15:52.640> to<01:15:52.960> er<01:15:53.360> this<01:15:53.600> is<01:15:53.760> a<01:15:53.920> great<01:15:54.320> discussion 01:15:54.950 --> 01:15:54.960 align:start position:0% need to er this is a great discussion 01:15:54.960 --> 01:15:57.110 align:start position:0% need to er this is a great discussion for<01:15:55.600> deep<01:15:55.840> discussion 01:15:57.110 --> 01:15:57.120 align:start position:0% for deep discussion 01:15:57.120 --> 01:15:59.030 align:start position:0% for deep discussion that's<01:15:57.280> what<01:15:57.440> we're<01:15:57.600> here<01:15:57.840> i<01:15:58.000> am 01:15:59.030 --> 01:15:59.040 align:start position:0% that's what we're here i am 01:15:59.040 --> 01:16:01.910 align:start position:0% that's what we're here i am um 01:16:01.910 --> 01:16:01.920 align:start position:0% 01:16:01.920 --> 01:16:04.310 align:start position:0% the<01:16:02.080> way<01:16:02.320> that<01:16:02.480> i<01:16:02.719> see<01:16:03.360> these<01:16:03.600> resources<01:16:04.159> on 01:16:04.310 --> 01:16:04.320 align:start position:0% the way that i see these resources on 01:16:04.320 --> 01:16:07.030 align:start position:0% the way that i see these resources on the<01:16:04.400> system<01:16:05.040> is<01:16:05.920> and<01:16:06.239> if<01:16:06.320> you're<01:16:06.719> if<01:16:06.880> we're 01:16:07.030 --> 01:16:07.040 align:start position:0% the system is and if you're if we're 01:16:07.040 --> 01:16:09.110 align:start position:0% the system is and if you're if we're saying<01:16:07.280> about<01:16:07.520> this<01:16:08.000> specifically<01:16:08.719> wind<01:16:08.960> and 01:16:09.110 --> 01:16:09.120 align:start position:0% saying about this specifically wind and 01:16:09.120 --> 01:16:11.830 align:start position:0% saying about this specifically wind and solar<01:16:09.760> so<01:16:10.159> so<01:16:10.640> intermittent<01:16:11.199> resources 01:16:11.830 --> 01:16:11.840 align:start position:0% solar so so intermittent resources 01:16:11.840 --> 01:16:13.430 align:start position:0% solar so so intermittent resources they're<01:16:12.000> not<01:16:12.159> getting<01:16:12.480> paid 01:16:13.430 --> 01:16:13.440 align:start position:0% they're not getting paid 01:16:13.440 --> 01:16:14.470 align:start position:0% they're not getting paid to<01:16:13.600> be 01:16:14.470 --> 01:16:14.480 align:start position:0% to be 01:16:14.480 --> 01:16:17.030 align:start position:0% to be around<01:16:14.880> 24<01:16:15.360> 7. 01:16:17.030 --> 01:16:17.040 align:start position:0% around 24 7. 01:16:17.040 --> 01:16:20.790 align:start position:0% around 24 7. um<01:16:17.760> they<01:16:18.000> they<01:16:18.239> are<01:16:18.320> getting<01:16:18.640> paid<01:16:18.880> to<01:16:18.960> provide 01:16:20.790 --> 01:16:20.800 align:start position:0% um they they are getting paid to provide 01:16:20.800 --> 01:16:22.790 align:start position:0% um they they are getting paid to provide they<01:16:21.040> are<01:16:21.360> yeah<01:16:21.520> let's<01:16:21.840> say<01:16:22.000> they<01:16:22.159> are<01:16:22.400> oh<01:16:22.560> one 01:16:22.790 --> 01:16:22.800 align:start position:0% they are yeah let's say they are oh one 01:16:22.800 --> 01:16:23.990 align:start position:0% they are yeah let's say they are oh one is<01:16:22.960> wind<01:16:23.199> is 01:16:23.990 --> 01:16:24.000 align:start position:0% is wind is 01:16:24.000 --> 01:16:26.070 align:start position:0% is wind is getting<01:16:24.320> paid<01:16:24.640> to<01:16:24.800> be<01:16:25.120> they're<01:16:25.360> getting<01:16:25.600> paid 01:16:26.070 --> 01:16:26.080 align:start position:0% getting paid to be they're getting paid 01:16:26.080 --> 01:16:27.590 align:start position:0% getting paid to be they're getting paid production<01:16:26.560> tax<01:16:26.880> credit<01:16:27.120> based<01:16:27.440> on 01:16:27.590 --> 01:16:27.600 align:start position:0% production tax credit based on 01:16:27.600 --> 01:16:28.870 align:start position:0% production tax credit based on production<01:16:28.159> so 01:16:28.870 --> 01:16:28.880 align:start position:0% production so 01:16:28.880 --> 01:16:30.950 align:start position:0% production so when<01:16:29.040> they<01:16:29.199> don't<01:16:29.600> so<01:16:29.920> when<01:16:30.080> they<01:16:30.239> don't<01:16:30.560> run 01:16:30.950 --> 01:16:30.960 align:start position:0% when they don't so when they don't run 01:16:30.960 --> 01:16:32.950 align:start position:0% when they don't so when they don't run at<01:16:31.199> noon<01:16:32.000> therefore<01:16:32.560> they're<01:16:32.640> getting 01:16:32.950 --> 01:16:32.960 align:start position:0% at noon therefore they're getting 01:16:32.960 --> 01:16:34.390 align:start position:0% at noon therefore they're getting nothing<01:16:33.360> tax<01:16:33.679> credit<01:16:34.000> they're<01:16:34.159> getting 01:16:34.390 --> 01:16:34.400 align:start position:0% nothing tax credit they're getting 01:16:34.400 --> 01:16:35.910 align:start position:0% nothing tax credit they're getting nothing<01:16:34.800> that's<01:16:35.040> right 01:16:35.910 --> 01:16:35.920 align:start position:0% nothing that's right 01:16:35.920 --> 01:16:39.910 align:start position:0% nothing that's right and<01:16:36.560> um 01:16:39.910 --> 01:16:39.920 align:start position:0% 01:16:39.920 --> 01:16:41.910 align:start position:0% again<01:16:40.159> the<01:16:40.320> way<01:16:40.480> that<01:16:40.719> i<01:16:40.960> see<01:16:41.120> this<01:16:41.360> system<01:16:41.760> is 01:16:41.910 --> 01:16:41.920 align:start position:0% again the way that i see this system is 01:16:41.920 --> 01:16:44.390 align:start position:0% again the way that i see this system is a<01:16:42.080> megawatt<01:16:42.560> is<01:16:42.640> a<01:16:42.719> megawatt 01:16:44.390 --> 01:16:44.400 align:start position:0% a megawatt is a megawatt 01:16:44.400 --> 01:16:48.310 align:start position:0% a megawatt is a megawatt and<01:16:44.960> that<01:16:45.520> they're<01:16:45.840> all<01:16:46.159> equal 01:16:48.310 --> 01:16:48.320 align:start position:0% and that they're all equal 01:16:48.320 --> 01:16:51.750 align:start position:0% and that they're all equal they<01:16:48.640> all<01:16:49.280> serve<01:16:49.600> the<01:16:49.760> exact<01:16:50.480> same 01:16:51.750 --> 01:16:51.760 align:start position:0% they all serve the exact same 01:16:51.760 --> 01:16:52.950 align:start position:0% they all serve the exact same um 01:16:52.950 --> 01:16:52.960 align:start position:0% um 01:16:52.960 --> 01:16:55.189 align:start position:0% um issue<01:16:53.360> which<01:16:53.600> is<01:16:53.760> to<01:16:53.920> provide 01:16:55.189 --> 01:16:55.199 align:start position:0% issue which is to provide 01:16:55.199 --> 01:16:57.590 align:start position:0% issue which is to provide electricity<01:16:55.920> for<01:16:56.080> our<01:16:56.239> consumers 01:16:57.590 --> 01:16:57.600 align:start position:0% electricity for our consumers 01:16:57.600 --> 01:17:00.550 align:start position:0% electricity for our consumers and<01:16:57.920> we<01:16:58.159> have<01:16:58.400> never<01:16:59.040> in<01:16:59.120> this<01:16:59.360> system 01:17:00.550 --> 01:17:00.560 align:start position:0% and we have never in this system 01:17:00.560 --> 01:17:02.870 align:start position:0% and we have never in this system in<01:17:00.719> urcot<01:17:01.360> ever 01:17:02.870 --> 01:17:02.880 align:start position:0% in urcot ever 01:17:02.880 --> 01:17:06.550 align:start position:0% in urcot ever just<01:17:03.199> allocated<01:17:03.920> one<01:17:04.560> cost<01:17:05.360> to<01:17:05.679> one<01:17:06.000> resource 01:17:06.550 --> 01:17:06.560 align:start position:0% just allocated one cost to one resource 01:17:06.560 --> 01:17:07.430 align:start position:0% just allocated one cost to one resource type 01:17:07.430 --> 01:17:07.440 align:start position:0% type 01:17:07.440 --> 01:17:09.110 align:start position:0% type that's<01:17:07.840> in<01:17:08.000> my<01:17:08.159> opinion<01:17:08.480> that's<01:17:08.560> a<01:17:08.640> wholesale 01:17:09.110 --> 01:17:09.120 align:start position:0% that's in my opinion that's a wholesale 01:17:09.120 --> 01:17:10.310 align:start position:0% that's in my opinion that's a wholesale change<01:17:09.520> we've<01:17:09.679> never<01:17:09.920> done<01:17:10.080> it<01:17:10.239> on 01:17:10.310 --> 01:17:10.320 align:start position:0% change we've never done it on 01:17:10.320 --> 01:17:11.990 align:start position:0% change we've never done it on transmission<01:17:10.960> causation<01:17:11.440> wouldn't<01:17:11.679> allow 01:17:11.990 --> 01:17:12.000 align:start position:0% transmission causation wouldn't allow 01:17:12.000 --> 01:17:13.990 align:start position:0% transmission causation wouldn't allow for<01:17:12.159> that<01:17:12.400> either<01:17:12.800> commissioner<01:17:13.679> under<01:17:13.840> the 01:17:13.990 --> 01:17:14.000 align:start position:0% for that either commissioner under the 01:17:14.000 --> 01:17:17.270 align:start position:0% for that either commissioner under the statute<01:17:14.480> and<01:17:15.120> the<01:17:15.280> statute<01:17:16.080> as<01:17:16.320> i<01:17:16.719> and<01:17:16.800> we<01:17:16.960> can 01:17:17.270 --> 01:17:17.280 align:start position:0% statute and the statute as i and we can 01:17:17.280 --> 01:17:19.350 align:start position:0% statute and the statute as i and we can pull<01:17:17.520> folks<01:17:18.000> who<01:17:18.239> are<01:17:18.480> uh<01:17:18.800> instrumental 01:17:19.350 --> 01:17:19.360 align:start position:0% pull folks who are uh instrumental 01:17:19.360 --> 01:17:21.669 align:start position:0% pull folks who are uh instrumental advising<01:17:19.760> on<01:17:19.840> the<01:17:19.920> crafting<01:17:20.239> the<01:17:20.400> statute 01:17:21.669 --> 01:17:21.679 align:start position:0% advising on the crafting the statute 01:17:21.679 --> 01:17:23.590 align:start position:0% advising on the crafting the statute it<01:17:22.000> it<01:17:22.080> doesn't<01:17:22.320> get<01:17:22.560> assigned<01:17:22.960> to<01:17:23.120> one 01:17:23.590 --> 01:17:23.600 align:start position:0% it it doesn't get assigned to one 01:17:23.600 --> 01:17:24.709 align:start position:0% it it doesn't get assigned to one resource 01:17:24.709 --> 01:17:24.719 align:start position:0% resource 01:17:24.719 --> 01:17:26.630 align:start position:0% resource it<01:17:24.880> is<01:17:25.040> proportionately<01:17:25.840> assigned<01:17:26.400> you<01:17:26.480> know 01:17:26.630 --> 01:17:26.640 align:start position:0% it is proportionately assigned you know 01:17:26.640 --> 01:17:28.070 align:start position:0% it is proportionately assigned you know that<01:17:26.800> that<01:17:26.960> was<01:17:27.120> the<01:17:27.199> beauty<01:17:27.600> of<01:17:27.679> the<01:17:27.920> the 01:17:28.070 --> 01:17:28.080 align:start position:0% that that was the beauty of the the 01:17:28.080 --> 01:17:29.189 align:start position:0% that that was the beauty of the the statutory<01:17:28.560> development<01:17:29.040> and<01:17:29.120> the 01:17:29.189 --> 01:17:29.199 align:start position:0% statutory development and the 01:17:29.199 --> 01:17:31.510 align:start position:0% statutory development and the negotiations<01:17:30.480> in<01:17:30.560> the<01:17:30.640> legislature<01:17:31.280> as<01:17:31.440> i 01:17:31.510 --> 01:17:31.520 align:start position:0% negotiations in the legislature as i 01:17:31.520 --> 01:17:33.270 align:start position:0% negotiations in the legislature as i understood<01:17:31.920> them<01:17:32.159> at<01:17:32.239> the<01:17:32.320> time 01:17:33.270 --> 01:17:33.280 align:start position:0% understood them at the time 01:17:33.280 --> 01:17:34.470 align:start position:0% understood them at the time and<01:17:33.440> do<01:17:33.520> you<01:17:33.600> know<01:17:33.679> who<01:17:33.840> i<01:17:33.920> think<01:17:34.159> is<01:17:34.320> going<01:17:34.400> to 01:17:34.470 --> 01:17:34.480 align:start position:0% and do you know who i think is going to 01:17:34.480 --> 01:17:38.470 align:start position:0% and do you know who i think is going to be<01:17:34.560> the<01:17:34.640> big<01:17:34.880> loser<01:17:35.360> in<01:17:35.520> that<01:17:36.239> consumers<01:17:36.960> gas 01:17:38.470 --> 01:17:38.480 align:start position:0% be the big loser in that consumers gas 01:17:38.480 --> 01:17:40.390 align:start position:0% be the big loser in that consumers gas gas-fired<01:17:39.040> power<01:17:39.360> plants<01:17:39.679> because<01:17:40.000> when<01:17:40.159> they 01:17:40.390 --> 01:17:40.400 align:start position:0% gas-fired power plants because when they 01:17:40.400 --> 01:17:43.189 align:start position:0% gas-fired power plants because when they trip<01:17:40.640> offline<01:17:41.440> and<01:17:41.600> they<01:17:41.840> cause<01:17:42.159> a<01:17:42.320> problem 01:17:43.189 --> 01:17:43.199 align:start position:0% trip offline and they cause a problem 01:17:43.199 --> 01:17:44.709 align:start position:0% trip offline and they cause a problem during<01:17:43.440> the<01:17:43.520> middle<01:17:43.760> of<01:17:43.840> the<01:17:44.000> day<01:17:44.239> when<01:17:44.400> costs 01:17:44.709 --> 01:17:44.719 align:start position:0% during the middle of the day when costs 01:17:44.719 --> 01:17:46.070 align:start position:0% during the middle of the day when costs are<01:17:44.800> the<01:17:44.960> highest 01:17:46.070 --> 01:17:46.080 align:start position:0% are the highest 01:17:46.080 --> 01:17:47.590 align:start position:0% are the highest they're<01:17:46.320> going<01:17:46.400> to<01:17:46.480> pay<01:17:46.640> the<01:17:46.719> biggest<01:17:47.040> penalty 01:17:47.590 --> 01:17:47.600 align:start position:0% they're going to pay the biggest penalty 01:17:47.600 --> 01:17:49.590 align:start position:0% they're going to pay the biggest penalty they<01:17:47.679> will<01:17:47.920> pay<01:17:48.000> a<01:17:48.080> penalty<01:17:48.400> yes<01:17:48.560> sir<01:17:49.199> and<01:17:49.360> that 01:17:49.590 --> 01:17:49.600 align:start position:0% they will pay a penalty yes sir and that 01:17:49.600 --> 01:17:53.990 align:start position:0% they will pay a penalty yes sir and that will<01:17:49.760> be<01:17:50.320> the<01:17:50.480> end<01:17:50.719> of<01:17:50.880> gas<01:17:51.199> on<01:17:51.280> the<01:17:51.440> system 01:17:53.990 --> 01:17:54.000 align:start position:0% 01:17:54.000 --> 01:17:55.189 align:start position:0% you'll<01:17:54.239> pay<01:17:54.400> a<01:17:54.480> penalty<01:17:54.800> under<01:17:54.960> what 01:17:55.189 --> 01:17:55.199 align:start position:0% you'll pay a penalty under what 01:17:55.199 --> 01:17:57.750 align:start position:0% you'll pay a penalty under what framework<01:17:56.000> contracts<01:17:56.480> cost<01:17:56.719> causation<01:17:57.600> well 01:17:57.750 --> 01:17:57.760 align:start position:0% framework contracts cost causation well 01:17:57.760 --> 01:17:59.750 align:start position:0% framework contracts cost causation well they<01:17:57.840> already<01:17:58.080> pay<01:17:58.239> a<01:17:58.320> penalty<01:17:58.880> through<01:17:59.040> their 01:17:59.750 --> 01:17:59.760 align:start position:0% they already pay a penalty through their 01:17:59.760 --> 01:18:02.390 align:start position:0% they already pay a penalty through their obligations<01:18:00.400> if<01:18:00.560> they've 01:18:02.390 --> 01:18:02.400 align:start position:0% obligations if they've 01:18:02.400 --> 01:18:03.430 align:start position:0% obligations if they've i<01:18:02.480> mean<01:18:02.560> they<01:18:02.719> pay<01:18:02.960> if<01:18:03.120> they've<01:18:03.280> got<01:18:03.360> to 01:18:03.430 --> 01:18:03.440 align:start position:0% i mean they pay if they've got to 01:18:03.440 --> 01:18:05.510 align:start position:0% i mean they pay if they've got to replace<01:18:03.840> that<01:18:04.000> megawatt<01:18:04.719> and<01:18:04.880> the<01:18:04.960> spot<01:18:05.280> price 01:18:05.510 --> 01:18:05.520 align:start position:0% replace that megawatt and the spot price 01:18:05.520 --> 01:18:06.950 align:start position:0% replace that megawatt and the spot price and<01:18:05.600> the<01:18:05.760> scarcity<01:18:06.159> event<01:18:06.400> they<01:18:06.560> pay<01:18:06.719> a<01:18:06.800> big 01:18:06.950 --> 01:18:06.960 align:start position:0% and the scarcity event they pay a big 01:18:06.960 --> 01:18:09.110 align:start position:0% and the scarcity event they pay a big penalty<01:18:07.440> which<01:18:07.600> is<01:18:07.920> what<01:18:08.560> it's<01:18:08.719> equally 01:18:09.110 --> 01:18:09.120 align:start position:0% penalty which is what it's equally 01:18:09.120 --> 01:18:10.870 align:start position:0% penalty which is what it's equally shared 01:18:10.870 --> 01:18:10.880 align:start position:0% shared 01:18:10.880 --> 01:18:14.630 align:start position:0% shared i<01:18:10.960> mean<01:18:11.120> we'll<01:18:11.360> see 01:18:14.630 --> 01:18:14.640 align:start position:0% 01:18:14.640 --> 01:18:17.350 align:start position:0% i<01:18:14.800> hear<01:18:14.960> you 01:18:17.350 --> 01:18:17.360 align:start position:0% 01:18:17.360 --> 01:18:21.270 align:start position:0% the<01:18:17.600> um 01:18:21.270 --> 01:18:21.280 align:start position:0% 01:18:21.280 --> 01:18:23.110 align:start position:0% the 01:18:23.110 --> 01:18:23.120 align:start position:0% the 01:18:23.120 --> 01:18:24.950 align:start position:0% the and<01:18:23.199> by<01:18:23.360> the<01:18:23.440> way<01:18:23.920> i<01:18:24.000> don't<01:18:24.239> want<01:18:24.560> this<01:18:24.719> to<01:18:24.880> be 01:18:24.950 --> 01:18:24.960 align:start position:0% and by the way i don't want this to be 01:18:24.960 --> 01:18:26.950 align:start position:0% and by the way i don't want this to be the<01:18:25.040> end<01:18:25.280> of<01:18:25.360> gas<01:18:25.600> on<01:18:25.760> our<01:18:25.920> system 01:18:26.950 --> 01:18:26.960 align:start position:0% the end of gas on our system 01:18:26.960 --> 01:18:29.830 align:start position:0% the end of gas on our system i<01:18:27.360> want<01:18:28.000> gas<01:18:28.400> on<01:18:28.480> this<01:18:28.719> system<01:18:29.440> i'm<01:18:29.600> pretty 01:18:29.830 --> 01:18:29.840 align:start position:0% i want gas on this system i'm pretty 01:18:29.840 --> 01:18:31.350 align:start position:0% i want gas on this system i'm pretty sure<01:18:30.000> the<01:18:30.159> end<01:18:30.320> of<01:18:30.400> gas<01:18:30.640> on<01:18:30.800> this<01:18:30.880> system<01:18:31.199> would 01:18:31.350 --> 01:18:31.360 align:start position:0% sure the end of gas on this system would 01:18:31.360 --> 01:18:34.310 align:start position:0% sure the end of gas on this system would be<01:18:31.440> the<01:18:31.520> end<01:18:31.679> of<01:18:31.760> the<01:18:31.840> system 01:18:34.310 --> 01:18:34.320 align:start position:0% 01:18:34.320 --> 01:18:38.830 align:start position:0% or<01:18:34.480> at<01:18:34.560> least<01:18:34.800> in<01:18:34.960> the<01:18:35.040> near<01:18:35.280> future 01:18:38.830 --> 01:18:38.840 align:start position:0% 01:18:38.840 --> 01:18:43.510 align:start position:0% i'll<01:18:39.920> provide<01:18:40.320> a<01:18:40.719> counterpoint<01:18:41.360> in<01:18:41.520> the<01:18:42.080> um 01:18:43.510 --> 01:18:43.520 align:start position:0% i'll provide a counterpoint in the um 01:18:43.520 --> 01:18:46.550 align:start position:0% i'll provide a counterpoint in the um in<01:18:43.840> a<01:18:44.000> more<01:18:44.400> a 01:18:46.550 --> 01:18:46.560 align:start position:0% in a more a 01:18:46.560 --> 01:18:48.630 align:start position:0% in a more a picture<01:18:46.880> book<01:18:47.120> kind<01:18:47.280> of<01:18:47.360> way 01:18:48.630 --> 01:18:48.640 align:start position:0% picture book kind of way 01:18:48.640 --> 01:18:51.669 align:start position:0% picture book kind of way in<01:18:48.800> the<01:18:49.120> absence<01:18:49.920> of<01:18:50.480> intermittence<01:18:51.199> just<01:18:51.440> i 01:18:51.669 --> 01:18:51.679 align:start position:0% in the absence of intermittence just i 01:18:51.679 --> 01:18:53.430 align:start position:0% in the absence of intermittence just i don't<01:18:51.760> know<01:18:51.920> go<01:18:52.080> back<01:18:52.320> to<01:18:52.640> the<01:18:52.800> hypothetical 01:18:53.430 --> 01:18:53.440 align:start position:0% don't know go back to the hypothetical 01:18:53.440 --> 01:18:54.550 align:start position:0% don't know go back to the hypothetical where 01:18:54.550 --> 01:18:54.560 align:start position:0% where 01:18:54.560 --> 01:18:55.630 align:start position:0% where go<01:18:54.719> back<01:18:54.960> to 01:18:55.630 --> 01:18:55.640 align:start position:0% go back to 01:18:55.640 --> 01:18:58.070 align:start position:0% go back to 1995<01:18:56.719> or 01:18:58.070 --> 01:18:58.080 align:start position:0% 1995 or 01:18:58.080 --> 01:19:00.390 align:start position:0% 1995 or or<01:18:58.400> there's<01:18:58.560> some<01:18:58.880> hypothetical<01:18:59.520> where<01:19:00.159> we've 01:19:00.390 --> 01:19:00.400 align:start position:0% or there's some hypothetical where we've 01:19:00.400 --> 01:19:01.750 align:start position:0% or there's some hypothetical where we've got<01:19:00.800> all 01:19:01.750 --> 01:19:01.760 align:start position:0% got all 01:19:01.760 --> 01:19:03.750 align:start position:0% got all zero<01:19:02.080> emission<01:19:02.560> nuclear<01:19:03.120> base<01:19:03.360> load<01:19:03.600> and 01:19:03.750 --> 01:19:03.760 align:start position:0% zero emission nuclear base load and 01:19:03.760 --> 01:19:05.030 align:start position:0% zero emission nuclear base load and modular<01:19:04.320> and 01:19:05.030 --> 01:19:05.040 align:start position:0% modular and 01:19:05.040 --> 01:19:08.070 align:start position:0% modular and there's<01:19:05.520> there's<01:19:06.320> no<01:19:06.840> intermittence<01:19:07.920> or 01:19:08.070 --> 01:19:08.080 align:start position:0% there's there's no intermittence or 01:19:08.080 --> 01:19:09.990 align:start position:0% there's there's no intermittence or weather<01:19:08.400> dependent<01:19:08.800> resources 01:19:09.990 --> 01:19:10.000 align:start position:0% weather dependent resources 01:19:10.000 --> 01:19:13.669 align:start position:0% weather dependent resources would<01:19:10.320> we<01:19:10.480> need<01:19:10.640> to<01:19:10.800> build<01:19:11.040> ecrs<01:19:12.080> yes<01:19:12.400> or<01:19:12.480> no 01:19:13.669 --> 01:19:13.679 align:start position:0% would we need to build ecrs yes or no 01:19:13.679 --> 01:19:15.350 align:start position:0% would we need to build ecrs yes or no it<01:19:13.920> seems<01:19:14.239> pretty<01:19:14.560> apparent<01:19:14.880> to<01:19:14.960> me<01:19:15.120> that<01:19:15.280> we 01:19:15.350 --> 01:19:15.360 align:start position:0% it seems pretty apparent to me that we 01:19:15.360 --> 01:19:17.270 align:start position:0% it seems pretty apparent to me that we wouldn't 01:19:17.270 --> 01:19:17.280 align:start position:0% wouldn't 01:19:17.280 --> 01:19:18.870 align:start position:0% wouldn't so 01:19:18.870 --> 01:19:18.880 align:start position:0% so 01:19:18.880 --> 01:19:21.030 align:start position:0% so why<01:19:19.120> do<01:19:19.199> we<01:19:19.360> need<01:19:19.520> to<01:19:19.600> build<01:19:19.920> it 01:19:21.030 --> 01:19:21.040 align:start position:0% why do we need to build it 01:19:21.040 --> 01:19:23.030 align:start position:0% why do we need to build it these<01:19:21.360> are<01:19:21.440> the<01:19:21.520> only<01:19:21.760> resources<01:19:22.320> that<01:19:22.480> can<01:19:22.719> go 01:19:23.030 --> 01:19:23.040 align:start position:0% these are the only resources that can go 01:19:23.040 --> 01:19:24.470 align:start position:0% these are the only resources that can go from 01:19:24.470 --> 01:19:24.480 align:start position:0% from 01:19:24.480 --> 01:19:26.790 align:start position:0% from can<01:19:24.719> go<01:19:24.880> to<01:19:25.120> zero<01:19:25.520> percent 01:19:26.790 --> 01:19:26.800 align:start position:0% can go to zero percent 01:19:26.800 --> 01:19:29.590 align:start position:0% can go to zero percent contributing<01:19:27.360> to<01:19:27.520> the<01:19:27.600> grid 01:19:29.590 --> 01:19:29.600 align:start position:0% contributing to the grid 01:19:29.600 --> 01:19:31.910 align:start position:0% contributing to the grid so<01:19:30.000> that's<01:19:30.480> where<01:19:30.719> the<01:19:30.800> costs<01:19:31.280> would<01:19:31.440> go<01:19:31.760> but 01:19:31.910 --> 01:19:31.920 align:start position:0% so that's where the costs would go but 01:19:31.920 --> 01:19:33.990 align:start position:0% so that's where the costs would go but but<01:19:32.159> also<01:19:32.400> to<01:19:32.560> me<01:19:32.640> it's<01:19:32.800> a<01:19:32.960> it's<01:19:33.120> a<01:19:33.199> normalizing 01:19:33.990 --> 01:19:34.000 align:start position:0% but also to me it's a it's a normalizing 01:19:34.000 --> 01:19:36.790 align:start position:0% but also to me it's a it's a normalizing process<01:19:34.560> we<01:19:34.960> we<01:19:35.199> do<01:19:35.440> this<01:19:35.760> in<01:19:35.920> order<01:19:36.159> to<01:19:36.320> allow 01:19:36.790 --> 01:19:36.800 align:start position:0% process we we do this in order to allow 01:19:36.800 --> 01:19:39.750 align:start position:0% process we we do this in order to allow more<01:19:37.199> solar<01:19:37.760> onto<01:19:38.080> the<01:19:38.239> system<01:19:39.040> and<01:19:39.199> more<01:19:39.440> wind 01:19:39.750 --> 01:19:39.760 align:start position:0% more solar onto the system and more wind 01:19:39.760 --> 01:19:41.590 align:start position:0% more solar onto the system and more wind onto<01:19:40.000> the<01:19:40.159> system<01:19:40.480> it's<01:19:40.640> a<01:19:40.800> normalizing 01:19:41.590 --> 01:19:41.600 align:start position:0% onto the system it's a normalizing 01:19:41.600 --> 01:19:44.149 align:start position:0% onto the system it's a normalizing product<01:19:42.400> it<01:19:42.560> is<01:19:42.719> to<01:19:42.880> allow<01:19:43.280> that<01:19:43.600> particular 01:19:44.149 --> 01:19:44.159 align:start position:0% product it is to allow that particular 01:19:44.159 --> 01:19:46.390 align:start position:0% product it is to allow that particular product<01:19:44.719> to<01:19:44.880> get<01:19:45.040> to<01:19:45.199> market<01:19:46.080> where<01:19:46.239> it 01:19:46.390 --> 01:19:46.400 align:start position:0% product to get to market where it 01:19:46.400 --> 01:19:49.669 align:start position:0% product to get to market where it benefits<01:19:46.880> consumers<01:19:47.440> on<01:19:47.600> there's<01:19:47.920> zero<01:19:48.400> cost 01:19:49.669 --> 01:19:49.679 align:start position:0% benefits consumers on there's zero cost 01:19:49.679 --> 01:19:53.990 align:start position:0% benefits consumers on there's zero cost and<01:19:50.159> a<01:19:50.800> carbon<01:19:51.440> neutral<01:19:52.320> whey<01:19:52.880> and 01:19:53.990 --> 01:19:54.000 align:start position:0% and a carbon neutral whey and 01:19:54.000 --> 01:19:55.030 align:start position:0% and a carbon neutral whey and so 01:19:55.030 --> 01:19:55.040 align:start position:0% so 01:19:55.040 --> 01:19:56.790 align:start position:0% so positive<01:19:55.440> scenario<01:19:56.159> and<01:19:56.320> this<01:19:56.480> is<01:19:56.560> what<01:19:56.719> i've 01:19:56.790 --> 01:19:56.800 align:start position:0% positive scenario and this is what i've 01:19:56.800 --> 01:19:58.229 align:start position:0% positive scenario and this is what i've thought<01:19:56.960> about 01:19:58.229 --> 01:19:58.239 align:start position:0% thought about 01:19:58.239 --> 01:19:59.990 align:start position:0% thought about so<01:19:58.560> in<01:19:58.719> 2024 01:19:59.990 --> 01:20:00.000 align:start position:0% so in 2024 01:20:00.000 --> 01:20:02.310 align:start position:0% so in 2024 when<01:20:00.159> we<01:20:00.320> have<01:20:00.480> 30<01:20:00.800> gigawatts<01:20:01.360> of<01:20:01.520> solar<01:20:02.080> and 01:20:02.310 --> 01:20:02.320 align:start position:0% when we have 30 gigawatts of solar and 01:20:02.320 --> 01:20:04.630 align:start position:0% when we have 30 gigawatts of solar and over<01:20:02.640> 30<01:20:02.880> gigawatts<01:20:03.440> of<01:20:03.520> wind<01:20:04.080> in<01:20:04.320> shoulder 01:20:04.630 --> 01:20:04.640 align:start position:0% over 30 gigawatts of wind in shoulder 01:20:04.640 --> 01:20:08.149 align:start position:0% over 30 gigawatts of wind in shoulder months<01:20:05.360> and<01:20:05.520> the<01:20:05.600> base<01:20:05.920> load<01:20:06.159> fleet<01:20:06.719> is<01:20:06.960> on 01:20:08.149 --> 01:20:08.159 align:start position:0% months and the base load fleet is on 01:20:08.159 --> 01:20:09.990 align:start position:0% months and the base load fleet is on planned<01:20:08.560> outage 01:20:09.990 --> 01:20:10.000 align:start position:0% planned outage 01:20:10.000 --> 01:20:13.750 align:start position:0% planned outage take<01:20:10.239> in<01:20:10.400> the<01:20:10.480> spring<01:20:11.360> or<01:20:11.679> no<01:20:12.080> taking<01:20:12.320> the<01:20:12.480> fall 01:20:13.750 --> 01:20:13.760 align:start position:0% take in the spring or no taking the fall 01:20:13.760 --> 01:20:15.669 align:start position:0% take in the spring or no taking the fall same<01:20:14.000> scenario<01:20:14.480> applies 01:20:15.669 --> 01:20:15.679 align:start position:0% same scenario applies 01:20:15.679 --> 01:20:17.110 align:start position:0% same scenario applies and 01:20:17.110 --> 01:20:17.120 align:start position:0% and 01:20:17.120 --> 01:20:18.790 align:start position:0% and normal<01:20:17.600> load 01:20:18.790 --> 01:20:18.800 align:start position:0% normal load 01:20:18.800 --> 01:20:21.430 align:start position:0% normal load peak<01:20:19.040> load<01:20:19.440> in<01:20:19.600> the<01:20:19.920> the<01:20:20.080> fall<01:20:20.560> is<01:20:20.719> what<01:20:21.280> you 01:20:21.430 --> 01:20:21.440 align:start position:0% peak load in the the fall is what you 01:20:21.440 --> 01:20:24.709 align:start position:0% peak load in the the fall is what you know<01:20:21.600> max<01:20:22.239> 50<01:20:22.880> gigs<01:20:23.600> okay<01:20:23.840> that's<01:20:24.080> a<01:20:24.159> big<01:20:24.480> load 01:20:24.709 --> 01:20:24.719 align:start position:0% know max 50 gigs okay that's a big load 01:20:24.719 --> 01:20:26.229 align:start position:0% know max 50 gigs okay that's a big load day<01:20:25.120> you<01:20:25.280> know 01:20:26.229 --> 01:20:26.239 align:start position:0% day you know 01:20:26.239 --> 01:20:28.950 align:start position:0% day you know tiac's<01:20:27.440> partners<01:20:27.920> are<01:20:28.080> humming<01:20:28.639> at<01:20:28.719> that 01:20:28.950 --> 01:20:28.960 align:start position:0% tiac's partners are humming at that 01:20:28.960 --> 01:20:30.790 align:start position:0% tiac's partners are humming at that point 01:20:30.790 --> 01:20:30.800 align:start position:0% point 01:20:30.800 --> 01:20:31.590 align:start position:0% point but 01:20:31.590 --> 01:20:31.600 align:start position:0% but 01:20:31.600 --> 01:20:34.149 align:start position:0% but the<01:20:31.760> sun<01:20:32.080> is<01:20:32.239> shining<01:20:32.719> and<01:20:33.360> solar<01:20:33.760> has<01:20:33.920> an 01:20:34.149 --> 01:20:34.159 align:start position:0% the sun is shining and solar has an 01:20:34.159 --> 01:20:35.110 align:start position:0% the sun is shining and solar has an excellent 01:20:35.110 --> 01:20:35.120 align:start position:0% excellent 01:20:35.120 --> 01:20:37.830 align:start position:0% excellent capacity<01:20:35.840> rating<01:20:36.239> i<01:20:36.320> mean<01:20:36.560> it<01:20:36.719> performs<01:20:37.520> on<01:20:37.679> a 01:20:37.830 --> 01:20:37.840 align:start position:0% capacity rating i mean it performs on a 01:20:37.840 --> 01:20:39.350 align:start position:0% capacity rating i mean it performs on a clear<01:20:38.159> day<01:20:38.560> um 01:20:39.350 --> 01:20:39.360 align:start position:0% clear day um 01:20:39.360 --> 01:20:40.550 align:start position:0% clear day um after<01:20:39.679> a 01:20:40.550 --> 01:20:40.560 align:start position:0% after a 01:20:40.560 --> 01:20:42.149 align:start position:0% after a front<01:20:40.880> is<01:20:41.040> coming<01:20:41.280> through<01:20:41.440> or<01:20:41.679> before<01:20:42.000> a 01:20:42.149 --> 01:20:42.159 align:start position:0% front is coming through or before a 01:20:42.159 --> 01:20:43.669 align:start position:0% front is coming through or before a front<01:20:42.400> is<01:20:42.480> coming<01:20:42.719> through<01:20:42.960> and<01:20:43.040> that<01:20:43.280> wind 01:20:43.669 --> 01:20:43.679 align:start position:0% front is coming through and that wind 01:20:43.679 --> 01:20:44.950 align:start position:0% front is coming through and that wind picks<01:20:44.000> up 01:20:44.950 --> 01:20:44.960 align:start position:0% picks up 01:20:44.960 --> 01:20:47.189 align:start position:0% picks up clouds<01:20:45.360> are<01:20:45.440> moved<01:20:45.679> out<01:20:45.920> clear<01:20:46.159> sky<01:20:46.480> day<01:20:46.880> wind 01:20:47.189 --> 01:20:47.199 align:start position:0% clouds are moved out clear sky day wind 01:20:47.199 --> 01:20:49.430 align:start position:0% clouds are moved out clear sky day wind is<01:20:47.280> picked<01:20:47.600> up 01:20:49.430 --> 01:20:49.440 align:start position:0% is picked up 01:20:49.440 --> 01:20:52.070 align:start position:0% is picked up any<01:20:49.840> other<01:20:50.480> base<01:20:50.800> load<01:20:51.120> or<01:20:51.280> not<01:20:51.600> base<01:20:51.840> load 01:20:52.070 --> 01:20:52.080 align:start position:0% any other base load or not base load 01:20:52.080 --> 01:20:53.750 align:start position:0% any other base load or not base load dispatchable<01:20:52.639> peakers<01:20:53.280> that<01:20:53.440> are<01:20:53.600> on<01:20:53.679> the 01:20:53.750 --> 01:20:53.760 align:start position:0% dispatchable peakers that are on the 01:20:53.760 --> 01:20:56.629 align:start position:0% dispatchable peakers that are on the system<01:20:54.159> would<01:20:54.400> be<01:20:54.719> uneconomic<01:20:55.600> to<01:20:55.760> dispatch 01:20:56.629 --> 01:20:56.639 align:start position:0% system would be uneconomic to dispatch 01:20:56.639 --> 01:20:57.430 align:start position:0% system would be uneconomic to dispatch on 01:20:57.430 --> 01:20:57.440 align:start position:0% on 01:20:57.440 --> 01:20:58.709 align:start position:0% on their<01:20:57.760> face 01:20:58.709 --> 01:20:58.719 align:start position:0% their face 01:20:58.719 --> 01:21:00.390 align:start position:0% their face at<01:20:58.880> that<01:20:59.120> time<01:20:59.600> because 01:21:00.390 --> 01:21:00.400 align:start position:0% at that time because 01:21:00.400 --> 01:21:02.390 align:start position:0% at that time because renewables<01:21:00.960> are<01:21:01.120> providing 01:21:02.390 --> 01:21:02.400 align:start position:0% renewables are providing 01:21:02.400 --> 01:21:05.270 align:start position:0% renewables are providing that<01:21:02.719> the<01:21:02.960> answer<01:21:03.679> on<01:21:03.840> an<01:21:04.000> economic<01:21:04.480> basis<01:21:05.120> on 01:21:05.270 --> 01:21:05.280 align:start position:0% that the answer on an economic basis on 01:21:05.280 --> 01:21:07.270 align:start position:0% that the answer on an economic basis on a<01:21:05.440> megawatt<01:21:05.920> is<01:21:06.000> a<01:21:06.080> megawatt<01:21:06.719> but<01:21:06.880> they're<01:21:07.040> not 01:21:07.270 --> 01:21:07.280 align:start position:0% a megawatt is a megawatt but they're not 01:21:07.280 --> 01:21:08.950 align:start position:0% a megawatt is a megawatt but they're not at<01:21:07.360> that<01:21:07.600> time<01:21:07.920> because<01:21:08.159> they<01:21:08.320> have<01:21:08.480> crowded 01:21:08.950 --> 01:21:08.960 align:start position:0% at that time because they have crowded 01:21:08.960 --> 01:21:11.669 align:start position:0% at that time because they have crowded out<01:21:09.360> the<01:21:09.520> inertial<01:21:10.000> support<01:21:10.480> voltage<01:21:10.880> support 01:21:11.669 --> 01:21:11.679 align:start position:0% out the inertial support voltage support 01:21:11.679 --> 01:21:13.350 align:start position:0% out the inertial support voltage support resources<01:21:12.239> that<01:21:12.400> can<01:21:12.560> be<01:21:12.639> there<01:21:12.800> that<01:21:13.040> allows 01:21:13.350 --> 01:21:13.360 align:start position:0% resources that can be there that allows 01:21:13.360 --> 01:21:15.350 align:start position:0% resources that can be there that allows their<01:21:13.600> product<01:21:13.920> to<01:21:14.000> get<01:21:14.159> to<01:21:14.239> market 01:21:15.350 --> 01:21:15.360 align:start position:0% their product to get to market 01:21:15.360 --> 01:21:17.590 align:start position:0% their product to get to market so<01:21:15.520> we<01:21:15.679> have<01:21:15.840> to<01:21:16.000> overcome<01:21:16.560> this<01:21:16.960> and<01:21:17.280> assign 01:21:17.590 --> 01:21:17.600 align:start position:0% so we have to overcome this and assign 01:21:17.600 --> 01:21:18.790 align:start position:0% so we have to overcome this and assign it<01:21:17.760> on<01:21:17.840> a<01:21:17.920> proportional<01:21:18.320> basis<01:21:18.560> is<01:21:18.639> my 01:21:18.790 --> 01:21:18.800 align:start position:0% it on a proportional basis is my 01:21:18.800 --> 01:21:19.750 align:start position:0% it on a proportional basis is my argument 01:21:19.750 --> 01:21:19.760 align:start position:0% argument 01:21:19.760 --> 01:21:22.550 align:start position:0% argument so<01:21:20.080> um<01:21:20.880> you<01:21:20.960> know<01:21:21.120> i<01:21:21.760> i<01:21:21.920> think<01:21:22.080> the<01:21:22.239> overall 01:21:22.550 --> 01:21:22.560 align:start position:0% so um you know i i think the overall 01:21:22.560 --> 01:21:24.870 align:start position:0% so um you know i i think the overall policy<01:21:22.960> on<01:21:23.120> cost<01:21:23.440> allocation 01:21:24.870 --> 01:21:24.880 align:start position:0% policy on cost allocation 01:21:24.880 --> 01:21:26.149 align:start position:0% policy on cost allocation we<01:21:25.040> need<01:21:25.199> to<01:21:25.280> think<01:21:25.440> about<01:21:25.679> a<01:21:25.679> little<01:21:25.840> bit<01:21:26.000> more 01:21:26.149 --> 01:21:26.159 align:start position:0% we need to think about a little bit more 01:21:26.159 --> 01:21:27.990 align:start position:0% we need to think about a little bit more i<01:21:26.239> think<01:21:26.400> i<01:21:26.560> agree<01:21:26.719> with<01:21:26.880> your<01:21:27.040> technical 01:21:27.990 --> 01:21:28.000 align:start position:0% i think i agree with your technical 01:21:28.000 --> 01:21:31.270 align:start position:0% i think i agree with your technical analysis<01:21:28.639> or<01:21:29.040> back<01:21:29.600> backup<01:21:29.920> we<01:21:30.080> need<01:21:30.239> to<01:21:30.400> have 01:21:31.270 --> 01:21:31.280 align:start position:0% analysis or back backup we need to have 01:21:31.280 --> 01:21:33.430 align:start position:0% analysis or back backup we need to have um<01:21:31.760> sp3 01:21:33.430 --> 01:21:33.440 align:start position:0% um sp3 01:21:33.440 --> 01:21:35.830 align:start position:0% um sp3 clearly<01:21:33.920> states<01:21:34.400> that<01:21:34.800> um 01:21:35.830 --> 01:21:35.840 align:start position:0% clearly states that um 01:21:35.840 --> 01:21:37.030 align:start position:0% clearly states that um there<01:21:36.000> will<01:21:36.080> be<01:21:36.239> cost<01:21:36.480> allocation<01:21:36.880> on<01:21:36.960> a 01:21:37.030 --> 01:21:37.040 align:start position:0% there will be cost allocation on a 01:21:37.040 --> 01:21:38.790 align:start position:0% there will be cost allocation on a non-discriminatory<01:21:37.840> basis 01:21:38.790 --> 01:21:38.800 align:start position:0% non-discriminatory basis 01:21:38.800 --> 01:21:41.750 align:start position:0% non-discriminatory basis and<01:21:39.360> um<01:21:39.920> i'd<01:21:40.080> like<01:21:40.239> to<01:21:40.480> understand<01:21:41.280> you<01:21:41.440> know 01:21:41.750 --> 01:21:41.760 align:start position:0% and um i'd like to understand you know 01:21:41.760 --> 01:21:44.229 align:start position:0% and um i'd like to understand you know and<01:21:42.000> this<01:21:42.239> issue's<01:21:42.719> come<01:21:42.960> up<01:21:43.120> in<01:21:43.199> the<01:21:43.360> past<01:21:43.920> on 01:21:44.229 --> 01:21:44.239 align:start position:0% and this issue's come up in the past on 01:21:44.239 --> 01:21:47.110 align:start position:0% and this issue's come up in the past on allocating<01:21:44.880> costs<01:21:45.199> to<01:21:45.440> to<01:21:45.600> renewables<01:21:46.320> and 01:21:47.110 --> 01:21:47.120 align:start position:0% allocating costs to to renewables and 01:21:47.120 --> 01:21:48.709 align:start position:0% allocating costs to to renewables and the<01:21:47.199> commission<01:21:47.679> sort<01:21:47.840> of<01:21:48.000> spun<01:21:48.239> on<01:21:48.400> it<01:21:48.480> for<01:21:48.639> a 01:21:48.709 --> 01:21:48.719 align:start position:0% the commission sort of spun on it for a 01:21:48.719 --> 01:21:50.709 align:start position:0% the commission sort of spun on it for a while<01:21:49.440> and<01:21:49.760> was<01:21:49.920> trying<01:21:50.159> to<01:21:50.239> come<01:21:50.400> up<01:21:50.480> with<01:21:50.639> a 01:21:50.709 --> 01:21:50.719 align:start position:0% while and was trying to come up with a 01:21:50.719 --> 01:21:52.950 align:start position:0% while and was trying to come up with a methodology<01:21:51.440> of<01:21:51.520> doing<01:21:51.840> so 01:21:52.950 --> 01:21:52.960 align:start position:0% methodology of doing so 01:21:52.960 --> 01:21:55.910 align:start position:0% methodology of doing so but<01:21:53.520> i'd<01:21:53.679> like<01:21:53.840> to<01:21:53.920> understand<01:21:54.239> from<01:21:54.480> ercot 01:21:55.910 --> 01:21:55.920 align:start position:0% but i'd like to understand from ercot 01:21:55.920 --> 01:21:58.070 align:start position:0% but i'd like to understand from ercot you<01:21:56.000> know<01:21:56.320> when<01:21:56.719> they<01:21:56.800> go<01:21:56.960> out<01:21:57.120> to<01:21:57.280> procure 01:21:58.070 --> 01:21:58.080 align:start position:0% you know when they go out to procure 01:21:58.080 --> 01:22:00.229 align:start position:0% you know when they go out to procure ancillary<01:21:58.639> services<01:21:59.120> today 01:22:00.229 --> 01:22:00.239 align:start position:0% ancillary services today 01:22:00.239 --> 01:22:02.709 align:start position:0% ancillary services today non-spin<01:22:00.960> regulation<01:22:01.600> reserve<01:22:02.000> service<01:22:02.480> reg 01:22:02.709 --> 01:22:02.719 align:start position:0% non-spin regulation reserve service reg 01:22:02.719 --> 01:22:04.229 align:start position:0% non-spin regulation reserve service reg up<01:22:02.880> or<01:22:02.960> down 01:22:04.229 --> 01:22:04.239 align:start position:0% up or down 01:22:04.239 --> 01:22:07.270 align:start position:0% up or down if<01:22:04.480> they<01:22:04.639> can<01:22:05.040> if<01:22:05.440> it<01:22:06.000> how<01:22:06.239> difficult<01:22:06.719> it<01:22:06.880> is<01:22:07.120> to 01:22:07.270 --> 01:22:07.280 align:start position:0% if they can if it how difficult it is to 01:22:07.280 --> 01:22:08.470 align:start position:0% if they can if it how difficult it is to see 01:22:08.470 --> 01:22:08.480 align:start position:0% see 01:22:08.480 --> 01:22:10.550 align:start position:0% see if<01:22:08.639> they're<01:22:08.880> buying<01:22:09.280> it<01:22:09.520> for<01:22:10.159> whether<01:22:10.400> they 01:22:10.550 --> 01:22:10.560 align:start position:0% if they're buying it for whether they 01:22:10.560 --> 01:22:12.709 align:start position:0% if they're buying it for whether they can<01:22:10.639> determine<01:22:11.040> what<01:22:11.199> they're<01:22:11.360> buying 01:22:12.709 --> 01:22:12.719 align:start position:0% can determine what they're buying 01:22:12.719 --> 01:22:14.550 align:start position:0% can determine what they're buying from<01:22:12.880> those<01:22:13.040> ancillary<01:22:13.520> services<01:22:13.920> the<01:22:14.080> amount 01:22:14.550 --> 01:22:14.560 align:start position:0% from those ancillary services the amount 01:22:14.560 --> 01:22:15.669 align:start position:0% from those ancillary services the amount um 01:22:15.669 --> 01:22:15.679 align:start position:0% um 01:22:15.679 --> 01:22:17.750 align:start position:0% um what<01:22:15.840> percentage<01:22:16.400> or<01:22:16.560> what<01:22:16.880> amount<01:22:17.280> is<01:22:17.600> is 01:22:17.750 --> 01:22:17.760 align:start position:0% what percentage or what amount is is 01:22:17.760 --> 01:22:18.950 align:start position:0% what percentage or what amount is is needed 01:22:18.950 --> 01:22:18.960 align:start position:0% needed 01:22:18.960 --> 01:22:21.030 align:start position:0% needed to<01:22:19.120> address<01:22:19.520> swings<01:22:19.920> and<01:22:20.000> load 01:22:21.030 --> 01:22:21.040 align:start position:0% to address swings and load 01:22:21.040 --> 01:22:23.350 align:start position:0% to address swings and load or<01:22:21.199> swings<01:22:21.520> in<01:22:21.679> renewable<01:22:22.159> generation 01:22:23.350 --> 01:22:23.360 align:start position:0% or swings in renewable generation 01:22:23.360 --> 01:22:25.110 align:start position:0% or swings in renewable generation because<01:22:23.760> ultimately 01:22:25.110 --> 01:22:25.120 align:start position:0% because ultimately 01:22:25.120 --> 01:22:26.709 align:start position:0% because ultimately we've<01:22:25.360> got<01:22:25.520> it<01:22:25.679> we've<01:22:25.840> got<01:22:25.920> to<01:22:26.159> start<01:22:26.400> thinking 01:22:26.709 --> 01:22:26.719 align:start position:0% we've got it we've got to start thinking 01:22:26.719 --> 01:22:28.709 align:start position:0% we've got it we've got to start thinking about<01:22:27.360> you<01:22:27.520> know<01:22:27.679> from<01:22:27.840> their<01:22:28.080> standpoint<01:22:28.639> is 01:22:28.709 --> 01:22:28.719 align:start position:0% about you know from their standpoint is 01:22:28.719 --> 01:22:30.790 align:start position:0% about you know from their standpoint is that<01:22:28.960> something<01:22:29.199> they<01:22:29.360> can<01:22:29.600> clearly<01:22:30.080> see<01:22:30.560> and 01:22:30.790 --> 01:22:30.800 align:start position:0% that something they can clearly see and 01:22:30.800 --> 01:22:33.189 align:start position:0% that something they can clearly see and and<01:22:30.960> if<01:22:31.199> not<01:22:31.520> then<01:22:31.840> have<01:22:32.080> some<01:22:32.239> kind<01:22:32.480> of<01:22:33.040> you 01:22:33.189 --> 01:22:33.199 align:start position:0% and if not then have some kind of you 01:22:33.199 --> 01:22:33.910 align:start position:0% and if not then have some kind of you know 01:22:33.910 --> 01:22:33.920 align:start position:0% know 01:22:33.920 --> 01:22:36.629 align:start position:0% know modeling<01:22:34.400> or<01:22:34.560> technical<01:22:35.520> analysis<01:22:36.159> done<01:22:36.400> so 01:22:36.629 --> 01:22:36.639 align:start position:0% modeling or technical analysis done so 01:22:36.639 --> 01:22:39.110 align:start position:0% modeling or technical analysis done so that<01:22:36.719> we<01:22:36.880> can<01:22:37.120> extract<01:22:38.159> how<01:22:38.400> those<01:22:38.719> how<01:22:38.960> our 01:22:39.110 --> 01:22:39.120 align:start position:0% that we can extract how those how our 01:22:39.120 --> 01:22:40.629 align:start position:0% that we can extract how those how our cod<01:22:39.360> is<01:22:39.440> procuring<01:22:39.840> those<01:22:40.080> ancillary 01:22:40.629 --> 01:22:40.639 align:start position:0% cod is procuring those ancillary 01:22:40.639 --> 01:22:42.470 align:start position:0% cod is procuring those ancillary services<01:22:41.280> and<01:22:41.520> and<01:22:41.679> if<01:22:41.760> we<01:22:41.920> are<01:22:42.080> going<01:22:42.239> to<01:22:42.320> do 01:22:42.470 --> 01:22:42.480 align:start position:0% services and and if we are going to do 01:22:42.480 --> 01:22:44.229 align:start position:0% services and and if we are going to do some<01:22:42.639> kind<01:22:42.800> of<01:22:42.960> cost<01:22:43.280> allocation<01:22:43.840> that<01:22:44.000> we're 01:22:44.229 --> 01:22:44.239 align:start position:0% some kind of cost allocation that we're 01:22:44.239 --> 01:22:46.470 align:start position:0% some kind of cost allocation that we're able<01:22:44.480> to<01:22:44.560> do<01:22:44.719> it<01:22:44.960> in 01:22:46.470 --> 01:22:46.480 align:start position:0% able to do it in 01:22:46.480 --> 01:22:48.950 align:start position:0% able to do it in in<01:22:46.639> an<01:22:46.800> equitable<01:22:47.360> way<01:22:47.760> where<01:22:48.239> you<01:22:48.320> know<01:22:48.560> we're 01:22:48.950 --> 01:22:48.960 align:start position:0% in an equitable way where you know we're 01:22:48.960 --> 01:22:51.510 align:start position:0% in an equitable way where you know we're able<01:22:49.199> to<01:22:49.360> see<01:22:49.760> why<01:22:50.159> why<01:22:50.400> ercot<01:22:50.800> is<01:22:50.880> purchasing 01:22:51.510 --> 01:22:51.520 align:start position:0% able to see why why ercot is purchasing 01:22:51.520 --> 01:22:53.270 align:start position:0% able to see why why ercot is purchasing those<01:22:51.760> ancillary<01:22:52.320> services<01:22:52.800> and<01:22:52.880> so<01:22:53.040> i<01:22:53.199> don't 01:22:53.270 --> 01:22:53.280 align:start position:0% those ancillary services and so i don't 01:22:53.280 --> 01:22:54.550 align:start position:0% those ancillary services and so i don't know<01:22:53.440> what<01:22:53.600> he<01:22:53.840> um 01:22:54.550 --> 01:22:54.560 align:start position:0% know what he um 01:22:54.560 --> 01:23:02.870 align:start position:0% know what he um if<01:22:54.719> he's<01:22:54.880> in<01:22:54.960> here 01:23:02.870 --> 01:23:02.880 align:start position:0% 01:23:02.880 --> 01:23:08.390 align:start position:0% oh<01:23:03.199> dave's<01:23:03.520> tagging<01:23:03.840> him 01:23:08.390 --> 01:23:08.400 align:start position:0% 01:23:08.400 --> 01:23:10.470 align:start position:0% i<01:23:08.480> guess<01:23:08.719> the<01:23:08.880> question<01:23:09.199> is<01:23:09.600> is<01:23:09.840> do<01:23:10.000> you<01:23:10.159> have<01:23:10.400> a 01:23:10.470 --> 01:23:10.480 align:start position:0% i guess the question is is do you have a 01:23:10.480 --> 01:23:12.550 align:start position:0% i guess the question is is do you have a methodology<01:23:11.199> today<01:23:11.679> that<01:23:11.840> would<01:23:12.000> allow<01:23:12.320> you 01:23:12.550 --> 01:23:12.560 align:start position:0% methodology today that would allow you 01:23:12.560 --> 01:23:13.910 align:start position:0% methodology today that would allow you to 01:23:13.910 --> 01:23:13.920 align:start position:0% to 01:23:13.920 --> 01:23:16.229 align:start position:0% to determine<01:23:14.560> how<01:23:14.719> much<01:23:15.199> you're<01:23:15.440> buying<01:23:15.840> for 01:23:16.229 --> 01:23:16.239 align:start position:0% determine how much you're buying for 01:23:16.239 --> 01:23:18.629 align:start position:0% determine how much you're buying for load<01:23:16.480> swings<01:23:17.040> and<01:23:17.520> for<01:23:17.920> you<01:23:18.000> know<01:23:18.159> drop-offs 01:23:18.629 --> 01:23:18.639 align:start position:0% load swings and for you know drop-offs 01:23:18.639 --> 01:23:20.070 align:start position:0% load swings and for you know drop-offs of<01:23:18.719> renewables<01:23:19.199> or<01:23:19.360> any<01:23:19.520> other<01:23:19.679> type<01:23:19.920> of 01:23:20.070 --> 01:23:20.080 align:start position:0% of renewables or any other type of 01:23:20.080 --> 01:23:21.270 align:start position:0% of renewables or any other type of generation 01:23:21.270 --> 01:23:21.280 align:start position:0% generation 01:23:21.280 --> 01:23:23.030 align:start position:0% generation day<01:23:21.520> module<01:23:21.760> with<01:23:21.920> aircon<01:23:22.400> you<01:23:22.480> know<01:23:22.639> as<01:23:22.880> part 01:23:23.030 --> 01:23:23.040 align:start position:0% day module with aircon you know as part 01:23:23.040 --> 01:23:24.629 align:start position:0% day module with aircon you know as part of<01:23:23.199> the<01:23:23.280> methodology 01:23:24.629 --> 01:23:24.639 align:start position:0% of the methodology 01:23:24.639 --> 01:23:26.149 align:start position:0% of the methodology we<01:23:24.800> do<01:23:24.960> have<01:23:25.120> the<01:23:25.280> different<01:23:25.600> inputs<01:23:25.920> that<01:23:26.000> we 01:23:26.149 --> 01:23:26.159 align:start position:0% we do have the different inputs that we 01:23:26.159 --> 01:23:28.070 align:start position:0% we do have the different inputs that we use<01:23:26.400> so<01:23:26.560> for<01:23:26.719> example 01:23:28.070 --> 01:23:28.080 align:start position:0% use so for example 01:23:28.080 --> 01:23:30.310 align:start position:0% use so for example we<01:23:28.400> look<01:23:28.560> at<01:23:28.719> the<01:23:29.120> net<01:23:29.280> load<01:23:29.520> forecast<01:23:30.000> there 01:23:30.310 --> 01:23:30.320 align:start position:0% we look at the net load forecast there 01:23:30.320 --> 01:23:31.590 align:start position:0% we look at the net load forecast there for 01:23:31.590 --> 01:23:31.600 align:start position:0% for 01:23:31.600 --> 01:23:33.270 align:start position:0% for fed<01:23:31.840> and<01:23:31.920> considers<01:23:32.400> both<01:23:32.960> load<01:23:33.199> and 01:23:33.270 --> 01:23:33.280 align:start position:0% fed and considers both load and 01:23:33.280 --> 01:23:34.950 align:start position:0% fed and considers both load and renewables<01:23:34.000> i<01:23:34.080> mean<01:23:34.159> i<01:23:34.320> think<01:23:34.480> there<01:23:34.719> is<01:23:34.880> a 01:23:34.950 --> 01:23:34.960 align:start position:0% renewables i mean i think there is a 01:23:34.960 --> 01:23:36.229 align:start position:0% renewables i mean i think there is a technical<01:23:35.440> way 01:23:36.229 --> 01:23:36.239 align:start position:0% technical way 01:23:36.239 --> 01:23:38.709 align:start position:0% technical way to<01:23:36.480> to<01:23:36.719> try<01:23:37.040> to<01:23:37.360> parse<01:23:37.679> that<01:23:37.920> out 01:23:38.709 --> 01:23:38.719 align:start position:0% to to try to parse that out 01:23:38.719 --> 01:23:40.470 align:start position:0% to to try to parse that out uh<01:23:38.960> to<01:23:39.360> look<01:23:39.600> at<01:23:39.679> the<01:23:39.840> for<01:23:40.000> example<01:23:40.320> the 01:23:40.470 --> 01:23:40.480 align:start position:0% uh to look at the for example the 01:23:40.480 --> 01:23:41.750 align:start position:0% uh to look at the for example the different<01:23:40.639> components<01:23:41.120> of<01:23:41.199> that<01:23:41.280> forecast 01:23:41.750 --> 01:23:41.760 align:start position:0% different components of that forecast 01:23:41.760 --> 01:23:42.470 align:start position:0% different components of that forecast there<01:23:41.920> and<01:23:42.000> thinking<01:23:42.320> through<01:23:42.400> the 01:23:42.470 --> 01:23:42.480 align:start position:0% there and thinking through the 01:23:42.480 --> 01:23:43.830 align:start position:0% there and thinking through the methodology 01:23:43.830 --> 01:23:43.840 align:start position:0% methodology 01:23:43.840 --> 01:23:45.189 align:start position:0% methodology um 01:23:45.189 --> 01:23:45.199 align:start position:0% um 01:23:45.199 --> 01:23:46.870 align:start position:0% um so<01:23:45.440> so<01:23:45.600> i<01:23:45.679> think<01:23:45.840> there<01:23:46.000> is<01:23:46.159> ways<01:23:46.400> to<01:23:46.560> sort<01:23:46.800> of 01:23:46.870 --> 01:23:46.880 align:start position:0% so so i think there is ways to sort of 01:23:46.880 --> 01:23:48.229 align:start position:0% so so i think there is ways to sort of do<01:23:47.040> that<01:23:47.199> type<01:23:47.440> of<01:23:47.520> breakout<01:23:47.840> within<01:23:48.000> the 01:23:48.229 --> 01:23:48.239 align:start position:0% do that type of breakout within the 01:23:48.239 --> 01:23:49.830 align:start position:0% do that type of breakout within the methodology<01:23:48.880> process<01:23:49.280> there<01:23:49.440> i<01:23:49.520> think<01:23:49.679> there 01:23:49.830 --> 01:23:49.840 align:start position:0% methodology process there i think there 01:23:49.840 --> 01:23:51.750 align:start position:0% methodology process there i think there may<01:23:49.920> be<01:23:50.239> other<01:23:50.480> considerations 01:23:51.750 --> 01:23:51.760 align:start position:0% may be other considerations 01:23:51.760 --> 01:23:53.910 align:start position:0% may be other considerations as<01:23:51.920> well<01:23:52.159> on<01:23:52.239> top<01:23:52.480> of<01:23:52.560> that<01:23:52.800> but<01:23:52.960> from<01:23:53.199> uh<01:23:53.679> from 01:23:53.910 --> 01:23:53.920 align:start position:0% as well on top of that but from uh from 01:23:53.920 --> 01:23:55.270 align:start position:0% as well on top of that but from uh from a<01:23:54.000> technical<01:23:54.400> point<01:23:54.560> of<01:23:54.639> view<01:23:54.800> i<01:23:54.880> think<01:23:55.040> you 01:23:55.270 --> 01:23:55.280 align:start position:0% a technical point of view i think you 01:23:55.280 --> 01:23:56.629 align:start position:0% a technical point of view i think you could<01:23:55.520> do<01:23:55.679> that<01:23:55.840> with<01:23:56.000> some<01:23:56.239> form<01:23:56.480> of<01:23:56.560> the 01:23:56.629 --> 01:23:56.639 align:start position:0% could do that with some form of the 01:23:56.639 --> 01:23:58.550 align:start position:0% could do that with some form of the methodology<01:23:57.199> we<01:23:57.280> have<01:23:57.440> in<01:23:57.520> place 01:23:58.550 --> 01:23:58.560 align:start position:0% methodology we have in place 01:23:58.560 --> 01:24:00.149 align:start position:0% methodology we have in place okay<01:23:58.960> so<01:23:59.280> so 01:24:00.149 --> 01:24:00.159 align:start position:0% okay so so 01:24:00.159 --> 01:24:02.149 align:start position:0% okay so so that's<01:24:00.400> good<01:24:00.560> to<01:24:00.719> hear<01:24:01.120> as<01:24:01.440> we<01:24:01.600> sort<01:24:01.840> of<01:24:01.920> think 01:24:02.149 --> 01:24:02.159 align:start position:0% that's good to hear as we sort of think 01:24:02.159 --> 01:24:03.110 align:start position:0% that's good to hear as we sort of think about 01:24:03.110 --> 01:24:03.120 align:start position:0% about 01:24:03.120 --> 01:24:05.030 align:start position:0% about um<01:24:03.760> how<01:24:03.920> we<01:24:04.080> move<01:24:04.239> forward<01:24:04.480> with<01:24:04.639> this<01:24:04.800> very 01:24:05.030 --> 01:24:05.040 align:start position:0% um how we move forward with this very 01:24:05.040 --> 01:24:07.189 align:start position:0% um how we move forward with this very important<01:24:05.440> issue<01:24:05.760> and<01:24:05.920> i<01:24:06.000> think<01:24:06.239> if<01:24:06.880> as<01:24:07.040> we 01:24:07.189 --> 01:24:07.199 align:start position:0% important issue and i think if as we 01:24:07.199 --> 01:24:08.950 align:start position:0% important issue and i think if as we look<01:24:07.360> to<01:24:07.520> move<01:24:07.760> forward<01:24:08.000> with<01:24:08.159> this<01:24:08.320> issue<01:24:08.719> i 01:24:08.950 --> 01:24:08.960 align:start position:0% look to move forward with this issue i 01:24:08.960 --> 01:24:09.830 align:start position:0% look to move forward with this issue i think 01:24:09.830 --> 01:24:09.840 align:start position:0% think 01:24:09.840 --> 01:24:11.750 align:start position:0% think we're<01:24:10.000> going<01:24:10.159> to<01:24:10.239> have<01:24:10.400> to<01:24:10.639> sort<01:24:10.880> of<01:24:11.280> do<01:24:11.520> it<01:24:11.679> in 01:24:11.750 --> 01:24:11.760 align:start position:0% we're going to have to sort of do it in 01:24:11.760 --> 01:24:14.470 align:start position:0% we're going to have to sort of do it in a<01:24:11.840> way<01:24:12.159> that<01:24:12.639> we<01:24:12.800> have<01:24:13.520> a<01:24:13.679> project<01:24:14.159> with 01:24:14.470 --> 01:24:14.480 align:start position:0% a way that we have a project with 01:24:14.480 --> 01:24:16.629 align:start position:0% a way that we have a project with stakeholder<01:24:15.120> input<01:24:16.000> as<01:24:16.159> we<01:24:16.320> look<01:24:16.480> to 01:24:16.629 --> 01:24:16.639 align:start position:0% stakeholder input as we look to 01:24:16.639 --> 01:24:20.229 align:start position:0% stakeholder input as we look to implement<01:24:17.040> that<01:24:17.199> portion<01:24:17.600> of<01:24:17.760> sp3 01:24:20.229 --> 01:24:20.239 align:start position:0% implement that portion of sp3 01:24:20.239 --> 01:24:22.709 align:start position:0% implement that portion of sp3 something<01:24:20.560> to<01:24:20.719> consider 01:24:22.709 --> 01:24:22.719 align:start position:0% something to consider 01:24:22.719 --> 01:24:24.470 align:start position:0% something to consider any<01:24:22.880> other<01:24:23.040> questions<01:24:23.360> for<01:24:23.520> dave<01:24:24.000> what<01:24:24.239> one 01:24:24.470 --> 01:24:24.480 align:start position:0% any other questions for dave what one 01:24:24.480 --> 01:24:26.870 align:start position:0% any other questions for dave what one question<01:24:24.960> on 01:24:26.870 --> 01:24:26.880 align:start position:0% question on 01:24:26.880 --> 01:24:29.350 align:start position:0% question on crossing<01:24:27.760> rivers 01:24:29.350 --> 01:24:29.360 align:start position:0% crossing rivers 01:24:29.360 --> 01:24:31.430 align:start position:0% crossing rivers as<01:24:29.600> a<01:24:29.840> as<01:24:30.000> a<01:24:30.080> technical<01:24:30.560> point 01:24:31.430 --> 01:24:31.440 align:start position:0% as a as a technical point 01:24:31.440 --> 01:24:33.030 align:start position:0% as a as a technical point ems<01:24:32.000> upgrade 01:24:33.030 --> 01:24:33.040 align:start position:0% ems upgrade 01:24:33.040 --> 01:24:34.149 align:start position:0% ems upgrade is<01:24:33.199> moving 01:24:34.149 --> 01:24:34.159 align:start position:0% is moving 01:24:34.159 --> 01:24:35.910 align:start position:0% is moving along<01:24:34.880> um 01:24:35.910 --> 01:24:35.920 align:start position:0% along um 01:24:35.920 --> 01:24:38.070 align:start position:0% along um 2023 01:24:38.070 --> 01:24:38.080 align:start position:0% 2023 01:24:38.080 --> 01:24:39.350 align:start position:0% 2023 is<01:24:38.320> our 01:24:39.350 --> 01:24:39.360 align:start position:0% is our 01:24:39.360 --> 01:24:42.550 align:start position:0% is our yeah<01:24:39.920> 2024<01:24:40.880> is<01:24:41.040> our<01:24:41.199> projected<01:24:42.000> completion 01:24:42.550 --> 01:24:42.560 align:start position:0% yeah 2024 is our projected completion 01:24:42.560 --> 01:24:45.270 align:start position:0% yeah 2024 is our projected completion date<01:24:42.800> and<01:24:42.960> again<01:24:43.199> to<01:24:43.440> have<01:24:43.679> a<01:24:43.920> formalized<01:24:45.040> new 01:24:45.270 --> 01:24:45.280 align:start position:0% date and again to have a formalized new 01:24:45.280 --> 01:24:47.910 align:start position:0% date and again to have a formalized new system<01:24:45.760> of<01:24:45.920> settlements<01:24:46.560> to<01:24:46.800> where<01:24:47.040> we<01:24:47.199> can 01:24:47.910 --> 01:24:47.920 align:start position:0% system of settlements to where we can 01:24:47.920 --> 01:24:48.870 align:start position:0% system of settlements to where we can um 01:24:48.870 --> 01:24:48.880 align:start position:0% um 01:24:48.880 --> 01:24:52.629 align:start position:0% um impose<01:24:49.280> a<01:24:49.440> framework<01:24:50.080> of<01:24:50.320> cost<01:24:50.639> allocation 01:24:52.629 --> 01:24:52.639 align:start position:0% impose a framework of cost allocation 01:24:52.639 --> 01:24:55.189 align:start position:0% impose a framework of cost allocation we<01:24:52.880> know<01:24:53.520> we<01:24:53.679> need<01:24:53.920> a<01:24:54.000> service 01:24:55.189 --> 01:24:55.199 align:start position:0% we know we need a service 01:24:55.199 --> 01:25:01.030 align:start position:0% we know we need a service we<01:24:55.360> know<01:24:55.679> it's<01:24:55.840> got<01:24:55.920> to<01:24:56.000> be<01:24:56.159> paid<01:24:56.400> for 01:25:01.030 --> 01:25:01.040 align:start position:0% 01:25:01.040 --> 01:25:03.430 align:start position:0% it<01:25:01.280> it<01:25:01.440> will<01:25:01.679> take<01:25:02.159> some<01:25:02.400> time<01:25:02.639> how<01:25:03.120> how 01:25:03.430 --> 01:25:03.440 align:start position:0% it it will take some time how how 01:25:03.440 --> 01:25:06.149 align:start position:0% it it will take some time how how quickly<01:25:04.000> can<01:25:04.159> you<01:25:04.320> do<01:25:04.560> analysis<01:25:05.600> to<01:25:05.760> do<01:25:06.000> all 01:25:06.149 --> 01:25:06.159 align:start position:0% quickly can you do analysis to do all 01:25:06.159 --> 01:25:09.030 align:start position:0% quickly can you do analysis to do all these<01:25:06.639> associated<01:25:07.280> assignment<01:25:08.000> of<01:25:08.239> costs<01:25:08.800> by 01:25:09.030 --> 01:25:09.040 align:start position:0% these associated assignment of costs by 01:25:09.040 --> 01:25:10.229 align:start position:0% these associated assignment of costs by resource 01:25:10.229 --> 01:25:10.239 align:start position:0% resource 01:25:10.239 --> 01:25:11.350 align:start position:0% resource and 01:25:11.350 --> 01:25:11.360 align:start position:0% and 01:25:11.360 --> 01:25:14.229 align:start position:0% and how<01:25:11.520> do<01:25:11.679> you<01:25:11.840> envision<01:25:12.320> that<01:25:12.880> functioning<01:25:13.920> uh 01:25:14.229 --> 01:25:14.239 align:start position:0% how do you envision that functioning uh 01:25:14.239 --> 01:25:17.189 align:start position:0% how do you envision that functioning uh is<01:25:14.320> that<01:25:14.560> on<01:25:14.719> a<01:25:15.199> zonal<01:25:15.600> basis<01:25:16.320> is<01:25:16.480> that<01:25:16.719> on<01:25:16.880> a 01:25:17.189 --> 01:25:17.199 align:start position:0% is that on a zonal basis is that on a 01:25:17.199 --> 01:25:19.830 align:start position:0% is that on a zonal basis is that on a nodal<01:25:17.679> basis<01:25:18.639> you<01:25:18.800> know<01:25:18.960> to<01:25:19.120> that<01:25:19.360> degree<01:25:19.760> of 01:25:19.830 --> 01:25:19.840 align:start position:0% nodal basis you know to that degree of 01:25:19.840 --> 01:25:22.229 align:start position:0% nodal basis you know to that degree of granularity<01:25:20.960> to<01:25:21.120> assign<01:25:21.520> costs<01:25:21.840> on<01:25:21.920> a<01:25:22.000> cost 01:25:22.229 --> 01:25:22.239 align:start position:0% granularity to assign costs on a cost 01:25:22.239 --> 01:25:24.229 align:start position:0% granularity to assign costs on a cost causation<01:25:22.800> basis 01:25:24.229 --> 01:25:24.239 align:start position:0% causation basis 01:25:24.239 --> 01:25:25.750 align:start position:0% causation basis yeah<01:25:24.560> well<01:25:24.800> and<01:25:24.880> i<01:25:24.960> guess<01:25:25.120> just<01:25:25.280> real<01:25:25.440> quick<01:25:25.600> on 01:25:25.750 --> 01:25:25.760 align:start position:0% yeah well and i guess just real quick on 01:25:25.760 --> 01:25:27.750 align:start position:0% yeah well and i guess just real quick on the<01:25:26.080> ems<01:25:26.480> upgrade<01:25:26.880> that<01:25:27.120> that's<01:25:27.440> separate 01:25:27.750 --> 01:25:27.760 align:start position:0% the ems upgrade that that's separate 01:25:27.760 --> 01:25:29.189 align:start position:0% the ems upgrade that that's separate from<01:25:27.920> our<01:25:28.239> settlement<01:25:28.639> system<01:25:28.960> so<01:25:29.120> that 01:25:29.189 --> 01:25:29.199 align:start position:0% from our settlement system so that 01:25:29.199 --> 01:25:30.870 align:start position:0% from our settlement system so that that's<01:25:29.440> a<01:25:29.679> upgrade<01:25:30.000> truly<01:25:30.239> just<01:25:30.400> our<01:25:30.560> energy 01:25:30.870 --> 01:25:30.880 align:start position:0% that's a upgrade truly just our energy 01:25:30.880 --> 01:25:32.870 align:start position:0% that's a upgrade truly just our energy management<01:25:31.280> system<01:25:32.000> um<01:25:32.400> you<01:25:32.480> know<01:25:32.639> i<01:25:32.719> guess 01:25:32.870 --> 01:25:32.880 align:start position:0% management system um you know i guess 01:25:32.880 --> 01:25:34.550 align:start position:0% management system um you know i guess we've<01:25:33.120> talked<01:25:33.360> a<01:25:33.360> little<01:25:33.520> bit<01:25:33.679> on<01:25:34.159> with<01:25:34.400> uh 01:25:34.550 --> 01:25:34.560 align:start position:0% we've talked a little bit on with uh 01:25:34.560 --> 01:25:35.590 align:start position:0% we've talked a little bit on with uh woody's<01:25:34.880> question<01:25:35.120> in<01:25:35.199> terms<01:25:35.440> of<01:25:35.520> the 01:25:35.590 --> 01:25:35.600 align:start position:0% woody's question in terms of the 01:25:35.600 --> 01:25:38.310 align:start position:0% woody's question in terms of the timeline<01:25:36.239> with<01:25:36.719> ecrs<01:25:37.360> and<01:25:37.679> initiating<01:25:38.159> that 01:25:38.310 --> 01:25:38.320 align:start position:0% timeline with ecrs and initiating that 01:25:38.320 --> 01:25:40.629 align:start position:0% timeline with ecrs and initiating that project<01:25:38.719> now<01:25:39.440> i<01:25:39.520> think<01:25:39.679> we<01:25:39.920> wanted<01:25:40.239> to<01:25:40.320> look<01:25:40.480> at 01:25:40.629 --> 01:25:40.639 align:start position:0% project now i think we wanted to look at 01:25:40.639 --> 01:25:43.030 align:start position:0% project now i think we wanted to look at changes<01:25:41.040> to<01:25:41.199> the<01:25:41.520> to<01:25:41.679> the<01:25:41.760> cost<01:25:42.159> allocation 01:25:43.030 --> 01:25:43.040 align:start position:0% changes to the to the cost allocation 01:25:43.040 --> 01:25:44.709 align:start position:0% changes to the to the cost allocation that<01:25:43.199> may<01:25:43.360> be<01:25:43.440> something<01:25:43.760> we'd<01:25:43.920> want<01:25:44.080> to<01:25:44.239> do<01:25:44.480> as 01:25:44.709 --> 01:25:44.719 align:start position:0% that may be something we'd want to do as 01:25:44.719 --> 01:25:47.270 align:start position:0% that may be something we'd want to do as a<01:25:44.960> as<01:25:45.120> a<01:25:45.280> separate<01:25:45.679> phase<01:25:46.080> i<01:25:46.239> think<01:25:46.400> that<01:25:46.639> would 01:25:47.270 --> 01:25:47.280 align:start position:0% a as a separate phase i think that would 01:25:47.280 --> 01:25:48.870 align:start position:0% a as a separate phase i think that would i<01:25:47.520> just<01:25:47.679> naturally<01:25:48.080> put<01:25:48.239> a<01:25:48.320> delay<01:25:48.639> in<01:25:48.719> that 01:25:48.870 --> 01:25:48.880 align:start position:0% i just naturally put a delay in that 01:25:48.880 --> 01:25:51.110 align:start position:0% i just naturally put a delay in that there's<01:25:49.120> a<01:25:49.199> lot<01:25:49.280> of<01:25:49.360> pressures<01:25:49.760> right<01:25:49.920> now 01:25:51.110 --> 01:25:51.120 align:start position:0% there's a lot of pressures right now 01:25:51.120 --> 01:25:53.030 align:start position:0% there's a lot of pressures right now on<01:25:51.360> changes<01:25:51.679> to<01:25:51.840> the<01:25:51.920> settlement<01:25:52.320> systems 01:25:53.030 --> 01:25:53.040 align:start position:0% on changes to the settlement systems 01:25:53.040 --> 01:25:54.950 align:start position:0% on changes to the settlement systems kind<01:25:53.199> of<01:25:53.280> part<01:25:53.440> of<01:25:53.520> the<01:25:53.760> our<01:25:53.920> comments<01:25:54.320> we<01:25:54.480> had 01:25:54.950 --> 01:25:54.960 align:start position:0% kind of part of the our comments we had 01:25:54.960 --> 01:25:56.550 align:start position:0% kind of part of the our comments we had i<01:25:55.040> mean<01:25:55.199> i<01:25:55.360> think<01:25:55.440> that<01:25:55.600> would<01:25:55.679> be<01:25:55.760> up<01:25:55.840> to<01:25:56.239> how 01:25:56.550 --> 01:25:56.560 align:start position:0% i mean i think that would be up to how 01:25:56.560 --> 01:25:58.390 align:start position:0% i mean i think that would be up to how how<01:25:56.800> grand<01:25:57.040> you<01:25:57.199> want<01:25:57.360> to<01:25:57.440> get<01:25:57.840> as<01:25:58.080> i<01:25:58.159> kind<01:25:58.320> of 01:25:58.390 --> 01:25:58.400 align:start position:0% how grand you want to get as i kind of 01:25:58.400 --> 01:26:00.229 align:start position:0% how grand you want to get as i kind of describe<01:25:58.800> the<01:25:58.880> methodology 01:26:00.229 --> 01:26:00.239 align:start position:0% describe the methodology 01:26:00.239 --> 01:26:01.990 align:start position:0% describe the methodology uh<01:26:00.480> today<01:26:00.880> and<01:26:01.120> in<01:26:01.199> terms<01:26:01.440> of<01:26:01.600> determining 01:26:01.990 --> 01:26:02.000 align:start position:0% uh today and in terms of determining 01:26:02.000 --> 01:26:05.270 align:start position:0% uh today and in terms of determining iranian<01:26:02.560> services<01:26:02.960> that<01:26:03.120> really<01:26:03.600> just<01:26:03.920> is<01:26:04.080> a 01:26:05.270 --> 01:26:05.280 align:start position:0% iranian services that really just is a 01:26:05.280 --> 01:26:06.709 align:start position:0% iranian services that really just is a for<01:26:05.520> example 01:26:06.709 --> 01:26:06.719 align:start position:0% for example 01:26:06.719 --> 01:26:09.030 align:start position:0% for example wind<01:26:07.199> and<01:26:07.440> solar<01:26:07.840> forecast<01:26:08.320> there<01:26:08.560> feeds<01:26:08.880> into 01:26:09.030 --> 01:26:09.040 align:start position:0% wind and solar forecast there feeds into 01:26:09.040 --> 01:26:11.189 align:start position:0% wind and solar forecast there feeds into that<01:26:09.280> at<01:26:09.840> at<01:26:10.000> the<01:26:10.159> system-wide<01:26:10.800> level<01:26:11.040> so 01:26:11.189 --> 01:26:11.199 align:start position:0% that at at the system-wide level so 01:26:11.199 --> 01:26:13.189 align:start position:0% that at at the system-wide level so there's<01:26:11.600> no<01:26:11.840> sort<01:26:12.000> of<01:26:12.159> specific<01:26:12.560> analysis<01:26:13.040> to 01:26:13.189 --> 01:26:13.199 align:start position:0% there's no sort of specific analysis to 01:26:13.199 --> 01:26:14.229 align:start position:0% there's no sort of specific analysis to dig<01:26:13.440> into 01:26:14.229 --> 01:26:14.239 align:start position:0% dig into 01:26:14.239 --> 01:26:16.709 align:start position:0% dig into maybe<01:26:14.639> resource-specific<01:26:16.000> causation<01:26:16.560> or 01:26:16.709 --> 01:26:16.719 align:start position:0% maybe resource-specific causation or 01:26:16.719 --> 01:26:18.070 align:start position:0% maybe resource-specific causation or anything<01:26:16.960> like<01:26:17.120> that<01:26:17.280> sure 01:26:18.070 --> 01:26:18.080 align:start position:0% anything like that sure 01:26:18.080 --> 01:26:20.070 align:start position:0% anything like that sure because<01:26:18.560> uh<01:26:19.120> i<01:26:19.199> guess<01:26:19.360> this<01:26:19.520> is<01:26:19.600> not<01:26:19.760> just<01:26:20.000> a 01:26:20.070 --> 01:26:20.080 align:start position:0% because uh i guess this is not just a 01:26:20.080 --> 01:26:23.110 align:start position:0% because uh i guess this is not just a question<01:26:20.400> for<01:26:20.560> you<01:26:20.800> but 01:26:23.110 --> 01:26:23.120 align:start position:0% 01:26:23.120 --> 01:26:25.830 align:start position:0% has<01:26:23.280> there<01:26:23.440> been<01:26:23.600> any<01:26:23.760> analysis<01:26:24.800> on 01:26:25.830 --> 01:26:25.840 align:start position:0% has there been any analysis on 01:26:25.840 --> 01:26:28.709 align:start position:0% has there been any analysis on the<01:26:26.320> procurement<01:26:26.960> of<01:26:27.600> potentially 01:26:28.709 --> 01:26:28.719 align:start position:0% the procurement of potentially 01:26:28.719 --> 01:26:31.350 align:start position:0% the procurement of potentially staggering<01:26:29.199> amounts<01:26:29.920> of<01:26:30.159> what's<01:26:30.880> going<01:26:31.040> to<01:26:31.120> be 01:26:31.350 --> 01:26:31.360 align:start position:0% staggering amounts of what's going to be 01:26:31.360 --> 01:26:33.030 align:start position:0% staggering amounts of what's going to be peakers<01:26:31.840> essentially<01:26:32.239> to<01:26:32.400> meet<01:26:32.639> that 01:26:33.030 --> 01:26:33.040 align:start position:0% peakers essentially to meet that 01:26:33.040 --> 01:26:34.790 align:start position:0% peakers essentially to meet that operational<01:26:33.600> requirement 01:26:34.790 --> 01:26:34.800 align:start position:0% operational requirement 01:26:34.800 --> 01:26:36.950 align:start position:0% operational requirement which<01:26:35.040> are<01:26:35.199> the<01:26:35.760> one<01:26:35.920> of<01:26:36.000> the<01:26:36.159> least<01:26:36.400> efficient 01:26:36.950 --> 01:26:36.960 align:start position:0% which are the one of the least efficient 01:26:36.960 --> 01:26:39.430 align:start position:0% which are the one of the least efficient most<01:26:37.280> expensive<01:26:37.920> versions<01:26:38.480> of<01:26:38.639> gas 01:26:39.430 --> 01:26:39.440 align:start position:0% most expensive versions of gas 01:26:39.440 --> 01:26:41.110 align:start position:0% most expensive versions of gas generation 01:26:41.110 --> 01:26:41.120 align:start position:0% generation 01:26:41.120 --> 01:26:44.229 align:start position:0% generation has<01:26:41.280> there<01:26:41.360> been<01:26:41.760> any<01:26:42.000> analysis<01:26:42.880> about<01:26:43.679> the 01:26:44.229 --> 01:26:44.239 align:start position:0% has there been any analysis about the 01:26:44.239 --> 01:26:47.030 align:start position:0% has there been any analysis about the total<01:26:44.639> cost<01:26:44.960> of<01:26:45.120> procuring<01:26:45.600> ecrs<01:26:46.560> expected 01:26:47.030 --> 01:26:47.040 align:start position:0% total cost of procuring ecrs expected 01:26:47.040 --> 01:26:49.189 align:start position:0% total cost of procuring ecrs expected ecrs<01:26:48.000> over 01:26:49.189 --> 01:26:49.199 align:start position:0% ecrs over 01:26:49.199 --> 01:26:51.669 align:start position:0% ecrs over the<01:26:49.280> next<01:26:49.679> 10<01:26:49.920> or<01:26:50.000> 20<01:26:50.320> years 01:26:51.669 --> 01:26:51.679 align:start position:0% the next 10 or 20 years 01:26:51.679 --> 01:26:54.629 align:start position:0% the next 10 or 20 years and<01:26:51.920> if<01:26:52.080> that<01:26:52.480> amount<01:26:52.880> of<01:26:53.120> cost 01:26:54.629 --> 01:26:54.639 align:start position:0% and if that amount of cost 01:26:54.639 --> 01:26:55.750 align:start position:0% and if that amount of cost is 01:26:55.750 --> 01:26:55.760 align:start position:0% is 01:26:55.760 --> 01:26:56.950 align:start position:0% is uh 01:26:56.950 --> 01:26:56.960 align:start position:0% uh 01:26:56.960 --> 01:26:57.910 align:start position:0% uh is 01:26:57.910 --> 01:26:57.920 align:start position:0% is 01:26:57.920 --> 01:27:01.110 align:start position:0% is more<01:26:58.159> or<01:26:58.400> less<01:26:58.800> than<01:26:59.040> the<01:26:59.520> savings<01:27:00.239> from 01:27:01.110 --> 01:27:01.120 align:start position:0% more or less than the savings from 01:27:01.120 --> 01:27:03.910 align:start position:0% more or less than the savings from zero<01:27:01.440> marginal<01:27:01.840> cost<01:27:02.159> solar 01:27:03.910 --> 01:27:03.920 align:start position:0% zero marginal cost solar 01:27:03.920 --> 01:27:05.430 align:start position:0% zero marginal cost solar i<01:27:04.000> guess<01:27:04.239> as<01:27:04.400> of<01:27:04.480> that<01:27:04.639> we<01:27:04.800> don't<01:27:04.960> have<01:27:05.040> a<01:27:05.199> study 01:27:05.430 --> 01:27:05.440 align:start position:0% i guess as of that we don't have a study 01:27:05.440 --> 01:27:07.270 align:start position:0% i guess as of that we don't have a study like<01:27:05.600> that<01:27:05.920> as<01:27:06.239> as<01:27:06.480> woody<01:27:06.719> mentioned<01:27:07.040> i<01:27:07.199> i 01:27:07.270 --> 01:27:07.280 align:start position:0% like that as as woody mentioned i i 01:27:07.280 --> 01:27:09.990 align:start position:0% like that as as woody mentioned i i don't<01:27:07.520> think<01:27:07.679> we<01:27:07.840> have<01:27:08.480> to<01:27:08.560> say<01:27:08.880> some<01:27:09.440> finalize 01:27:09.990 --> 01:27:10.000 align:start position:0% don't think we have to say some finalize 01:27:10.000 --> 01:27:11.270 align:start position:0% don't think we have to say some finalize what<01:27:10.159> the<01:27:10.239> methodology<01:27:10.800> is<01:27:10.960> going<01:27:11.040> to<01:27:11.120> look 01:27:11.270 --> 01:27:11.280 align:start position:0% what the methodology is going to look 01:27:11.280 --> 01:27:12.629 align:start position:0% what the methodology is going to look like<01:27:11.440> through<01:27:11.679> crs<01:27:12.000> and<01:27:12.080> obviously<01:27:12.400> that's 01:27:12.629 --> 01:27:12.639 align:start position:0% like through crs and obviously that's 01:27:12.639 --> 01:27:14.149 align:start position:0% like through crs and obviously that's the<01:27:13.040> the<01:27:13.199> first<01:27:13.440> question<01:27:13.760> is<01:27:13.840> how<01:27:14.000> many 01:27:14.149 --> 01:27:14.159 align:start position:0% the the first question is how many 01:27:14.159 --> 01:27:15.910 align:start position:0% the the first question is how many megawatts<01:27:14.639> you<01:27:14.800> need<01:27:15.120> and<01:27:15.520> you<01:27:15.600> could<01:27:15.760> dig 01:27:15.910 --> 01:27:15.920 align:start position:0% megawatts you need and you could dig 01:27:15.920 --> 01:27:18.070 align:start position:0% megawatts you need and you could dig into<01:27:16.239> of<01:27:16.320> course<01:27:17.120> trying<01:27:17.280> to<01:27:17.440> analyze<01:27:17.760> the 01:27:18.070 --> 01:27:18.080 align:start position:0% into of course trying to analyze the 01:27:18.080 --> 01:27:19.669 align:start position:0% into of course trying to analyze the cost<01:27:18.400> impact<01:27:18.719> but<01:27:18.880> i<01:27:19.040> think<01:27:19.120> that's<01:27:19.360> the<01:27:19.440> first 01:27:19.669 --> 01:27:19.679 align:start position:0% cost impact but i think that's the first 01:27:19.679 --> 01:27:21.110 align:start position:0% cost impact but i think that's the first component<01:27:20.159> we<01:27:20.320> need<01:27:20.480> to<01:27:20.560> do<01:27:20.639> that<01:27:20.800> type<01:27:20.960> of 01:27:21.110 --> 01:27:21.120 align:start position:0% component we need to do that type of 01:27:21.120 --> 01:27:24.070 align:start position:0% component we need to do that type of work<01:27:21.679> yeah<01:27:22.239> it's<01:27:22.639> as<01:27:22.800> we<01:27:22.880> get<01:27:23.120> closer<01:27:23.440> to<01:27:23.920> the 01:27:24.070 --> 01:27:24.080 align:start position:0% work yeah it's as we get closer to the 01:27:24.080 --> 01:27:25.750 align:start position:0% work yeah it's as we get closer to the fine<01:27:24.320> details<01:27:24.719> on<01:27:24.880> that<01:27:25.040> it<01:27:25.199> may<01:27:25.360> be<01:27:25.440> worth 01:27:25.750 --> 01:27:25.760 align:start position:0% fine details on that it may be worth 01:27:25.760 --> 01:27:27.990 align:start position:0% fine details on that it may be worth asking<01:27:26.239> even<01:27:26.480> at<01:27:26.639> a<01:27:26.719> philosophical<01:27:27.360> level<01:27:27.679> is 01:27:27.990 --> 01:27:28.000 align:start position:0% asking even at a philosophical level is 01:27:28.000 --> 01:27:29.510 align:start position:0% asking even at a philosophical level is are<01:27:28.080> we<01:27:28.239> going<01:27:28.400> to<01:27:28.480> spend<01:27:28.719> more<01:27:28.960> money 01:27:29.510 --> 01:27:29.520 align:start position:0% are we going to spend more money 01:27:29.520 --> 01:27:33.669 align:start position:0% are we going to spend more money building<01:27:29.840> the<01:27:30.320> you<01:27:30.480> know<01:27:31.040> 100<01:27:31.440> 200<01:27:32.000> 300 01:27:33.669 --> 01:27:33.679 align:start position:0% building the you know 100 200 300 01:27:33.679 --> 01:27:35.270 align:start position:0% building the you know 100 200 300 peakers 01:27:35.270 --> 01:27:35.280 align:start position:0% peakers 01:27:35.280 --> 01:27:38.070 align:start position:0% peakers then<01:27:35.440> we're<01:27:35.600> saving<01:27:35.920> by<01:27:36.080> having<01:27:36.320> solar<01:27:36.719> versus 01:27:38.070 --> 01:27:38.080 align:start position:0% then we're saving by having solar versus 01:27:38.080 --> 01:27:40.070 align:start position:0% then we're saving by having solar versus base<01:27:38.320> you<01:27:38.480> know<01:27:38.800> baseload<01:27:39.440> i<01:27:39.600> don't<01:27:39.760> know<01:27:39.920> the 01:27:40.070 --> 01:27:40.080 align:start position:0% base you know baseload i don't know the 01:27:40.080 --> 01:27:41.270 align:start position:0% base you know baseload i don't know the answer 01:27:41.270 --> 01:27:41.280 align:start position:0% answer 01:27:41.280 --> 01:27:43.990 align:start position:0% answer but<01:27:41.440> i<01:27:41.520> certainly<01:27:41.840> want<01:27:42.000> to<01:27:42.080> ask<01:27:42.239> the<01:27:42.320> question 01:27:43.990 --> 01:27:44.000 align:start position:0% but i certainly want to ask the question 01:27:44.000 --> 01:27:46.070 align:start position:0% but i certainly want to ask the question that<01:27:44.239> feeds<01:27:44.480> into<01:27:44.800> what<01:27:44.960> i<01:27:45.440> what<01:27:45.679> i<01:27:45.760> think<01:27:45.920> we 01:27:46.070 --> 01:27:46.080 align:start position:0% that feeds into what i what i think we 01:27:46.080 --> 01:27:48.229 align:start position:0% that feeds into what i what i think we need<01:27:46.400> from<01:27:46.719> from<01:27:46.960> our<01:27:47.120> cot<01:27:47.440> i<01:27:47.679> know<01:27:47.920> what<01:27:48.080> he 01:27:48.229 --> 01:27:48.239 align:start position:0% need from from our cot i know what he 01:27:48.239 --> 01:27:49.990 align:start position:0% need from from our cot i know what he just<01:27:48.400> mentioned<01:27:48.719> a<01:27:48.800> comprehensive<01:27:49.440> study<01:27:49.760> for 01:27:49.990 --> 01:27:50.000 align:start position:0% just mentioned a comprehensive study for 01:27:50.000 --> 01:27:52.470 align:start position:0% just mentioned a comprehensive study for 2022<01:27:50.719> we<01:27:51.120> we<01:27:51.280> need<01:27:51.760> we<01:27:51.920> need<01:27:52.080> some<01:27:52.239> more 01:27:52.470 --> 01:27:52.480 align:start position:0% 2022 we we need we need some more 01:27:52.480 --> 01:27:53.990 align:start position:0% 2022 we we need we need some more analysis<01:27:53.040> on<01:27:53.120> where<01:27:53.280> we're<01:27:53.440> headed<01:27:53.760> with 01:27:53.990 --> 01:27:54.000 align:start position:0% analysis on where we're headed with 01:27:54.000 --> 01:27:55.189 align:start position:0% analysis on where we're headed with respect<01:27:54.400> to 01:27:55.189 --> 01:27:55.199 align:start position:0% respect to 01:27:55.199 --> 01:27:57.350 align:start position:0% respect to these<01:27:55.440> operational<01:27:56.080> issues<01:27:56.639> and 01:27:57.350 --> 01:27:57.360 align:start position:0% these operational issues and 01:27:57.360 --> 01:27:58.070 align:start position:0% these operational issues and and 01:27:58.070 --> 01:27:58.080 align:start position:0% and 01:27:58.080 --> 01:27:59.750 align:start position:0% and trying<01:27:58.320> to<01:27:58.400> determine<01:27:59.120> how<01:27:59.280> much<01:27:59.520> of<01:27:59.679> the 01:27:59.750 --> 01:27:59.760 align:start position:0% trying to determine how much of the 01:27:59.760 --> 01:28:01.510 align:start position:0% trying to determine how much of the existing<01:28:00.480> ancillary<01:28:00.880> services<01:28:01.280> we're<01:28:01.440> going 01:28:01.510 --> 01:28:01.520 align:start position:0% existing ancillary services we're going 01:28:01.520 --> 01:28:03.430 align:start position:0% existing ancillary services we're going to<01:28:01.600> need<01:28:01.760> how<01:28:01.920> much<01:28:02.480> ecrs<01:28:03.120> we're<01:28:03.280> going<01:28:03.360> to 01:28:03.430 --> 01:28:03.440 align:start position:0% to need how much ecrs we're going to 01:28:03.440 --> 01:28:06.070 align:start position:0% to need how much ecrs we're going to need<01:28:03.760> what<01:28:03.920> what<01:28:04.080> the<01:28:04.239> associated<01:28:04.800> costs<01:28:05.120> are 01:28:06.070 --> 01:28:06.080 align:start position:0% need what what the associated costs are 01:28:06.080 --> 01:28:08.390 align:start position:0% need what what the associated costs are and<01:28:06.639> and<01:28:06.800> that<01:28:07.040> i<01:28:07.199> think<01:28:07.440> that<01:28:07.679> analysis<01:28:08.239> will 01:28:08.390 --> 01:28:08.400 align:start position:0% and and that i think that analysis will 01:28:08.400 --> 01:28:10.149 align:start position:0% and and that i think that analysis will help<01:28:08.639> feed<01:28:08.960> into 01:28:10.149 --> 01:28:10.159 align:start position:0% help feed into 01:28:10.159 --> 01:28:12.629 align:start position:0% help feed into our<01:28:10.400> implementation<01:28:11.120> of<01:28:11.280> sp3<01:28:12.080> from<01:28:12.239> a<01:28:12.320> cost 01:28:12.629 --> 01:28:12.639 align:start position:0% our implementation of sp3 from a cost 01:28:12.639 --> 01:28:15.030 align:start position:0% our implementation of sp3 from a cost allocation<01:28:13.199> standpoint<01:28:14.159> um<01:28:14.719> from<01:28:14.880> my 01:28:15.030 --> 01:28:15.040 align:start position:0% allocation standpoint um from my 01:28:15.040 --> 01:28:16.950 align:start position:0% allocation standpoint um from my perspective<01:28:15.760> i<01:28:15.840> don't<01:28:16.320> know<01:28:16.480> that<01:28:16.639> we<01:28:16.719> need<01:28:16.880> to 01:28:16.950 --> 01:28:16.960 align:start position:0% perspective i don't know that we need to 01:28:16.960 --> 01:28:19.430 align:start position:0% perspective i don't know that we need to make<01:28:17.199> any<01:28:17.679> any<01:28:17.920> decision<01:28:18.400> on<01:28:18.480> that<01:28:18.719> yet<01:28:19.120> i 01:28:19.430 --> 01:28:19.440 align:start position:0% make any any decision on that yet i 01:28:19.440 --> 01:28:21.510 align:start position:0% make any any decision on that yet i think<01:28:19.679> we<01:28:20.159> as<01:28:20.320> part<01:28:20.560> of<01:28:20.639> our<01:28:20.880> sp3 01:28:21.510 --> 01:28:21.520 align:start position:0% think we as part of our sp3 01:28:21.520 --> 01:28:23.350 align:start position:0% think we as part of our sp3 implementation<01:28:22.320> that<01:28:22.560> that's<01:28:22.880> its<01:28:23.040> own 01:28:23.350 --> 01:28:23.360 align:start position:0% implementation that that's its own 01:28:23.360 --> 01:28:26.229 align:start position:0% implementation that that's its own process<01:28:23.920> so<01:28:24.080> that<01:28:24.800> we<01:28:24.960> can<01:28:25.280> allow<01:28:25.679> ercot<01:28:26.080> to 01:28:26.229 --> 01:28:26.239 align:start position:0% process so that we can allow ercot to 01:28:26.239 --> 01:28:28.390 align:start position:0% process so that we can allow ercot to develop<01:28:26.560> the<01:28:26.719> analysis<01:28:27.280> that<01:28:27.440> we<01:28:27.600> need 01:28:28.390 --> 01:28:28.400 align:start position:0% develop the analysis that we need 01:28:28.400 --> 01:28:29.189 align:start position:0% develop the analysis that we need um 01:28:29.189 --> 01:28:29.199 align:start position:0% um 01:28:29.199 --> 01:28:30.950 align:start position:0% um not<01:28:29.360> only<01:28:29.520> from<01:28:29.679> an<01:28:29.920> overall<01:28:30.400> ancillary 01:28:30.950 --> 01:28:30.960 align:start position:0% not only from an overall ancillary 01:28:30.960 --> 01:28:32.070 align:start position:0% not only from an overall ancillary service 01:28:32.070 --> 01:28:32.080 align:start position:0% service 01:28:32.080 --> 01:28:34.310 align:start position:0% service perspective<01:28:33.040> but<01:28:33.280> also 01:28:34.310 --> 01:28:34.320 align:start position:0% perspective but also 01:28:34.320 --> 01:28:37.430 align:start position:0% perspective but also you<01:28:34.400> know<01:28:34.719> subset<01:28:35.199> on<01:28:35.440> cost<01:28:36.000> and<01:28:36.159> amounts 01:28:37.430 --> 01:28:37.440 align:start position:0% you know subset on cost and amounts 01:28:37.440 --> 01:28:41.350 align:start position:0% you know subset on cost and amounts and<01:28:37.760> and<01:28:38.000> also<01:28:38.639> um<01:28:39.120> right<01:28:39.440> you<01:28:39.520> know<01:28:39.679> how<01:28:39.840> many 01:28:41.350 --> 01:28:41.360 align:start position:0% and and also um right you know how many 01:28:41.360 --> 01:28:43.430 align:start position:0% and and also um right you know how many just<01:28:41.520> kind<01:28:41.679> of<01:28:42.080> give<01:28:42.320> us<01:28:42.400> that<01:28:42.719> comprehensive 01:28:43.430 --> 01:28:43.440 align:start position:0% just kind of give us that comprehensive 01:28:43.440 --> 01:28:47.350 align:start position:0% just kind of give us that comprehensive picture<01:28:44.000> so<01:28:44.159> that<01:28:44.400> we<01:28:44.560> can<01:28:44.719> then<01:28:44.960> determine 01:28:47.350 --> 01:28:47.360 align:start position:0% picture so that we can then determine 01:28:47.360 --> 01:28:49.270 align:start position:0% picture so that we can then determine how<01:28:47.679> as<01:28:47.840> we<01:28:48.000> go<01:28:48.159> into<01:28:48.400> cost<01:28:48.719> allocation 01:28:49.270 --> 01:28:49.280 align:start position:0% how as we go into cost allocation 01:28:49.280 --> 01:28:51.189 align:start position:0% how as we go into cost allocation implementing<01:28:49.760> sp3 01:28:51.189 --> 01:28:51.199 align:start position:0% implementing sp3 01:28:51.199 --> 01:28:52.790 align:start position:0% implementing sp3 what<01:28:51.520> we're<01:28:51.679> looking<01:28:52.000> at<01:28:52.159> what<01:28:52.320> numbers<01:28:52.639> we're 01:28:52.790 --> 01:28:52.800 align:start position:0% what we're looking at what numbers we're 01:28:52.800 --> 01:28:54.950 align:start position:0% what we're looking at what numbers we're looking<01:28:53.120> at<01:28:53.440> and<01:28:53.679> and<01:28:54.400> it<01:28:54.480> sounds<01:28:54.719> like<01:28:54.880> our 01:28:54.950 --> 01:28:54.960 align:start position:0% looking at and and it sounds like our 01:28:54.960 --> 01:28:56.870 align:start position:0% looking at and and it sounds like our cut<01:28:55.199> has<01:28:55.280> a<01:28:55.360> methodology<01:28:56.159> that<01:28:56.320> they<01:28:56.480> can<01:28:56.639> use 01:28:56.870 --> 01:28:56.880 align:start position:0% cut has a methodology that they can use 01:28:56.880 --> 01:28:58.229 align:start position:0% cut has a methodology that they can use for<01:28:57.120> just<01:28:57.360> you<01:28:57.520> know 01:28:58.229 --> 01:28:58.239 align:start position:0% for just you know 01:28:58.239 --> 01:29:00.550 align:start position:0% for just you know maybe<01:28:58.560> it's<01:28:58.719> not<01:28:58.880> that<01:28:59.040> granular 01:29:00.550 --> 01:29:00.560 align:start position:0% maybe it's not that granular 01:29:00.560 --> 01:29:01.430 align:start position:0% maybe it's not that granular but 01:29:01.430 --> 01:29:01.440 align:start position:0% but 01:29:01.440 --> 01:29:03.910 align:start position:0% but they<01:29:01.600> have<01:29:01.760> a<01:29:01.840> starting<01:29:02.239> point<01:29:02.960> at<01:29:03.120> least<01:29:03.679> that 01:29:03.910 --> 01:29:03.920 align:start position:0% they have a starting point at least that 01:29:03.920 --> 01:29:05.990 align:start position:0% they have a starting point at least that that<01:29:04.159> can<01:29:04.639> you<01:29:04.719> know<01:29:05.280> be<01:29:05.440> a<01:29:05.520> starting<01:29:05.840> point 01:29:05.990 --> 01:29:06.000 align:start position:0% that can you know be a starting point 01:29:06.000 --> 01:29:08.070 align:start position:0% that can you know be a starting point for<01:29:06.159> our<01:29:06.320> discussions<01:29:06.880> in 01:29:08.070 --> 01:29:08.080 align:start position:0% for our discussions in 01:29:08.080 --> 01:29:09.910 align:start position:0% for our discussions in that<01:29:08.320> separate<01:29:08.719> project<01:29:09.120> that<01:29:09.199> we<01:29:09.440> would<01:29:09.679> need 01:29:09.910 --> 01:29:09.920 align:start position:0% that separate project that we would need 01:29:09.920 --> 01:29:11.189 align:start position:0% that separate project that we would need to<01:29:10.080> have<01:29:10.400> so<01:29:10.560> that<01:29:10.639> we<01:29:10.800> could<01:29:10.960> have 01:29:11.189 --> 01:29:11.199 align:start position:0% to have so that we could have 01:29:11.199 --> 01:29:13.830 align:start position:0% to have so that we could have stakeholder<01:29:11.760> input<01:29:12.080> on<01:29:12.159> that<01:29:12.400> issue 01:29:13.830 --> 01:29:13.840 align:start position:0% stakeholder input on that issue 01:29:13.840 --> 01:29:16.070 align:start position:0% stakeholder input on that issue and<01:29:14.320> um<01:29:14.639> i<01:29:14.719> think<01:29:14.880> this<01:29:15.120> is<01:29:15.280> an<01:29:15.600> ongoing 01:29:16.070 --> 01:29:16.080 align:start position:0% and um i think this is an ongoing 01:29:16.080 --> 01:29:18.550 align:start position:0% and um i think this is an ongoing conversation<01:29:17.280> um 01:29:18.550 --> 01:29:18.560 align:start position:0% conversation um 01:29:18.560 --> 01:29:21.110 align:start position:0% conversation um that<01:29:18.719> we<01:29:18.880> continue<01:29:19.360> to<01:29:19.520> have<01:29:19.760> i<01:29:20.320> i<01:29:20.719> i<01:29:20.880> don't 01:29:21.110 --> 01:29:21.120 align:start position:0% that we continue to have i i i don't 01:29:21.120 --> 01:29:22.390 align:start position:0% that we continue to have i i i don't know<01:29:21.280> that<01:29:21.440> it's<01:29:21.600> something<01:29:22.000> we<01:29:22.159> make<01:29:22.320> a 01:29:22.390 --> 01:29:22.400 align:start position:0% know that it's something we make a 01:29:22.400 --> 01:29:24.070 align:start position:0% know that it's something we make a decision<01:29:22.880> on<01:29:23.040> by<01:29:23.199> the<01:29:23.360> end<01:29:23.440> of<01:29:23.520> the<01:29:23.679> year 01:29:24.070 --> 01:29:24.080 align:start position:0% decision on by the end of the year 01:29:24.080 --> 01:29:26.470 align:start position:0% decision on by the end of the year without<01:29:24.480> having<01:29:25.360> holistic 01:29:26.470 --> 01:29:26.480 align:start position:0% without having holistic 01:29:26.480 --> 01:29:28.229 align:start position:0% without having holistic comprehensive 01:29:28.229 --> 01:29:28.239 align:start position:0% comprehensive 01:29:28.239 --> 01:29:32.870 align:start position:0% comprehensive analysis<01:29:28.960> from<01:29:29.360> from<01:29:30.000> ercot<01:29:30.800> and<01:29:31.120> also<01:29:31.760> having 01:29:32.870 --> 01:29:32.880 align:start position:0% analysis from from ercot and also having 01:29:32.880 --> 01:29:35.189 align:start position:0% analysis from from ercot and also having i<01:29:32.960> mean<01:29:33.360> stakeholder<01:29:33.920> input 01:29:35.189 --> 01:29:35.199 align:start position:0% i mean stakeholder input 01:29:35.199 --> 01:29:37.110 align:start position:0% i mean stakeholder input as<01:29:35.440> part<01:29:35.600> of 01:29:37.110 --> 01:29:37.120 align:start position:0% as part of 01:29:37.120 --> 01:29:37.830 align:start position:0% as part of implementation the 01:29:37.830 --> 01:29:37.840 align:start position:0% implementation the 01:29:37.840 --> 01:29:40.390 align:start position:0% implementation the all<01:29:37.920> full<01:29:38.320> on<01:29:38.480> stakeholder<01:29:39.120> input 01:29:40.390 --> 01:29:40.400 align:start position:0% all full on stakeholder input 01:29:40.400 --> 01:29:41.910 align:start position:0% all full on stakeholder input but<01:29:40.560> we'll<01:29:40.800> continue<01:29:41.120> to<01:29:41.199> take<01:29:41.360> stakeholder 01:29:41.910 --> 01:29:41.920 align:start position:0% but we'll continue to take stakeholder 01:29:41.920 --> 01:29:42.950 align:start position:0% but we'll continue to take stakeholder input 01:29:42.950 --> 01:29:42.960 align:start position:0% input 01:29:42.960 --> 01:29:43.990 align:start position:0% input um 01:29:43.990 --> 01:29:44.000 align:start position:0% um 01:29:44.000 --> 01:29:45.669 align:start position:0% um and<01:29:44.159> i<01:29:44.400> i'd<01:29:44.880> certainly<01:29:45.199> be<01:29:45.280> comfortable 01:29:45.669 --> 01:29:45.679 align:start position:0% and i i'd certainly be comfortable 01:29:45.679 --> 01:29:46.950 align:start position:0% and i i'd certainly be comfortable making<01:29:45.920> a<01:29:45.920> decision<01:29:46.239> by<01:29:46.400> the<01:29:46.480> end<01:29:46.639> of<01:29:46.719> the<01:29:46.800> year 01:29:46.950 --> 01:29:46.960 align:start position:0% making a decision by the end of the year 01:29:46.960 --> 01:29:48.229 align:start position:0% making a decision by the end of the year but<01:29:47.120> we<01:29:47.280> don't<01:29:47.600> we<01:29:47.760> definitely<01:29:48.080> aren't<01:29:48.159> going 01:29:48.229 --> 01:29:48.239 align:start position:0% but we don't we definitely aren't going 01:29:48.239 --> 01:29:50.870 align:start position:0% but we don't we definitely aren't going to<01:29:48.320> make<01:29:48.400> a<01:29:48.560> decision<01:29:48.880> today 01:29:50.870 --> 01:29:50.880 align:start position:0% to make a decision today 01:29:50.880 --> 01:29:53.510 align:start position:0% to make a decision today any<01:29:51.120> other<01:29:51.280> questions<01:29:51.520> for<01:29:51.679> dave 01:29:53.510 --> 01:29:53.520 align:start position:0% any other questions for dave 01:29:53.520 --> 01:29:56.310 align:start position:0% any other questions for dave all<01:29:53.679> right<01:29:54.000> thank<01:29:54.159> you<01:29:54.400> sir<01:29:54.960> uh<01:29:55.280> brief<01:29:56.000> uh 01:29:56.310 --> 01:29:56.320 align:start position:0% all right thank you sir uh brief uh 01:29:56.320 --> 01:29:58.950 align:start position:0% all right thank you sir uh brief uh logistics<01:29:57.120> note<01:29:57.679> if<01:29:58.239> it<01:29:58.320> works<01:29:58.560> for<01:29:58.719> everybody 01:29:58.950 --> 01:29:58.960 align:start position:0% logistics note if it works for everybody 01:29:58.960 --> 01:30:01.030 align:start position:0% logistics note if it works for everybody we'll<01:29:59.120> aim<01:29:59.280> for<01:29:59.360> 11<01:29:59.679> 30 01:30:01.030 --> 01:30:01.040 align:start position:0% we'll aim for 11 30 01:30:01.040 --> 01:30:01.830 align:start position:0% we'll aim for 11 30 uh 01:30:01.830 --> 01:30:01.840 align:start position:0% uh 01:30:01.840 --> 01:30:02.950 align:start position:0% uh lunch<01:30:02.159> break 01:30:02.950 --> 01:30:02.960 align:start position:0% lunch break 01:30:02.960 --> 01:30:04.870 align:start position:0% lunch break it's<01:30:03.120> at<01:30:03.280> work 01:30:04.870 --> 01:30:04.880 align:start position:0% it's at work 01:30:04.880 --> 01:30:06.470 align:start position:0% it's at work and 01:30:06.470 --> 01:30:06.480 align:start position:0% and 01:30:06.480 --> 01:30:09.750 align:start position:0% and aimed<01:30:06.800> to<01:30:07.199> we'll<01:30:07.520> break<01:30:07.760> at<01:30:07.840> 11<01:30:08.239> 30<01:30:08.880> and<01:30:09.440> aim<01:30:09.600> to 01:30:09.750 --> 01:30:09.760 align:start position:0% aimed to we'll break at 11 30 and aim to 01:30:09.760 --> 01:30:10.709 align:start position:0% aimed to we'll break at 11 30 and aim to be<01:30:09.920> back 01:30:10.709 --> 01:30:10.719 align:start position:0% be back 01:30:10.719 --> 01:30:13.350 align:start position:0% be back reconvene<01:30:11.280> at<01:30:11.360> 12<01:30:11.679> 15. 01:30:13.350 --> 01:30:13.360 align:start position:0% reconvene at 12 15. 01:30:13.360 --> 01:30:14.050 align:start position:0% reconvene at 12 15. and 01:30:14.050 --> 01:30:14.060 align:start position:0% and 01:30:14.060 --> 01:30:16.229 align:start position:0% and [Music] 01:30:16.229 --> 01:30:16.239 align:start position:0% [Music] 01:30:16.239 --> 01:30:18.310 align:start position:0% [Music] that<01:30:16.480> will<01:30:16.800> bring<01:30:17.040> us<01:30:17.280> to 01:30:18.310 --> 01:30:18.320 align:start position:0% that will bring us to 01:30:18.320 --> 01:30:20.550 align:start position:0% that will bring us to a<01:30:18.800> charging<01:30:19.199> ahead<01:30:19.760> fast<01:30:20.000> frequency 01:30:20.550 --> 01:30:20.560 align:start position:0% a charging ahead fast frequency 01:30:20.560 --> 01:30:21.750 align:start position:0% a charging ahead fast frequency responsive<01:30:21.040> service<01:30:21.360> i<01:30:21.440> think<01:30:21.600> that's 01:30:21.750 --> 01:30:21.760 align:start position:0% responsive service i think that's 01:30:21.760 --> 01:30:23.350 align:start position:0% responsive service i think that's already<01:30:22.080> in<01:30:22.159> process<01:30:22.639> everybody<01:30:22.960> agrees<01:30:23.199> that 01:30:23.350 --> 01:30:23.360 align:start position:0% already in process everybody agrees that 01:30:23.360 --> 01:30:25.830 align:start position:0% already in process everybody agrees that it's<01:30:23.520> needed<01:30:24.159> um<01:30:24.960> no 01:30:25.830 --> 01:30:25.840 align:start position:0% it's needed um no 01:30:25.840 --> 01:30:26.629 align:start position:0% it's needed um no i<01:30:25.920> don't<01:30:26.080> think<01:30:26.159> there's<01:30:26.400> anything 01:30:26.629 --> 01:30:26.639 align:start position:0% i don't think there's anything 01:30:26.639 --> 01:30:28.950 align:start position:0% i don't think there's anything controversial<01:30:27.280> about<01:30:27.440> that 01:30:28.950 --> 01:30:28.960 align:start position:0% controversial about that 01:30:28.960 --> 01:30:30.870 align:start position:0% controversial about that on<01:30:29.199> that<01:30:29.360> sir<01:30:29.760> um 01:30:30.870 --> 01:30:30.880 align:start position:0% on that sir um 01:30:30.880 --> 01:30:34.550 align:start position:0% on that sir um given<01:30:31.520> the<01:30:31.920> the<01:30:32.080> view<01:30:32.639> of<01:30:33.199> the<01:30:33.360> chart 01:30:34.550 --> 01:30:34.560 align:start position:0% given the the view of the chart 01:30:34.560 --> 01:30:36.709 align:start position:0% given the the view of the chart and 01:30:36.709 --> 01:30:36.719 align:start position:0% and 01:30:36.719 --> 01:30:38.629 align:start position:0% and a<01:30:36.880> resting<01:30:37.280> volatility 01:30:38.629 --> 01:30:38.639 align:start position:0% a resting volatility 01:30:38.639 --> 01:30:41.270 align:start position:0% a resting volatility right<01:30:38.880> now<01:30:39.199> the<01:30:39.360> program<01:30:39.920> is<01:30:40.000> envisioned<01:30:40.719> at 01:30:41.270 --> 01:30:41.280 align:start position:0% right now the program is envisioned at 01:30:41.280 --> 01:30:43.270 align:start position:0% right now the program is envisioned at 450<01:30:42.000> megawatts 01:30:43.270 --> 01:30:43.280 align:start position:0% 450 megawatts 01:30:43.280 --> 01:30:44.149 align:start position:0% 450 megawatts is 01:30:44.149 --> 01:30:44.159 align:start position:0% is 01:30:44.159 --> 01:30:45.910 align:start position:0% is and<01:30:44.239> again<01:30:44.560> i'm<01:30:44.639> just<01:30:44.800> trying<01:30:45.120> to 01:30:45.910 --> 01:30:45.920 align:start position:0% and again i'm just trying to 01:30:45.920 --> 01:30:48.790 align:start position:0% and again i'm just trying to absorb<01:30:46.400> as<01:30:46.560> much<01:30:47.199> cost<01:30:47.520> below<01:30:47.920> as<01:30:48.080> possible<01:30:48.560> so 01:30:48.790 --> 01:30:48.800 align:start position:0% absorb as much cost below as possible so 01:30:48.800 --> 01:30:50.709 align:start position:0% absorb as much cost below as possible so the<01:30:48.960> industry<01:30:49.360> the<01:30:49.520> markets<01:30:50.000> can<01:30:50.159> absorb<01:30:50.639> as 01:30:50.709 --> 01:30:50.719 align:start position:0% the industry the markets can absorb as 01:30:50.719 --> 01:30:54.709 align:start position:0% the industry the markets can absorb as much<01:30:50.960> of<01:30:51.040> this<01:30:51.600> over<01:30:51.840> a<01:30:51.920> long<01:30:52.239> spectrum 01:30:54.709 --> 01:30:54.719 align:start position:0% much of this over a long spectrum 01:30:54.719 --> 01:30:56.310 align:start position:0% much of this over a long spectrum now<01:30:55.199> as<01:30:55.360> possible<01:30:55.679> so<01:30:55.840> that<01:30:56.000> they're<01:30:56.159> not 01:30:56.310 --> 01:30:56.320 align:start position:0% now as possible so that they're not 01:30:56.320 --> 01:30:57.990 align:start position:0% now as possible so that they're not surprised<01:30:56.880> so<01:30:57.040> that<01:30:57.199> this<01:30:57.440> doesn't<01:30:57.679> catch 01:30:57.990 --> 01:30:58.000 align:start position:0% surprised so that this doesn't catch 01:30:58.000 --> 01:31:01.510 align:start position:0% surprised so that this doesn't catch consumers<01:30:58.800> flat-footed<01:30:59.840> my<01:31:00.080> question<01:31:00.400> is 01:31:01.510 --> 01:31:01.520 align:start position:0% consumers flat-footed my question is 01:31:01.520 --> 01:31:03.430 align:start position:0% consumers flat-footed my question is does<01:31:01.760> ercot<01:31:02.239> conceive<01:31:02.639> of<01:31:02.719> scenarios<01:31:03.360> to 01:31:03.430 --> 01:31:03.440 align:start position:0% does ercot conceive of scenarios to 01:31:03.440 --> 01:31:05.750 align:start position:0% does ercot conceive of scenarios to where<01:31:03.600> they<01:31:03.760> would<01:31:03.920> need<01:31:04.239> several<01:31:04.719> tranches 01:31:05.750 --> 01:31:05.760 align:start position:0% where they would need several tranches 01:31:05.760 --> 01:31:08.550 align:start position:0% where they would need several tranches of<01:31:06.000> 450<01:31:07.280> megawatt 01:31:08.550 --> 01:31:08.560 align:start position:0% of 450 megawatt 01:31:08.560 --> 01:31:10.950 align:start position:0% of 450 megawatt fast<01:31:08.880> frequency<01:31:09.440> response<01:31:10.320> in<01:31:10.400> the<01:31:10.560> event<01:31:10.800> of 01:31:10.950 --> 01:31:10.960 align:start position:0% fast frequency response in the event of 01:31:10.960 --> 01:31:12.550 align:start position:0% fast frequency response in the event of a<01:31:11.120> large<01:31:11.360> scale 01:31:12.550 --> 01:31:12.560 align:start position:0% a large scale 01:31:12.560 --> 01:31:13.430 align:start position:0% a large scale drop 01:31:13.430 --> 01:31:13.440 align:start position:0% drop 01:31:13.440 --> 01:31:16.070 align:start position:0% drop inertial<01:31:13.920> drop<01:31:14.320> akin<01:31:14.639> to<01:31:14.960> a<01:31:15.120> winter<01:31:15.360> storm 01:31:16.070 --> 01:31:16.080 align:start position:0% inertial drop akin to a winter storm 01:31:16.080 --> 01:31:18.149 align:start position:0% inertial drop akin to a winter storm yuri<01:31:16.480> type<01:31:16.719> event<01:31:17.360> again<01:31:17.679> that<01:31:17.840> would<01:31:18.000> be 01:31:18.149 --> 01:31:18.159 align:start position:0% yuri type event again that would be 01:31:18.159 --> 01:31:20.149 align:start position:0% yuri type event again that would be unexpected<01:31:18.880> rather<01:31:19.120> than<01:31:19.360> expected<01:31:19.840> which<01:31:20.080> is 01:31:20.149 --> 01:31:20.159 align:start position:0% unexpected rather than expected which is 01:31:20.159 --> 01:31:21.750 align:start position:0% unexpected rather than expected which is a<01:31:20.320> solar<01:31:20.800> duck 01:31:21.750 --> 01:31:21.760 align:start position:0% a solar duck 01:31:21.760 --> 01:31:24.709 align:start position:0% a solar duck um<01:31:22.320> so<01:31:22.560> more<01:31:22.960> more<01:31:23.360> quantity<01:31:23.760> than<01:31:23.920> the<01:31:24.000> 450 01:31:24.709 --> 01:31:24.719 align:start position:0% um so more more quantity than the 450 01:31:24.719 --> 01:31:26.470 align:start position:0% um so more more quantity than the 450 that's<01:31:25.040> my<01:31:25.199> understanding<01:31:25.520> of<01:31:25.920> the<01:31:26.080> program 01:31:26.470 --> 01:31:26.480 align:start position:0% that's my understanding of the program 01:31:26.480 --> 01:31:29.510 align:start position:0% that's my understanding of the program sir<01:31:26.800> is<01:31:27.040> they<01:31:27.280> acquire<01:31:27.920> 450<01:31:28.719> megawatts 01:31:29.510 --> 01:31:29.520 align:start position:0% sir is they acquire 450 megawatts 01:31:29.520 --> 01:31:30.790 align:start position:0% sir is they acquire 450 megawatts because<01:31:29.760> they<01:31:29.920> don't<01:31:30.080> want<01:31:30.239> to<01:31:30.320> overshoot 01:31:30.790 --> 01:31:30.800 align:start position:0% because they don't want to overshoot 01:31:30.800 --> 01:31:32.070 align:start position:0% because they don't want to overshoot because<01:31:30.960> it's<01:31:31.120> a<01:31:31.199> targeted<01:31:31.600> frequency 01:31:32.070 --> 01:31:32.080 align:start position:0% because it's a targeted frequency 01:31:32.080 --> 01:31:33.830 align:start position:0% because it's a targeted frequency response 01:31:33.830 --> 01:31:33.840 align:start position:0% response 01:31:33.840 --> 01:31:35.510 align:start position:0% response because<01:31:34.080> if<01:31:34.159> they<01:31:34.320> overshoot<01:31:35.040> in<01:31:35.120> terms<01:31:35.360> of 01:31:35.510 --> 01:31:35.520 align:start position:0% because if they overshoot in terms of 01:31:35.520 --> 01:31:37.750 align:start position:0% because if they overshoot in terms of the<01:31:35.600> procurement<01:31:36.320> then<01:31:36.560> it<01:31:36.719> spikes<01:31:37.280> frequency 01:31:37.750 --> 01:31:37.760 align:start position:0% the procurement then it spikes frequency 01:31:37.760 --> 01:31:39.510 align:start position:0% the procurement then it spikes frequency to<01:31:37.920> the<01:31:38.000> upper<01:31:38.239> bounds<01:31:38.560> which<01:31:38.719> is<01:31:38.880> a<01:31:38.960> problem 01:31:39.510 --> 01:31:39.520 align:start position:0% to the upper bounds which is a problem 01:31:39.520 --> 01:31:41.110 align:start position:0% to the upper bounds which is a problem as<01:31:39.840> as<01:31:40.000> we<01:31:40.239> saw 01:31:41.110 --> 01:31:41.120 align:start position:0% as as we saw 01:31:41.120 --> 01:31:42.390 align:start position:0% as as we saw so 01:31:42.390 --> 01:31:42.400 align:start position:0% so 01:31:42.400 --> 01:31:45.030 align:start position:0% so do<01:31:42.560> you<01:31:42.719> need<01:31:43.120> several<01:31:43.520> tranches<01:31:44.159> of<01:31:44.320> 450 01:31:45.030 --> 01:31:45.040 align:start position:0% do you need several tranches of 450 01:31:45.040 --> 01:31:46.310 align:start position:0% do you need several tranches of 450 ready<01:31:45.360> to<01:31:45.440> go 01:31:46.310 --> 01:31:46.320 align:start position:0% ready to go 01:31:46.320 --> 01:31:49.910 align:start position:0% ready to go uh<01:31:46.800> at<01:31:47.120> on<01:31:47.440> a<01:31:47.520> seasonal<01:31:48.000> basis<01:31:48.719> um 01:31:49.910 --> 01:31:49.920 align:start position:0% uh at on a seasonal basis um 01:31:49.920 --> 01:31:51.750 align:start position:0% uh at on a seasonal basis um in<01:31:50.000> the<01:31:50.080> event<01:31:50.480> of<01:31:50.880> winter<01:31:51.199> storm<01:31:51.440> hearing 01:31:51.750 --> 01:31:51.760 align:start position:0% in the event of winter storm hearing 01:31:51.760 --> 01:31:54.070 align:start position:0% in the event of winter storm hearing part<01:31:52.000> two<01:31:52.719> uh<01:31:53.040> it<01:31:53.199> sounds<01:31:53.520> like<01:31:53.679> a<01:31:53.760> woody 01:31:54.070 --> 01:31:54.080 align:start position:0% part two uh it sounds like a woody 01:31:54.080 --> 01:31:55.990 align:start position:0% part two uh it sounds like a woody question<01:31:54.320> yes<01:31:54.560> sir<01:31:54.800> um 01:31:55.990 --> 01:31:56.000 align:start position:0% question yes sir um 01:31:56.000 --> 01:31:57.110 align:start position:0% question yes sir um and 01:31:57.110 --> 01:31:57.120 align:start position:0% and 01:31:57.120 --> 01:31:59.590 align:start position:0% and i'd<01:31:57.520> also<01:31:57.920> want<01:31:58.080> to<01:31:58.560> ask<01:31:58.800> him<01:31:58.960> to<01:31:59.120> distinguish 01:31:59.590 --> 01:31:59.600 align:start position:0% i'd also want to ask him to distinguish 01:31:59.600 --> 01:32:01.510 align:start position:0% i'd also want to ask him to distinguish between<01:31:59.920> the<01:32:00.000> procurement<01:32:00.560> and<01:32:00.639> deployment 01:32:01.510 --> 01:32:01.520 align:start position:0% between the procurement and deployment 01:32:01.520 --> 01:32:09.270 align:start position:0% between the procurement and deployment of<01:32:02.000> of<01:32:02.159> those<01:32:02.400> resources<01:32:03.199> yes<01:32:03.360> sir 01:32:09.270 --> 01:32:09.280 align:start position:0% 01:32:09.280 --> 01:32:12.390 align:start position:0% so<01:32:09.840> the<01:32:10.080> answer<01:32:10.400> is<01:32:10.719> no<01:32:11.199> okay 01:32:12.390 --> 01:32:12.400 align:start position:0% so the answer is no okay 01:32:12.400 --> 01:32:15.110 align:start position:0% so the answer is no okay you<01:32:12.560> would<01:32:12.880> uh<01:32:13.280> backfill<01:32:13.760> for<01:32:14.000> it<01:32:14.320> you'd<01:32:14.639> use 01:32:15.110 --> 01:32:15.120 align:start position:0% you would uh backfill for it you'd use 01:32:15.120 --> 01:32:17.270 align:start position:0% you would uh backfill for it you'd use bring<01:32:15.280> up<01:32:15.440> something<01:32:15.840> else<01:32:16.080> to<01:32:16.239> restore<01:32:16.719> it<01:32:17.040> so 01:32:17.270 --> 01:32:17.280 align:start position:0% bring up something else to restore it so 01:32:17.280 --> 01:32:19.750 align:start position:0% bring up something else to restore it so it's<01:32:17.440> there<01:32:17.840> so<01:32:18.000> you<01:32:18.080> could<01:32:18.239> use<01:32:18.480> it<01:32:18.560> again 01:32:19.750 --> 01:32:19.760 align:start position:0% it's there so you could use it again 01:32:19.760 --> 01:32:22.149 align:start position:0% it's there so you could use it again okay<01:32:20.159> that<01:32:20.320> makes<01:32:20.560> sense 01:32:22.149 --> 01:32:22.159 align:start position:0% okay that makes sense 01:32:22.159 --> 01:32:24.709 align:start position:0% okay that makes sense just<01:32:22.400> like<01:32:22.480> we<01:32:22.560> do<01:32:22.719> with<01:32:22.800> the<01:32:22.880> regulation<01:32:23.440> now 01:32:24.709 --> 01:32:24.719 align:start position:0% just like we do with the regulation now 01:32:24.719 --> 01:32:26.790 align:start position:0% just like we do with the regulation now so<01:32:24.960> if<01:32:25.120> we<01:32:25.440> run<01:32:25.600> out<01:32:25.760> of<01:32:25.920> upright<01:32:26.400> we<01:32:26.560> bring 01:32:26.790 --> 01:32:26.800 align:start position:0% so if we run out of upright we bring 01:32:26.800 --> 01:32:28.390 align:start position:0% so if we run out of upright we bring something<01:32:27.120> else<01:32:27.360> in 01:32:28.390 --> 01:32:28.400 align:start position:0% something else in 01:32:28.400 --> 01:32:30.550 align:start position:0% something else in let<01:32:28.560> that<01:32:28.880> upper<01:32:29.120> egg<01:32:29.440> go<01:32:29.600> back<01:32:29.760> to<01:32:29.920> zero<01:32:30.239> so<01:32:30.400> we 01:32:30.550 --> 01:32:30.560 align:start position:0% let that upper egg go back to zero so we 01:32:30.560 --> 01:32:32.149 align:start position:0% let that upper egg go back to zero so we have<01:32:30.719> it<01:32:30.880> in<01:32:30.960> our<01:32:31.040> pocket<01:32:31.440> for<01:32:31.600> the<01:32:31.679> next<01:32:31.840> time 01:32:32.149 --> 01:32:32.159 align:start position:0% have it in our pocket for the next time 01:32:32.159 --> 01:32:33.910 align:start position:0% have it in our pocket for the next time you<01:32:32.239> think<01:32:32.400> you'll<01:32:32.560> have<01:32:32.719> enough<01:32:33.440> i'll<01:32:33.600> defer 01:32:33.910 --> 01:32:33.920 align:start position:0% you think you'll have enough i'll defer 01:32:33.920 --> 01:32:35.910 align:start position:0% you think you'll have enough i'll defer to<01:32:34.320> commissioner<01:32:34.800> uh<01:32:35.199> kobe's<01:32:35.520> but<01:32:35.679> do<01:32:35.840> you 01:32:35.910 --> 01:32:35.920 align:start position:0% to commissioner uh kobe's but do you 01:32:35.920 --> 01:32:37.350 align:start position:0% to commissioner uh kobe's but do you think<01:32:36.000> you'll<01:32:36.159> have<01:32:36.320> enough<01:32:36.560> because<01:32:36.880> again 01:32:37.350 --> 01:32:37.360 align:start position:0% think you'll have enough because again 01:32:37.360 --> 01:32:39.750 align:start position:0% think you'll have enough because again the<01:32:37.440> whole<01:32:37.679> point<01:32:37.920> of<01:32:38.400> ffrs<01:32:39.040> is<01:32:39.199> you<01:32:39.280> have<01:32:39.440> near 01:32:39.750 --> 01:32:39.760 align:start position:0% the whole point of ffrs is you have near 01:32:39.760 --> 01:32:41.669 align:start position:0% the whole point of ffrs is you have near instantaneous<01:32:40.480> response<01:32:41.199> so<01:32:41.360> you<01:32:41.520> have 01:32:41.669 --> 01:32:41.679 align:start position:0% instantaneous response so you have 01:32:41.679 --> 01:32:43.030 align:start position:0% instantaneous response so you have enough<01:32:42.000> kind<01:32:42.159> of 01:32:43.030 --> 01:32:43.040 align:start position:0% enough kind of 01:32:43.040 --> 01:32:44.390 align:start position:0% enough kind of in<01:32:43.120> the<01:32:43.199> rest<01:32:43.440> of<01:32:43.520> the<01:32:43.600> system<01:32:43.920> that<01:32:44.080> can<01:32:44.239> do 01:32:44.390 --> 01:32:44.400 align:start position:0% in the rest of the system that can do 01:32:44.400 --> 01:32:46.310 align:start position:0% in the rest of the system that can do that<01:32:44.560> if<01:32:44.800> the<01:32:45.280> there's<01:32:45.440> no<01:32:45.679> ramp<01:32:46.000> that's 01:32:46.310 --> 01:32:46.320 align:start position:0% that if the there's no ramp that's 01:32:46.320 --> 01:32:48.709 align:start position:0% that if the there's no ramp that's instantaneous<01:32:47.040> response<01:32:47.520> to<01:32:47.679> fill<01:32:47.920> that<01:32:48.560> that 01:32:48.709 --> 01:32:48.719 align:start position:0% instantaneous response to fill that that 01:32:48.719 --> 01:32:49.750 align:start position:0% instantaneous response to fill that that performance<01:32:49.040> that<01:32:49.199> would<01:32:49.280> be<01:32:49.440> the<01:32:49.520> way<01:32:49.679> it 01:32:49.750 --> 01:32:49.760 align:start position:0% performance that would be the way it 01:32:49.760 --> 01:32:51.590 align:start position:0% performance that would be the way it would<01:32:49.840> be<01:32:50.000> designed<01:32:50.719> it<01:32:50.800> wouldn't<01:32:51.040> be<01:32:51.120> as<01:32:51.280> fast 01:32:51.590 --> 01:32:51.600 align:start position:0% would be designed it wouldn't be as fast 01:32:51.600 --> 01:32:55.189 align:start position:0% would be designed it wouldn't be as fast as<01:32:51.760> the<01:32:51.840> ffr<01:32:52.719> uh 01:32:55.189 --> 01:32:55.199 align:start position:0% as the ffr uh 01:32:55.199 --> 01:32:56.629 align:start position:0% as the ffr uh you'd<01:32:55.440> ramp<01:32:55.679> it<01:32:55.840> up 01:32:56.629 --> 01:32:56.639 align:start position:0% you'd ramp it up 01:32:56.639 --> 01:32:58.790 align:start position:0% you'd ramp it up replace<01:32:57.040> the<01:32:57.199> ffr<01:32:58.000> and<01:32:58.159> have<01:32:58.320> it<01:32:58.400> go<01:32:58.560> back<01:32:58.639> to 01:32:58.790 --> 01:32:58.800 align:start position:0% replace the ffr and have it go back to 01:32:58.800 --> 01:33:00.390 align:start position:0% replace the ffr and have it go back to zero<01:32:59.120> and<01:32:59.199> have<01:32:59.280> it<01:32:59.440> available<01:32:59.920> for<01:33:00.080> the<01:33:00.159> next 01:33:00.390 --> 01:33:00.400 align:start position:0% zero and have it available for the next 01:33:00.400 --> 01:33:02.070 align:start position:0% zero and have it available for the next one<01:33:00.880> yeah<01:33:01.120> okay 01:33:02.070 --> 01:33:02.080 align:start position:0% one yeah okay 01:33:02.080 --> 01:33:03.830 align:start position:0% one yeah okay so<01:33:02.320> i<01:33:02.560> think<01:33:02.719> your<01:33:02.960> question<01:33:03.520> commissioner 01:33:03.830 --> 01:33:03.840 align:start position:0% so i think your question commissioner 01:33:03.840 --> 01:33:05.830 align:start position:0% so i think your question commissioner mcadams<01:33:04.400> is<01:33:04.960> i'm<01:33:05.120> just<01:33:05.280> trying<01:33:05.440> to<01:33:05.520> make<01:33:05.600> sure 01:33:05.830 --> 01:33:05.840 align:start position:0% mcadams is i'm just trying to make sure 01:33:05.840 --> 01:33:07.189 align:start position:0% mcadams is i'm just trying to make sure before<01:33:06.080> i<01:33:06.159> ask 01:33:07.189 --> 01:33:07.199 align:start position:0% before i ask 01:33:07.199 --> 01:33:09.590 align:start position:0% before i ask additional<01:33:07.520> questions<01:33:08.080> um<01:33:08.480> is<01:33:09.199> whether<01:33:09.520> or 01:33:09.590 --> 01:33:09.600 align:start position:0% additional questions um is whether or 01:33:09.600 --> 01:33:11.590 align:start position:0% additional questions um is whether or not<01:33:09.840> we<01:33:10.000> should<01:33:10.239> be<01:33:10.719> whether<01:33:11.040> or<01:33:11.120> not<01:33:11.280> ercot 01:33:11.590 --> 01:33:11.600 align:start position:0% not we should be whether or not ercot 01:33:11.600 --> 01:33:14.149 align:start position:0% not we should be whether or not ercot should<01:33:11.760> be<01:33:11.840> procuring<01:33:12.320> more<01:33:12.639> ffrs<01:33:13.440> to<01:33:13.600> help 01:33:14.149 --> 01:33:14.159 align:start position:0% should be procuring more ffrs to help 01:33:14.159 --> 01:33:15.430 align:start position:0% should be procuring more ffrs to help manage<01:33:14.639> with 01:33:15.430 --> 01:33:15.440 align:start position:0% manage with 01:33:15.440 --> 01:33:18.790 align:start position:0% manage with the<01:33:15.840> frequency<01:33:16.800> issue<01:33:17.120> that<01:33:17.280> we<01:33:17.440> may<01:33:17.920> have<01:33:18.560> uh 01:33:18.790 --> 01:33:18.800 align:start position:0% the frequency issue that we may have uh 01:33:18.800 --> 01:33:20.470 align:start position:0% the frequency issue that we may have uh with<01:33:18.960> the<01:33:19.120> solar<01:33:19.360> deck<01:33:19.520> current 01:33:20.470 --> 01:33:20.480 align:start position:0% with the solar deck current 01:33:20.480 --> 01:33:23.750 align:start position:0% with the solar deck current well<01:33:20.880> actually<01:33:21.280> on<01:33:21.520> on<01:33:22.000> that<01:33:22.159> commissioner 01:33:23.750 --> 01:33:23.760 align:start position:0% well actually on on that commissioner 01:33:23.760 --> 01:33:27.189 align:start position:0% well actually on on that commissioner again<01:33:24.000> i<01:33:24.159> think<01:33:24.320> ecrs<01:33:25.040> is<01:33:25.199> being<01:33:25.440> developed 01:33:27.189 --> 01:33:27.199 align:start position:0% again i think ecrs is being developed 01:33:27.199 --> 01:33:29.110 align:start position:0% again i think ecrs is being developed solar<01:33:27.520> duct<01:33:27.760> curve<01:33:28.080> occurs 01:33:29.110 --> 01:33:29.120 align:start position:0% solar duct curve occurs 01:33:29.120 --> 01:33:30.870 align:start position:0% solar duct curve occurs with<01:33:29.280> a<01:33:29.360> degree<01:33:29.679> of<01:33:29.840> frequency<01:33:30.320> to<01:33:30.480> where<01:33:30.719> they 01:33:30.870 --> 01:33:30.880 align:start position:0% with a degree of frequency to where they 01:33:30.880 --> 01:33:33.110 align:start position:0% with a degree of frequency to where they can<01:33:31.040> manage<01:33:31.440> it<01:33:31.920> and<01:33:32.239> as<01:33:32.480> it's<01:33:32.560> been<01:33:32.719> proposed 01:33:33.110 --> 01:33:33.120 align:start position:0% can manage it and as it's been proposed 01:33:33.120 --> 01:33:36.390 align:start position:0% can manage it and as it's been proposed to<01:33:33.199> me<01:33:33.360> they<01:33:33.520> can<01:33:33.600> manage<01:33:34.000> it<01:33:34.080> with<01:33:34.400> ecrs<01:33:35.600> ffrs 01:33:36.390 --> 01:33:36.400 align:start position:0% to me they can manage it with ecrs ffrs 01:33:36.400 --> 01:33:39.669 align:start position:0% to me they can manage it with ecrs ffrs is<01:33:36.560> again<01:33:36.880> those<01:33:37.679> um<01:33:38.239> unexpected<01:33:39.040> spikes<01:33:39.520> in 01:33:39.669 --> 01:33:39.679 align:start position:0% is again those um unexpected spikes in 01:33:39.679 --> 01:33:41.750 align:start position:0% is again those um unexpected spikes in frequency<01:33:40.320> that<01:33:40.800> they<01:33:40.960> need<01:33:41.120> to<01:33:41.280> arrest 01:33:41.750 --> 01:33:41.760 align:start position:0% frequency that they need to arrest 01:33:41.760 --> 01:33:45.270 align:start position:0% frequency that they need to arrest instantaneously<01:33:42.960> okay<01:33:43.120> so<01:33:43.520> so<01:33:43.920> uh<01:33:44.480> seconds 01:33:45.270 --> 01:33:45.280 align:start position:0% instantaneously okay so so uh seconds 01:33:45.280 --> 01:33:47.110 align:start position:0% instantaneously okay so so uh seconds yes<01:33:45.600> yeah<01:33:45.760> so<01:33:45.920> it's<01:33:46.080> a<01:33:46.159> broader<01:33:46.719> broader 01:33:47.110 --> 01:33:47.120 align:start position:0% yes yeah so it's a broader broader 01:33:47.120 --> 01:33:49.430 align:start position:0% yes yeah so it's a broader broader question<01:33:47.760> if<01:33:47.920> we<01:33:48.000> need<01:33:48.239> more<01:33:48.400> than<01:33:48.560> just<01:33:48.719> 450 01:33:49.430 --> 01:33:49.440 align:start position:0% question if we need more than just 450 01:33:49.440 --> 01:33:51.430 align:start position:0% question if we need more than just 450 megawatts<01:33:50.159> okay 01:33:51.430 --> 01:33:51.440 align:start position:0% megawatts okay 01:33:51.440 --> 01:33:52.550 align:start position:0% megawatts okay um 01:33:52.550 --> 01:33:52.560 align:start position:0% um 01:33:52.560 --> 01:33:53.350 align:start position:0% um okay 01:33:53.350 --> 01:33:53.360 align:start position:0% okay 01:33:53.360 --> 01:33:55.669 align:start position:0% okay and<01:33:53.520> so<01:33:53.679> the<01:33:53.840> answer<01:33:54.159> is<01:33:54.239> no<01:33:54.719> right<01:33:55.360> good 01:33:55.669 --> 01:33:55.679 align:start position:0% and so the answer is no right good 01:33:55.679 --> 01:33:57.110 align:start position:0% and so the answer is no right good because<01:33:55.840> you<01:33:55.920> would<01:33:56.080> backfill<01:33:56.480> it<01:33:56.560> with<01:33:56.719> other 01:33:57.110 --> 01:33:57.120 align:start position:0% because you would backfill it with other 01:33:57.120 --> 01:33:59.830 align:start position:0% because you would backfill it with other ancillary<01:33:57.520> services<01:33:58.080> okay 01:33:59.830 --> 01:33:59.840 align:start position:0% ancillary services okay 01:33:59.840 --> 01:34:02.229 align:start position:0% ancillary services okay i'm<01:34:00.000> good<01:34:00.400> thank<01:34:00.560> you<01:34:00.719> woody<01:34:01.199> thanks 01:34:02.229 --> 01:34:02.239 align:start position:0% i'm good thank you woody thanks 01:34:02.239 --> 01:34:04.629 align:start position:0% i'm good thank you woody thanks all<01:34:02.480> right<01:34:02.880> uh<01:34:03.920> sounds<01:34:04.159> like<01:34:04.320> everybody's 01:34:04.629 --> 01:34:04.639 align:start position:0% all right uh sounds like everybody's 01:34:04.639 --> 01:34:07.990 align:start position:0% all right uh sounds like everybody's pretty<01:34:04.880> squared<01:34:05.199> away<01:34:05.360> with<01:34:05.520> ffrs<01:34:06.400> uh 01:34:07.990 --> 01:34:08.000 align:start position:0% pretty squared away with ffrs uh 01:34:08.000 --> 01:34:10.229 align:start position:0% pretty squared away with ffrs uh next<01:34:08.400> up<01:34:08.639> would<01:34:08.800> be 01:34:10.229 --> 01:34:10.239 align:start position:0% next up would be 01:34:10.239 --> 01:34:11.990 align:start position:0% next up would be winter<01:34:10.639> firming<01:34:11.120> product<01:34:11.600> and<01:34:11.679> this<01:34:11.920> is 01:34:11.990 --> 01:34:12.000 align:start position:0% winter firming product and this is 01:34:12.000 --> 01:34:14.070 align:start position:0% winter firming product and this is another<01:34:12.320> item<01:34:12.639> where<01:34:12.880> we<01:34:13.040> don't<01:34:13.600> quite<01:34:13.840> have 01:34:14.070 --> 01:34:14.080 align:start position:0% another item where we don't quite have 01:34:14.080 --> 01:34:16.950 align:start position:0% another item where we don't quite have all<01:34:14.239> the<01:34:14.800> scenario<01:34:15.280> analysis<01:34:15.840> and<01:34:16.320> menu<01:34:16.800> of 01:34:16.950 --> 01:34:16.960 align:start position:0% all the scenario analysis and menu of 01:34:16.960 --> 01:34:19.270 align:start position:0% all the scenario analysis and menu of options<01:34:17.440> and<01:34:17.600> definitions<01:34:18.400> that<01:34:18.880> we<01:34:19.040> were 01:34:19.270 --> 01:34:19.280 align:start position:0% options and definitions that we were 01:34:19.280 --> 01:34:20.629 align:start position:0% options and definitions that we were hoping<01:34:19.600> to<01:34:19.679> have 01:34:20.629 --> 01:34:20.639 align:start position:0% hoping to have 01:34:20.639 --> 01:34:24.870 align:start position:0% hoping to have so<01:34:20.800> we'll<01:34:20.960> have<01:34:21.120> to<01:34:21.199> put<01:34:21.440> a<01:34:21.760> tbd<01:34:22.320> here<01:34:23.120> but<01:34:23.760> um 01:34:24.870 --> 01:34:24.880 align:start position:0% so we'll have to put a tbd here but um 01:34:24.880 --> 01:34:26.149 align:start position:0% so we'll have to put a tbd here but um of<01:34:24.960> course<01:34:25.120> if<01:34:25.280> anybody<01:34:25.520> has<01:34:25.679> the<01:34:25.760> updated 01:34:26.149 --> 01:34:26.159 align:start position:0% of course if anybody has the updated 01:34:26.159 --> 01:34:27.510 align:start position:0% of course if anybody has the updated thoughts 01:34:27.510 --> 01:34:27.520 align:start position:0% thoughts 01:34:27.520 --> 01:34:28.310 align:start position:0% thoughts that 01:34:28.310 --> 01:34:28.320 align:start position:0% that 01:34:28.320 --> 01:34:30.709 align:start position:0% that happy<01:34:28.639> to<01:34:28.800> hear<01:34:29.040> them<01:34:29.280> i<01:34:29.360> would<01:34:29.760> ask<01:34:30.080> that<01:34:30.400> as 01:34:30.709 --> 01:34:30.719 align:start position:0% happy to hear them i would ask that as 01:34:30.719 --> 01:34:32.790 align:start position:0% happy to hear them i would ask that as we 01:34:32.790 --> 01:34:32.800 align:start position:0% we 01:34:32.800 --> 01:34:34.149 align:start position:0% we each<01:34:32.960> of<01:34:33.120> our<01:34:33.199> offices<01:34:33.600> moves<01:34:33.840> through<01:34:34.080> the 01:34:34.149 --> 01:34:34.159 align:start position:0% each of our offices moves through the 01:34:34.159 --> 01:34:36.070 align:start position:0% each of our offices moves through the next<01:34:34.639> couple<01:34:34.880> of<01:34:35.040> weeks 01:34:36.070 --> 01:34:36.080 align:start position:0% next couple of weeks 01:34:36.080 --> 01:34:37.610 align:start position:0% next couple of weeks i<01:34:36.159> know<01:34:36.320> we<01:34:36.480> want<01:34:36.639> to<01:34:36.719> get<01:34:36.960> away<01:34:37.280> from 01:34:37.610 --> 01:34:37.620 align:start position:0% i know we want to get away from 01:34:37.620 --> 01:34:39.910 align:start position:0% i know we want to get away from [Music] 01:34:39.910 --> 01:34:39.920 align:start position:0% [Music] 01:34:39.920 --> 01:34:41.189 align:start position:0% [Music] multiple<01:34:40.320> questions<01:34:40.639> to<01:34:40.719> the<01:34:40.800> broader 01:34:41.189 --> 01:34:41.199 align:start position:0% multiple questions to the broader 01:34:41.199 --> 01:34:42.629 align:start position:0% multiple questions to the broader universe<01:34:41.600> that<01:34:41.760> all<01:34:41.840> our<01:34:42.000> stakeholders<01:34:42.480> have 01:34:42.629 --> 01:34:42.639 align:start position:0% universe that all our stakeholders have 01:34:42.639 --> 01:34:44.310 align:start position:0% universe that all our stakeholders have to 01:34:44.310 --> 01:34:44.320 align:start position:0% to 01:34:44.320 --> 01:34:46.629 align:start position:0% to respond<01:34:44.719> to<01:34:44.880> and<01:34:45.040> our<01:34:45.119> staff's<01:34:45.520> gotta 01:34:46.629 --> 01:34:46.639 align:start position:0% respond to and our staff's gotta 01:34:46.639 --> 01:34:48.790 align:start position:0% respond to and our staff's gotta uh<01:34:47.280> to<01:34:47.600> process 01:34:48.790 --> 01:34:48.800 align:start position:0% uh to process 01:34:48.800 --> 01:34:50.870 align:start position:0% uh to process so<01:34:49.199> i<01:34:49.360> would<01:34:49.600> ask<01:34:49.920> that<01:34:50.239> as<01:34:50.400> we<01:34:50.560> go<01:34:50.639> through<01:34:50.800> the 01:34:50.870 --> 01:34:50.880 align:start position:0% so i would ask that as we go through the 01:34:50.880 --> 01:34:53.270 align:start position:0% so i would ask that as we go through the next<01:34:51.040> couple<01:34:51.360> weeks<01:34:51.600> each<01:34:51.920> office<01:34:52.719> put<01:34:52.960> pen<01:34:53.119> to 01:34:53.270 --> 01:34:53.280 align:start position:0% next couple weeks each office put pen to 01:34:53.280 --> 01:34:55.669 align:start position:0% next couple weeks each office put pen to paper<01:34:53.600> on<01:34:53.840> what<01:34:54.000> they<01:34:54.400> individually<01:34:55.199> think 01:34:55.669 --> 01:34:55.679 align:start position:0% paper on what they individually think 01:34:55.679 --> 01:34:56.790 align:start position:0% paper on what they individually think would<01:34:55.840> be 01:34:56.790 --> 01:34:56.800 align:start position:0% would be 01:34:56.800 --> 01:35:00.390 align:start position:0% would be uh<01:34:57.360> good 01:35:00.390 --> 01:35:00.400 align:start position:0% 01:35:00.400 --> 01:35:03.030 align:start position:0% a<01:35:00.560> good<01:35:00.880> definition<01:35:01.520> or<01:35:01.920> framework<01:35:02.400> for<01:35:02.800> the 01:35:03.030 --> 01:35:03.040 align:start position:0% a good definition or framework for the 01:35:03.040 --> 01:35:04.390 align:start position:0% a good definition or framework for the fuel<01:35:03.360> standards 01:35:04.390 --> 01:35:04.400 align:start position:0% fuel standards 01:35:04.400 --> 01:35:06.390 align:start position:0% fuel standards you<01:35:04.480> know<01:35:04.639> dual<01:35:04.880> fuel<01:35:05.280> on<01:35:05.520> site<01:35:05.920> offsite 01:35:06.390 --> 01:35:06.400 align:start position:0% you know dual fuel on site offsite 01:35:06.400 --> 01:35:09.270 align:start position:0% you know dual fuel on site offsite storage<01:35:07.360> uh<01:35:07.679> reserve<01:35:08.159> you<01:35:08.320> know<01:35:08.960> firm 01:35:09.270 --> 01:35:09.280 align:start position:0% storage uh reserve you know firm 01:35:09.280 --> 01:35:11.189 align:start position:0% storage uh reserve you know firm transport<01:35:09.760> from<01:35:10.320> uh 01:35:11.189 --> 01:35:11.199 align:start position:0% transport from uh 01:35:11.199 --> 01:35:15.270 align:start position:0% transport from uh molecules<01:35:12.320> uh<01:35:12.719> also<01:35:13.199> duration 01:35:15.270 --> 01:35:15.280 align:start position:0% molecules uh also duration 01:35:15.280 --> 01:35:19.189 align:start position:0% molecules uh also duration uh<01:35:15.679> and<01:35:15.840> then<01:35:16.239> structure<01:35:17.280> they<01:35:17.679> use<01:35:18.000> existing 01:35:19.189 --> 01:35:19.199 align:start position:0% uh and then structure they use existing 01:35:19.199 --> 01:35:21.270 align:start position:0% uh and then structure they use existing if<01:35:19.360> we<01:35:19.440> do<01:35:19.520> an<01:35:19.679> independent<01:35:20.080> a<01:35:20.239> s<01:35:20.560> winner<01:35:20.880> as<01:35:21.199> do 01:35:21.270 --> 01:35:21.280 align:start position:0% if we do an independent a s winner as do 01:35:21.280 --> 01:35:23.430 align:start position:0% if we do an independent a s winner as do we<01:35:21.360> do<01:35:21.600> existing<01:35:22.239> what<01:35:22.480> structure 01:35:23.430 --> 01:35:23.440 align:start position:0% we do existing what structure 01:35:23.440 --> 01:35:26.390 align:start position:0% we do existing what structure existing<01:35:23.840> block<01:35:24.080> start<01:35:24.400> structure<01:35:25.119> or 01:35:26.390 --> 01:35:26.400 align:start position:0% existing block start structure or 01:35:26.400 --> 01:35:28.390 align:start position:0% existing block start structure or another<01:35:27.040> mechanism 01:35:28.390 --> 01:35:28.400 align:start position:0% another mechanism 01:35:28.400 --> 01:35:30.390 align:start position:0% another mechanism that<01:35:28.560> may<01:35:28.719> already<01:35:28.960> exist<01:35:29.280> or<01:35:29.920> one<01:35:30.159> to<01:35:30.239> be 01:35:30.390 --> 01:35:30.400 align:start position:0% that may already exist or one to be 01:35:30.400 --> 01:35:31.350 align:start position:0% that may already exist or one to be created 01:35:31.350 --> 01:35:31.360 align:start position:0% created 01:35:31.360 --> 01:35:33.510 align:start position:0% created and<01:35:31.520> of<01:35:31.600> course 01:35:33.510 --> 01:35:33.520 align:start position:0% and of course 01:35:33.520 --> 01:35:35.590 align:start position:0% and of course there<01:35:33.679> will<01:35:33.920> be<01:35:34.320> i'm<01:35:34.880> sure<01:35:35.040> we'll<01:35:35.280> all<01:35:35.360> have 01:35:35.590 --> 01:35:35.600 align:start position:0% there will be i'm sure we'll all have 01:35:35.600 --> 01:35:38.629 align:start position:0% there will be i'm sure we'll all have questions<01:35:36.159> but<01:35:36.400> in<01:35:36.480> the<01:35:36.639> sake<01:35:36.880> of 01:35:38.629 --> 01:35:38.639 align:start position:0% questions but in the sake of 01:35:38.639 --> 01:35:41.030 align:start position:0% questions but in the sake of streamlining<01:35:39.199> this<01:35:39.360> process 01:35:41.030 --> 01:35:41.040 align:start position:0% streamlining this process 01:35:41.040 --> 01:35:42.709 align:start position:0% streamlining this process please<01:35:41.360> pursue<01:35:41.679> those<01:35:42.080> lines<01:35:42.320> of<01:35:42.400> questions 01:35:42.709 --> 01:35:42.719 align:start position:0% please pursue those lines of questions 01:35:42.719 --> 01:35:44.070 align:start position:0% please pursue those lines of questions with<01:35:42.880> whatever<01:35:43.199> stakeholders<01:35:43.760> you<01:35:43.920> think 01:35:44.070 --> 01:35:44.080 align:start position:0% with whatever stakeholders you think 01:35:44.080 --> 01:35:45.430 align:start position:0% with whatever stakeholders you think most<01:35:44.400> appropriate 01:35:45.430 --> 01:35:45.440 align:start position:0% most appropriate 01:35:45.440 --> 01:35:46.870 align:start position:0% most appropriate independently 01:35:46.870 --> 01:35:46.880 align:start position:0% independently 01:35:46.880 --> 01:35:48.470 align:start position:0% independently i 01:35:48.470 --> 01:35:48.480 align:start position:0% i 01:35:48.480 --> 01:35:49.990 align:start position:0% i think<01:35:48.719> you'll<01:35:49.360> still<01:35:49.520> get<01:35:49.679> plenty<01:35:49.920> of 01:35:49.990 --> 01:35:50.000 align:start position:0% think you'll still get plenty of 01:35:50.000 --> 01:35:52.229 align:start position:0% think you'll still get plenty of responses 01:35:52.229 --> 01:35:52.239 align:start position:0% responses 01:35:52.239 --> 01:35:54.870 align:start position:0% responses any<01:35:52.560> any<01:35:52.800> other<01:35:53.199> thoughts<01:35:53.520> on<01:35:53.840> winter<01:35:54.239> as 01:35:54.870 --> 01:35:54.880 align:start position:0% any any other thoughts on winter as 01:35:54.880 --> 01:35:56.950 align:start position:0% any any other thoughts on winter as right<01:35:55.040> now<01:35:55.360> i<01:35:55.440> think<01:35:55.679> it's<01:35:55.840> a<01:35:55.920> pretty 01:35:56.950 --> 01:35:56.960 align:start position:0% right now i think it's a pretty 01:35:56.960 --> 01:35:58.709 align:start position:0% right now i think it's a pretty it's<01:35:57.199> a<01:35:57.280> pretty<01:35:57.520> well<01:35:57.679> defined<01:35:58.080> universe<01:35:58.560> we 01:35:58.709 --> 01:35:58.719 align:start position:0% it's a pretty well defined universe we 01:35:58.719 --> 01:36:00.390 align:start position:0% it's a pretty well defined universe we just<01:35:58.880> need<01:35:59.040> to<01:35:59.199> get<01:35:59.360> some<01:35:59.520> menu<01:35:59.840> of<01:36:00.000> options<01:36:00.320> in 01:36:00.390 --> 01:36:00.400 align:start position:0% just need to get some menu of options in 01:36:00.400 --> 01:36:03.669 align:start position:0% just need to get some menu of options in front<01:36:00.560> of<01:36:00.719> us<01:36:00.880> from<01:36:01.040> our<01:36:01.280> various<01:36:02.000> vendors<01:36:02.400> and 01:36:03.669 --> 01:36:03.679 align:start position:0% front of us from our various vendors and 01:36:03.679 --> 01:36:06.470 align:start position:0% front of us from our various vendors and start<01:36:04.239> start<01:36:04.400> nailing<01:36:04.719> down<01:36:04.880> what<01:36:05.119> that<01:36:05.280> could 01:36:06.470 --> 01:36:06.480 align:start position:0% start start nailing down what that could 01:36:06.480 --> 01:36:08.550 align:start position:0% start start nailing down what that could that<01:36:06.639> could<01:36:06.800> look<01:36:07.040> like 01:36:08.550 --> 01:36:08.560 align:start position:0% that could look like 01:36:08.560 --> 01:36:11.109 align:start position:0% that could look like from<01:36:08.719> my<01:36:08.880> perspective<01:36:09.679> and<01:36:09.840> thank<01:36:10.000> you<01:36:10.239> for<01:36:10.719> um 01:36:11.109 --> 01:36:11.119 align:start position:0% from my perspective and thank you for um 01:36:11.119 --> 01:36:13.430 align:start position:0% from my perspective and thank you for um bringing<01:36:11.440> this<01:36:12.080> item<01:36:12.400> up<01:36:12.560> again<01:36:12.800> i<01:36:13.040> continue 01:36:13.430 --> 01:36:13.440 align:start position:0% bringing this item up again i continue 01:36:13.440 --> 01:36:17.030 align:start position:0% bringing this item up again i continue to<01:36:13.520> believe<01:36:13.760> it's<01:36:13.920> a<01:36:14.000> very<01:36:14.159> important 01:36:17.030 --> 01:36:17.040 align:start position:0% 01:36:17.040 --> 01:36:19.109 align:start position:0% important<01:36:17.520> action<01:36:17.760> we<01:36:17.920> need<01:36:18.080> to<01:36:18.239> take 01:36:19.109 --> 01:36:19.119 align:start position:0% important action we need to take 01:36:19.119 --> 01:36:21.270 align:start position:0% important action we need to take in<01:36:19.199> the<01:36:19.360> interim<01:36:20.320> even<01:36:20.560> if<01:36:20.639> we<01:36:20.719> decide<01:36:21.040> to<01:36:21.119> go 01:36:21.270 --> 01:36:21.280 align:start position:0% in the interim even if we decide to go 01:36:21.280 --> 01:36:23.669 align:start position:0% in the interim even if we decide to go with<01:36:21.360> a<01:36:21.440> broader<01:36:21.760> proposal<01:36:22.400> ultimately 01:36:23.669 --> 01:36:23.679 align:start position:0% with a broader proposal ultimately 01:36:23.679 --> 01:36:25.109 align:start position:0% with a broader proposal ultimately we<01:36:23.840> need<01:36:24.000> to<01:36:24.159> have 01:36:25.109 --> 01:36:25.119 align:start position:0% we need to have 01:36:25.119 --> 01:36:26.709 align:start position:0% we need to have some<01:36:25.280> kind<01:36:25.440> of<01:36:25.520> firming<01:36:26.159> and<01:36:26.320> the<01:36:26.400> question 01:36:26.709 --> 01:36:26.719 align:start position:0% some kind of firming and the question 01:36:26.719 --> 01:36:28.149 align:start position:0% some kind of firming and the question then<01:36:26.880> becomes<01:36:27.280> as<01:36:27.440> you<01:36:27.520> said<01:36:27.760> we<01:36:27.840> got<01:36:28.000> to 01:36:28.149 --> 01:36:28.159 align:start position:0% then becomes as you said we got to 01:36:28.159 --> 01:36:30.709 align:start position:0% then becomes as you said we got to define<01:36:28.560> what<01:36:28.800> we're<01:36:28.960> going<01:36:29.040> to 01:36:30.709 --> 01:36:30.719 align:start position:0% define what we're going to 01:36:30.719 --> 01:36:32.709 align:start position:0% define what we're going to consider<01:36:31.199> firm<01:36:32.000> because<01:36:32.159> we've<01:36:32.400> gotten<01:36:32.639> a 01:36:32.709 --> 01:36:32.719 align:start position:0% consider firm because we've gotten a 01:36:32.719 --> 01:36:34.310 align:start position:0% consider firm because we've gotten a variety<01:36:33.040> of<01:36:33.119> stakeholder<01:36:33.600> comments<01:36:34.000> that 01:36:34.310 --> 01:36:34.320 align:start position:0% variety of stakeholder comments that 01:36:34.320 --> 01:36:36.950 align:start position:0% variety of stakeholder comments that keep<01:36:34.560> it<01:36:34.960> more<01:36:35.199> towards<01:36:36.000> gas<01:36:36.480> and<01:36:36.639> maybe<01:36:36.880> a 01:36:36.950 --> 01:36:36.960 align:start position:0% keep it more towards gas and maybe a 01:36:36.960 --> 01:36:38.550 align:start position:0% keep it more towards gas and maybe a little<01:36:37.119> bit<01:36:37.280> of<01:36:37.360> expansion<01:36:37.840> of<01:36:37.920> coal<01:36:38.239> and<01:36:38.320> then 01:36:38.550 --> 01:36:38.560 align:start position:0% little bit of expansion of coal and then 01:36:38.560 --> 01:36:39.910 align:start position:0% little bit of expansion of coal and then much<01:36:38.800> broader 01:36:39.910 --> 01:36:39.920 align:start position:0% much broader 01:36:39.920 --> 01:36:42.390 align:start position:0% much broader to<01:36:40.000> hydro<01:36:40.480> and<01:36:40.880> nuclear<01:36:41.440> so<01:36:42.000> we've<01:36:42.159> got<01:36:42.320> to 01:36:42.390 --> 01:36:42.400 align:start position:0% to hydro and nuclear so we've got to 01:36:42.400 --> 01:36:44.229 align:start position:0% to hydro and nuclear so we've got to really<01:36:42.800> sort<01:36:43.040> of<01:36:43.119> define<01:36:43.679> what<01:36:43.920> what<01:36:44.080> we're 01:36:44.229 --> 01:36:44.239 align:start position:0% really sort of define what what we're 01:36:44.239 --> 01:36:46.390 align:start position:0% really sort of define what what we're going<01:36:44.320> to<01:36:44.400> be<01:36:44.960> paying<01:36:45.280> for 01:36:46.390 --> 01:36:46.400 align:start position:0% going to be paying for 01:36:46.400 --> 01:36:47.189 align:start position:0% going to be paying for and 01:36:47.189 --> 01:36:47.199 align:start position:0% and 01:36:47.199 --> 01:36:48.870 align:start position:0% and structure<01:36:47.760> with<01:36:47.920> respect<01:36:48.320> to<01:36:48.400> structure<01:36:48.800> i 01:36:48.870 --> 01:36:48.880 align:start position:0% structure with respect to structure i 01:36:48.880 --> 01:36:51.430 align:start position:0% structure with respect to structure i mean<01:36:49.119> i<01:36:49.199> think<01:36:49.600> resoundingly<01:36:50.719> it's<01:36:50.960> been<01:36:51.360> a 01:36:51.430 --> 01:36:51.440 align:start position:0% mean i think resoundingly it's been a 01:36:51.440 --> 01:36:55.109 align:start position:0% mean i think resoundingly it's been a black<01:36:51.679> start<01:36:52.560> contractual<01:36:53.440> rfp 01:36:55.109 --> 01:36:55.119 align:start position:0% black start contractual rfp 01:36:55.119 --> 01:36:57.510 align:start position:0% black start contractual rfp black<01:36:55.360> start<01:36:55.679> like<01:36:56.320> contractual<01:36:56.880> rp<01:36:57.199> process 01:36:57.510 --> 01:36:57.520 align:start position:0% black start like contractual rp process 01:36:57.520 --> 01:36:59.350 align:start position:0% black start like contractual rp process by<01:36:57.679> ircot<01:36:58.080> i<01:36:58.239> think<01:36:58.320> there's<01:36:58.560> a<01:36:58.639> lot<01:36:58.800> of 01:36:59.350 --> 01:36:59.360 align:start position:0% by ircot i think there's a lot of 01:36:59.360 --> 01:37:01.590 align:start position:0% by ircot i think there's a lot of resounding 01:37:01.590 --> 01:37:01.600 align:start position:0% resounding 01:37:01.600 --> 01:37:03.750 align:start position:0% resounding recommendations<01:37:02.480> that<01:37:02.639> we've<01:37:02.880> heard 01:37:03.750 --> 01:37:03.760 align:start position:0% recommendations that we've heard 01:37:03.760 --> 01:37:05.189 align:start position:0% recommendations that we've heard over<01:37:04.000> and<01:37:04.159> over<01:37:04.320> again<01:37:04.639> that<01:37:04.800> i<01:37:04.880> think<01:37:05.040> we've 01:37:05.189 --> 01:37:05.199 align:start position:0% over and over again that i think we've 01:37:05.199 --> 01:37:07.350 align:start position:0% over and over again that i think we've got<01:37:05.360> a<01:37:05.440> lot<01:37:06.080> we've<01:37:06.320> got<01:37:06.560> what<01:37:06.719> we<01:37:06.800> need<01:37:07.040> there 01:37:07.350 --> 01:37:07.360 align:start position:0% got a lot we've got what we need there 01:37:07.360 --> 01:37:08.709 align:start position:0% got a lot we've got what we need there it's<01:37:07.520> just<01:37:07.679> trying<01:37:07.920> to<01:37:08.000> determine<01:37:08.560> the 01:37:08.709 --> 01:37:08.719 align:start position:0% it's just trying to determine the 01:37:08.719 --> 01:37:09.990 align:start position:0% it's just trying to determine the definition 01:37:09.990 --> 01:37:10.000 align:start position:0% definition 01:37:10.000 --> 01:37:12.310 align:start position:0% definition and<01:37:10.480> um 01:37:12.310 --> 01:37:12.320 align:start position:0% and um 01:37:12.320 --> 01:37:13.750 align:start position:0% and um maybe<01:37:12.560> perhaps<01:37:12.880> some<01:37:13.040> duration<01:37:13.360> requirements 01:37:13.750 --> 01:37:13.760 align:start position:0% maybe perhaps some duration requirements 01:37:13.760 --> 01:37:15.669 align:start position:0% maybe perhaps some duration requirements and<01:37:13.920> some<01:37:14.159> additional<01:37:14.480> detail<01:37:14.880> but<01:37:15.360> i<01:37:15.520> would 01:37:15.669 --> 01:37:15.679 align:start position:0% and some additional detail but i would 01:37:15.679 --> 01:37:17.270 align:start position:0% and some additional detail but i would say<01:37:16.000> that<01:37:16.320> um 01:37:17.270 --> 01:37:17.280 align:start position:0% say that um 01:37:17.280 --> 01:37:19.270 align:start position:0% say that um you<01:37:17.440> know<01:37:17.679> if<01:37:17.840> we<01:37:17.920> can<01:37:18.080> get<01:37:18.239> this<01:37:18.800> then<01:37:19.040> i<01:37:19.119> know 01:37:19.270 --> 01:37:19.280 align:start position:0% you know if we can get this then i know 01:37:19.280 --> 01:37:20.229 align:start position:0% you know if we can get this then i know i've<01:37:19.360> had<01:37:19.520> this<01:37:19.679> discussion<01:37:20.000> with<01:37:20.080> you 01:37:20.229 --> 01:37:20.239 align:start position:0% i've had this discussion with you 01:37:20.239 --> 01:37:22.149 align:start position:0% i've had this discussion with you chairman<01:37:20.560> but<01:37:20.880> i<01:37:20.960> think<01:37:21.119> if<01:37:21.199> we<01:37:21.360> can 01:37:22.149 --> 01:37:22.159 align:start position:0% chairman but i think if we can 01:37:22.159 --> 01:37:23.189 align:start position:0% chairman but i think if we can have 01:37:23.189 --> 01:37:23.199 align:start position:0% have 01:37:23.199 --> 01:37:24.950 align:start position:0% have the<01:37:23.360> details<01:37:23.840> defined 01:37:24.950 --> 01:37:24.960 align:start position:0% the details defined 01:37:24.960 --> 01:37:27.189 align:start position:0% the details defined uh<01:37:25.520> you<01:37:25.679> know<01:37:26.080> we<01:37:26.239> should 01:37:27.189 --> 01:37:27.199 align:start position:0% uh you know we should 01:37:27.199 --> 01:37:28.229 align:start position:0% uh you know we should consider 01:37:28.229 --> 01:37:28.239 align:start position:0% consider 01:37:28.239 --> 01:37:29.910 align:start position:0% consider pulling<01:37:28.560> the<01:37:28.719> trigger<01:37:29.119> and<01:37:29.280> having<01:37:29.600> aircut 01:37:29.910 --> 01:37:29.920 align:start position:0% pulling the trigger and having aircut 01:37:29.920 --> 01:37:31.990 align:start position:0% pulling the trigger and having aircut get<01:37:30.080> going<01:37:30.880> so<01:37:31.119> we<01:37:31.199> can<01:37:31.360> have<01:37:31.520> it<01:37:31.600> ready<01:37:31.840> by 01:37:31.990 --> 01:37:32.000 align:start position:0% get going so we can have it ready by 01:37:32.000 --> 01:37:34.149 align:start position:0% get going so we can have it ready by next<01:37:32.159> winter<01:37:32.639> oh<01:37:32.880> i'm<01:37:32.960> very<01:37:33.199> trigger<01:37:33.920> trigger 01:37:34.149 --> 01:37:34.159 align:start position:0% next winter oh i'm very trigger trigger 01:37:34.159 --> 01:37:37.430 align:start position:0% next winter oh i'm very trigger trigger happening 01:37:37.430 --> 01:37:37.440 align:start position:0% 01:37:37.440 --> 01:37:39.590 align:start position:0% we'll<01:37:37.679> put 01:37:39.590 --> 01:37:39.600 align:start position:0% we'll put 01:37:39.600 --> 01:37:40.310 align:start position:0% we'll put so 01:37:40.310 --> 01:37:40.320 align:start position:0% so 01:37:40.320 --> 01:37:42.470 align:start position:0% so on<01:37:40.560> that<01:37:40.639> mr<01:37:41.119> will<01:37:41.280> we<01:37:41.360> have 01:37:42.470 --> 01:37:42.480 align:start position:0% on that mr will we have 01:37:42.480 --> 01:37:44.550 align:start position:0% on that mr will we have could<01:37:42.880> as<01:37:43.119> per<01:37:43.280> this<01:37:43.520> segment 01:37:44.550 --> 01:37:44.560 align:start position:0% could as per this segment 01:37:44.560 --> 01:37:46.149 align:start position:0% could as per this segment and<01:37:44.719> i'll<01:37:44.880> we'll<01:37:45.040> work<01:37:45.360> through<01:37:45.520> the 01:37:46.149 --> 01:37:46.159 align:start position:0% and i'll we'll work through the 01:37:46.159 --> 01:37:48.550 align:start position:0% and i'll we'll work through the details<01:37:46.800> of<01:37:46.960> that<01:37:47.440> but<01:37:47.679> i<01:37:47.760> did<01:37:48.000> have<01:37:48.320> a 01:37:48.550 --> 01:37:48.560 align:start position:0% details of that but i did have a 01:37:48.560 --> 01:37:50.629 align:start position:0% details of that but i did have a technical<01:37:49.040> question<01:37:49.440> for<01:37:49.600> woody<01:37:50.080> if<01:37:50.400> if<01:37:50.560> i 01:37:50.629 --> 01:37:50.639 align:start position:0% technical question for woody if if i 01:37:50.639 --> 01:37:51.130 align:start position:0% technical question for woody if if i could 01:37:51.130 --> 01:37:51.140 align:start position:0% could 01:37:51.140 --> 01:37:53.590 align:start position:0% could [Laughter] 01:37:53.590 --> 01:37:53.600 align:start position:0% [Laughter] 01:37:53.600 --> 01:37:55.430 align:start position:0% [Laughter] what<01:37:53.760> he's<01:37:54.239> getting<01:37:54.400> a<01:37:54.480> workout<01:37:54.960> he<01:37:55.040> could<01:37:55.199> sit 01:37:55.430 --> 01:37:55.440 align:start position:0% what he's getting a workout he could sit 01:37:55.440 --> 01:37:57.590 align:start position:0% what he's getting a workout he could sit up<01:37:55.520> here<01:37:55.920> for<01:37:56.000> a<01:37:56.080> long<01:37:56.320> time<01:37:56.639> if<01:37:56.800> he<01:37:56.880> wanted<01:37:57.119> to 01:37:57.590 --> 01:37:57.600 align:start position:0% up here for a long time if he wanted to 01:37:57.600 --> 01:37:59.830 align:start position:0% up here for a long time if he wanted to um<01:37:58.159> he's<01:37:58.400> getting<01:37:58.639> the<01:37:58.800> squats<01:37:59.119> work<01:37:59.440> out<01:37:59.600> in 01:37:59.830 --> 01:37:59.840 align:start position:0% um he's getting the squats work out in 01:37:59.840 --> 01:38:05.270 align:start position:0% um he's getting the squats work out in appreciate<01:38:00.239> what 01:38:05.270 --> 01:38:05.280 align:start position:0% 01:38:05.280 --> 01:38:08.310 align:start position:0% okay<01:38:05.679> on<01:38:06.080> on<01:38:06.400> a<01:38:07.040> winter<01:38:07.360> ancillary<01:38:07.760> service<01:38:08.080> in 01:38:08.310 --> 01:38:08.320 align:start position:0% okay on on a winter ancillary service in 01:38:08.320 --> 01:38:11.830 align:start position:0% okay on on a winter ancillary service in in<01:38:08.400> this<01:38:08.560> context<01:38:09.119> backup<01:38:09.520> fuel<01:38:10.159> on<01:38:10.320> site<01:38:10.560> fuel 01:38:11.830 --> 01:38:11.840 align:start position:0% in this context backup fuel on site fuel 01:38:11.840 --> 01:38:13.910 align:start position:0% in this context backup fuel on site fuel do<01:38:12.000> we<01:38:12.159> need<01:38:12.320> to<01:38:12.480> consider<01:38:13.040> this<01:38:13.440> on<01:38:13.679> a 01:38:13.910 --> 01:38:13.920 align:start position:0% do we need to consider this on a 01:38:13.920 --> 01:38:15.990 align:start position:0% do we need to consider this on a regional<01:38:14.400> basis<01:38:14.960> when<01:38:15.119> you<01:38:15.360> consider<01:38:15.840> an 01:38:15.990 --> 01:38:16.000 align:start position:0% regional basis when you consider an 01:38:16.000 --> 01:38:17.669 align:start position:0% regional basis when you consider an ancillary<01:38:16.480> service<01:38:16.800> product<01:38:17.199> because<01:38:17.440> if<01:38:17.600> a 01:38:17.669 --> 01:38:17.679 align:start position:0% ancillary service product because if a 01:38:17.679 --> 01:38:19.350 align:start position:0% ancillary service product because if a squirrel<01:38:18.080> lands<01:38:18.320> on<01:38:18.400> the<01:38:18.480> wrong<01:38:18.800> transformer 01:38:19.350 --> 01:38:19.360 align:start position:0% squirrel lands on the wrong transformer 01:38:19.360 --> 01:38:21.510 align:start position:0% squirrel lands on the wrong transformer at<01:38:19.440> the<01:38:19.520> right<01:38:20.080> wrong<01:38:20.400> place<01:38:20.800> during<01:38:21.119> a<01:38:21.199> winter 01:38:21.510 --> 01:38:21.520 align:start position:0% at the right wrong place during a winter 01:38:21.520 --> 01:38:22.950 align:start position:0% at the right wrong place during a winter storm<01:38:21.840> or<01:38:22.000> something<01:38:22.320> like<01:38:22.480> that<01:38:22.719> even<01:38:22.880> a 01:38:22.950 --> 01:38:22.960 align:start position:0% storm or something like that even a 01:38:22.960 --> 01:38:24.629 align:start position:0% storm or something like that even a moderate<01:38:23.360> one 01:38:24.629 --> 01:38:24.639 align:start position:0% moderate one 01:38:24.639 --> 01:38:26.390 align:start position:0% moderate one transmission<01:38:25.280> constraints<01:38:25.840> congestion 01:38:26.390 --> 01:38:26.400 align:start position:0% transmission constraints congestion 01:38:26.400 --> 01:38:28.550 align:start position:0% transmission constraints congestion could<01:38:26.560> be<01:38:26.719> an<01:38:26.880> issue 01:38:28.550 --> 01:38:28.560 align:start position:0% could be an issue 01:38:28.560 --> 01:38:31.430 align:start position:0% could be an issue again<01:38:28.960> you<01:38:29.119> want<01:38:29.600> you<01:38:29.760> want<01:38:30.159> do<01:38:30.320> you<01:38:30.400> want<01:38:30.800> fuel 01:38:31.430 --> 01:38:31.440 align:start position:0% again you want you want do you want fuel 01:38:31.440 --> 01:38:37.350 align:start position:0% again you want you want do you want fuel reserved<01:38:32.080> regionally 01:38:37.350 --> 01:38:37.360 align:start position:0% 01:38:37.360 --> 01:38:40.310 align:start position:0% well 01:38:40.310 --> 01:38:40.320 align:start position:0% 01:38:40.320 --> 01:38:41.830 align:start position:0% i<01:38:40.480> don't<01:38:40.639> think<01:38:40.800> so 01:38:41.830 --> 01:38:41.840 align:start position:0% i don't think so 01:38:41.840 --> 01:38:44.950 align:start position:0% i don't think so i<01:38:42.000> think<01:38:42.159> we<01:38:42.400> see<01:38:43.040> fuel<01:38:43.679> issues 01:38:44.950 --> 01:38:44.960 align:start position:0% i think we see fuel issues 01:38:44.960 --> 01:38:46.709 align:start position:0% i think we see fuel issues across<01:38:45.280> the<01:38:45.440> entire<01:38:45.760> grid 01:38:46.709 --> 01:38:46.719 align:start position:0% across the entire grid 01:38:46.719 --> 01:38:48.070 align:start position:0% across the entire grid i<01:38:46.800> think<01:38:46.960> it's<01:38:47.119> more<01:38:47.280> likely<01:38:47.679> for<01:38:47.920> the 01:38:48.070 --> 01:38:48.080 align:start position:0% i think it's more likely for the 01:38:48.080 --> 01:38:49.750 align:start position:0% i think it's more likely for the northern<01:38:48.480> areas<01:38:48.800> to<01:38:48.960> have 01:38:49.750 --> 01:38:49.760 align:start position:0% northern areas to have 01:38:49.760 --> 01:38:52.310 align:start position:0% northern areas to have freezing<01:38:50.239> problems<01:38:50.639> but<01:38:50.800> we<01:38:51.040> see 01:38:52.310 --> 01:38:52.320 align:start position:0% freezing problems but we see 01:38:52.320 --> 01:38:56.790 align:start position:0% freezing problems but we see gas<01:38:52.880> issues<01:38:53.520> even<01:38:53.840> in<01:38:54.159> even<01:38:54.480> in<01:38:54.560> the<01:38:54.639> valley 01:38:56.790 --> 01:38:56.800 align:start position:0% gas issues even in even in the valley 01:38:56.800 --> 01:38:58.870 align:start position:0% gas issues even in even in the valley so<01:38:57.280> pipeline<01:38:57.760> issues<01:38:58.159> and<01:38:58.239> things<01:38:58.480> like<01:38:58.639> that 01:38:58.870 --> 01:38:58.880 align:start position:0% so pipeline issues and things like that 01:38:58.880 --> 01:39:00.149 align:start position:0% so pipeline issues and things like that which<01:38:59.119> would<01:38:59.280> be 01:39:00.149 --> 01:39:00.159 align:start position:0% which would be 01:39:00.159 --> 01:39:01.189 align:start position:0% which would be you<01:39:00.320> know<01:39:00.400> one<01:39:00.560> of<01:39:00.560> the<01:39:00.719> reasons<01:39:00.960> you<01:39:01.119> would 01:39:01.189 --> 01:39:01.199 align:start position:0% you know one of the reasons you would 01:39:01.199 --> 01:39:02.950 align:start position:0% you know one of the reasons you would want<01:39:01.360> to<01:39:01.440> have<01:39:01.600> on-site<01:39:02.080> fuel<01:39:02.480> i<01:39:02.560> think<01:39:02.719> that 01:39:02.950 --> 01:39:02.960 align:start position:0% want to have on-site fuel i think that 01:39:02.960 --> 01:39:05.109 align:start position:0% want to have on-site fuel i think that is<01:39:03.119> a<01:39:03.440> regional-wide 01:39:05.109 --> 01:39:05.119 align:start position:0% is a regional-wide 01:39:05.119 --> 01:39:09.109 align:start position:0% is a regional-wide i<01:39:05.199> think<01:39:05.840> there's<01:39:06.080> room<01:39:06.320> for<01:39:06.480> debate<01:39:06.800> there 01:39:09.109 --> 01:39:09.119 align:start position:0% 01:39:09.119 --> 01:39:10.790 align:start position:0% yeah<01:39:09.280> that's<01:39:09.520> a<01:39:09.600> very<01:39:09.760> interesting<01:39:10.159> question 01:39:10.790 --> 01:39:10.800 align:start position:0% yeah that's a very interesting question 01:39:10.800 --> 01:39:11.990 align:start position:0% yeah that's a very interesting question yeah<01:39:10.960> because<01:39:11.280> because<01:39:11.600> so<01:39:11.679> much<01:39:11.840> of<01:39:11.920> a 01:39:11.990 --> 01:39:12.000 align:start position:0% yeah because because so much of a 01:39:12.000 --> 01:39:15.030 align:start position:0% yeah because because so much of a concentration<01:39:12.960> of<01:39:13.440> storage<01:39:13.840> capacity 01:39:15.030 --> 01:39:15.040 align:start position:0% concentration of storage capacity 01:39:15.040 --> 01:39:16.709 align:start position:0% concentration of storage capacity texas<01:39:15.440> gulf<01:39:15.679> coast<01:39:16.080> and<01:39:16.159> stuff<01:39:16.320> like<01:39:16.480> that<01:39:16.639> and 01:39:16.709 --> 01:39:16.719 align:start position:0% texas gulf coast and stuff like that and 01:39:16.719 --> 01:39:18.550 align:start position:0% texas gulf coast and stuff like that and i<01:39:16.800> just<01:39:16.880> want<01:39:17.040> this<01:39:17.199> to<01:39:17.280> be<01:39:17.440> resilient<01:39:18.239> in<01:39:18.320> case 01:39:18.550 --> 01:39:18.560 align:start position:0% i just want this to be resilient in case 01:39:18.560 --> 01:39:20.950 align:start position:0% i just want this to be resilient in case of<01:39:18.800> hurricanes<01:39:19.600> and<01:39:19.760> snow<01:39:20.000> storms<01:39:20.480> agreed 01:39:20.950 --> 01:39:20.960 align:start position:0% of hurricanes and snow storms agreed 01:39:20.960 --> 01:39:21.669 align:start position:0% of hurricanes and snow storms agreed yeah 01:39:21.669 --> 01:39:21.679 align:start position:0% yeah 01:39:21.679 --> 01:39:23.270 align:start position:0% yeah i<01:39:22.000> would<01:39:22.239> also 01:39:23.270 --> 01:39:23.280 align:start position:0% i would also 01:39:23.280 --> 01:39:24.870 align:start position:0% i would also want<01:39:23.440> to<01:39:23.520> make<01:39:23.679> sure<01:39:23.840> we<01:39:23.920> think<01:39:24.159> hard<01:39:24.400> about 01:39:24.870 --> 01:39:24.880 align:start position:0% want to make sure we think hard about 01:39:24.880 --> 01:39:26.709 align:start position:0% want to make sure we think hard about the<01:39:25.199> geological<01:39:25.840> constraints<01:39:26.480> if<01:39:26.560> we 01:39:26.709 --> 01:39:26.719 align:start position:0% the geological constraints if we 01:39:26.719 --> 01:39:28.390 align:start position:0% the geological constraints if we consider<01:39:27.119> off-site<01:39:27.520> fuel 01:39:28.390 --> 01:39:28.400 align:start position:0% consider off-site fuel 01:39:28.400 --> 01:39:29.750 align:start position:0% consider off-site fuel if<01:39:28.560> it's<01:39:28.719> off-site 01:39:29.750 --> 01:39:29.760 align:start position:0% if it's off-site 01:39:29.760 --> 01:39:31.270 align:start position:0% if it's off-site i<01:39:29.840> mean<01:39:29.920> i<01:39:30.000> think<01:39:30.159> it's<01:39:30.800> worthwhile 01:39:31.270 --> 01:39:31.280 align:start position:0% i mean i think it's worthwhile 01:39:31.280 --> 01:39:33.830 align:start position:0% i mean i think it's worthwhile considering<01:39:31.760> off-site<01:39:32.159> fuel<01:39:32.560> firm<01:39:32.880> fuel 01:39:33.830 --> 01:39:33.840 align:start position:0% considering off-site fuel firm fuel 01:39:33.840 --> 01:39:37.189 align:start position:0% considering off-site fuel firm fuel with<01:39:34.080> firm<01:39:34.400> transport<01:39:35.440> uh 01:39:37.189 --> 01:39:37.199 align:start position:0% with firm transport uh 01:39:37.199 --> 01:39:39.270 align:start position:0% with firm transport uh in<01:39:37.360> that<01:39:37.520> take<01:39:37.920> in<01:39:38.080> a<01:39:38.159> gas<01:39:38.639> gas<01:39:38.880> world<01:39:39.119> that 01:39:39.270 --> 01:39:39.280 align:start position:0% in that take in a gas gas world that 01:39:39.280 --> 01:39:41.990 align:start position:0% in that take in a gas gas world that takes<01:39:39.520> the<01:39:40.000> shape<01:39:40.239> of<01:39:40.400> a<01:39:40.480> salt<01:39:40.719> dome 01:39:41.990 --> 01:39:42.000 align:start position:0% takes the shape of a salt dome 01:39:42.000 --> 01:39:43.750 align:start position:0% takes the shape of a salt dome underground<01:39:42.400> storage<01:39:42.800> and 01:39:43.750 --> 01:39:43.760 align:start position:0% underground storage and 01:39:43.760 --> 01:39:45.189 align:start position:0% underground storage and you<01:39:43.920> can't<01:39:44.080> put<01:39:44.320> those<01:39:44.560> just<01:39:44.800> wherever<01:39:45.119> you 01:39:45.189 --> 01:39:45.199 align:start position:0% you can't put those just wherever you 01:39:45.199 --> 01:39:46.070 align:start position:0% you can't put those just wherever you want<01:39:45.440> them 01:39:46.070 --> 01:39:46.080 align:start position:0% want them 01:39:46.080 --> 01:39:48.070 align:start position:0% want them uh<01:39:46.320> that's<01:39:46.560> a<01:39:46.719> that's<01:39:46.960> a<01:39:47.040> jeep<01:39:47.520> you<01:39:47.840> just<01:39:48.000> got 01:39:48.070 --> 01:39:48.080 align:start position:0% uh that's a that's a jeep you just got 01:39:48.080 --> 01:39:49.750 align:start position:0% uh that's a that's a jeep you just got to<01:39:48.159> store<01:39:48.320> the<01:39:48.400> gas<01:39:48.639> where<01:39:48.800> the<01:39:48.880> salt<01:39:49.119> dome<01:39:49.360> is 01:39:49.750 --> 01:39:49.760 align:start position:0% to store the gas where the salt dome is 01:39:49.760 --> 01:39:51.030 align:start position:0% to store the gas where the salt dome is so<01:39:50.000> i<01:39:50.159> wouldn't 01:39:51.030 --> 01:39:51.040 align:start position:0% so i wouldn't 01:39:51.040 --> 01:39:53.750 align:start position:0% so i wouldn't i'd<01:39:51.280> want<01:39:51.440> to<01:39:51.679> weigh<01:39:51.840> that<01:39:52.000> argument<01:39:52.400> with 01:39:53.750 --> 01:39:53.760 align:start position:0% i'd want to weigh that argument with 01:39:53.760 --> 01:39:55.189 align:start position:0% i'd want to weigh that argument with cutting<01:39:54.080> out 01:39:55.189 --> 01:39:55.199 align:start position:0% cutting out 01:39:55.199 --> 01:39:57.270 align:start position:0% cutting out uh<01:39:55.760> geological<01:39:56.400> resources<01:39:56.880> that<01:39:56.960> could<01:39:57.119> be<01:39:57.199> a 01:39:57.270 --> 01:39:57.280 align:start position:0% uh geological resources that could be a 01:39:57.280 --> 01:39:59.030 align:start position:0% uh geological resources that could be a big<01:39:57.440> benefit<01:39:58.000> i<01:39:58.080> don't<01:39:58.239> know<01:39:58.400> the<01:39:58.480> answer<01:39:58.800> yet 01:39:59.030 --> 01:39:59.040 align:start position:0% big benefit i don't know the answer yet 01:39:59.040 --> 01:39:59.910 align:start position:0% big benefit i don't know the answer yet but<01:39:59.119> i<01:39:59.199> think 01:39:59.910 --> 01:39:59.920 align:start position:0% but i think 01:39:59.920 --> 01:40:02.149 align:start position:0% but i think we<01:40:00.080> need<01:40:00.159> to<01:40:00.239> keep<01:40:00.400> that<01:40:00.560> in<01:40:00.639> mind<01:40:00.880> as<01:40:00.960> well<01:40:01.600> so 01:40:02.149 --> 01:40:02.159 align:start position:0% we need to keep that in mind as well so 01:40:02.159 --> 01:40:04.550 align:start position:0% we need to keep that in mind as well so there<01:40:02.239> are<01:40:02.480> multi-day<01:40:03.440> small<01:40:03.760> lng<01:40:04.239> storage 01:40:04.550 --> 01:40:04.560 align:start position:0% there are multi-day small lng storage 01:40:04.560 --> 01:40:06.390 align:start position:0% there are multi-day small lng storage facilities<01:40:05.199> as<01:40:05.280> well 01:40:06.390 --> 01:40:06.400 align:start position:0% facilities as well 01:40:06.400 --> 01:40:08.950 align:start position:0% facilities as well the<01:40:06.560> city<01:40:06.800> of<01:40:06.880> memphis<01:40:07.280> has<01:40:07.440> one<01:40:08.159> um<01:40:08.560> that<01:40:08.719> they 01:40:08.950 --> 01:40:08.960 align:start position:0% the city of memphis has one um that they 01:40:08.960 --> 01:40:11.189 align:start position:0% the city of memphis has one um that they use<01:40:09.440> uh<01:40:09.920> for<01:40:10.080> this<01:40:10.320> exact<01:40:10.639> purpose<01:40:10.960> but 01:40:11.189 --> 01:40:11.199 align:start position:0% use uh for this exact purpose but 01:40:11.199 --> 01:40:13.430 align:start position:0% use uh for this exact purpose but primarily<01:40:11.679> on<01:40:11.760> the<01:40:11.840> gas<01:40:12.080> side<01:40:12.639> uh<01:40:12.960> on<01:40:13.040> the<01:40:13.280> on 01:40:13.430 --> 01:40:13.440 align:start position:0% primarily on the gas side uh on the on 01:40:13.440 --> 01:40:16.070 align:start position:0% primarily on the gas side uh on the on the<01:40:13.600> gas<01:40:13.840> delivery<01:40:14.400> side<01:40:14.800> uh<01:40:15.040> for<01:40:15.199> heating<01:40:15.600> but 01:40:16.070 --> 01:40:16.080 align:start position:0% the gas delivery side uh for heating but 01:40:16.080 --> 01:40:18.310 align:start position:0% the gas delivery side uh for heating but um<01:40:16.400> it<01:40:16.639> is<01:40:16.960> it's<01:40:17.199> a<01:40:17.280> small<01:40:17.600> facility<01:40:18.080> but<01:40:18.239> it 01:40:18.310 --> 01:40:18.320 align:start position:0% um it is it's a small facility but it 01:40:18.320 --> 01:40:20.149 align:start position:0% um it is it's a small facility but it gives<01:40:18.560> them<01:40:18.719> three<01:40:18.960> or<01:40:19.040> four<01:40:19.199> days<01:40:19.520> of<01:40:19.920> gas 01:40:20.149 --> 01:40:20.159 align:start position:0% gives them three or four days of gas 01:40:20.159 --> 01:40:21.350 align:start position:0% gives them three or four days of gas reserve<01:40:20.560> so 01:40:21.350 --> 01:40:21.360 align:start position:0% reserve so 01:40:21.360 --> 01:40:23.590 align:start position:0% reserve so in<01:40:21.440> addition<01:40:21.760> to<01:40:22.239> the<01:40:22.400> salt<01:40:22.639> domes 01:40:23.590 --> 01:40:23.600 align:start position:0% in addition to the salt domes 01:40:23.600 --> 01:40:25.189 align:start position:0% in addition to the salt domes there<01:40:23.920> are<01:40:24.080> technologies<01:40:24.800> out<01:40:24.880> there<01:40:25.040> that 01:40:25.189 --> 01:40:25.199 align:start position:0% there are technologies out there that 01:40:25.199 --> 01:40:26.950 align:start position:0% there are technologies out there that could<01:40:25.360> be<01:40:25.440> used<01:40:25.840> you<01:40:25.920> know<01:40:26.320> and<01:40:26.400> would<01:40:26.560> welcome 01:40:26.950 --> 01:40:26.960 align:start position:0% could be used you know and would welcome 01:40:26.960 --> 01:40:28.790 align:start position:0% could be used you know and would welcome i<01:40:27.040> just<01:40:27.199> wouldn't<01:40:27.440> want<01:40:27.600> to<01:40:27.679> cut<01:40:27.920> out<01:40:28.159> a<01:40:28.320> great 01:40:28.790 --> 01:40:28.800 align:start position:0% i just wouldn't want to cut out a great 01:40:28.800 --> 01:40:31.510 align:start position:0% i just wouldn't want to cut out a great consultant<01:40:29.360> resource<01:40:29.920> agreed<01:40:30.719> um 01:40:31.510 --> 01:40:31.520 align:start position:0% consultant resource agreed um 01:40:31.520 --> 01:40:33.510 align:start position:0% consultant resource agreed um that's<01:40:31.920> sitting<01:40:32.159> there<01:40:32.400> unused<01:40:32.880> absolutely 01:40:33.510 --> 01:40:33.520 align:start position:0% that's sitting there unused absolutely 01:40:33.520 --> 01:40:35.750 align:start position:0% that's sitting there unused absolutely so<01:40:33.920> i<01:40:34.000> think<01:40:34.719> given 01:40:35.750 --> 01:40:35.760 align:start position:0% so i think given 01:40:35.760 --> 01:40:37.430 align:start position:0% so i think given this<01:40:36.000> discussion<01:40:36.800> i<01:40:36.880> think<01:40:37.040> it<01:40:37.199> would<01:40:37.280> be 01:40:37.430 --> 01:40:37.440 align:start position:0% this discussion i think it would be 01:40:37.440 --> 01:40:39.430 align:start position:0% this discussion i think it would be really<01:40:37.679> important<01:40:38.159> as<01:40:38.320> we<01:40:38.480> move<01:40:38.719> forward<01:40:39.119> with 01:40:39.430 --> 01:40:39.440 align:start position:0% really important as we move forward with 01:40:39.440 --> 01:40:41.189 align:start position:0% really important as we move forward with scoping<01:40:39.840> out<01:40:40.000> the<01:40:40.080> firm<01:40:40.239> fuel<01:40:40.560> product<01:40:40.880> and 01:40:41.189 --> 01:40:41.199 align:start position:0% scoping out the firm fuel product and 01:40:41.199 --> 01:40:43.189 align:start position:0% scoping out the firm fuel product and giving<01:40:41.440> narcotic<01:40:41.840> direction<01:40:42.320> on<01:40:42.480> it<01:40:42.960> for 01:40:43.189 --> 01:40:43.199 align:start position:0% giving narcotic direction on it for 01:40:43.199 --> 01:40:44.629 align:start position:0% giving narcotic direction on it for ercot<01:40:43.679> to 01:40:44.629 --> 01:40:44.639 align:start position:0% ercot to 01:40:44.639 --> 01:40:47.030 align:start position:0% ercot to get<01:40:44.800> some<01:40:45.040> expertise<01:40:45.679> on<01:40:45.920> helping<01:40:46.480> identify 01:40:47.030 --> 01:40:47.040 align:start position:0% get some expertise on helping identify 01:40:47.040 --> 01:40:49.189 align:start position:0% get some expertise on helping identify what<01:40:47.280> what<01:40:47.520> areas<01:40:48.320> of<01:40:48.800> you<01:40:48.880> know<01:40:48.960> what 01:40:49.189 --> 01:40:49.199 align:start position:0% what what areas of you know what 01:40:49.199 --> 01:40:51.669 align:start position:0% what what areas of you know what resources<01:40:49.840> what<01:40:50.080> areas<01:40:50.400> of<01:40:50.480> the<01:40:50.639> state<01:40:51.440> would 01:40:51.669 --> 01:40:51.679 align:start position:0% resources what areas of the state would 01:40:51.679 --> 01:40:53.830 align:start position:0% resources what areas of the state would be<01:40:52.159> able<01:40:52.400> to<01:40:52.560> meet<01:40:52.719> those<01:40:52.960> firm<01:40:53.199> requirements 01:40:53.830 --> 01:40:53.840 align:start position:0% be able to meet those firm requirements 01:40:53.840 --> 01:40:54.709 align:start position:0% be able to meet those firm requirements because 01:40:54.709 --> 01:40:54.719 align:start position:0% because 01:40:54.719 --> 01:40:55.750 align:start position:0% because you<01:40:54.880> know<01:40:55.199> we're<01:40:55.360> going<01:40:55.440> to<01:40:55.520> have<01:40:55.600> to<01:40:55.679> have 01:40:55.750 --> 01:40:55.760 align:start position:0% you know we're going to have to have 01:40:55.760 --> 01:40:57.270 align:start position:0% you know we're going to have to have some<01:40:56.000> expertise<01:40:56.480> to<01:40:56.560> make<01:40:56.719> sure<01:40:56.960> that<01:40:57.119> what 01:40:57.270 --> 01:40:57.280 align:start position:0% some expertise to make sure that what 01:40:57.280 --> 01:40:59.669 align:start position:0% some expertise to make sure that what we're<01:40:57.440> paying<01:40:57.760> for 01:40:59.669 --> 01:40:59.679 align:start position:0% we're paying for 01:40:59.679 --> 01:41:01.030 align:start position:0% we're paying for we're<01:40:59.920> actually<01:41:00.239> going<01:41:00.320> to<01:41:00.400> get<01:41:00.639> and<01:41:00.800> i<01:41:00.880> think 01:41:01.030 --> 01:41:01.040 align:start position:0% we're actually going to get and i think 01:41:01.040 --> 01:41:02.310 align:start position:0% we're actually going to get and i think that's<01:41:01.199> going<01:41:01.360> to<01:41:01.440> take<01:41:01.600> some<01:41:01.760> specialized 01:41:02.310 --> 01:41:02.320 align:start position:0% that's going to take some specialized 01:41:02.320 --> 01:41:03.750 align:start position:0% that's going to take some specialized verification 01:41:03.750 --> 01:41:03.760 align:start position:0% verification 01:41:03.760 --> 01:41:06.229 align:start position:0% verification and<01:41:03.840> then<01:41:04.080> also<01:41:04.400> reviewing<01:41:05.040> um 01:41:06.229 --> 01:41:06.239 align:start position:0% and then also reviewing um 01:41:06.239 --> 01:41:08.629 align:start position:0% and then also reviewing um the<01:41:06.639> um<01:41:07.040> rfps<01:41:07.600> from<01:41:07.840> a<01:41:08.000> from<01:41:08.239> a<01:41:08.320> cost 01:41:08.629 --> 01:41:08.639 align:start position:0% the um rfps from a from a cost 01:41:08.639 --> 01:41:11.270 align:start position:0% the um rfps from a from a cost effectiveness<01:41:09.199> standpoint 01:41:11.270 --> 01:41:11.280 align:start position:0% effectiveness standpoint 01:41:11.280 --> 01:41:13.030 align:start position:0% effectiveness standpoint so<01:41:11.440> i<01:41:11.520> think<01:41:11.679> that<01:41:11.840> would<01:41:12.000> be<01:41:12.159> prudent<01:41:12.719> on<01:41:12.880> our 01:41:13.030 --> 01:41:13.040 align:start position:0% so i think that would be prudent on our 01:41:13.040 --> 01:41:15.350 align:start position:0% so i think that would be prudent on our end<01:41:13.280> is<01:41:13.440> to<01:41:13.600> have<01:41:14.000> urcat<01:41:14.480> if<01:41:14.719> you<01:41:14.880> know<01:41:15.040> what 01:41:15.350 --> 01:41:15.360 align:start position:0% end is to have urcat if you know what 01:41:15.360 --> 01:41:17.030 align:start position:0% end is to have urcat if you know what woody<01:41:15.679> i<01:41:16.000> suspect<01:41:16.400> that<01:41:16.639> you<01:41:16.719> may<01:41:16.880> have 01:41:17.030 --> 01:41:17.040 align:start position:0% woody i suspect that you may have 01:41:17.040 --> 01:41:18.310 align:start position:0% woody i suspect that you may have thoughts<01:41:17.280> on<01:41:17.360> whether<01:41:17.600> or<01:41:17.600> not<01:41:17.760> you<01:41:17.920> have<01:41:18.000> this 01:41:18.310 --> 01:41:18.320 align:start position:0% thoughts on whether or not you have this 01:41:18.320 --> 01:41:19.510 align:start position:0% thoughts on whether or not you have this expertise 01:41:19.510 --> 01:41:19.520 align:start position:0% expertise 01:41:19.520 --> 01:41:21.750 align:start position:0% expertise but<01:41:19.840> if<01:41:20.000> you<01:41:20.080> don't<01:41:20.480> i<01:41:20.639> think<01:41:21.119> getting<01:41:21.600> the 01:41:21.750 --> 01:41:21.760 align:start position:0% but if you don't i think getting the 01:41:21.760 --> 01:41:24.310 align:start position:0% but if you don't i think getting the expertise<01:41:22.400> to<01:41:22.880> help<01:41:23.119> with<01:41:23.600> with 01:41:24.310 --> 01:41:24.320 align:start position:0% expertise to help with with 01:41:24.320 --> 01:41:26.310 align:start position:0% expertise to help with with evaluating<01:41:25.199> locations<01:41:25.920> and<01:41:26.000> different 01:41:26.310 --> 01:41:26.320 align:start position:0% evaluating locations and different 01:41:26.320 --> 01:41:28.709 align:start position:0% evaluating locations and different resources<01:41:26.960> ultimately<01:41:27.440> on<01:41:27.520> how<01:41:27.679> we<01:41:27.840> define 01:41:28.709 --> 01:41:28.719 align:start position:0% resources ultimately on how we define 01:41:28.719 --> 01:41:30.709 align:start position:0% resources ultimately on how we define what<01:41:28.880> the<01:41:29.040> firm<01:41:29.280> fuel<01:41:29.520> product<01:41:29.920> is<01:41:30.159> if<01:41:30.320> it's 01:41:30.709 --> 01:41:30.719 align:start position:0% what the firm fuel product is if it's 01:41:30.719 --> 01:41:32.629 align:start position:0% what the firm fuel product is if it's you<01:41:30.800> know<01:41:31.040> just<01:41:31.520> tied<01:41:31.760> to<01:41:31.840> gas<01:41:32.159> well<01:41:32.320> then<01:41:32.480> we 01:41:32.629 --> 01:41:32.639 align:start position:0% you know just tied to gas well then we 01:41:32.639 --> 01:41:35.189 align:start position:0% you know just tied to gas well then we got<01:41:32.719> to<01:41:32.800> make<01:41:32.960> sure<01:41:33.280> that<01:41:33.440> those<01:41:33.920> resources 01:41:35.189 --> 01:41:35.199 align:start position:0% got to make sure that those resources 01:41:35.199 --> 01:41:37.669 align:start position:0% got to make sure that those resources that<01:41:35.520> are<01:41:35.920> um<01:41:36.639> going<01:41:36.880> to<01:41:36.960> be<01:41:37.040> participating<01:41:37.600> in 01:41:37.669 --> 01:41:37.679 align:start position:0% that are um going to be participating in 01:41:37.679 --> 01:41:39.430 align:start position:0% that are um going to be participating in the<01:41:37.760> firm<01:41:38.000> fuel<01:41:38.239> product 01:41:39.430 --> 01:41:39.440 align:start position:0% the firm fuel product 01:41:39.440 --> 01:41:41.189 align:start position:0% the firm fuel product actually<01:41:39.840> have<01:41:40.159> access<01:41:40.639> and<01:41:40.960> in<01:41:41.040> our 01:41:41.189 --> 01:41:41.199 align:start position:0% actually have access and in our 01:41:41.199 --> 01:41:43.990 align:start position:0% actually have access and in our structure<01:41:41.679> are<01:41:42.080> located<01:41:42.639> and<01:41:42.800> have<01:41:43.119> the<01:41:43.520> um 01:41:43.990 --> 01:41:44.000 align:start position:0% structure are located and have the um 01:41:44.000 --> 01:41:46.550 align:start position:0% structure are located and have the um mechanisms<01:41:44.719> to<01:41:44.880> actually<01:41:45.280> fulfill 01:41:46.550 --> 01:41:46.560 align:start position:0% mechanisms to actually fulfill 01:41:46.560 --> 01:41:48.629 align:start position:0% mechanisms to actually fulfill their<01:41:46.960> firm<01:41:47.280> fuel<01:41:47.600> product 01:41:48.629 --> 01:41:48.639 align:start position:0% their firm fuel product 01:41:48.639 --> 01:41:50.870 align:start position:0% their firm fuel product delivery 01:41:50.870 --> 01:41:50.880 align:start position:0% delivery 01:41:50.880 --> 01:41:53.189 align:start position:0% delivery yeah<01:41:51.040> i<01:41:51.119> think<01:41:51.360> it's<01:41:51.520> a 01:41:53.189 --> 01:41:53.199 align:start position:0% yeah i think it's a 01:41:53.199 --> 01:41:54.950 align:start position:0% yeah i think it's a it's<01:41:53.360> not<01:41:53.520> something<01:41:53.840> we<01:41:54.000> currently 01:41:54.950 --> 01:41:54.960 align:start position:0% it's not something we currently 01:41:54.960 --> 01:41:57.109 align:start position:0% it's not something we currently have<01:41:55.199> focused<01:41:55.600> on<01:41:55.840> at<01:41:56.000> our<01:41:56.159> guide<01:41:56.560> as<01:41:56.800> far<01:41:56.960> as 01:41:57.109 --> 01:41:57.119 align:start position:0% have focused on at our guide as far as 01:41:57.119 --> 01:41:58.870 align:start position:0% have focused on at our guide as far as the<01:41:57.280> capabilities<01:41:58.000> of<01:41:58.159> different<01:41:58.480> parts<01:41:58.800> of 01:41:58.870 --> 01:41:58.880 align:start position:0% the capabilities of different parts of 01:41:58.880 --> 01:42:01.030 align:start position:0% the capabilities of different parts of the<01:41:59.520> grid<01:41:59.920> or<01:42:00.159> different 01:42:01.030 --> 01:42:01.040 align:start position:0% the grid or different 01:42:01.040 --> 01:42:03.270 align:start position:0% the grid or different regions<01:42:01.520> might<01:42:01.760> have<01:42:02.000> over<01:42:02.639> over<01:42:02.800> another<01:42:03.199> i 01:42:03.270 --> 01:42:03.280 align:start position:0% regions might have over over another i 01:42:03.280 --> 01:42:04.310 align:start position:0% regions might have over over another i think 01:42:04.310 --> 01:42:04.320 align:start position:0% think 01:42:04.320 --> 01:42:06.629 align:start position:0% think hurricanes 01:42:06.629 --> 01:42:06.639 align:start position:0% hurricanes 01:42:06.639 --> 01:42:09.189 align:start position:0% hurricanes ice<01:42:06.880> storms<01:42:07.679> gas<01:42:08.000> pipeline<01:42:08.480> issues<01:42:08.800> those<01:42:09.040> are 01:42:09.189 --> 01:42:09.199 align:start position:0% ice storms gas pipeline issues those are 01:42:09.199 --> 01:42:11.990 align:start position:0% ice storms gas pipeline issues those are all<01:42:09.520> things<01:42:09.760> that<01:42:10.080> factor<01:42:10.480> into<01:42:10.719> that<01:42:11.199> okay<01:42:11.840> we 01:42:11.990 --> 01:42:12.000 align:start position:0% all things that factor into that okay we 01:42:12.000 --> 01:42:13.270 align:start position:0% all things that factor into that okay we also<01:42:12.159> don't<01:42:12.320> get<01:42:12.480> a<01:42:12.560> lot<01:42:12.639> of<01:42:12.719> hurricanes<01:42:13.199> in 01:42:13.270 --> 01:42:13.280 align:start position:0% also don't get a lot of hurricanes in 01:42:13.280 --> 01:42:14.470 align:start position:0% also don't get a lot of hurricanes in winter 01:42:14.470 --> 01:42:14.480 align:start position:0% winter 01:42:14.480 --> 01:42:17.109 align:start position:0% winter so<01:42:14.800> that's<01:42:15.280> i<01:42:15.600> know<01:42:16.239> i'm<01:42:16.400> calculating<01:42:16.960> for 01:42:17.109 --> 01:42:17.119 align:start position:0% so that's i know i'm calculating for 01:42:17.119 --> 01:42:18.950 align:start position:0% so that's i know i'm calculating for that<01:42:17.360> you<01:42:17.440> know<01:42:17.600> it's<01:42:17.840> it's<01:42:18.000> the<01:42:18.080> squirrel<01:42:18.800> you 01:42:18.950 --> 01:42:18.960 align:start position:0% that you know it's it's the squirrel you 01:42:18.960 --> 01:42:21.750 align:start position:0% that you know it's it's the squirrel you know<01:42:19.280> that<01:42:19.679> gets<01:42:19.920> you<01:42:20.400> and<01:42:20.639> uh 01:42:21.750 --> 01:42:21.760 align:start position:0% know that gets you and uh 01:42:21.760 --> 01:42:25.830 align:start position:0% know that gets you and uh absolutely<01:42:22.400> but 01:42:25.830 --> 01:42:25.840 align:start position:0% 01:42:25.840 --> 01:42:29.270 align:start position:0% so<01:42:26.080> i<01:42:26.320> will<01:42:26.639> say<01:42:26.960> you<01:42:27.119> know<01:42:27.520> just<01:42:27.760> to<01:42:28.159> to<01:42:28.320> add 01:42:29.270 --> 01:42:29.280 align:start position:0% so i will say you know just to to add 01:42:29.280 --> 01:42:31.350 align:start position:0% so i will say you know just to to add one<01:42:29.520> closing<01:42:30.000> piece<01:42:30.239> to<01:42:30.400> this 01:42:31.350 --> 01:42:31.360 align:start position:0% one closing piece to this 01:42:31.360 --> 01:42:32.629 align:start position:0% one closing piece to this is<01:42:31.520> that 01:42:32.629 --> 01:42:32.639 align:start position:0% is that 01:42:32.639 --> 01:42:35.270 align:start position:0% is that you<01:42:32.800> know<01:42:32.960> sp3<01:42:33.920> in<01:42:34.080> my<01:42:34.239> mind<01:42:34.480> requires<01:42:34.960> a<01:42:35.040> firm 01:42:35.270 --> 01:42:35.280 align:start position:0% you know sp3 in my mind requires a firm 01:42:35.280 --> 01:42:37.270 align:start position:0% you know sp3 in my mind requires a firm fuel<01:42:35.520> product<01:42:35.920> firm<01:42:36.159> fuel 01:42:37.270 --> 01:42:37.280 align:start position:0% fuel product firm fuel 01:42:37.280 --> 01:42:39.510 align:start position:0% fuel product firm fuel or<01:42:37.360> at<01:42:37.440> least<01:42:37.679> winter<01:42:38.000> resource<01:42:38.400> capability 01:42:39.510 --> 01:42:39.520 align:start position:0% or at least winter resource capability 01:42:39.520 --> 01:42:42.070 align:start position:0% or at least winter resource capability and<01:42:40.000> it<01:42:40.159> does<01:42:40.480> reference<01:42:41.199> including<01:42:41.679> on-site 01:42:42.070 --> 01:42:42.080 align:start position:0% and it does reference including on-site 01:42:42.080 --> 01:42:44.229 align:start position:0% and it does reference including on-site fuel<01:42:42.320> storage<01:42:42.719> dual<01:42:42.880> fuel<01:42:43.119> capability<01:42:44.000> or 01:42:44.229 --> 01:42:44.239 align:start position:0% fuel storage dual fuel capability or 01:42:44.239 --> 01:42:45.830 align:start position:0% fuel storage dual fuel capability or fuel<01:42:44.480> supply<01:42:44.800> arrangements<01:42:45.360> to<01:42:45.440> ensure 01:42:45.830 --> 01:42:45.840 align:start position:0% fuel supply arrangements to ensure 01:42:45.840 --> 01:42:48.070 align:start position:0% fuel supply arrangements to ensure winter<01:42:46.159> performance<01:42:46.639> for<01:42:46.800> several<01:42:47.119> days 01:42:48.070 --> 01:42:48.080 align:start position:0% winter performance for several days 01:42:48.080 --> 01:42:49.030 align:start position:0% winter performance for several days so 01:42:49.030 --> 01:42:49.040 align:start position:0% so 01:42:49.040 --> 01:42:51.510 align:start position:0% so as<01:42:49.280> we<01:42:49.440> look<01:42:49.679> to 01:42:51.510 --> 01:42:51.520 align:start position:0% as we look to 01:42:51.520 --> 01:42:52.550 align:start position:0% as we look to define 01:42:52.550 --> 01:42:52.560 align:start position:0% define 01:42:52.560 --> 01:42:54.310 align:start position:0% define and<01:42:52.719> build<01:42:53.040> this<01:42:53.199> product 01:42:54.310 --> 01:42:54.320 align:start position:0% and build this product 01:42:54.320 --> 01:42:57.590 align:start position:0% and build this product it's<01:42:54.560> important<01:42:54.960> to<01:42:55.119> note<01:42:55.440> that<01:42:55.840> sp3 01:42:57.590 --> 01:42:57.600 align:start position:0% it's important to note that sp3 01:42:57.600 --> 01:42:59.030 align:start position:0% it's important to note that sp3 requires<01:42:58.159> it 01:42:59.030 --> 01:42:59.040 align:start position:0% requires it 01:42:59.040 --> 01:43:00.310 align:start position:0% requires it in<01:42:59.119> my<01:42:59.360> opinion 01:43:00.310 --> 01:43:00.320 align:start position:0% in my opinion 01:43:00.320 --> 01:43:03.189 align:start position:0% in my opinion and<01:43:00.880> um<01:43:01.600> to<01:43:01.760> look<01:43:02.000> at<01:43:02.480> what<01:43:02.639> they've<01:43:02.880> at<01:43:02.960> least 01:43:03.189 --> 01:43:03.199 align:start position:0% and um to look at what they've at least 01:43:03.199 --> 01:43:05.669 align:start position:0% and um to look at what they've at least cited<01:43:03.520> to<01:43:03.679> it<01:43:03.760> says<01:43:04.000> including<01:43:04.960> but<01:43:05.440> which 01:43:05.669 --> 01:43:05.679 align:start position:0% cited to it says including but which 01:43:05.679 --> 01:43:07.830 align:start position:0% cited to it says including but which means<01:43:05.920> it's<01:43:06.080> not<01:43:06.320> an<01:43:06.480> exhaustive<01:43:07.040> list 01:43:07.830 --> 01:43:07.840 align:start position:0% means it's not an exhaustive list 01:43:07.840 --> 01:43:09.750 align:start position:0% means it's not an exhaustive list but<01:43:08.000> there<01:43:08.239> are<01:43:08.320> some<01:43:08.560> references<01:43:09.040> in<01:43:09.199> sp3 01:43:09.750 --> 01:43:09.760 align:start position:0% but there are some references in sp3 01:43:09.760 --> 01:43:12.149 align:start position:0% but there are some references in sp3 that<01:43:09.920> i<01:43:10.000> think<01:43:10.159> we<01:43:10.239> should<01:43:10.400> be<01:43:10.560> mindful<01:43:10.960> of 01:43:12.149 --> 01:43:12.159 align:start position:0% that i think we should be mindful of 01:43:12.159 --> 01:43:14.229 align:start position:0% that i think we should be mindful of uh<01:43:12.400> and<01:43:12.480> also<01:43:12.719> when<01:43:13.360> each<01:43:13.600> of<01:43:13.679> your<01:43:13.840> offices 01:43:14.229 --> 01:43:14.239 align:start position:0% uh and also when each of your offices 01:43:14.239 --> 01:43:16.229 align:start position:0% uh and also when each of your offices goes<01:43:14.480> through<01:43:14.719> puts<01:43:14.960> pen<01:43:15.119> to<01:43:15.280> paper<01:43:15.840> would<01:43:16.080> you 01:43:16.229 --> 01:43:16.239 align:start position:0% goes through puts pen to paper would you 01:43:16.239 --> 01:43:18.870 align:start position:0% goes through puts pen to paper would you please<01:43:16.560> also<01:43:16.800> consider<01:43:17.199> the<01:43:17.440> quantity 01:43:18.870 --> 01:43:18.880 align:start position:0% please also consider the quantity 01:43:18.880 --> 01:43:21.910 align:start position:0% please also consider the quantity uh<01:43:19.280> expected<01:43:19.760> to<01:43:19.920> be<01:43:20.400> or<01:43:21.040> the<01:43:21.199> ranges<01:43:21.679> or<01:43:21.840> a 01:43:21.910 --> 01:43:21.920 align:start position:0% uh expected to be or the ranges or a 01:43:21.920 --> 01:43:24.149 align:start position:0% uh expected to be or the ranges or a range<01:43:22.159> of<01:43:22.320> quantities 01:43:24.149 --> 01:43:24.159 align:start position:0% range of quantities 01:43:24.159 --> 01:43:26.070 align:start position:0% range of quantities and<01:43:24.320> that<01:43:24.480> goes<01:43:24.719> to<01:43:24.880> my<01:43:25.119> point<01:43:25.440> of<01:43:25.679> how<01:43:25.840> much 01:43:26.070 --> 01:43:26.080 align:start position:0% and that goes to my point of how much 01:43:26.080 --> 01:43:28.390 align:start position:0% and that goes to my point of how much are<01:43:26.239> we<01:43:26.400> how<01:43:26.560> much<01:43:26.880> quantities<01:43:27.280> of<01:43:27.440> everything 01:43:28.390 --> 01:43:28.400 align:start position:0% are we how much quantities of everything 01:43:28.400 --> 01:43:29.750 align:start position:0% are we how much quantities of everything that<01:43:28.480> we're<01:43:28.639> going<01:43:28.800> to<01:43:28.880> need<01:43:29.119> including<01:43:29.520> firm 01:43:29.750 --> 01:43:29.760 align:start position:0% that we're going to need including firm 01:43:29.760 --> 01:43:31.910 align:start position:0% that we're going to need including firm fuel<01:43:30.320> as<01:43:30.400> we<01:43:30.560> look<01:43:30.719> at<01:43:30.880> our<01:43:31.040> overall<01:43:31.440> ancillary 01:43:31.910 --> 01:43:31.920 align:start position:0% fuel as we look at our overall ancillary 01:43:31.920 --> 01:43:33.590 align:start position:0% fuel as we look at our overall ancillary service<01:43:32.320> plate<01:43:32.719> and 01:43:33.590 --> 01:43:33.600 align:start position:0% service plate and 01:43:33.600 --> 01:43:34.550 align:start position:0% service plate and and 01:43:34.550 --> 01:43:34.560 align:start position:0% and 01:43:34.560 --> 01:43:36.790 align:start position:0% and you<01:43:34.639> know<01:43:34.800> ecrs<01:43:35.840> because<01:43:36.080> it's<01:43:36.239> hard<01:43:36.400> for<01:43:36.639> us 01:43:36.790 --> 01:43:36.800 align:start position:0% you know ecrs because it's hard for us 01:43:36.800 --> 01:43:38.390 align:start position:0% you know ecrs because it's hard for us to<01:43:36.880> determine<01:43:37.360> a<01:43:37.440> quantity<01:43:37.920> right<01:43:38.000> now<01:43:38.159> i<01:43:38.239> mean 01:43:38.390 --> 01:43:38.400 align:start position:0% to determine a quantity right now i mean 01:43:38.400 --> 01:43:39.590 align:start position:0% to determine a quantity right now i mean we<01:43:38.480> could<01:43:38.560> look<01:43:38.719> at<01:43:38.800> historical<01:43:39.280> data<01:43:39.520> in 01:43:39.590 --> 01:43:39.600 align:start position:0% we could look at historical data in 01:43:39.600 --> 01:43:41.510 align:start position:0% we could look at historical data in winter<01:43:39.920> storm<01:43:40.159> uri 01:43:41.510 --> 01:43:41.520 align:start position:0% winter storm uri 01:43:41.520 --> 01:43:43.510 align:start position:0% winter storm uri the<01:43:41.679> 2011<01:43:42.320> event 01:43:43.510 --> 01:43:43.520 align:start position:0% the 2011 event 01:43:43.520 --> 01:43:45.430 align:start position:0% the 2011 event and<01:43:43.840> and<01:43:44.080> come<01:43:44.320> up<01:43:44.400> with<01:43:44.639> just<01:43:44.880> figures<01:43:45.280> but 01:43:45.430 --> 01:43:45.440 align:start position:0% and and come up with just figures but 01:43:45.440 --> 01:43:46.709 align:start position:0% and and come up with just figures but we're<01:43:45.600> going<01:43:45.679> to<01:43:45.760> need<01:43:45.920> a<01:43:45.920> little<01:43:46.080> bit<01:43:46.239> of 01:43:46.709 --> 01:43:46.719 align:start position:0% we're going to need a little bit of 01:43:46.719 --> 01:43:49.350 align:start position:0% we're going to need a little bit of assistance<01:43:47.199> here<01:43:47.600> on<01:43:48.239> shaping<01:43:48.560> that 01:43:49.350 --> 01:43:49.360 align:start position:0% assistance here on shaping that 01:43:49.360 --> 01:43:51.189 align:start position:0% assistance here on shaping that megawatt<01:43:49.760> amount<01:43:50.080> because<01:43:50.480> my<01:43:50.639> understanding 01:43:51.189 --> 01:43:51.199 align:start position:0% megawatt amount because my understanding 01:43:51.199 --> 01:43:52.790 align:start position:0% megawatt amount because my understanding is<01:43:51.280> these<01:43:51.440> firm<01:43:51.679> fuel<01:43:51.920> products<01:43:52.239> won't<01:43:52.480> be<01:43:52.719> you 01:43:52.790 --> 01:43:52.800 align:start position:0% is these firm fuel products won't be you 01:43:52.800 --> 01:43:54.470 align:start position:0% is these firm fuel products won't be you know<01:43:52.960> sitting<01:43:53.199> on<01:43:53.280> the<01:43:53.360> sideline<01:43:54.080> they'll<01:43:54.320> be 01:43:54.470 --> 01:43:54.480 align:start position:0% know sitting on the sideline they'll be 01:43:54.480 --> 01:43:55.910 align:start position:0% know sitting on the sideline they'll be able<01:43:54.639> to<01:43:54.719> participate<01:43:55.280> in<01:43:55.360> the<01:43:55.440> energy<01:43:55.760> and 01:43:55.910 --> 01:43:55.920 align:start position:0% able to participate in the energy and 01:43:55.920 --> 01:43:57.669 align:start position:0% able to participate in the energy and ancillary<01:43:56.320> service<01:43:57.119> markets<01:43:57.520> in<01:43:57.600> the 01:43:57.669 --> 01:43:57.679 align:start position:0% ancillary service markets in the 01:43:57.679 --> 01:43:58.870 align:start position:0% ancillary service markets in the meantime 01:43:58.870 --> 01:43:58.880 align:start position:0% meantime 01:43:58.880 --> 01:44:00.149 align:start position:0% meantime so 01:44:00.149 --> 01:44:00.159 align:start position:0% so 01:44:00.159 --> 01:44:02.310 align:start position:0% so we<01:44:00.320> want<01:44:00.480> to<01:44:00.560> make<01:44:00.719> sure<01:44:01.119> that 01:44:02.310 --> 01:44:02.320 align:start position:0% we want to make sure that 01:44:02.320 --> 01:44:04.149 align:start position:0% we want to make sure that as<01:44:02.480> we<01:44:02.800> we're<01:44:02.960> looking<01:44:03.360> at 01:44:04.149 --> 01:44:04.159 align:start position:0% as we we're looking at 01:44:04.159 --> 01:44:05.669 align:start position:0% as we we're looking at the<01:44:04.320> broader<01:44:04.719> ancillary<01:44:05.199> service 01:44:05.669 --> 01:44:05.679 align:start position:0% the broader ancillary service 01:44:05.679 --> 01:44:07.669 align:start position:0% the broader ancillary service reliability<01:44:06.400> service 01:44:07.669 --> 01:44:07.679 align:start position:0% reliability service 01:44:07.679 --> 01:44:08.790 align:start position:0% reliability service um 01:44:08.790 --> 01:44:08.800 align:start position:0% um 01:44:08.800 --> 01:44:10.870 align:start position:0% um picture<01:44:09.600> that<01:44:10.080> we<01:44:10.159> get<01:44:10.320> a<01:44:10.400> little<01:44:10.560> bit<01:44:10.639> more 01:44:10.870 --> 01:44:10.880 align:start position:0% picture that we get a little bit more 01:44:10.880 --> 01:44:12.550 align:start position:0% picture that we get a little bit more feedback<01:44:11.360> so<01:44:11.520> that<01:44:11.679> we're<01:44:11.840> right-sizing<01:44:12.480> it 01:44:12.550 --> 01:44:12.560 align:start position:0% feedback so that we're right-sizing it 01:44:12.560 --> 01:44:13.990 align:start position:0% feedback so that we're right-sizing it because<01:44:12.719> it<01:44:12.880> is<01:44:13.040> going<01:44:13.119> to<01:44:13.199> be<01:44:13.600> it's<01:44:13.840> going<01:44:13.920> to 01:44:13.990 --> 01:44:14.000 align:start position:0% because it is going to be it's going to 01:44:14.000 --> 01:44:15.430 align:start position:0% because it is going to be it's going to be<01:44:14.080> exciting<01:44:14.320> absolutely 01:44:15.430 --> 01:44:15.440 align:start position:0% be exciting absolutely 01:44:15.440 --> 01:44:18.550 align:start position:0% be exciting absolutely and<01:44:15.600> it's<01:44:15.760> a<01:44:15.840> well-spent<01:44:16.560> money<01:44:16.960> to 01:44:18.550 --> 01:44:18.560 align:start position:0% and it's a well-spent money to 01:44:18.560 --> 01:44:20.310 align:start position:0% and it's a well-spent money to provide<01:44:18.960> the<01:44:19.119> public<01:44:19.440> confidence<01:44:20.000> that<01:44:20.159> we 01:44:20.310 --> 01:44:20.320 align:start position:0% provide the public confidence that we 01:44:20.320 --> 01:44:22.149 align:start position:0% provide the public confidence that we are<01:44:20.480> preparing<01:44:21.040> for<01:44:21.199> cold<01:44:21.440> weather<01:44:21.760> events<01:44:22.080> in 01:44:22.149 --> 01:44:22.159 align:start position:0% are preparing for cold weather events in 01:44:22.159 --> 01:44:23.189 align:start position:0% are preparing for cold weather events in the<01:44:22.239> future 01:44:23.189 --> 01:44:23.199 align:start position:0% the future 01:44:23.199 --> 01:44:24.629 align:start position:0% the future but<01:44:23.360> we<01:44:23.520> want<01:44:23.679> to<01:44:23.760> make<01:44:23.920> sure<01:44:24.159> that<01:44:24.239> we're<01:44:24.400> also 01:44:24.629 --> 01:44:24.639 align:start position:0% but we want to make sure that we're also 01:44:24.639 --> 01:44:26.390 align:start position:0% but we want to make sure that we're also prudent<01:44:25.040> with<01:44:25.199> the<01:44:25.280> cost<01:44:25.600> and<01:44:25.760> right-sizing 01:44:26.390 --> 01:44:26.400 align:start position:0% prudent with the cost and right-sizing 01:44:26.400 --> 01:44:27.590 align:start position:0% prudent with the cost and right-sizing it<01:44:26.480> so<01:44:26.639> we're<01:44:26.800> not 01:44:27.590 --> 01:44:27.600 align:start position:0% it so we're not 01:44:27.600 --> 01:44:28.790 align:start position:0% it so we're not over<01:44:27.840> procuring 01:44:28.790 --> 01:44:28.800 align:start position:0% over procuring 01:44:28.800 --> 01:44:30.550 align:start position:0% over procuring i 01:44:30.550 --> 01:44:30.560 align:start position:0% i 01:44:30.560 --> 01:44:32.790 align:start position:0% i trust<01:44:30.800> you'll<01:44:31.040> ask<01:44:31.199> those<01:44:31.440> questions<01:44:31.840> and 01:44:32.790 --> 01:44:32.800 align:start position:0% trust you'll ask those questions and 01:44:32.800 --> 01:44:34.310 align:start position:0% trust you'll ask those questions and seek<01:44:33.040> out<01:44:33.119> the<01:44:33.280> stakeholders<01:44:33.760> that<01:44:33.920> can<01:44:34.080> best 01:44:34.310 --> 01:44:34.320 align:start position:0% seek out the stakeholders that can best 01:44:34.320 --> 01:44:36.790 align:start position:0% seek out the stakeholders that can best answer<01:44:34.560> those<01:44:34.960> so<01:44:35.119> so<01:44:35.280> mr<01:44:35.520> chairman<01:44:35.920> uh<01:44:36.480> you<01:44:36.560> do 01:44:36.790 --> 01:44:36.800 align:start position:0% answer those so so mr chairman uh you do 01:44:36.800 --> 01:44:38.310 align:start position:0% answer those so so mr chairman uh you do envision<01:44:37.119> we'll<01:44:37.280> be<01:44:37.360> able<01:44:37.520> to<01:44:38.000> i'll<01:44:38.159> be<01:44:38.239> able 01:44:38.310 --> 01:44:38.320 align:start position:0% envision we'll be able to i'll be able 01:44:38.320 --> 01:44:41.030 align:start position:0% envision we'll be able to i'll be able to<01:44:38.400> get<01:44:38.560> woody<01:44:38.880> back<01:44:39.440> uh<01:44:40.159> you<01:44:40.320> know<01:44:40.719> on<01:44:40.880> the 01:44:41.030 --> 01:44:41.040 align:start position:0% to get woody back uh you know on the 01:44:41.040 --> 01:44:43.510 align:start position:0% to get woody back uh you know on the 18th<01:44:41.679> or<01:44:42.080> one<01:44:42.239> of<01:44:42.320> those<01:44:42.560> yeah<01:44:43.119> we'll<01:44:43.280> do<01:44:43.360> a 01:44:43.510 --> 01:44:43.520 align:start position:0% 18th or one of those yeah we'll do a 01:44:43.520 --> 01:44:45.430 align:start position:0% 18th or one of those yeah we'll do a work<01:44:43.679> session<01:44:44.000> the<01:44:44.159> week<01:44:44.400> of<01:44:44.560> that<01:44:45.040> week<01:44:45.280> i 01:44:45.430 --> 01:44:45.440 align:start position:0% work session the week of that week i 01:44:45.440 --> 01:44:47.270 align:start position:0% work session the week of that week i don't<01:44:45.760> it'll<01:44:46.000> depend<01:44:46.320> on<01:44:46.400> how<01:44:46.800> robust<01:44:47.199> the 01:44:47.270 --> 01:44:47.280 align:start position:0% don't it'll depend on how robust the 01:44:47.280 --> 01:44:49.189 align:start position:0% don't it'll depend on how robust the agenda<01:44:47.600> for<01:44:47.679> that<01:44:47.840> open<01:44:48.080> meeting<01:44:48.320> is<01:44:48.800> we'll<01:44:49.040> do 01:44:49.189 --> 01:44:49.199 align:start position:0% agenda for that open meeting is we'll do 01:44:49.199 --> 01:44:51.669 align:start position:0% agenda for that open meeting is we'll do something<01:44:49.440> there 01:44:51.669 --> 01:44:51.679 align:start position:0% something there 01:44:51.679 --> 01:44:52.390 align:start position:0% something there good 01:44:52.390 --> 01:44:52.400 align:start position:0% good 01:44:52.400 --> 01:44:54.229 align:start position:0% good i'm<01:44:52.639> good<01:44:52.960> i<01:44:53.199> do<01:44:53.280> have<01:44:53.440> a<01:44:53.520> question<01:44:53.840> for<01:44:54.000> woody 01:44:54.229 --> 01:44:54.239 align:start position:0% i'm good i do have a question for woody 01:44:54.239 --> 01:44:58.070 align:start position:0% i'm good i do have a question for woody though<01:44:54.639> i'm<01:44:54.800> just<01:44:55.040> kidding 01:44:58.070 --> 01:44:58.080 align:start position:0% 01:44:58.080 --> 01:44:59.510 align:start position:0% well<01:44:58.400> played 01:44:59.510 --> 01:44:59.520 align:start position:0% well played 01:44:59.520 --> 01:45:01.189 align:start position:0% well played well<01:44:59.840> played 01:45:01.189 --> 01:45:01.199 align:start position:0% well played 01:45:01.199 --> 01:45:03.990 align:start position:0% well played all<01:45:01.440> right<01:45:01.760> the 01:45:03.990 --> 01:45:04.000 align:start position:0% 01:45:04.000 --> 01:45:05.990 align:start position:0% last<01:45:04.719> uh 01:45:05.990 --> 01:45:06.000 align:start position:0% last uh 01:45:06.000 --> 01:45:08.229 align:start position:0% last uh last<01:45:06.320> item<01:45:06.639> on<01:45:06.880> the 01:45:08.229 --> 01:45:08.239 align:start position:0% last item on the 01:45:08.239 --> 01:45:10.070 align:start position:0% last item on the existing<01:45:08.719> solution<01:45:09.280> set 01:45:10.070 --> 01:45:10.080 align:start position:0% existing solution set 01:45:10.080 --> 01:45:12.470 align:start position:0% existing solution set i've<01:45:10.320> got<01:45:10.480> is<01:45:10.639> voltage<01:45:11.040> support<01:45:11.840> uh<01:45:12.080> the<01:45:12.239> big 01:45:12.470 --> 01:45:12.480 align:start position:0% i've got is voltage support uh the big 01:45:12.480 --> 01:45:15.030 align:start position:0% i've got is voltage support uh the big questions<01:45:13.040> there<01:45:13.520> i<01:45:13.600> mean<01:45:14.080> in<01:45:14.320> many<01:45:14.560> ways<01:45:14.880> i 01:45:15.030 --> 01:45:15.040 align:start position:0% questions there i mean in many ways i 01:45:15.040 --> 01:45:16.870 align:start position:0% questions there i mean in many ways i think<01:45:15.760> we've<01:45:15.920> heard<01:45:16.159> a<01:45:16.159> lot<01:45:16.320> of<01:45:16.400> feedback<01:45:16.719> that 01:45:16.870 --> 01:45:16.880 align:start position:0% think we've heard a lot of feedback that 01:45:16.880 --> 01:45:18.229 align:start position:0% think we've heard a lot of feedback that this<01:45:17.119> is<01:45:17.199> just<01:45:17.360> catching<01:45:17.679> up<01:45:17.840> with<01:45:18.000> every 01:45:18.229 --> 01:45:18.239 align:start position:0% this is just catching up with every 01:45:18.239 --> 01:45:20.709 align:start position:0% this is just catching up with every other<01:45:18.400> iso 01:45:20.709 --> 01:45:20.719 align:start position:0% other iso 01:45:20.719 --> 01:45:22.950 align:start position:0% other iso i<01:45:20.880> don't<01:45:21.040> know<01:45:21.280> if<01:45:21.360> we<01:45:21.679> if<01:45:21.760> we<01:45:22.320> we<01:45:22.480> already<01:45:22.719> know 01:45:22.950 --> 01:45:22.960 align:start position:0% i don't know if we if we we already know 01:45:22.960 --> 01:45:24.390 align:start position:0% i don't know if we if we we already know we're<01:45:23.119> going<01:45:23.199> to<01:45:23.280> be<01:45:23.520> curtailing 01:45:24.390 --> 01:45:24.400 align:start position:0% we're going to be curtailing 01:45:24.400 --> 01:45:27.030 align:start position:0% we're going to be curtailing intermittence<01:45:25.040> at<01:45:25.199> some<01:45:25.920> upper<01:45:26.159> limit 01:45:27.030 --> 01:45:27.040 align:start position:0% intermittence at some upper limit 01:45:27.040 --> 01:45:30.470 align:start position:0% intermittence at some upper limit for<01:45:27.600> uh<01:45:28.320> inertia<01:45:28.960> as<01:45:29.119> we<01:45:29.199> heard<01:45:29.440> earlier 01:45:30.470 --> 01:45:30.480 align:start position:0% for uh inertia as we heard earlier 01:45:30.480 --> 01:45:32.390 align:start position:0% for uh inertia as we heard earlier i<01:45:30.639> don't<01:45:30.719> know<01:45:30.960> if<01:45:31.040> that<01:45:31.440> solves<01:45:31.840> some<01:45:32.159> part<01:45:32.320> of 01:45:32.390 --> 01:45:32.400 align:start position:0% i don't know if that solves some part of 01:45:32.400 --> 01:45:34.790 align:start position:0% i don't know if that solves some part of the<01:45:32.480> problem<01:45:32.800> or<01:45:33.040> if<01:45:33.199> that<01:45:33.440> problem<01:45:34.080> um<01:45:34.639> so 01:45:34.790 --> 01:45:34.800 align:start position:0% the problem or if that problem um so 01:45:34.800 --> 01:45:37.270 align:start position:0% the problem or if that problem um so that<01:45:34.960> i<01:45:35.040> guess<01:45:35.199> the<01:45:35.280> question<01:45:35.600> for<01:45:35.760> you<01:45:35.920> all<01:45:36.159> is 01:45:37.270 --> 01:45:37.280 align:start position:0% that i guess the question for you all is 01:45:37.280 --> 01:45:39.990 align:start position:0% that i guess the question for you all is to<01:45:37.440> consider<01:45:37.920> think<01:45:38.080> about<01:45:38.400> is<01:45:39.040> does<01:45:39.440> a 01:45:39.990 --> 01:45:40.000 align:start position:0% to consider think about is does a 01:45:40.000 --> 01:45:42.149 align:start position:0% to consider think about is does a curtailment<01:45:40.719> mechanism<01:45:41.679> that<01:45:41.840> we're<01:45:42.000> going 01:45:42.149 --> 01:45:42.159 align:start position:0% curtailment mechanism that we're going 01:45:42.159 --> 01:45:44.629 align:start position:0% curtailment mechanism that we're going to<01:45:42.239> have<01:45:42.400> to<01:45:42.560> use<01:45:42.800> anyway 01:45:44.629 --> 01:45:44.639 align:start position:0% to have to use anyway 01:45:44.639 --> 01:45:46.790 align:start position:0% to have to use anyway solve<01:45:44.960> that<01:45:45.119> problem<01:45:45.520> or<01:45:45.679> can<01:45:45.840> be<01:45:46.000> adjusted<01:45:46.639> to 01:45:46.790 --> 01:45:46.800 align:start position:0% solve that problem or can be adjusted to 01:45:46.800 --> 01:45:50.070 align:start position:0% solve that problem or can be adjusted to solve<01:45:47.040> that<01:45:47.280> problem<01:45:47.679> and<01:45:47.840> is<01:45:48.000> that<01:45:48.320> more 01:45:50.070 --> 01:45:50.080 align:start position:0% solve that problem and is that more 01:45:50.080 --> 01:45:51.910 align:start position:0% solve that problem and is that more is<01:45:50.239> that<01:45:50.400> a<01:45:50.480> lower<01:45:50.800> cost<01:45:51.040> for<01:45:51.199> the<01:45:51.360> consumer 01:45:51.910 --> 01:45:51.920 align:start position:0% is that a lower cost for the consumer 01:45:51.920 --> 01:45:53.910 align:start position:0% is that a lower cost for the consumer versus<01:45:52.320> building<01:45:52.719> out<01:45:53.040> and<01:45:53.440> quicker<01:45:53.760> to 01:45:53.910 --> 01:45:53.920 align:start position:0% versus building out and quicker to 01:45:53.920 --> 01:45:55.030 align:start position:0% versus building out and quicker to implement 01:45:55.030 --> 01:45:55.040 align:start position:0% implement 01:45:55.040 --> 01:45:56.709 align:start position:0% implement versus<01:45:55.440> building<01:45:55.760> out<01:45:55.920> a<01:45:56.000> new<01:45:56.159> financial 01:45:56.709 --> 01:45:56.719 align:start position:0% versus building out a new financial 01:45:56.719 --> 01:46:00.149 align:start position:0% versus building out a new financial product<01:45:57.119> or<01:45:57.280> a<01:45:57.360> new<01:45:58.320> um<01:45:58.800> a<01:45:58.960> new 01:46:00.149 --> 01:46:00.159 align:start position:0% product or a new um a new 01:46:00.159 --> 01:46:01.270 align:start position:0% product or a new um a new service 01:46:01.270 --> 01:46:01.280 align:start position:0% service 01:46:01.280 --> 01:46:02.550 align:start position:0% service i<01:46:01.360> don't<01:46:01.520> know<01:46:01.679> the<01:46:01.760> answer<01:46:02.080> and<01:46:02.239> obviously 01:46:02.550 --> 01:46:02.560 align:start position:0% i don't know the answer and obviously 01:46:02.560 --> 01:46:03.910 align:start position:0% i don't know the answer and obviously not<01:46:02.719> going<01:46:02.800> to<01:46:02.880> make<01:46:03.040> a<01:46:03.119> decision<01:46:03.520> today<01:46:03.840> i 01:46:03.910 --> 01:46:03.920 align:start position:0% not going to make a decision today i 01:46:03.920 --> 01:46:05.270 align:start position:0% not going to make a decision today i think<01:46:04.080> this<01:46:04.320> is<01:46:04.400> also<01:46:04.639> another<01:46:04.880> one<01:46:05.040> where 01:46:05.270 --> 01:46:05.280 align:start position:0% think this is also another one where 01:46:05.280 --> 01:46:07.030 align:start position:0% think this is also another one where we're<01:46:05.440> kind<01:46:05.600> of<01:46:05.760> waiting<01:46:06.159> on<01:46:06.320> some 01:46:07.030 --> 01:46:07.040 align:start position:0% we're kind of waiting on some 01:46:07.040 --> 01:46:09.669 align:start position:0% we're kind of waiting on some menu<01:46:07.360> of<01:46:07.840> options<01:46:08.320> and<01:46:08.560> whatever<01:46:09.119> i<01:46:09.199> i<01:46:09.520> would 01:46:09.669 --> 01:46:09.679 align:start position:0% menu of options and whatever i i would 01:46:09.679 --> 01:46:12.390 align:start position:0% menu of options and whatever i i would like<01:46:09.920> uh<01:46:10.239> to<01:46:10.400> see 01:46:12.390 --> 01:46:12.400 align:start position:0% like uh to see 01:46:12.400 --> 01:46:14.310 align:start position:0% like uh to see bridal<01:46:12.800> look<01:46:13.040> at<01:46:13.119> this<01:46:13.360> and<01:46:13.440> tell<01:46:13.679> us<01:46:13.920> what<01:46:14.159> the 01:46:14.310 --> 01:46:14.320 align:start position:0% bridal look at this and tell us what the 01:46:14.320 --> 01:46:15.109 align:start position:0% bridal look at this and tell us what the other 01:46:15.109 --> 01:46:15.119 align:start position:0% other 01:46:15.119 --> 01:46:18.629 align:start position:0% other region<01:46:15.840> regional<01:46:16.239> rtos<01:46:16.719> or<01:46:16.800> isos<01:46:17.360> do 01:46:18.629 --> 01:46:18.639 align:start position:0% region regional rtos or isos do 01:46:18.639 --> 01:46:20.629 align:start position:0% region regional rtos or isos do from<01:46:18.800> my<01:46:19.040> perspective<01:46:19.760> this 01:46:20.629 --> 01:46:20.639 align:start position:0% from my perspective this 01:46:20.639 --> 01:46:21.750 align:start position:0% from my perspective this really<01:46:20.960> doesn't<01:46:21.199> have<01:46:21.360> to<01:46:21.440> do<01:46:21.600> with 01:46:21.750 --> 01:46:21.760 align:start position:0% really doesn't have to do with 01:46:21.760 --> 01:46:23.910 align:start position:0% really doesn't have to do with curtailing<01:46:22.320> it<01:46:22.400> has<01:46:22.560> to<01:46:22.719> do<01:46:22.880> with 01:46:23.910 --> 01:46:23.920 align:start position:0% curtailing it has to do with 01:46:23.920 --> 01:46:26.310 align:start position:0% curtailing it has to do with generators<01:46:24.800> that<01:46:25.040> are<01:46:25.360> putting<01:46:25.679> bars<01:46:26.080> on<01:46:26.159> the 01:46:26.310 --> 01:46:26.320 align:start position:0% generators that are putting bars on the 01:46:26.320 --> 01:46:28.629 align:start position:0% generators that are putting bars on the system<01:46:27.199> when<01:46:27.440> you<01:46:27.520> put<01:46:27.760> vars<01:46:28.080> on<01:46:28.159> the<01:46:28.239> system 01:46:28.629 --> 01:46:28.639 align:start position:0% system when you put vars on the system 01:46:28.639 --> 01:46:30.629 align:start position:0% system when you put vars on the system you<01:46:28.880> reduce<01:46:29.199> your<01:46:29.280> megawatts<01:46:30.080> output<01:46:30.480> and 01:46:30.629 --> 01:46:30.639 align:start position:0% you reduce your megawatts output and 01:46:30.639 --> 01:46:32.149 align:start position:0% you reduce your megawatts output and there's<01:46:30.880> a<01:46:30.960> delta<01:46:31.360> there<01:46:31.520> that<01:46:31.679> you<01:46:31.840> should<01:46:32.000> be 01:46:32.149 --> 01:46:32.159 align:start position:0% there's a delta there that you should be 01:46:32.159 --> 01:46:33.270 align:start position:0% there's a delta there that you should be paid<01:46:32.480> for 01:46:33.270 --> 01:46:33.280 align:start position:0% paid for 01:46:33.280 --> 01:46:34.709 align:start position:0% paid for vars<01:46:33.600> on<01:46:33.679> the<01:46:33.760> system<01:46:34.159> are<01:46:34.239> absolutely 01:46:34.709 --> 01:46:34.719 align:start position:0% vars on the system are absolutely 01:46:34.719 --> 01:46:36.149 align:start position:0% vars on the system are absolutely critical<01:46:35.119> for<01:46:35.440> every<01:46:35.679> bit<01:46:35.840> of<01:46:36.000> our 01:46:36.149 --> 01:46:36.159 align:start position:0% critical for every bit of our 01:46:36.159 --> 01:46:38.629 align:start position:0% critical for every bit of our transmission<01:46:36.639> to<01:46:36.800> work<01:46:37.520> and<01:46:37.760> if<01:46:37.920> you<01:46:38.239> are<01:46:38.480> if 01:46:38.629 --> 01:46:38.639 align:start position:0% transmission to work and if you are if 01:46:38.639 --> 01:46:42.390 align:start position:0% transmission to work and if you are if there's<01:46:38.880> a<01:46:39.440> um<01:46:40.080> a<01:46:40.560> a<01:46:40.719> balancing<01:46:41.280> act<01:46:41.600> with<01:46:42.159> uh 01:46:42.390 --> 01:46:42.400 align:start position:0% there's a um a a balancing act with uh 01:46:42.400 --> 01:46:44.229 align:start position:0% there's a um a a balancing act with uh reducing<01:46:42.880> megawatts<01:46:43.440> to<01:46:43.600> put<01:46:43.760> vars<01:46:44.080> on<01:46:44.159> the 01:46:44.229 --> 01:46:44.239 align:start position:0% reducing megawatts to put vars on the 01:46:44.239 --> 01:46:47.270 align:start position:0% reducing megawatts to put vars on the system<01:46:44.639> then<01:46:45.280> uh<01:46:45.760> we're<01:46:46.320> reducing<01:46:46.880> their 01:46:47.270 --> 01:46:47.280 align:start position:0% system then uh we're reducing their 01:46:47.280 --> 01:46:50.870 align:start position:0% system then uh we're reducing their economic<01:46:48.320> value<01:46:49.280> for<01:46:49.440> the<01:46:49.520> good<01:46:49.760> of<01:46:49.920> everybody 01:46:50.870 --> 01:46:50.880 align:start position:0% economic value for the good of everybody 01:46:50.880 --> 01:46:52.310 align:start position:0% economic value for the good of everybody and<01:46:51.040> when<01:46:51.199> that<01:46:51.440> happens<01:46:51.760> they<01:46:51.920> should<01:46:52.080> have 01:46:52.310 --> 01:46:52.320 align:start position:0% and when that happens they should have 01:46:52.320 --> 01:46:55.189 align:start position:0% and when that happens they should have some<01:46:52.840> some<01:46:53.119> uh<01:46:53.840> profitability<01:46:54.560> associated 01:46:55.189 --> 01:46:55.199 align:start position:0% some some uh profitability associated 01:46:55.199 --> 01:46:57.510 align:start position:0% some some uh profitability associated with<01:46:55.360> that<01:46:56.080> um<01:46:56.320> i<01:46:56.480> don't<01:46:56.560> know<01:46:56.719> how<01:46:56.960> the<01:46:57.119> other 01:46:57.510 --> 01:46:57.520 align:start position:0% with that um i don't know how the other 01:46:57.520 --> 01:46:58.790 align:start position:0% with that um i don't know how the other regions<01:46:57.920> do<01:46:58.159> it 01:46:58.790 --> 01:46:58.800 align:start position:0% regions do it 01:46:58.800 --> 01:47:00.470 align:start position:0% regions do it so<01:46:58.960> that's<01:46:59.119> what<01:46:59.280> i'm<01:46:59.440> looking<01:46:59.679> to<01:46:59.760> bridal<01:47:00.159> to 01:47:00.470 --> 01:47:00.480 align:start position:0% so that's what i'm looking to bridal to 01:47:00.480 --> 01:47:03.030 align:start position:0% so that's what i'm looking to bridal to bring<01:47:00.719> to<01:47:00.800> the<01:47:00.880> table<01:47:01.199> agree<01:47:01.520> on<01:47:01.600> both 01:47:03.030 --> 01:47:03.040 align:start position:0% bring to the table agree on both 01:47:03.040 --> 01:47:05.030 align:start position:0% bring to the table agree on both so<01:47:03.199> from<01:47:03.520> so<01:47:03.760> for<01:47:03.920> me<01:47:04.080> the<01:47:04.159> grid<01:47:04.400> of<01:47:04.480> the<01:47:04.560> future 01:47:05.030 --> 01:47:05.040 align:start position:0% so from so for me the grid of the future 01:47:05.040 --> 01:47:07.350 align:start position:0% so from so for me the grid of the future is<01:47:05.760> curtailment's<01:47:06.400> not<01:47:06.639> the<01:47:06.800> answer<01:47:07.119> for 01:47:07.350 --> 01:47:07.360 align:start position:0% is curtailment's not the answer for 01:47:07.360 --> 01:47:09.510 align:start position:0% is curtailment's not the answer for consumers<01:47:08.000> or<01:47:08.239> the<01:47:08.400> generators<01:47:09.119> so<01:47:09.280> again 01:47:09.510 --> 01:47:09.520 align:start position:0% consumers or the generators so again 01:47:09.520 --> 01:47:11.830 align:start position:0% consumers or the generators so again it's<01:47:09.679> kind<01:47:09.840> of<01:47:09.920> like<01:47:10.560> building<01:47:10.960> out 01:47:11.830 --> 01:47:11.840 align:start position:0% it's kind of like building out 01:47:11.840 --> 01:47:15.109 align:start position:0% it's kind of like building out on-ramps<01:47:12.960> to<01:47:13.199> a<01:47:13.360> new<01:47:13.600> development<01:47:14.320> you<01:47:14.480> know 01:47:15.109 --> 01:47:15.119 align:start position:0% on-ramps to a new development you know 01:47:15.119 --> 01:47:16.950 align:start position:0% on-ramps to a new development you know we<01:47:15.280> need<01:47:15.440> to<01:47:15.520> be<01:47:15.600> able<01:47:15.760> to<01:47:15.920> do<01:47:16.159> that<01:47:16.800> to 01:47:16.950 --> 01:47:16.960 align:start position:0% we need to be able to do that to 01:47:16.960 --> 01:47:19.109 align:start position:0% we need to be able to do that to accommodate<01:47:17.520> growth<01:47:18.159> both<01:47:18.480> in<01:47:18.560> the<01:47:18.639> need<01:47:18.880> for 01:47:19.109 --> 01:47:19.119 align:start position:0% accommodate growth both in the need for 01:47:19.119 --> 01:47:22.070 align:start position:0% accommodate growth both in the need for energy<01:47:19.679> on<01:47:19.840> the<01:47:19.920> system<01:47:20.800> and<01:47:21.119> for<01:47:21.440> access<01:47:21.920> to 01:47:22.070 --> 01:47:22.080 align:start position:0% energy on the system and for access to 01:47:22.080 --> 01:47:24.870 align:start position:0% energy on the system and for access to new<01:47:22.400> and<01:47:22.560> innovative<01:47:23.040> technologies 01:47:24.870 --> 01:47:24.880 align:start position:0% new and innovative technologies 01:47:24.880 --> 01:47:27.030 align:start position:0% new and innovative technologies so<01:47:25.440> voltage<01:47:25.840> support<01:47:26.400> is<01:47:26.480> one<01:47:26.719> of<01:47:26.800> those 01:47:27.030 --> 01:47:27.040 align:start position:0% so voltage support is one of those 01:47:27.040 --> 01:47:29.910 align:start position:0% so voltage support is one of those instances<01:47:27.679> and<01:47:27.840> again<01:47:28.239> it<01:47:28.480> meets 01:47:29.910 --> 01:47:29.920 align:start position:0% instances and again it meets 01:47:29.920 --> 01:47:32.870 align:start position:0% instances and again it meets one<01:47:30.159> that<01:47:30.320> blue<01:47:30.639> sky<01:47:30.960> day<01:47:31.679> scenario<01:47:32.400> that<01:47:32.639> i 01:47:32.870 --> 01:47:32.880 align:start position:0% one that blue sky day scenario that i 01:47:32.880 --> 01:47:35.189 align:start position:0% one that blue sky day scenario that i articulated<01:47:33.600> about<01:47:33.920> fall 01:47:35.189 --> 01:47:35.199 align:start position:0% articulated about fall 01:47:35.199 --> 01:47:37.030 align:start position:0% articulated about fall when<01:47:35.600> there<01:47:36.000> is 01:47:37.030 --> 01:47:37.040 align:start position:0% when there is 01:47:37.040 --> 01:47:41.109 align:start position:0% when there is 60<01:47:37.520> gigs<01:47:38.159> of<01:47:38.719> intermittent<01:47:39.360> base<01:47:39.920> non-uh 01:47:41.109 --> 01:47:41.119 align:start position:0% 60 gigs of intermittent base non-uh 01:47:41.119 --> 01:47:44.470 align:start position:0% 60 gigs of intermittent base non-uh inver<01:47:41.840> or<01:47:42.159> inverter<01:47:42.639> based<01:47:43.440> technology<01:47:44.239> that 01:47:44.470 --> 01:47:44.480 align:start position:0% inver or inverter based technology that 01:47:44.480 --> 01:47:46.550 align:start position:0% inver or inverter based technology that is<01:47:44.639> not<01:47:44.960> supporting<01:47:45.920> the<01:47:46.080> inertial 01:47:46.550 --> 01:47:46.560 align:start position:0% is not supporting the inertial 01:47:46.560 --> 01:47:48.470 align:start position:0% is not supporting the inertial requirements<01:47:47.119> of<01:47:47.199> the<01:47:47.360> system<01:47:48.080> that<01:47:48.320> you 01:47:48.470 --> 01:47:48.480 align:start position:0% requirements of the system that you 01:47:48.480 --> 01:47:51.669 align:start position:0% requirements of the system that you would<01:47:48.800> have<01:47:49.440> good<01:47:49.679> a<01:47:50.159> a<01:47:50.320> good<01:47:50.719> base<01:47:51.119> load 01:47:51.669 --> 01:47:51.679 align:start position:0% would have good a a good base load 01:47:51.679 --> 01:47:54.149 align:start position:0% would have good a a good base load capability<01:47:52.719> that<01:47:52.880> is<01:47:53.040> providing<01:47:53.840> that 01:47:54.149 --> 01:47:54.159 align:start position:0% capability that is providing that 01:47:54.159 --> 01:47:56.470 align:start position:0% capability that is providing that service<01:47:54.800> you<01:47:54.960> know<01:47:55.119> to<01:47:55.280> cover<01:47:55.600> that<01:47:56.000> to<01:47:56.159> again 01:47:56.470 --> 01:47:56.480 align:start position:0% service you know to cover that to again 01:47:56.480 --> 01:47:57.910 align:start position:0% service you know to cover that to again accommodate<01:47:57.040> everybody<01:47:57.520> getting<01:47:57.760> their 01:47:57.910 --> 01:47:57.920 align:start position:0% accommodate everybody getting their 01:47:57.920 --> 01:48:00.149 align:start position:0% accommodate everybody getting their product<01:47:58.320> to<01:47:58.480> market<01:47:59.040> and<01:47:59.199> allowing<01:47:59.679> consumers 01:48:00.149 --> 01:48:00.159 align:start position:0% product to market and allowing consumers 01:48:00.159 --> 01:48:01.669 align:start position:0% product to market and allowing consumers to<01:48:00.320> consume<01:48:00.719> it 01:48:01.669 --> 01:48:01.679 align:start position:0% to consume it 01:48:01.679 --> 01:48:04.390 align:start position:0% to consume it it<01:48:01.920> also<01:48:02.320> stands<01:48:02.800> there<01:48:03.119> at<01:48:03.360> all<01:48:03.600> times 01:48:04.390 --> 01:48:04.400 align:start position:0% it also stands there at all times 01:48:04.400 --> 01:48:06.790 align:start position:0% it also stands there at all times to<01:48:04.639> where<01:48:04.960> it<01:48:05.280> could<01:48:05.520> be<01:48:06.159> they're<01:48:06.320> bidding<01:48:06.719> a 01:48:06.790 --> 01:48:06.800 align:start position:0% to where it could be they're bidding a 01:48:06.800 --> 01:48:10.470 align:start position:0% to where it could be they're bidding a portion<01:48:07.360> of<01:48:07.520> their<01:48:08.159> their<01:48:08.480> uh<01:48:09.119> capacity<01:48:10.239> to 01:48:10.470 --> 01:48:10.480 align:start position:0% portion of their their uh capacity to 01:48:10.480 --> 01:48:12.229 align:start position:0% portion of their their uh capacity to serve<01:48:10.800> that<01:48:11.040> purpose<01:48:11.440> but<01:48:11.600> they<01:48:11.760> could<01:48:12.080> be 01:48:12.229 --> 01:48:12.239 align:start position:0% serve that purpose but they could be 01:48:12.239 --> 01:48:14.070 align:start position:0% serve that purpose but they could be there<01:48:12.480> as<01:48:12.639> a<01:48:12.800> rampable 01:48:14.070 --> 01:48:14.080 align:start position:0% there as a rampable 01:48:14.080 --> 01:48:16.310 align:start position:0% there as a rampable you<01:48:14.159> know<01:48:14.639> service<01:48:15.040> later<01:48:15.360> on<01:48:15.600> not<01:48:15.840> service 01:48:16.310 --> 01:48:16.320 align:start position:0% you know service later on not service 01:48:16.320 --> 01:48:19.270 align:start position:0% you know service later on not service but<01:48:16.880> a<01:48:17.040> rampable<01:48:17.520> product<01:48:18.159> that's<01:48:18.400> selling<01:48:18.800> in 01:48:19.270 --> 01:48:19.280 align:start position:0% but a rampable product that's selling in 01:48:19.280 --> 01:48:21.590 align:start position:0% but a rampable product that's selling in as<01:48:19.520> as<01:48:19.760> price<01:48:20.080> responsive<01:48:20.560> behavior<01:48:20.960> dictates 01:48:21.590 --> 01:48:21.600 align:start position:0% as as price responsive behavior dictates 01:48:21.600 --> 01:48:22.629 align:start position:0% as as price responsive behavior dictates price 01:48:22.629 --> 01:48:22.639 align:start position:0% price 01:48:22.639 --> 01:48:25.669 align:start position:0% price i<01:48:22.719> mean<01:48:23.119> as<01:48:23.360> ordc<01:48:23.920> dictates<01:48:24.719> so<01:48:24.960> i<01:48:25.119> believe<01:48:25.520> you 01:48:25.669 --> 01:48:25.679 align:start position:0% i mean as ordc dictates so i believe you 01:48:25.679 --> 01:48:26.950 align:start position:0% i mean as ordc dictates so i believe you do<01:48:25.920> need<01:48:26.239> a 01:48:26.950 --> 01:48:26.960 align:start position:0% do need a 01:48:26.960 --> 01:48:29.750 align:start position:0% do need a specific<01:48:27.840> service<01:48:28.560> to<01:48:28.800> support<01:48:29.199> this<01:48:29.600> with 01:48:29.750 --> 01:48:29.760 align:start position:0% specific service to support this with 01:48:29.760 --> 01:48:30.550 align:start position:0% specific service to support this with the 01:48:30.550 --> 01:48:30.560 align:start position:0% the 01:48:30.560 --> 01:48:32.470 align:start position:0% the resource<01:48:31.119> mix<01:48:31.679> that<01:48:31.840> we're<01:48:32.000> going<01:48:32.159> to<01:48:32.239> see 01:48:32.470 --> 01:48:32.480 align:start position:0% resource mix that we're going to see 01:48:32.480 --> 01:48:34.550 align:start position:0% resource mix that we're going to see over<01:48:32.639> the<01:48:32.719> next<01:48:32.960> 20<01:48:33.280> years<01:48:33.920> and<01:48:34.159> we<01:48:34.320> would<01:48:34.400> be 01:48:34.550 --> 01:48:34.560 align:start position:0% over the next 20 years and we would be 01:48:34.560 --> 01:48:36.550 align:start position:0% over the next 20 years and we would be prudent<01:48:34.960> to<01:48:35.119> develop<01:48:35.520> that<01:48:35.760> now<01:48:36.320> that<01:48:36.480> it 01:48:36.550 --> 01:48:36.560 align:start position:0% prudent to develop that now that it 01:48:36.560 --> 01:48:38.709 align:start position:0% prudent to develop that now that it could<01:48:36.719> be<01:48:36.960> scalable<01:48:37.679> to<01:48:37.920> match<01:48:38.239> that<01:48:38.560> with 01:48:38.709 --> 01:48:38.719 align:start position:0% could be scalable to match that with 01:48:38.719 --> 01:48:42.870 align:start position:0% could be scalable to match that with whatever<01:48:39.119> that<01:48:39.600> that<01:48:39.840> mix<01:48:40.159> dictates 01:48:42.870 --> 01:48:42.880 align:start position:0% 01:48:42.880 --> 01:48:44.229 align:start position:0% so<01:48:43.119> a<01:48:43.280> separate 01:48:44.229 --> 01:48:44.239 align:start position:0% so a separate 01:48:44.239 --> 01:48:45.990 align:start position:0% so a separate service<01:48:44.800> just<01:48:45.040> a<01:48:45.119> separate<01:48:45.440> voltage<01:48:45.440> voltage 01:48:45.990 --> 01:48:46.000 align:start position:0% service just a separate voltage voltage 01:48:46.000 --> 01:48:48.550 align:start position:0% service just a separate voltage voltage support<01:48:46.239> services 01:48:48.550 --> 01:48:48.560 align:start position:0% support services 01:48:48.560 --> 01:48:50.550 align:start position:0% support services uh<01:48:48.719> when<01:48:48.880> you<01:48:49.040> say<01:48:49.520> curtailment's<01:48:50.239> not<01:48:50.400> part 01:48:50.550 --> 01:48:50.560 align:start position:0% uh when you say curtailment's not part 01:48:50.560 --> 01:48:52.229 align:start position:0% uh when you say curtailment's not part of<01:48:50.639> the<01:48:50.719> solution<01:48:51.119> so<01:48:51.280> are<01:48:51.360> you<01:48:51.440> saying<01:48:51.679> no 01:48:52.229 --> 01:48:52.239 align:start position:0% of the solution so are you saying no 01:48:52.239 --> 01:48:54.310 align:start position:0% of the solution so are you saying no long<01:48:52.480> term<01:48:52.719> sir<01:48:53.119> i<01:48:53.199> mean<01:48:53.440> in<01:48:53.600> in<01:48:53.840> 20<01:48:54.080> years<01:48:54.239> in 01:48:54.310 --> 01:48:54.320 align:start position:0% long term sir i mean in in 20 years in 01:48:54.320 --> 01:48:55.990 align:start position:0% long term sir i mean in in 20 years in the<01:48:54.400> future<01:48:54.719> i'd<01:48:54.880> rather<01:48:55.119> not<01:48:55.280> be<01:48:55.440> curtailing 01:48:55.990 --> 01:48:56.000 align:start position:0% the future i'd rather not be curtailing 01:48:56.000 --> 01:48:57.590 align:start position:0% the future i'd rather not be curtailing i<01:48:56.159> i<01:48:56.480> think<01:48:56.639> we<01:48:56.719> need<01:48:56.880> to 01:48:57.590 --> 01:48:57.600 align:start position:0% i i think we need to 01:48:57.600 --> 01:48:58.950 align:start position:0% i i think we need to that's<01:48:57.840> what<01:48:58.000> we're<01:48:58.159> doing<01:48:58.320> here<01:48:58.719> we're 01:48:58.950 --> 01:48:58.960 align:start position:0% that's what we're doing here we're 01:48:58.960 --> 01:49:00.870 align:start position:0% that's what we're doing here we're building<01:48:59.199> the<01:48:59.360> architecture<01:48:59.920> to<01:49:00.080> a<01:49:00.159> system 01:49:00.870 --> 01:49:00.880 align:start position:0% building the architecture to a system 01:49:00.880 --> 01:49:02.790 align:start position:0% building the architecture to a system that<01:49:01.040> can<01:49:01.280> adapt<01:49:01.760> to<01:49:01.920> the<01:49:02.080> resource<01:49:02.480> mix<01:49:02.719> of 01:49:02.790 --> 01:49:02.800 align:start position:0% that can adapt to the resource mix of 01:49:02.800 --> 01:49:04.310 align:start position:0% that can adapt to the resource mix of the<01:49:02.960> future 01:49:04.310 --> 01:49:04.320 align:start position:0% the future 01:49:04.320 --> 01:49:06.470 align:start position:0% the future okay<01:49:04.560> well<01:49:04.800> i<01:49:04.800> mean<01:49:04.960> that's<01:49:05.280> that's 01:49:06.470 --> 01:49:06.480 align:start position:0% okay well i mean that's that's 01:49:06.480 --> 01:49:07.669 align:start position:0% okay well i mean that's that's that<01:49:06.719> i<01:49:06.800> mean<01:49:06.960> that<01:49:07.040> gets<01:49:07.280> a<01:49:07.360> broader 01:49:07.669 --> 01:49:07.679 align:start position:0% that i mean that gets a broader 01:49:07.679 --> 01:49:08.950 align:start position:0% that i mean that gets a broader philosophical<01:49:08.320> question<01:49:08.560> i<01:49:08.639> don't<01:49:08.719> know<01:49:08.800> we 01:49:08.950 --> 01:49:08.960 align:start position:0% philosophical question i don't know we 01:49:08.960 --> 01:49:10.070 align:start position:0% philosophical question i don't know we need<01:49:09.040> to<01:49:09.280> well<01:49:09.440> i<01:49:09.520> don't<01:49:09.600> want<01:49:09.679> to<01:49:09.760> go<01:49:09.840> into<01:49:10.000> a 01:49:10.070 --> 01:49:10.080 align:start position:0% need to well i don't want to go into a 01:49:10.080 --> 01:49:12.310 align:start position:0% need to well i don't want to go into a nebulous<01:49:10.560> philosophical<01:49:11.199> question<01:49:11.920> well<01:49:12.159> be 01:49:12.310 --> 01:49:12.320 align:start position:0% nebulous philosophical question well be 01:49:12.320 --> 01:49:14.070 align:start position:0% nebulous philosophical question well be like<01:49:12.400> that<01:49:12.719> that's<01:49:12.960> a<01:49:13.040> that's<01:49:13.199> an<01:49:13.360> exit<01:49:13.840> called 01:49:14.070 --> 01:49:14.080 align:start position:0% like that that's a that's an exit called 01:49:14.080 --> 01:49:15.990 align:start position:0% like that that's a that's an exit called an<01:49:14.239> existential<01:49:14.880> question<01:49:15.199> that<01:49:15.440> is<01:49:15.760> people 01:49:15.990 --> 01:49:16.000 align:start position:0% an existential question that is people 01:49:16.000 --> 01:49:17.270 align:start position:0% an existential question that is people are<01:49:16.159> grappling<01:49:16.400> with<01:49:16.639> around<01:49:16.800> the<01:49:16.880> world<01:49:17.119> can 01:49:17.270 --> 01:49:17.280 align:start position:0% are grappling with around the world can 01:49:17.280 --> 01:49:19.669 align:start position:0% are grappling with around the world can you<01:49:17.520> ever<01:49:17.679> have<01:49:17.920> an<01:49:18.080> entirely<01:49:18.480> inverter<01:49:18.880> based 01:49:19.669 --> 01:49:19.679 align:start position:0% you ever have an entirely inverter based 01:49:19.679 --> 01:49:21.430 align:start position:0% you ever have an entirely inverter based grid 01:49:21.430 --> 01:49:21.440 align:start position:0% grid 01:49:21.440 --> 01:49:23.910 align:start position:0% grid yes<01:49:21.679> or<01:49:21.840> no<01:49:22.480> if<01:49:22.639> the<01:49:22.800> answer<01:49:23.040> is<01:49:23.280> yes<01:49:23.599> that's 01:49:23.910 --> 01:49:23.920 align:start position:0% yes or no if the answer is yes that's 01:49:23.920 --> 01:49:26.629 align:start position:0% yes or no if the answer is yes that's one<01:49:24.400> path<01:49:24.639> to<01:49:24.719> go<01:49:24.880> down<01:49:25.119> if<01:49:25.199> the<01:49:25.360> answer<01:49:25.599> is<01:49:25.760> no 01:49:26.629 --> 01:49:26.639 align:start position:0% one path to go down if the answer is no 01:49:26.639 --> 01:49:28.390 align:start position:0% one path to go down if the answer is no then<01:49:26.800> we<01:49:26.960> need<01:49:27.119> to<01:49:27.199> be<01:49:27.360> realistic<01:49:27.920> about<01:49:28.080> that 01:49:28.390 --> 01:49:28.400 align:start position:0% then we need to be realistic about that 01:49:28.400 --> 01:49:29.910 align:start position:0% then we need to be realistic about that the<01:49:28.480> bank<01:49:28.719> of<01:49:28.880> england<01:49:29.119> and<01:49:29.199> the<01:49:29.280> u.s<01:49:29.599> federal 01:49:29.910 --> 01:49:29.920 align:start position:0% the bank of england and the u.s federal 01:49:29.920 --> 01:49:31.589 align:start position:0% the bank of england and the u.s federal reserve<01:49:30.400> seem<01:49:30.639> to<01:49:30.800> have<01:49:31.199> come<01:49:31.360> to<01:49:31.520> a 01:49:31.589 --> 01:49:31.599 align:start position:0% reserve seem to have come to a 01:49:31.599 --> 01:49:33.109 align:start position:0% reserve seem to have come to a conclusion<01:49:32.080> on<01:49:32.159> that<01:49:32.400> so<01:49:32.560> i'm<01:49:32.639> just<01:49:32.800> trying<01:49:33.040> to 01:49:33.109 --> 01:49:33.119 align:start position:0% conclusion on that so i'm just trying to 01:49:33.119 --> 01:49:34.390 align:start position:0% conclusion on that so i'm just trying to make<01:49:33.280> sure<01:49:33.520> like<01:49:33.679> i<01:49:33.760> said<01:49:34.000> look<01:49:34.159> at<01:49:34.239> what 01:49:34.390 --> 01:49:34.400 align:start position:0% make sure like i said look at what 01:49:34.400 --> 01:49:36.390 align:start position:0% make sure like i said look at what people<01:49:34.719> do<01:49:34.960> instead<01:49:35.199> of<01:49:35.280> what<01:49:35.440> they<01:49:35.599> say 01:49:36.390 --> 01:49:36.400 align:start position:0% people do instead of what they say 01:49:36.400 --> 01:49:39.109 align:start position:0% people do instead of what they say this<01:49:36.639> the<01:49:37.199> nation<01:49:37.520> of<01:49:37.679> england<01:49:38.400> just<01:49:38.560> went<01:49:38.880> all 01:49:39.109 --> 01:49:39.119 align:start position:0% this the nation of england just went all 01:49:39.119 --> 01:49:41.510 align:start position:0% this the nation of england just went all in<01:49:39.280> on<01:49:39.440> rotating<01:49:39.920> mass<01:49:40.239> thermal<01:49:40.560> nuke 01:49:41.510 --> 01:49:41.520 align:start position:0% in on rotating mass thermal nuke 01:49:41.520 --> 01:49:42.870 align:start position:0% in on rotating mass thermal nuke and<01:49:41.760> walked<01:49:42.000> away<01:49:42.239> from<01:49:42.480> wind<01:49:42.800> and 01:49:42.870 --> 01:49:42.880 align:start position:0% and walked away from wind and 01:49:42.880 --> 01:49:45.270 align:start position:0% and walked away from wind and intermittency<01:49:44.000> so<01:49:44.400> watch<01:49:44.639> what<01:49:44.880> people<01:49:45.040> do 01:49:45.270 --> 01:49:45.280 align:start position:0% intermittency so watch what people do 01:49:45.280 --> 01:49:48.550 align:start position:0% intermittency so watch what people do not<01:49:45.440> what<01:49:45.599> they<01:49:45.760> say<01:49:46.320> sure 01:49:48.550 --> 01:49:48.560 align:start position:0% 01:49:48.560 --> 01:49:50.070 align:start position:0% we<01:49:48.719> don't<01:49:48.880> need<01:49:49.119> to<01:49:49.199> go<01:49:49.360> down<01:49:49.599> that<01:49:49.760> entire 01:49:50.070 --> 01:49:50.080 align:start position:0% we don't need to go down that entire 01:49:50.080 --> 01:49:51.910 align:start position:0% we don't need to go down that entire road<01:49:50.320> but<01:49:50.480> that's<01:49:51.119> i<01:49:51.199> mean<01:49:51.280> that's<01:49:51.520> that's 01:49:51.910 --> 01:49:51.920 align:start position:0% road but that's i mean that's that's 01:49:51.920 --> 01:49:55.109 align:start position:0% road but that's i mean that's that's that's<01:49:52.159> an<01:49:52.239> important<01:49:52.560> yes<01:49:52.800> or<01:49:52.880> no<01:49:53.119> question 01:49:55.109 --> 01:49:55.119 align:start position:0% that's an important yes or no question 01:49:55.119 --> 01:49:56.310 align:start position:0% that's an important yes or no question and<01:49:55.360> it's<01:49:55.520> important<01:49:55.760> to<01:49:55.920> watch<01:49:56.159> what 01:49:56.310 --> 01:49:56.320 align:start position:0% and it's important to watch what 01:49:56.320 --> 01:49:58.709 align:start position:0% and it's important to watch what everybody<01:49:56.719> else<01:49:56.880> is<01:49:57.040> doing<01:49:57.280> around<01:49:57.520> the<01:49:57.599> world 01:49:58.709 --> 01:49:58.719 align:start position:0% everybody else is doing around the world 01:49:58.719 --> 01:50:00.950 align:start position:0% everybody else is doing around the world that<01:49:58.960> seems<01:49:59.199> to<01:49:59.280> be<01:49:59.520> a<01:49:59.760> pretty<01:50:00.080> quick<01:50:00.400> 60<01:50:00.719> 90 01:50:00.950 --> 01:50:00.960 align:start position:0% that seems to be a pretty quick 60 90 01:50:00.960 --> 01:50:02.070 align:start position:0% that seems to be a pretty quick 60 90 day<01:50:01.119> switch 01:50:02.070 --> 01:50:02.080 align:start position:0% day switch 01:50:02.080 --> 01:50:05.990 align:start position:0% day switch after<01:50:02.400> a<01:50:02.639> low<01:50:02.880> win<01:50:03.119> summer 01:50:05.990 --> 01:50:06.000 align:start position:0% 01:50:06.000 --> 01:50:07.510 align:start position:0% and<01:50:06.159> the<01:50:06.239> rest<01:50:06.480> of<01:50:06.560> the<01:50:06.560> world<01:50:06.800> is<01:50:06.880> going<01:50:07.280> to 01:50:07.510 --> 01:50:07.520 align:start position:0% and the rest of the world is going to 01:50:07.520 --> 01:50:09.350 align:start position:0% and the rest of the world is going to reliable<01:50:08.000> resources<01:50:08.560> a<01:50:08.639> different<01:50:08.960> form<01:50:09.199> we 01:50:09.350 --> 01:50:09.360 align:start position:0% reliable resources a different form we 01:50:09.360 --> 01:50:11.910 align:start position:0% reliable resources a different form we can't<01:50:09.520> do<01:50:09.679> anything<01:50:10.000> about<01:50:10.239> it<01:50:10.560> our<01:50:10.800> federal 01:50:11.910 --> 01:50:11.920 align:start position:0% can't do anything about it our federal 01:50:11.920 --> 01:50:13.510 align:start position:0% can't do anything about it our federal restrictions 01:50:13.510 --> 01:50:13.520 align:start position:0% restrictions 01:50:13.520 --> 01:50:15.350 align:start position:0% restrictions but<01:50:13.840> that's<01:50:14.159> a<01:50:14.480> something<01:50:14.800> to<01:50:14.880> consider 01:50:15.350 --> 01:50:15.360 align:start position:0% but that's a something to consider 01:50:15.360 --> 01:50:16.629 align:start position:0% but that's a something to consider seriously 01:50:16.629 --> 01:50:16.639 align:start position:0% seriously 01:50:16.639 --> 01:50:18.390 align:start position:0% seriously yes<01:50:16.880> or<01:50:17.040> no<01:50:17.679> on 01:50:18.390 --> 01:50:18.400 align:start position:0% yes or no on 01:50:18.400 --> 01:50:20.470 align:start position:0% yes or no on 100<01:50:18.960> inverter<01:50:19.360> based 01:50:20.470 --> 01:50:20.480 align:start position:0% 100 inverter based 01:50:20.480 --> 01:50:21.510 align:start position:0% 100 inverter based or<01:50:20.719> not 01:50:21.510 --> 01:50:21.520 align:start position:0% or not 01:50:21.520 --> 01:50:22.790 align:start position:0% or not we're<01:50:21.840> obviously<01:50:22.159> not<01:50:22.320> going<01:50:22.400> to<01:50:22.480> follow 01:50:22.790 --> 01:50:22.800 align:start position:0% we're obviously not going to follow 01:50:22.800 --> 01:50:25.750 align:start position:0% we're obviously not going to follow today<01:50:24.159> solve<01:50:24.480> it<01:50:24.639> all<01:50:24.800> today 01:50:25.750 --> 01:50:25.760 align:start position:0% today solve it all today 01:50:25.760 --> 01:50:27.750 align:start position:0% today solve it all today the 01:50:27.750 --> 01:50:27.760 align:start position:0% the 01:50:27.760 --> 01:50:29.750 align:start position:0% the like<01:50:28.080> everybody 01:50:29.750 --> 01:50:29.760 align:start position:0% like everybody 01:50:29.760 --> 01:50:31.270 align:start position:0% like everybody seems<01:50:30.000> supportive<01:50:30.480> of<01:50:30.560> some<01:50:30.800> version<01:50:31.199> of 01:50:31.270 --> 01:50:31.280 align:start position:0% seems supportive of some version of 01:50:31.280 --> 01:50:32.870 align:start position:0% seems supportive of some version of voltage<01:50:31.679> support 01:50:32.870 --> 01:50:32.880 align:start position:0% voltage support 01:50:32.880 --> 01:50:34.629 align:start position:0% voltage support the 01:50:34.629 --> 01:50:34.639 align:start position:0% the 01:50:34.639 --> 01:50:37.350 align:start position:0% the details<01:50:35.119> tbd<01:50:36.000> the<01:50:36.239> menu<01:50:36.719> i<01:50:36.800> think<01:50:36.960> is<01:50:37.119> already 01:50:37.350 --> 01:50:37.360 align:start position:0% details tbd the menu i think is already 01:50:37.360 --> 01:50:40.310 align:start position:0% details tbd the menu i think is already in<01:50:37.520> process<01:50:38.320> good<01:50:38.880> um<01:50:39.119> yes<01:50:39.440> ma'am 01:50:40.310 --> 01:50:40.320 align:start position:0% in process good um yes ma'am 01:50:40.320 --> 01:50:42.790 align:start position:0% in process good um yes ma'am so<01:50:40.560> chairman<01:50:41.040> um<01:50:41.440> one<01:50:41.599> thing<01:50:41.760> i<01:50:42.000> and<01:50:42.320> it<01:50:42.480> may<01:50:42.639> be 01:50:42.790 --> 01:50:42.800 align:start position:0% so chairman um one thing i and it may be 01:50:42.800 --> 01:50:44.550 align:start position:0% so chairman um one thing i and it may be on<01:50:42.880> your<01:50:43.040> list<01:50:43.280> but<01:50:43.440> i<01:50:43.920> want<01:50:44.080> to<01:50:44.159> make<01:50:44.320> sure 01:50:44.550 --> 01:50:44.560 align:start position:0% on your list but i want to make sure 01:50:44.560 --> 01:50:46.229 align:start position:0% on your list but i want to make sure that<01:50:44.719> we<01:50:44.800> do<01:50:45.040> cover<01:50:45.280> this<01:50:45.599> because<01:50:45.920> of<01:50:46.000> the 01:50:46.229 --> 01:50:46.239 align:start position:0% that we do cover this because of the 01:50:46.239 --> 01:50:48.790 align:start position:0% that we do cover this because of the upcoming<01:50:46.639> deadline<01:50:47.040> for<01:50:47.199> urcot's<01:50:47.679> rfp 01:50:48.790 --> 01:50:48.800 align:start position:0% upcoming deadline for urcot's rfp 01:50:48.800 --> 01:50:51.030 align:start position:0% upcoming deadline for urcot's rfp um<01:50:49.040> the<01:50:49.199> ers 01:50:51.030 --> 01:50:51.040 align:start position:0% um the ers 01:50:51.040 --> 01:50:53.030 align:start position:0% um the ers oh<01:50:51.280> yeah<01:50:51.520> winter<01:50:51.760> contract<01:50:52.159> period<01:50:52.639> um<01:50:52.880> we 01:50:53.030 --> 01:50:53.040 align:start position:0% oh yeah winter contract period um we 01:50:53.040 --> 01:50:55.270 align:start position:0% oh yeah winter contract period um we directed<01:50:53.440> our<01:50:53.599> content<01:50:54.159> it's<01:50:54.560> fine<01:50:54.800> uh<01:50:54.960> we<01:50:55.119> we 01:50:55.270 --> 01:50:55.280 align:start position:0% directed our content it's fine uh we we 01:50:55.280 --> 01:50:57.350 align:start position:0% directed our content it's fine uh we we directed<01:50:55.760> ercot<01:50:56.320> to 01:50:57.350 --> 01:50:57.360 align:start position:0% directed ercot to 01:50:57.360 --> 01:50:59.030 align:start position:0% directed ercot to look<01:50:57.599> at<01:50:58.080> um 01:50:59.030 --> 01:50:59.040 align:start position:0% look at um 01:50:59.040 --> 01:51:01.510 align:start position:0% look at um a<01:50:59.199> variety<01:50:59.599> of<01:50:59.760> options<01:51:00.080> to<01:51:00.239> bring<01:51:00.480> us<01:51:00.639> some 01:51:01.510 --> 01:51:01.520 align:start position:0% a variety of options to bring us some 01:51:01.520 --> 01:51:03.750 align:start position:0% a variety of options to bring us some some<01:51:01.760> options<01:51:02.159> as<01:51:02.320> to<01:51:02.480> how<01:51:03.119> to<01:51:03.360> for<01:51:03.599> us<01:51:03.679> to 01:51:03.750 --> 01:51:03.760 align:start position:0% some options as to how to for us to 01:51:03.760 --> 01:51:05.270 align:start position:0% some options as to how to for us to evaluate<01:51:04.239> how<01:51:04.400> much<01:51:04.639> additional<01:51:04.960> money<01:51:05.199> you 01:51:05.270 --> 01:51:05.280 align:start position:0% evaluate how much additional money you 01:51:05.280 --> 01:51:06.390 align:start position:0% evaluate how much additional money you want<01:51:05.360> to<01:51:05.520> add<01:51:05.599> to<01:51:05.679> the<01:51:05.760> winner<01:51:06.000> contract 01:51:06.390 --> 01:51:06.400 align:start position:0% want to add to the winner contract 01:51:06.400 --> 01:51:09.030 align:start position:0% want to add to the winner contract period<01:51:07.199> yes<01:51:07.760> we've<01:51:08.000> already<01:51:08.400> directed<01:51:08.880> them 01:51:09.030 --> 01:51:09.040 align:start position:0% period yes we've already directed them 01:51:09.040 --> 01:51:11.830 align:start position:0% period yes we've already directed them through<01:51:09.679> through<01:51:09.920> a<01:51:10.400> good<01:51:10.639> cause 01:51:11.830 --> 01:51:11.840 align:start position:0% through through a good cause 01:51:11.840 --> 01:51:13.830 align:start position:0% through through a good cause issue<01:51:12.080> not<01:51:12.239> an<01:51:12.400> order 01:51:13.830 --> 01:51:13.840 align:start position:0% issue not an order 01:51:13.840 --> 01:51:15.830 align:start position:0% issue not an order approving<01:51:14.239> a<01:51:14.320> good<01:51:14.480> cost<01:51:14.719> waiver<01:51:15.199> to<01:51:15.440> allow 01:51:15.830 --> 01:51:15.840 align:start position:0% approving a good cost waiver to allow 01:51:15.840 --> 01:51:17.589 align:start position:0% approving a good cost waiver to allow ercot<01:51:16.320> to<01:51:16.480> use 01:51:17.589 --> 01:51:17.599 align:start position:0% ercot to use 01:51:17.599 --> 01:51:20.950 align:start position:0% ercot to use ers<01:51:18.480> before<01:51:19.119> we<01:51:19.280> get<01:51:19.440> to<01:51:19.520> conservation 01:51:20.950 --> 01:51:20.960 align:start position:0% ers before we get to conservation 01:51:20.960 --> 01:51:22.470 align:start position:0% ers before we get to conservation absolutely<01:51:21.360> millions<01:51:21.679> of<01:51:21.760> texans<01:51:22.159> as<01:51:22.320> you 01:51:22.470 --> 01:51:22.480 align:start position:0% absolutely millions of texans as you 01:51:22.480 --> 01:51:25.109 align:start position:0% absolutely millions of texans as you said<01:51:22.800> to<01:51:23.199> um<01:51:23.440> change<01:51:23.679> their<01:51:24.000> daily<01:51:24.239> lives 01:51:25.109 --> 01:51:25.119 align:start position:0% said to um change their daily lives 01:51:25.119 --> 01:51:26.709 align:start position:0% said to um change their daily lives so<01:51:25.760> uh 01:51:26.709 --> 01:51:26.719 align:start position:0% so uh 01:51:26.719 --> 01:51:29.830 align:start position:0% so uh but<01:51:27.119> we've<01:51:27.360> got<01:51:27.599> to<01:51:28.239> uh<01:51:28.560> provide<01:51:29.119> feedback<01:51:29.679> to 01:51:29.830 --> 01:51:29.840 align:start position:0% but we've got to uh provide feedback to 01:51:29.840 --> 01:51:31.990 align:start position:0% but we've got to uh provide feedback to our<01:51:30.080> cod<01:51:30.320> as<01:51:30.480> that<01:51:30.880> how<01:51:31.040> much<01:51:31.360> money<01:51:31.599> we<01:51:31.760> want 01:51:31.990 --> 01:51:32.000 align:start position:0% our cod as that how much money we want 01:51:32.000 --> 01:51:34.229 align:start position:0% our cod as that how much money we want them<01:51:32.400> additional<01:51:32.880> money<01:51:33.119> we<01:51:33.280> want<01:51:33.520> them<01:51:34.159> to 01:51:34.229 --> 01:51:34.239 align:start position:0% them additional money we want them to 01:51:34.239 --> 01:51:36.229 align:start position:0% them additional money we want them to add<01:51:34.480> to<01:51:34.639> our<01:51:34.800> upcoming<01:51:35.280> winter<01:51:35.840> contract 01:51:36.229 --> 01:51:36.239 align:start position:0% add to our upcoming winter contract 01:51:36.239 --> 01:51:38.790 align:start position:0% add to our upcoming winter contract period<01:51:36.560> that<01:51:36.639> covers<01:51:37.360> december<01:51:38.239> january<01:51:38.639> and 01:51:38.790 --> 01:51:38.800 align:start position:0% period that covers december january and 01:51:38.800 --> 01:51:40.709 align:start position:0% period that covers december january and february<01:51:39.440> and<01:51:39.599> again<01:51:39.920> to<01:51:40.000> remind<01:51:40.320> the<01:51:40.400> public 01:51:40.709 --> 01:51:40.719 align:start position:0% february and again to remind the public 01:51:40.719 --> 01:51:42.310 align:start position:0% february and again to remind the public we<01:51:40.880> are<01:51:41.040> doing<01:51:41.360> this 01:51:42.310 --> 01:51:42.320 align:start position:0% we are doing this 01:51:42.320 --> 01:51:44.070 align:start position:0% we are doing this to 01:51:44.070 --> 01:51:44.080 align:start position:0% to 01:51:44.080 --> 01:51:45.589 align:start position:0% to add<01:51:44.400> an<01:51:44.560> additional 01:51:45.589 --> 01:51:45.599 align:start position:0% add an additional 01:51:45.599 --> 01:51:47.750 align:start position:0% add an additional tool<01:51:46.000> to<01:51:46.159> our<01:51:46.320> arsenal<01:51:46.800> of<01:51:46.960> tools<01:51:47.280> to<01:51:47.440> maintain 01:51:47.750 --> 01:51:47.760 align:start position:0% tool to our arsenal of tools to maintain 01:51:47.760 --> 01:51:49.669 align:start position:0% tool to our arsenal of tools to maintain reliability<01:51:48.480> for<01:51:48.639> this<01:51:48.960> upcoming<01:51:49.360> winter 01:51:49.669 --> 01:51:49.679 align:start position:0% reliability for this upcoming winter 01:51:49.679 --> 01:51:52.629 align:start position:0% reliability for this upcoming winter season<01:51:50.400> and<01:51:50.639> so<01:51:51.280> i<01:51:51.360> don't<01:51:51.520> know<01:51:51.679> if<01:51:51.760> david<01:51:52.320> dave 01:51:52.629 --> 01:51:52.639 align:start position:0% season and so i don't know if david dave 01:51:52.639 --> 01:51:53.750 align:start position:0% season and so i don't know if david dave maggio 01:51:53.750 --> 01:51:53.760 align:start position:0% maggio 01:51:53.760 --> 01:51:55.589 align:start position:0% maggio has<01:51:54.000> any<01:51:54.320> specific<01:51:54.800> feedback<01:51:55.199> for<01:51:55.360> us<01:51:55.520> that 01:51:55.589 --> 01:51:55.599 align:start position:0% has any specific feedback for us that 01:51:55.599 --> 01:51:58.149 align:start position:0% has any specific feedback for us that maybe<01:51:55.840> we<01:51:56.000> can<01:51:56.400> mule<01:51:56.719> over<01:51:56.960> and<01:51:57.040> then 01:51:58.149 --> 01:51:58.159 align:start position:0% maybe we can mule over and then 01:51:58.159 --> 01:52:00.070 align:start position:0% maybe we can mule over and then make<01:51:58.400> a<01:51:58.480> decision<01:51:58.880> now<01:51:59.119> or<01:51:59.440> come<01:51:59.599> back<01:51:59.840> after 01:52:00.070 --> 01:52:00.080 align:start position:0% make a decision now or come back after 01:52:00.080 --> 01:52:03.270 align:start position:0% make a decision now or come back after the<01:52:00.159> lunch<01:52:00.400> break<01:52:00.639> and<01:52:00.719> make<01:52:00.880> a<01:52:00.960> decision 01:52:03.270 --> 01:52:03.280 align:start position:0% the lunch break and make a decision 01:52:03.280 --> 01:52:05.430 align:start position:0% the lunch break and make a decision so<01:52:03.679> we<01:52:04.159> have<01:52:04.400> looked<01:52:04.639> at<01:52:04.880> some<01:52:05.119> different 01:52:05.430 --> 01:52:05.440 align:start position:0% so we have looked at some different 01:52:05.440 --> 01:52:07.030 align:start position:0% so we have looked at some different options<01:52:05.760> for<01:52:05.840> how<01:52:06.000> to<01:52:06.159> increase<01:52:06.560> specifically 01:52:07.030 --> 01:52:07.040 align:start position:0% options for how to increase specifically 01:52:07.040 --> 01:52:08.950 align:start position:0% options for how to increase specifically the<01:52:07.199> amount<01:52:07.440> of<01:52:07.520> money<01:52:07.760> we<01:52:07.920> spent<01:52:08.239> for<01:52:08.880> the 01:52:08.950 --> 01:52:08.960 align:start position:0% the amount of money we spent for the 01:52:08.960 --> 01:52:10.950 align:start position:0% the amount of money we spent for the winter<01:52:09.280> months 01:52:10.950 --> 01:52:10.960 align:start position:0% winter months 01:52:10.960 --> 01:52:11.910 align:start position:0% winter months we 01:52:11.910 --> 01:52:11.920 align:start position:0% we 01:52:11.920 --> 01:52:13.109 align:start position:0% we essentially<01:52:12.239> looked<01:52:12.480> at<01:52:12.560> four<01:52:12.800> different 01:52:13.109 --> 01:52:13.119 align:start position:0% essentially looked at four different 01:52:13.119 --> 01:52:14.310 align:start position:0% essentially looked at four different options 01:52:14.310 --> 01:52:14.320 align:start position:0% options 01:52:14.320 --> 01:52:16.550 align:start position:0% options one<01:52:14.560> was<01:52:15.040> increasing<01:52:15.440> it<01:52:15.520> by<01:52:15.760> 5<01:52:16.159> million<01:52:16.480> or 01:52:16.550 --> 01:52:16.560 align:start position:0% one was increasing it by 5 million or 01:52:16.560 --> 01:52:18.550 align:start position:0% one was increasing it by 5 million or approximately<01:52:17.040> 5<01:52:17.280> million<01:52:17.760> by<01:52:17.920> approximately 01:52:18.550 --> 01:52:18.560 align:start position:0% approximately 5 million by approximately 01:52:18.560 --> 01:52:19.350 align:start position:0% approximately 5 million by approximately 10 01:52:19.350 --> 01:52:19.360 align:start position:0% 10 01:52:19.360 --> 01:52:21.030 align:start position:0% 10 uh<01:52:19.679> approximately<01:52:20.159> 15<01:52:20.800> and<01:52:20.880> then 01:52:21.030 --> 01:52:21.040 align:start position:0% uh approximately 15 and then 01:52:21.040 --> 01:52:23.669 align:start position:0% uh approximately 15 and then approximately<01:52:21.599> 20<01:52:21.840> million<01:52:22.159> dollars 01:52:23.669 --> 01:52:23.679 align:start position:0% approximately 20 million dollars 01:52:23.679 --> 01:52:25.189 align:start position:0% approximately 20 million dollars i<01:52:24.000> i<01:52:24.080> guess<01:52:24.320> with<01:52:24.480> the<01:52:24.719> within<01:52:25.040> those 01:52:25.189 --> 01:52:25.199 align:start position:0% i i guess with the within those 01:52:25.199 --> 01:52:26.629 align:start position:0% i i guess with the within those different<01:52:25.520> options<01:52:25.840> for<01:52:26.000> the<01:52:26.159> first<01:52:26.400> two 01:52:26.629 --> 01:52:26.639 align:start position:0% different options for the first two 01:52:26.639 --> 01:52:29.430 align:start position:0% different options for the first two looking<01:52:26.960> at<01:52:27.520> uh<01:52:27.920> five<01:52:28.239> and<01:52:28.880> ten<01:52:29.119> million 01:52:29.430 --> 01:52:29.440 align:start position:0% looking at uh five and ten million 01:52:29.440 --> 01:52:32.149 align:start position:0% looking at uh five and ten million dollars<01:52:30.159> uh<01:52:30.719> we<01:52:30.880> would<01:52:31.119> largely<01:52:31.599> be<01:52:31.840> and<01:52:32.000> again 01:52:32.149 --> 01:52:32.159 align:start position:0% dollars uh we would largely be and again 01:52:32.159 --> 01:52:33.750 align:start position:0% dollars uh we would largely be and again this<01:52:32.320> sort<01:52:32.480> of<01:52:32.560> assumes<01:52:32.960> not<01:52:33.119> an<01:52:33.280> increase<01:52:33.599> to 01:52:33.750 --> 01:52:33.760 align:start position:0% this sort of assumes not an increase to 01:52:33.760 --> 01:52:35.030 align:start position:0% this sort of assumes not an increase to the<01:52:33.840> annual<01:52:34.159> budget<01:52:34.480> although<01:52:34.880> that's 01:52:35.030 --> 01:52:35.040 align:start position:0% the annual budget although that's 01:52:35.040 --> 01:52:36.629 align:start position:0% the annual budget although that's something<01:52:35.280> you<01:52:35.360> already<01:52:35.599> have<01:52:35.679> 10<01:52:35.920> or<01:52:36.000> 20<01:52:36.560> of 01:52:36.629 --> 01:52:36.639 align:start position:0% something you already have 10 or 20 of 01:52:36.639 --> 01:52:39.510 align:start position:0% something you already have 10 or 20 of the<01:52:37.199> annual<01:52:37.520> 50<01:52:37.840> million<01:52:38.400> so<01:52:39.040> so<01:52:39.199> right<01:52:39.360> now 01:52:39.510 --> 01:52:39.520 align:start position:0% the annual 50 million so so right now 01:52:39.520 --> 01:52:41.109 align:start position:0% the annual 50 million so so right now the<01:52:39.760> the<01:52:39.920> amount<01:52:40.239> that<01:52:40.400> we<01:52:40.560> current<01:52:40.800> spend 01:52:41.109 --> 01:52:41.119 align:start position:0% the the amount that we current spend 01:52:41.119 --> 01:52:43.270 align:start position:0% the the amount that we current spend with<01:52:41.280> the<01:52:41.440> with<01:52:41.599> the<01:52:41.760> current<01:52:42.000> rfp<01:52:42.960> the<01:52:43.040> amount 01:52:43.270 --> 01:52:43.280 align:start position:0% with the with the current rfp the amount 01:52:43.280 --> 01:52:45.270 align:start position:0% with the with the current rfp the amount we<01:52:43.440> spend<01:52:43.679> of<01:52:43.760> that<01:52:44.000> that<01:52:44.239> total<01:52:44.560> 50<01:52:44.880> million 01:52:45.270 --> 01:52:45.280 align:start position:0% we spend of that that total 50 million 01:52:45.280 --> 01:52:47.990 align:start position:0% we spend of that that total 50 million is<01:52:45.440> is<01:52:45.840> uh<01:52:46.159> just<01:52:46.400> over<01:52:46.639> 21<01:52:47.040> million<01:52:47.360> dollars 01:52:47.990 --> 01:52:48.000 align:start position:0% is is uh just over 21 million dollars 01:52:48.000 --> 01:52:49.189 align:start position:0% is is uh just over 21 million dollars and<01:52:48.080> they<01:52:48.239> were<01:52:48.400> talking<01:52:48.719> about<01:52:48.880> for<01:52:49.119> the 01:52:49.189 --> 01:52:49.199 align:start position:0% and they were talking about for the 01:52:49.199 --> 01:52:50.950 align:start position:0% and they were talking about for the winter<01:52:49.840> and<01:52:49.920> then<01:52:50.080> the<01:52:50.239> options<01:52:50.639> we<01:52:50.719> looked<01:52:50.880> at 01:52:50.950 --> 01:52:50.960 align:start position:0% winter and then the options we looked at 01:52:50.960 --> 01:52:53.350 align:start position:0% winter and then the options we looked at we're<01:52:51.199> increasing<01:52:51.599> that<01:52:51.760> by<01:52:52.000> 5<01:52:52.320> million 01:52:53.350 --> 01:52:53.360 align:start position:0% we're increasing that by 5 million 01:52:53.360 --> 01:52:55.109 align:start position:0% we're increasing that by 5 million 10<01:52:53.520> million<01:52:53.840> 15<01:52:54.159> million<01:52:54.480> and<01:52:54.560> 20<01:52:54.800> million 01:52:55.109 --> 01:52:55.119 align:start position:0% 10 million 15 million and 20 million 01:52:55.119 --> 01:52:56.550 align:start position:0% 10 million 15 million and 20 million thank<01:52:55.280> you<01:52:55.360> for<01:52:55.440> the<01:52:55.520> context 01:52:56.550 --> 01:52:56.560 align:start position:0% thank you for the context 01:52:56.560 --> 01:52:59.430 align:start position:0% thank you for the context yes<01:52:56.840> sir<01:52:57.679> uh<01:52:57.920> so<01:52:58.159> i<01:52:58.239> guess<01:52:58.400> within<01:52:58.880> the<01:52:59.199> really 01:52:59.430 --> 01:52:59.440 align:start position:0% yes sir uh so i guess within the really 01:52:59.440 --> 01:53:01.910 align:start position:0% yes sir uh so i guess within the really the<01:52:59.679> the<01:53:00.080> 5<01:53:00.400> million<01:53:00.719> and<01:53:00.880> 10<01:53:01.119> million<01:53:01.599> uh 01:53:01.910 --> 01:53:01.920 align:start position:0% the the 5 million and 10 million uh 01:53:01.920 --> 01:53:03.830 align:start position:0% the the 5 million and 10 million uh increase<01:53:02.400> and<01:53:02.560> again<01:53:02.800> this<01:53:02.960> assumes<01:53:03.360> no 01:53:03.830 --> 01:53:03.840 align:start position:0% increase and again this assumes no 01:53:03.840 --> 01:53:06.470 align:start position:0% increase and again this assumes no increase<01:53:04.159> to<01:53:04.320> the<01:53:04.480> annual<01:53:04.800> budget<01:53:05.599> uh 01:53:06.470 --> 01:53:06.480 align:start position:0% increase to the annual budget uh 01:53:06.480 --> 01:53:08.790 align:start position:0% increase to the annual budget uh largely<01:53:06.960> leaving<01:53:07.360> the<01:53:07.679> the<01:53:07.920> summer<01:53:08.480> months 01:53:08.790 --> 01:53:08.800 align:start position:0% largely leaving the the summer months 01:53:08.800 --> 01:53:10.550 align:start position:0% largely leaving the the summer months the<01:53:08.960> same<01:53:09.199> and<01:53:09.280> where<01:53:09.440> we<01:53:09.679> really<01:53:10.000> be<01:53:10.159> taking 01:53:10.550 --> 01:53:10.560 align:start position:0% the same and where we really be taking 01:53:10.560 --> 01:53:12.629 align:start position:0% the same and where we really be taking the<01:53:10.639> dollars<01:53:11.040> away<01:53:11.280> would<01:53:11.440> be<01:53:11.679> from<01:53:12.159> the<01:53:12.480> the 01:53:12.629 --> 01:53:12.639 align:start position:0% the dollars away would be from the the 01:53:12.639 --> 01:53:14.629 align:start position:0% the dollars away would be from the the spring<01:53:12.960> and<01:53:13.119> fall<01:53:13.280> months 01:53:14.629 --> 01:53:14.639 align:start position:0% spring and fall months 01:53:14.639 --> 01:53:17.109 align:start position:0% spring and fall months as<01:53:14.880> we<01:53:15.040> get<01:53:15.280> into<01:53:15.920> options<01:53:16.480> three<01:53:16.719> and<01:53:16.880> four 01:53:17.109 --> 01:53:17.119 align:start position:0% as we get into options three and four 01:53:17.119 --> 01:53:19.189 align:start position:0% as we get into options three and four for<01:53:17.280> the<01:53:17.520> the<01:53:17.679> 15<01:53:18.000> million<01:53:18.320> dollars<01:53:18.719> in<01:53:18.800> the<01:53:18.960> 20 01:53:19.189 --> 01:53:19.199 align:start position:0% for the the 15 million dollars in the 20 01:53:19.199 --> 01:53:21.430 align:start position:0% for the the 15 million dollars in the 20 million<01:53:19.440> dollar<01:53:19.760> increase<01:53:20.239> at<01:53:20.400> that<01:53:20.560> point 01:53:21.430 --> 01:53:21.440 align:start position:0% million dollar increase at that point 01:53:21.440 --> 01:53:23.589 align:start position:0% million dollar increase at that point again<01:53:21.679> this<01:53:21.840> assumes<01:53:22.320> not<01:53:22.880> no<01:53:23.119> increase<01:53:23.440> to 01:53:23.589 --> 01:53:23.599 align:start position:0% again this assumes not no increase to 01:53:23.599 --> 01:53:24.950 align:start position:0% again this assumes not no increase to the<01:53:23.679> annual<01:53:24.000> budget<01:53:24.239> we<01:53:24.400> would<01:53:24.560> start<01:53:24.719> to<01:53:24.800> be 01:53:24.950 --> 01:53:24.960 align:start position:0% the annual budget we would start to be 01:53:24.960 --> 01:53:27.109 align:start position:0% the annual budget we would start to be taking<01:53:25.520> more<01:53:25.760> dollars<01:53:26.159> away<01:53:26.480> from<01:53:26.719> what<01:53:26.880> we 01:53:27.109 --> 01:53:27.119 align:start position:0% taking more dollars away from what we 01:53:27.119 --> 01:53:30.550 align:start position:0% taking more dollars away from what we have<01:53:27.280> available<01:53:27.679> for<01:53:27.840> the<01:53:28.000> summer 01:53:30.550 --> 01:53:30.560 align:start position:0% 01:53:30.560 --> 01:53:32.470 align:start position:0% and<01:53:30.880> i<01:53:31.040> guess<01:53:31.440> if<01:53:31.599> it's<01:53:31.679> helpful<01:53:32.000> i<01:53:32.080> can<01:53:32.239> say 01:53:32.470 --> 01:53:32.480 align:start position:0% and i guess if it's helpful i can say 01:53:32.480 --> 01:53:34.629 align:start position:0% and i guess if it's helpful i can say the<01:53:32.880> in<01:53:33.040> those<01:53:33.280> options<01:53:33.760> for 01:53:34.629 --> 01:53:34.639 align:start position:0% the in those options for 01:53:34.639 --> 01:53:37.189 align:start position:0% the in those options for uh<01:53:34.960> for<01:53:35.119> the<01:53:35.280> summer<01:53:35.840> um<01:53:36.400> the<01:53:36.480> current<01:53:36.800> spend 01:53:37.189 --> 01:53:37.199 align:start position:0% uh for the summer um the current spend 01:53:37.199 --> 01:53:40.149 align:start position:0% uh for the summer um the current spend is<01:53:37.440> just<01:53:37.679> over<01:53:37.920> 17<01:53:38.320> million<01:53:38.840> dollars<01:53:39.760> and<01:53:40.000> that 01:53:40.149 --> 01:53:40.159 align:start position:0% is just over 17 million dollars and that 01:53:40.159 --> 01:53:42.310 align:start position:0% is just over 17 million dollars and that stays<01:53:40.480> again<01:53:40.719> relatively<01:53:41.199> the<01:53:41.280> same<01:53:41.599> for<01:53:41.920> for 01:53:42.310 --> 01:53:42.320 align:start position:0% stays again relatively the same for for 01:53:42.320 --> 01:53:43.589 align:start position:0% stays again relatively the same for for the<01:53:42.560> five<01:53:42.880> and<01:53:42.960> ten<01:53:43.119> million<01:53:43.360> dollar 01:53:43.589 --> 01:53:43.599 align:start position:0% the five and ten million dollar 01:53:43.599 --> 01:53:46.310 align:start position:0% the five and ten million dollar increases<01:53:44.159> for<01:53:44.480> the<01:53:44.719> 15<01:53:45.280> and<01:53:45.520> 20<01:53:45.840> that<01:53:46.000> drops 01:53:46.310 --> 01:53:46.320 align:start position:0% increases for the 15 and 20 that drops 01:53:46.320 --> 01:53:49.589 align:start position:0% increases for the 15 and 20 that drops to<01:53:46.639> first<01:53:47.360> uh<01:53:47.679> 12<01:53:48.239> million<01:53:48.639> and<01:53:49.040> a<01:53:49.280> little<01:53:49.440> bit 01:53:49.589 --> 01:53:49.599 align:start position:0% to first uh 12 million and a little bit 01:53:49.599 --> 01:53:52.149 align:start position:0% to first uh 12 million and a little bit above<01:53:49.840> that<01:53:50.159> and<01:53:50.239> then<01:53:50.880> finally<01:53:51.360> for<01:53:51.679> the<01:53:51.920> 20 01:53:52.149 --> 01:53:52.159 align:start position:0% above that and then finally for the 20 01:53:52.159 --> 01:53:53.910 align:start position:0% above that and then finally for the 20 million<01:53:52.639> increase<01:53:52.960> that<01:53:53.040> would<01:53:53.280> drop 01:53:53.910 --> 01:53:53.920 align:start position:0% million increase that would drop 01:53:53.920 --> 01:53:56.390 align:start position:0% million increase that would drop somewhere<01:53:54.239> down<01:53:54.480> to<01:53:54.960> seven<01:53:55.679> seven<01:53:56.000> and<01:53:56.080> a<01:53:56.159> half 01:53:56.390 --> 01:53:56.400 align:start position:0% somewhere down to seven seven and a half 01:53:56.400 --> 01:53:58.149 align:start position:0% somewhere down to seven seven and a half million<01:53:56.639> or<01:53:56.800> so<01:53:57.280> i<01:53:57.440> certainly<01:53:57.840> don't<01:53:58.000> want<01:53:58.080> to 01:53:58.149 --> 01:53:58.159 align:start position:0% million or so i certainly don't want to 01:53:58.159 --> 01:54:00.149 align:start position:0% million or so i certainly don't want to cut<01:53:58.400> into<01:53:58.560> summer<01:53:58.800> i<01:53:58.880> think<01:53:59.040> that's<01:53:59.280> the<01:53:59.440> first 01:54:00.149 --> 01:54:00.159 align:start position:0% cut into summer i think that's the first 01:54:00.159 --> 01:54:00.870 align:start position:0% cut into summer i think that's the first no 01:54:00.870 --> 01:54:00.880 align:start position:0% no 01:54:00.880 --> 01:54:02.390 align:start position:0% no first<01:54:01.199> decision<01:54:01.599> point 01:54:02.390 --> 01:54:02.400 align:start position:0% first decision point 01:54:02.400 --> 01:54:05.030 align:start position:0% first decision point mr<01:54:02.639> chairman<01:54:03.040> in<01:54:03.280> in<01:54:03.360> my<01:54:03.520> view<01:54:03.760> ers 01:54:05.030 --> 01:54:05.040 align:start position:0% mr chairman in in my view ers 01:54:05.040 --> 01:54:07.669 align:start position:0% mr chairman in in my view ers when<01:54:05.280> i<01:54:05.360> suggested<01:54:06.159> moving<01:54:06.560> uh<01:54:06.880> and<01:54:07.040> we<01:54:07.280> i 01:54:07.669 --> 01:54:07.679 align:start position:0% when i suggested moving uh and we i 01:54:07.679 --> 01:54:08.950 align:start position:0% when i suggested moving uh and we i think<01:54:07.840> we're<01:54:08.000> all<01:54:08.080> in<01:54:08.159> the<01:54:08.239> same<01:54:08.400> boat<01:54:08.639> when<01:54:08.800> we 01:54:08.950 --> 01:54:08.960 align:start position:0% think we're all in the same boat when we 01:54:08.960 --> 01:54:11.830 align:start position:0% think we're all in the same boat when we all<01:54:09.119> concurrently<01:54:09.679> suggested<01:54:10.800> moving<01:54:11.199> ers 01:54:11.830 --> 01:54:11.840 align:start position:0% all concurrently suggested moving ers 01:54:11.840 --> 01:54:14.310 align:start position:0% all concurrently suggested moving ers out<01:54:12.000> from<01:54:12.320> behind<01:54:12.719> eea<01:54:13.520> the<01:54:13.679> intent<01:54:14.000> was<01:54:14.159> not 01:54:14.310 --> 01:54:14.320 align:start position:0% out from behind eea the intent was not 01:54:14.320 --> 01:54:15.830 align:start position:0% out from behind eea the intent was not to<01:54:14.400> kill<01:54:14.719> ers 01:54:15.830 --> 01:54:15.840 align:start position:0% to kill ers 01:54:15.840 --> 01:54:18.070 align:start position:0% to kill ers and<01:54:16.239> what<01:54:16.400> would<01:54:16.560> kill<01:54:16.880> ers<01:54:17.360> is<01:54:17.520> to<01:54:17.679> drive 01:54:18.070 --> 01:54:18.080 align:start position:0% and what would kill ers is to drive 01:54:18.080 --> 01:54:20.709 align:start position:0% and what would kill ers is to drive participation<01:54:18.880> away<01:54:19.199> from<01:54:19.440> ers<01:54:20.159> and<01:54:20.320> so<01:54:20.560> as 01:54:20.709 --> 01:54:20.719 align:start position:0% participation away from ers and so as 01:54:20.719 --> 01:54:23.910 align:start position:0% participation away from ers and so as you<01:54:20.960> know<01:54:21.679> um<01:54:22.320> value<01:54:22.880> is<01:54:23.040> associated<01:54:23.679> with 01:54:23.910 --> 01:54:23.920 align:start position:0% you know um value is associated with 01:54:23.920 --> 01:54:26.550 align:start position:0% you know um value is associated with your<01:54:24.400> perceived<01:54:25.520> um 01:54:26.550 --> 01:54:26.560 align:start position:0% your perceived um 01:54:26.560 --> 01:54:29.030 align:start position:0% your perceived um probability<01:54:27.360> of<01:54:27.599> the<01:54:27.760> service<01:54:28.159> being<01:54:28.480> used 01:54:29.030 --> 01:54:29.040 align:start position:0% probability of the service being used 01:54:29.040 --> 01:54:31.589 align:start position:0% probability of the service being used and<01:54:29.360> many<01:54:29.679> participants<01:54:30.320> were 01:54:31.589 --> 01:54:31.599 align:start position:0% and many participants were 01:54:31.599 --> 01:54:32.709 align:start position:0% and many participants were considered<01:54:32.000> we're<01:54:32.239> never<01:54:32.400> going<01:54:32.480> to<01:54:32.560> get 01:54:32.709 --> 01:54:32.719 align:start position:0% considered we're never going to get 01:54:32.719 --> 01:54:34.149 align:start position:0% considered we're never going to get called<01:54:32.960> upon<01:54:33.280> you<01:54:33.360> know<01:54:33.440> we're<01:54:33.599> going<01:54:33.679> to<01:54:34.000> take 01:54:34.149 --> 01:54:34.159 align:start position:0% called upon you know we're going to take 01:54:34.159 --> 01:54:35.669 align:start position:0% called upon you know we're going to take money<01:54:34.480> and<01:54:34.560> we'll<01:54:34.719> sit<01:54:34.960> there<01:54:35.280> and<01:54:35.360> we'll<01:54:35.520> be 01:54:35.669 --> 01:54:35.679 align:start position:0% money and we'll sit there and we'll be 01:54:35.679 --> 01:54:37.589 align:start position:0% money and we'll sit there and we'll be the<01:54:35.840> break<01:54:36.000> the<01:54:36.159> glass<01:54:36.480> plan<01:54:36.800> and<01:54:36.880> we're 01:54:37.589 --> 01:54:37.599 align:start position:0% the break the glass plan and we're 01:54:37.599 --> 01:54:38.470 align:start position:0% the break the glass plan and we're within 01:54:38.470 --> 01:54:38.480 align:start position:0% within 01:54:38.480 --> 01:54:40.790 align:start position:0% within eea<01:54:39.360> but<01:54:39.520> now<01:54:39.679> we're<01:54:39.920> actively<01:54:40.320> discussing 01:54:40.790 --> 01:54:40.800 align:start position:0% eea but now we're actively discussing 01:54:40.800 --> 01:54:43.510 align:start position:0% eea but now we're actively discussing using<01:54:41.199> it<01:54:41.440> on<01:54:41.520> the<01:54:41.679> spectrum<01:54:42.639> of<01:54:42.960> options 01:54:43.510 --> 01:54:43.520 align:start position:0% using it on the spectrum of options 01:54:43.520 --> 01:54:44.870 align:start position:0% using it on the spectrum of options after<01:54:44.000> uh 01:54:44.870 --> 01:54:44.880 align:start position:0% after uh 01:54:44.880 --> 01:54:46.229 align:start position:0% after uh we've<01:54:45.119> already<01:54:45.360> granted<01:54:45.679> the<01:54:45.840> good<01:54:46.000> cause 01:54:46.229 --> 01:54:46.239 align:start position:0% we've already granted the good cause 01:54:46.239 --> 01:54:48.709 align:start position:0% we've already granted the good cause exceptions<01:54:47.199> yeah<01:54:47.760> we're<01:54:47.920> doing<01:54:48.080> committed 01:54:48.709 --> 01:54:48.719 align:start position:0% exceptions yeah we're doing committed 01:54:48.719 --> 01:54:51.589 align:start position:0% exceptions yeah we're doing committed yeah<01:54:49.199> so<01:54:49.760> um 01:54:51.589 --> 01:54:51.599 align:start position:0% yeah so um 01:54:51.599 --> 01:54:53.350 align:start position:0% yeah so um i<01:54:51.760> understand<01:54:52.159> ercot<01:54:52.480> is<01:54:52.560> just<01:54:52.880> moving<01:54:53.119> money 01:54:53.350 --> 01:54:53.360 align:start position:0% i understand ercot is just moving money 01:54:53.360 --> 01:54:54.790 align:start position:0% i understand ercot is just moving money around<01:54:53.760> to<01:54:53.840> make<01:54:54.080> it<01:54:54.159> work<01:54:54.400> and<01:54:54.480> they're<01:54:54.639> not 01:54:54.790 --> 01:54:54.800 align:start position:0% around to make it work and they're not 01:54:54.800 --> 01:54:55.990 align:start position:0% around to make it work and they're not assuming<01:54:55.199> that<01:54:55.280> we're<01:54:55.440> going<01:54:55.520> to<01:54:55.599> grant<01:54:55.840> them 01:54:55.990 --> 01:54:56.000 align:start position:0% assuming that we're going to grant them 01:54:56.000 --> 01:54:58.070 align:start position:0% assuming that we're going to grant them a<01:54:56.080> budget<01:54:56.480> two<01:54:56.639> different<01:54:56.880> things<01:54:57.280> right<01:54:57.760> yeah 01:54:58.070 --> 01:54:58.080 align:start position:0% a budget two different things right yeah 01:54:58.080 --> 01:55:00.550 align:start position:0% a budget two different things right yeah deploying<01:54:58.639> it<01:54:59.040> sooner<01:54:59.760> is<01:54:59.920> separate<01:55:00.239> from 01:55:00.550 --> 01:55:00.560 align:start position:0% deploying it sooner is separate from 01:55:00.560 --> 01:55:02.550 align:start position:0% deploying it sooner is separate from adjusting<01:55:01.040> the<01:55:01.199> amount<01:55:01.440> of<01:55:01.520> money<01:55:01.760> we<01:55:02.000> spend 01:55:02.550 --> 01:55:02.560 align:start position:0% adjusting the amount of money we spend 01:55:02.560 --> 01:55:05.589 align:start position:0% adjusting the amount of money we spend each<01:55:02.840> quarter<01:55:03.920> yeah<01:55:04.159> it<01:55:04.320> is<01:55:04.639> but<01:55:05.040> the<01:55:05.280> the 01:55:05.589 --> 01:55:05.599 align:start position:0% each quarter yeah it is but the the 01:55:05.599 --> 01:55:07.750 align:start position:0% each quarter yeah it is but the the value<01:55:06.080> of<01:55:06.159> the<01:55:06.400> service<01:55:06.880> is<01:55:07.040> going<01:55:07.199> to<01:55:07.440> change 01:55:07.750 --> 01:55:07.760 align:start position:0% value of the service is going to change 01:55:07.760 --> 01:55:09.270 align:start position:0% value of the service is going to change so<01:55:07.920> the<01:55:08.000> amount<01:55:08.239> of<01:55:08.400> money<01:55:08.719> that<01:55:08.800> they<01:55:09.040> will 01:55:09.270 --> 01:55:09.280 align:start position:0% so the amount of money that they will 01:55:09.280 --> 01:55:10.070 align:start position:0% so the amount of money that they will need 01:55:10.070 --> 01:55:10.080 align:start position:0% need 01:55:10.080 --> 01:55:11.910 align:start position:0% need uh<01:55:10.639> increases 01:55:11.910 --> 01:55:11.920 align:start position:0% uh increases 01:55:11.920 --> 01:55:14.629 align:start position:0% uh increases so<01:55:12.400> the<01:55:12.560> analysis<01:55:13.599> and<01:55:13.760> again 01:55:14.629 --> 01:55:14.639 align:start position:0% so the analysis and again 01:55:14.639 --> 01:55:16.470 align:start position:0% so the analysis and again there's<01:55:14.880> nothing<01:55:15.199> in<01:55:15.280> comments<01:55:16.080> so<01:55:16.320> i'm 01:55:16.470 --> 01:55:16.480 align:start position:0% there's nothing in comments so i'm 01:55:16.480 --> 01:55:17.910 align:start position:0% there's nothing in comments so i'm either<01:55:16.639> going<01:55:16.719> to<01:55:16.800> get<01:55:16.960> it<01:55:17.119> individually<01:55:17.679> but 01:55:17.910 --> 01:55:17.920 align:start position:0% either going to get it individually but 01:55:17.920 --> 01:55:19.350 align:start position:0% either going to get it individually but frankly<01:55:18.239> i'd<01:55:18.320> like<01:55:18.560> it<01:55:18.639> transparent<01:55:19.199> because 01:55:19.350 --> 01:55:19.360 align:start position:0% frankly i'd like it transparent because 01:55:19.360 --> 01:55:21.750 align:start position:0% frankly i'd like it transparent because this<01:55:19.520> is<01:55:19.679> a<01:55:19.760> market<01:55:20.480> how<01:55:20.719> much<01:55:20.960> money<01:55:21.360> do<01:55:21.520> we 01:55:21.750 --> 01:55:21.760 align:start position:0% this is a market how much money do we 01:55:21.760 --> 01:55:24.709 align:start position:0% this is a market how much money do we need<01:55:22.080> to<01:55:22.239> meet<01:55:22.480> the<01:55:22.880> the<01:55:23.360> high<01:55:23.679> level<01:55:24.000> 60<01:55:24.400> 000 01:55:24.709 --> 01:55:24.719 align:start position:0% need to meet the the high level 60 000 01:55:24.719 --> 01:55:27.189 align:start position:0% need to meet the the high level 60 000 foot<01:55:25.040> policy<01:55:25.520> goal<01:55:25.760> that<01:55:25.920> the<01:55:26.080> commission<01:55:26.960> has 01:55:27.189 --> 01:55:27.199 align:start position:0% foot policy goal that the commission has 01:55:27.199 --> 01:55:29.910 align:start position:0% foot policy goal that the commission has adopted<01:55:27.840> through<01:55:28.239> our<01:55:28.480> good<01:55:28.719> cause<01:55:29.040> exception 01:55:29.910 --> 01:55:29.920 align:start position:0% adopted through our good cause exception 01:55:29.920 --> 01:55:32.310 align:start position:0% adopted through our good cause exception do<01:55:30.159> we<01:55:30.320> need<01:55:30.639> on<01:55:30.800> an<01:55:30.960> annual<01:55:31.280> basis<01:55:31.920> with 01:55:32.310 --> 01:55:32.320 align:start position:0% do we need on an annual basis with 01:55:32.320 --> 01:55:37.030 align:start position:0% do we need on an annual basis with deployment<01:55:32.960> of<01:55:33.119> eea<01:55:33.920> of<01:55:34.400> ers<01:55:35.040> outside<01:55:35.520> of<01:55:35.760> eea 01:55:37.030 --> 01:55:37.040 align:start position:0% deployment of eea of ers outside of eea 01:55:37.040 --> 01:55:39.510 align:start position:0% deployment of eea of ers outside of eea um<01:55:37.679> how<01:55:37.840> do<01:55:38.000> we<01:55:38.239> size<01:55:38.560> that<01:55:38.800> before<01:55:39.199> before<01:55:39.440> you 01:55:39.510 --> 01:55:39.520 align:start position:0% um how do we size that before before you 01:55:39.520 --> 01:55:40.470 align:start position:0% um how do we size that before before you get<01:55:39.679> there<01:55:39.840> this<01:55:40.000> is<01:55:40.080> something<01:55:40.320> you've 01:55:40.470 --> 01:55:40.480 align:start position:0% get there this is something you've 01:55:40.480 --> 01:55:42.070 align:start position:0% get there this is something you've brought<01:55:40.639> up<01:55:40.800> before 01:55:42.070 --> 01:55:42.080 align:start position:0% brought up before 01:55:42.080 --> 01:55:43.270 align:start position:0% brought up before what<01:55:42.320> how<01:55:42.480> do<01:55:42.560> you<01:55:42.639> want<01:55:42.719> to<01:55:42.800> measure<01:55:43.119> it 01:55:43.270 --> 01:55:43.280 align:start position:0% what how do you want to measure it 01:55:43.280 --> 01:55:44.550 align:start position:0% what how do you want to measure it exactly<01:55:43.679> measure<01:55:43.920> it<01:55:44.000> in<01:55:44.080> dollars<01:55:44.400> or 01:55:44.550 --> 01:55:44.560 align:start position:0% exactly measure it in dollars or 01:55:44.560 --> 01:55:46.709 align:start position:0% exactly measure it in dollars or megawatts<01:55:45.520> i<01:55:45.679> think<01:55:45.840> there's<01:55:46.159> you've<01:55:46.320> made<01:55:46.560> a 01:55:46.709 --> 01:55:46.719 align:start position:0% megawatts i think there's you've made a 01:55:46.719 --> 01:55:48.790 align:start position:0% megawatts i think there's you've made a very<01:55:46.880> good<01:55:47.119> case<01:55:47.360> in<01:55:47.440> the<01:55:47.520> past<01:55:47.840> that<01:55:48.400> the 01:55:48.790 --> 01:55:48.800 align:start position:0% very good case in the past that the 01:55:48.800 --> 01:55:50.550 align:start position:0% very good case in the past that the annual<01:55:49.119> procurement<01:55:49.599> or<01:55:50.159> seasonal 01:55:50.550 --> 01:55:50.560 align:start position:0% annual procurement or seasonal 01:55:50.560 --> 01:55:52.149 align:start position:0% annual procurement or seasonal procurement<01:55:51.040> should<01:55:51.199> be<01:55:51.280> based<01:55:51.520> on<01:55:51.679> a<01:55:51.760> percent 01:55:52.149 --> 01:55:52.159 align:start position:0% procurement should be based on a percent 01:55:52.159 --> 01:55:53.109 align:start position:0% procurement should be based on a percent of 01:55:53.109 --> 01:55:53.119 align:start position:0% of 01:55:53.119 --> 01:55:55.990 align:start position:0% of or<01:55:53.360> some<01:55:53.760> some<01:55:54.080> metric<01:55:54.480> tied<01:55:54.800> to<01:55:54.960> anticipated 01:55:55.990 --> 01:55:56.000 align:start position:0% or some some metric tied to anticipated 01:55:56.000 --> 01:55:57.910 align:start position:0% or some some metric tied to anticipated peak<01:55:56.239> load 01:55:57.910 --> 01:55:57.920 align:start position:0% peak load 01:55:57.920 --> 01:55:59.270 align:start position:0% peak load and 01:55:59.270 --> 01:55:59.280 align:start position:0% and 01:55:59.280 --> 01:56:01.109 align:start position:0% and to<01:55:59.520> to<01:55:59.679> your 01:56:01.109 --> 01:56:01.119 align:start position:0% to to your 01:56:01.119 --> 01:56:04.310 align:start position:0% to to your good<01:56:01.360> point<01:56:01.679> that<01:56:01.920> in<01:56:02.000> the<01:56:02.080> past<01:56:02.560> ers<01:56:03.040> has<01:56:03.199> been 01:56:04.310 --> 01:56:04.320 align:start position:0% good point that in the past ers has been 01:56:04.320 --> 01:56:07.109 align:start position:0% good point that in the past ers has been uh<01:56:04.880> was<01:56:05.119> never<01:56:05.360> really<01:56:05.599> expected<01:56:06.080> to<01:56:06.159> be<01:56:06.320> used 01:56:07.109 --> 01:56:07.119 align:start position:0% uh was never really expected to be used 01:56:07.119 --> 01:56:09.109 align:start position:0% uh was never really expected to be used as<01:56:07.280> a<01:56:07.440> consumer<01:56:08.159> and<01:56:08.400> i<01:56:08.480> think<01:56:08.719> speaking<01:56:08.960> for 01:56:09.109 --> 01:56:09.119 align:start position:0% as a consumer and i think speaking for 01:56:09.119 --> 01:56:10.709 align:start position:0% as a consumer and i think speaking for all<01:56:09.280> consumers 01:56:10.709 --> 01:56:10.719 align:start position:0% all consumers 01:56:10.719 --> 01:56:11.589 align:start position:0% all consumers if 01:56:11.589 --> 01:56:11.599 align:start position:0% if 01:56:11.599 --> 01:56:12.709 align:start position:0% if our 01:56:12.709 --> 01:56:12.719 align:start position:0% our 01:56:12.719 --> 01:56:15.030 align:start position:0% our ratepayers<01:56:13.360> are<01:56:13.520> paying<01:56:13.840> for<01:56:14.000> something<01:56:14.880> they 01:56:15.030 --> 01:56:15.040 align:start position:0% ratepayers are paying for something they 01:56:15.040 --> 01:56:16.790 align:start position:0% ratepayers are paying for something they should<01:56:15.280> certainly<01:56:15.599> expect<01:56:16.000> to<01:56:16.320> receive<01:56:16.719> the 01:56:16.790 --> 01:56:16.800 align:start position:0% should certainly expect to receive the 01:56:16.800 --> 01:56:18.310 align:start position:0% should certainly expect to receive the benefit<01:56:17.360> of<01:56:17.520> it 01:56:18.310 --> 01:56:18.320 align:start position:0% benefit of it 01:56:18.320 --> 01:56:19.669 align:start position:0% benefit of it so<01:56:18.639> i'm 01:56:19.669 --> 01:56:19.679 align:start position:0% so i'm 01:56:19.679 --> 01:56:22.629 align:start position:0% so i'm i've<01:56:20.560> got<01:56:20.719> no<01:56:20.960> problem<01:56:21.599> utilizing<01:56:22.239> the<01:56:22.400> tool 01:56:22.629 --> 01:56:22.639 align:start position:0% i've got no problem utilizing the tool 01:56:22.639 --> 01:56:25.430 align:start position:0% i've got no problem utilizing the tool that<01:56:22.800> we've<01:56:23.040> paid<01:56:23.280> for 01:56:25.430 --> 01:56:25.440 align:start position:0% that we've paid for 01:56:25.440 --> 01:56:27.830 align:start position:0% that we've paid for increase<01:56:26.080> if<01:56:26.480> that's<01:56:26.800> up<01:56:26.880> to<01:56:27.040> the<01:56:27.119> market<01:56:27.679> to 01:56:27.830 --> 01:56:27.840 align:start position:0% increase if that's up to the market to 01:56:27.840 --> 01:56:30.229 align:start position:0% increase if that's up to the market to decide<01:56:28.239> how<01:56:28.480> much<01:56:29.040> uh<01:56:29.520> participation 01:56:30.229 --> 01:56:30.239 align:start position:0% decide how much uh participation 01:56:30.239 --> 01:56:32.149 align:start position:0% decide how much uh participation additional<01:56:30.639> burden<01:56:31.040> that<01:56:31.280> is 01:56:32.149 --> 01:56:32.159 align:start position:0% additional burden that is 01:56:32.159 --> 01:56:34.790 align:start position:0% additional burden that is um<01:56:32.880> you<01:56:33.040> know<01:56:33.199> and<01:56:33.280> that'll<01:56:33.520> vary<01:56:33.760> by 01:56:34.790 --> 01:56:34.800 align:start position:0% um you know and that'll vary by 01:56:34.800 --> 01:56:36.550 align:start position:0% um you know and that'll vary by type<01:56:35.040> of<01:56:35.440> participating<01:56:35.920> in<01:56:36.000> any<01:56:36.239> there's<01:56:36.400> no 01:56:36.550 --> 01:56:36.560 align:start position:0% type of participating in any there's no 01:56:36.560 --> 01:56:39.350 align:start position:0% type of participating in any there's no way<01:56:37.119> and<01:56:37.520> cost<01:56:37.840> of<01:56:38.320> feedstock<01:56:38.880> you<01:56:38.960> know<01:56:39.199> six 01:56:39.350 --> 01:56:39.360 align:start position:0% way and cost of feedstock you know six 01:56:39.360 --> 01:56:41.270 align:start position:0% way and cost of feedstock you know six dollar<01:56:39.679> gas<01:56:40.080> turning<01:56:40.400> on<01:56:40.480> your<01:56:40.639> gas<01:56:40.880> generator 01:56:41.270 --> 01:56:41.280 align:start position:0% dollar gas turning on your gas generator 01:56:41.280 --> 01:56:43.830 align:start position:0% dollar gas turning on your gas generator behind<01:56:41.599> the<01:56:42.239> fence<01:56:42.639> walmart<01:56:43.119> is<01:56:43.360> is<01:56:43.599> very 01:56:43.830 --> 01:56:43.840 align:start position:0% behind the fence walmart is is very 01:56:43.840 --> 01:56:46.550 align:start position:0% behind the fence walmart is is very different<01:56:44.080> than<01:56:44.239> two<01:56:44.400> dollar<01:56:44.719> gas 01:56:46.550 --> 01:56:46.560 align:start position:0% different than two dollar gas 01:56:46.560 --> 01:56:48.629 align:start position:0% different than two dollar gas so<01:56:46.719> one<01:56:46.960> thing<01:56:47.119> i<01:56:47.199> want<01:56:47.280> to<01:56:47.440> add<01:56:47.840> um<01:56:48.239> i<01:56:48.480> think 01:56:48.629 --> 01:56:48.639 align:start position:0% so one thing i want to add um i think 01:56:48.639 --> 01:56:51.430 align:start position:0% so one thing i want to add um i think your<01:56:48.880> point<01:56:49.199> is<01:56:49.360> um<01:56:49.920> it's<01:56:50.080> valid<01:56:50.800> and<01:56:51.199> we 01:56:51.430 --> 01:56:51.440 align:start position:0% your point is um it's valid and we 01:56:51.440 --> 01:56:52.950 align:start position:0% your point is um it's valid and we already<01:56:51.679> talked<01:56:51.920> about<01:56:52.159> it<01:56:52.239> to<01:56:52.320> some<01:56:52.560> degree<01:56:52.880> i 01:56:52.950 --> 01:56:52.960 align:start position:0% already talked about it to some degree i 01:56:52.960 --> 01:56:54.470 align:start position:0% already talked about it to some degree i think<01:56:53.119> canaan<01:56:53.520> was<01:56:53.599> here<01:56:53.840> at<01:56:53.920> the<01:56:54.000> last<01:56:54.239> work 01:56:54.470 --> 01:56:54.480 align:start position:0% think canaan was here at the last work 01:56:54.480 --> 01:56:55.510 align:start position:0% think canaan was here at the last work session<01:56:54.800> and<01:56:54.880> said<01:56:55.040> well<01:56:55.199> if<01:56:55.280> you're<01:56:55.360> going<01:56:55.440> to 01:56:55.510 --> 01:56:55.520 align:start position:0% session and said well if you're going to 01:56:55.520 --> 01:56:58.070 align:start position:0% session and said well if you're going to deploy<01:56:56.000> ers<01:56:56.480> earlier<01:56:56.880> you're<01:56:57.119> going<01:56:57.199> to 01:56:58.070 --> 01:56:58.080 align:start position:0% deploy ers earlier you're going to 01:56:58.080 --> 01:56:59.669 align:start position:0% deploy ers earlier you're going to pay<01:56:58.320> more<01:56:58.800> yeah 01:56:59.669 --> 01:56:59.679 align:start position:0% pay more yeah 01:56:59.679 --> 01:57:01.750 align:start position:0% pay more yeah because<01:56:59.920> these<01:57:00.239> you<01:57:00.320> know<01:57:00.960> consumers<01:57:01.599> are 01:57:01.750 --> 01:57:01.760 align:start position:0% because these you know consumers are 01:57:01.760 --> 01:57:04.390 align:start position:0% because these you know consumers are going<01:57:01.920> to<01:57:02.000> come<01:57:02.239> off<01:57:02.560> and<01:57:02.800> and<01:57:03.440> it's<01:57:03.599> going<01:57:03.760> to 01:57:04.390 --> 01:57:04.400 align:start position:0% going to come off and and it's going to 01:57:04.400 --> 01:57:05.750 align:start position:0% going to come off and and it's going to be<01:57:04.560> a<01:57:04.639> little<01:57:04.800> bit<01:57:04.880> more<01:57:05.119> intrusive<01:57:05.520> in<01:57:05.599> their 01:57:05.750 --> 01:57:05.760 align:start position:0% be a little bit more intrusive in their 01:57:05.760 --> 01:57:07.830 align:start position:0% be a little bit more intrusive in their day-to-day<01:57:06.159> operations<01:57:06.719> right<01:57:06.960> so 01:57:07.830 --> 01:57:07.840 align:start position:0% day-to-day operations right so 01:57:07.840 --> 01:57:10.390 align:start position:0% day-to-day operations right so we<01:57:08.080> expect<01:57:08.400> to<01:57:08.560> pay<01:57:09.040> a<01:57:09.119> little<01:57:09.280> bit<01:57:09.440> more<01:57:10.159> for 01:57:10.390 --> 01:57:10.400 align:start position:0% we expect to pay a little bit more for 01:57:10.400 --> 01:57:11.109 align:start position:0% we expect to pay a little bit more for it 01:57:11.109 --> 01:57:11.119 align:start position:0% it 01:57:11.119 --> 01:57:12.149 align:start position:0% it the<01:57:11.199> other<01:57:11.360> thing<01:57:11.520> we've<01:57:11.679> got<01:57:11.760> to<01:57:11.840> take<01:57:12.000> into 01:57:12.149 --> 01:57:12.159 align:start position:0% the other thing we've got to take into 01:57:12.159 --> 01:57:14.070 align:start position:0% the other thing we've got to take into consideration<01:57:13.040> is 01:57:14.070 --> 01:57:14.080 align:start position:0% consideration is 01:57:14.080 --> 01:57:16.950 align:start position:0% consideration is competing<01:57:14.560> tdu<01:57:15.040> load<01:57:15.280> management<01:57:15.679> programs 01:57:16.950 --> 01:57:16.960 align:start position:0% competing tdu load management programs 01:57:16.960 --> 01:57:19.750 align:start position:0% competing tdu load management programs and<01:57:17.199> so<01:57:17.760> often<01:57:18.080> if<01:57:18.239> you<01:57:18.400> participate<01:57:18.880> in<01:57:19.040> ers 01:57:19.750 --> 01:57:19.760 align:start position:0% and so often if you participate in ers 01:57:19.760 --> 01:57:21.430 align:start position:0% and so often if you participate in ers you<01:57:19.920> can't<01:57:20.159> participate<01:57:20.560> in<01:57:20.719> a<01:57:20.719> load<01:57:21.040> program 01:57:21.430 --> 01:57:21.440 align:start position:0% you can't participate in a load program 01:57:21.440 --> 01:57:24.149 align:start position:0% you can't participate in a load program with<01:57:21.599> the<01:57:21.679> tdu<01:57:22.480> and<01:57:22.960> um<01:57:23.280> oftentimes<01:57:23.840> they<01:57:24.000> do 01:57:24.149 --> 01:57:24.159 align:start position:0% with the tdu and um oftentimes they do 01:57:24.159 --> 01:57:25.910 align:start position:0% with the tdu and um oftentimes they do offer<01:57:24.400> competitive<01:57:24.960> rates<01:57:25.360> and<01:57:25.599> in<01:57:25.679> my 01:57:25.910 --> 01:57:25.920 align:start position:0% offer competitive rates and in my 01:57:25.920 --> 01:57:27.589 align:start position:0% offer competitive rates and in my understanding<01:57:26.480> at<01:57:26.560> least<01:57:27.199> from<01:57:27.360> what<01:57:27.440> i 01:57:27.589 --> 01:57:27.599 align:start position:0% understanding at least from what i 01:57:27.599 --> 01:57:28.950 align:start position:0% understanding at least from what i understand<01:57:27.840> for<01:57:28.000> mercot 01:57:28.950 --> 01:57:28.960 align:start position:0% understand for mercot 01:57:28.960 --> 01:57:31.270 align:start position:0% understand for mercot is<01:57:29.119> that<01:57:29.520> encore<01:57:30.000> increased 01:57:31.270 --> 01:57:31.280 align:start position:0% is that encore increased 01:57:31.280 --> 01:57:33.430 align:start position:0% is that encore increased recently<01:57:32.080> um<01:57:32.639> what<01:57:32.800> they're<01:57:32.960> paying<01:57:33.280> for 01:57:33.430 --> 01:57:33.440 align:start position:0% recently um what they're paying for 01:57:33.440 --> 01:57:35.350 align:start position:0% recently um what they're paying for their<01:57:33.599> demand<01:57:33.920> response<01:57:34.400> under<01:57:34.639> their 01:57:35.350 --> 01:57:35.360 align:start position:0% their demand response under their 01:57:35.360 --> 01:57:37.189 align:start position:0% their demand response under their program<01:57:36.320> so<01:57:36.480> we<01:57:36.639> got<01:57:36.800> at<01:57:36.880> least<01:57:37.040> stay 01:57:37.189 --> 01:57:37.199 align:start position:0% program so we got at least stay 01:57:37.199 --> 01:57:39.910 align:start position:0% program so we got at least stay competitive<01:57:38.000> um<01:57:38.239> with<01:57:38.400> that<01:57:38.800> um<01:57:39.199> to<01:57:39.760> because 01:57:39.910 --> 01:57:39.920 align:start position:0% competitive um with that um to because 01:57:39.920 --> 01:57:44.070 align:start position:0% competitive um with that um to because we<01:57:40.080> could<01:57:40.239> lose<01:57:40.480> resources<01:57:40.960> in<01:57:41.040> ers<01:57:42.000> and<01:57:42.239> so<01:57:42.800> um 01:57:44.070 --> 01:57:44.080 align:start position:0% we could lose resources in ers and so um 01:57:44.080 --> 01:57:45.910 align:start position:0% we could lose resources in ers and so um looking<01:57:44.400> at<01:57:44.480> that<01:57:44.639> holistically 01:57:45.910 --> 01:57:45.920 align:start position:0% looking at that holistically 01:57:45.920 --> 01:57:47.669 align:start position:0% looking at that holistically uh<01:57:46.320> paying<01:57:46.639> more<01:57:47.199> because<01:57:47.440> we're<01:57:47.599> gonna 01:57:47.669 --> 01:57:47.679 align:start position:0% uh paying more because we're gonna 01:57:47.679 --> 01:57:49.830 align:start position:0% uh paying more because we're gonna deploy<01:57:48.000> it<01:57:48.080> earlier<01:57:48.719> and 01:57:49.830 --> 01:57:49.840 align:start position:0% deploy it earlier and 01:57:49.840 --> 01:57:51.750 align:start position:0% deploy it earlier and also<01:57:50.159> because<01:57:50.800> we<01:57:50.960> have<01:57:51.280> a<01:57:51.360> little<01:57:51.520> bit<01:57:51.599> of 01:57:51.750 --> 01:57:51.760 align:start position:0% also because we have a little bit of 01:57:51.760 --> 01:57:53.270 align:start position:0% also because we have a little bit of competition<01:57:52.239> out<01:57:52.400> there 01:57:53.270 --> 01:57:53.280 align:start position:0% competition out there 01:57:53.280 --> 01:57:54.550 align:start position:0% competition out there um 01:57:54.550 --> 01:57:54.560 align:start position:0% um 01:57:54.560 --> 01:57:55.589 align:start position:0% um you<01:57:54.719> know<01:57:54.800> we<01:57:54.960> got<01:57:55.040> to<01:57:55.119> take<01:57:55.280> that<01:57:55.440> into 01:57:55.589 --> 01:57:55.599 align:start position:0% you know we got to take that into 01:57:55.599 --> 01:57:57.910 align:start position:0% you know we got to take that into consideration<01:57:56.480> and<01:57:56.719> from<01:57:56.880> my<01:57:57.040> perspective 01:57:57.910 --> 01:57:57.920 align:start position:0% consideration and from my perspective 01:57:57.920 --> 01:57:59.430 align:start position:0% consideration and from my perspective and<01:57:58.000> i<01:57:58.159> appreciate<01:57:58.560> the<01:57:58.800> information<01:57:59.280> you 01:57:59.430 --> 01:57:59.440 align:start position:0% and i appreciate the information you 01:57:59.440 --> 01:58:00.709 align:start position:0% and i appreciate the information you provided 01:58:00.709 --> 01:58:00.719 align:start position:0% provided 01:58:00.719 --> 01:58:01.990 align:start position:0% provided um 01:58:01.990 --> 01:58:02.000 align:start position:0% um 01:58:02.000 --> 01:58:03.270 align:start position:0% um you<01:58:02.080> know<01:58:02.239> we<01:58:02.400> certainly<01:58:02.639> don't<01:58:02.800> want<01:58:02.960> to<01:58:03.040> set 01:58:03.270 --> 01:58:03.280 align:start position:0% you know we certainly don't want to set 01:58:03.280 --> 01:58:04.950 align:start position:0% you know we certainly don't want to set ourselves<01:58:03.599> short<01:58:04.000> for<01:58:04.159> the<01:58:04.320> summer<01:58:04.719> and<01:58:04.880> we 01:58:04.950 --> 01:58:04.960 align:start position:0% ourselves short for the summer and we 01:58:04.960 --> 01:58:06.390 align:start position:0% ourselves short for the summer and we got<01:58:05.119> to<01:58:05.199> be<01:58:05.360> mindful<01:58:05.679> of<01:58:05.760> the<01:58:05.840> shoulder<01:58:06.159> months 01:58:06.390 --> 01:58:06.400 align:start position:0% got to be mindful of the shoulder months 01:58:06.400 --> 01:58:07.589 align:start position:0% got to be mindful of the shoulder months too 01:58:07.589 --> 01:58:07.599 align:start position:0% too 01:58:07.599 --> 01:58:10.470 align:start position:0% too um<01:58:07.920> i<01:58:08.000> think<01:58:08.159> your<01:58:08.480> your<01:58:08.880> your<01:58:09.360> uh<01:58:09.920> points<01:58:10.239> are 01:58:10.470 --> 01:58:10.480 align:start position:0% um i think your your your uh points are 01:58:10.480 --> 01:58:12.070 align:start position:0% um i think your your your uh points are are<01:58:10.560> very<01:58:10.800> well<01:58:10.960> taken<01:58:11.360> i<01:58:11.440> think<01:58:11.599> those<01:58:11.840> are 01:58:12.070 --> 01:58:12.080 align:start position:0% are very well taken i think those are 01:58:12.080 --> 01:58:13.750 align:start position:0% are very well taken i think those are left<01:58:12.239> for<01:58:12.480> an<01:58:12.560> ers<01:58:12.960> rulemaking<01:58:13.440> that<01:58:13.520> i<01:58:13.599> think 01:58:13.750 --> 01:58:13.760 align:start position:0% left for an ers rulemaking that i think 01:58:13.760 --> 01:58:16.470 align:start position:0% left for an ers rulemaking that i think we<01:58:13.840> should<01:58:14.080> add<01:58:14.239> to<01:58:14.320> our<01:58:14.480> blueprint 01:58:16.470 --> 01:58:16.480 align:start position:0% we should add to our blueprint 01:58:16.480 --> 01:58:19.350 align:start position:0% we should add to our blueprint to<01:58:16.880> look<01:58:17.119> at<01:58:17.199> that<01:58:17.360> more<01:58:17.520> broadly<01:58:18.400> and<01:58:19.040> but<01:58:19.199> for 01:58:19.350 --> 01:58:19.360 align:start position:0% to look at that more broadly and but for 01:58:19.360 --> 01:58:21.589 align:start position:0% to look at that more broadly and but for purposes<01:58:19.840> of<01:58:20.000> today<01:58:20.480> i<01:58:20.639> i<01:58:21.119> i'm<01:58:21.280> kind<01:58:21.440> of 01:58:21.589 --> 01:58:21.599 align:start position:0% purposes of today i i i'm kind of 01:58:21.599 --> 01:58:24.470 align:start position:0% purposes of today i i i'm kind of coalescing<01:58:22.239> around<01:58:23.040> the<01:58:23.280> five 01:58:24.470 --> 01:58:24.480 align:start position:0% coalescing around the five 01:58:24.480 --> 01:58:26.390 align:start position:0% coalescing around the five so<01:58:24.719> maybe<01:58:24.960> 10<01:58:25.199> million 01:58:26.390 --> 01:58:26.400 align:start position:0% so maybe 10 million 01:58:26.400 --> 01:58:28.070 align:start position:0% so maybe 10 million i<01:58:26.639> i<01:58:26.800> like<01:58:26.960> the<01:58:27.119> five<01:58:27.360> because<01:58:27.679> it<01:58:27.840> definitely 01:58:28.070 --> 01:58:28.080 align:start position:0% i i like the five because it definitely 01:58:28.080 --> 01:58:29.750 align:start position:0% i i like the five because it definitely doesn't<01:58:28.239> cut<01:58:28.480> into<01:58:28.719> summer<01:58:29.199> and<01:58:29.360> it<01:58:29.440> gets<01:58:29.679> us 01:58:29.750 --> 01:58:29.760 align:start position:0% doesn't cut into summer and it gets us 01:58:29.760 --> 01:58:32.390 align:start position:0% doesn't cut into summer and it gets us to<01:58:29.920> the<01:58:30.000> halfway<01:58:30.400> mark<01:58:30.639> of<01:58:30.880> the<01:58:31.040> 50<01:58:31.360> million 01:58:32.390 --> 01:58:32.400 align:start position:0% to the halfway mark of the 50 million 01:58:32.400 --> 01:58:33.189 align:start position:0% to the halfway mark of the 50 million um 01:58:33.189 --> 01:58:33.199 align:start position:0% um 01:58:33.199 --> 01:58:37.109 align:start position:0% um not<01:58:33.360> that<01:58:33.520> that's<01:58:34.239> any<01:58:34.800> particular<01:58:35.360> magic 01:58:37.109 --> 01:58:37.119 align:start position:0% not that that's any particular magic 01:58:37.119 --> 01:58:38.470 align:start position:0% not that that's any particular magic magic<01:58:37.440> number<01:58:37.679> of<01:58:37.760> megawatts<01:58:38.239> we<01:58:38.320> don't<01:58:38.400> know 01:58:38.470 --> 01:58:38.480 align:start position:0% magic number of megawatts we don't know 01:58:38.480 --> 01:58:39.910 align:start position:0% magic number of megawatts we don't know how<01:58:38.639> many<01:58:38.719> megawatts<01:58:39.199> it'll<01:58:39.360> get<01:58:39.520> us<01:58:39.599> until<01:58:39.840> we 01:58:39.910 --> 01:58:39.920 align:start position:0% how many megawatts it'll get us until we 01:58:39.920 --> 01:58:41.189 align:start position:0% how many megawatts it'll get us until we see<01:58:40.159> the<01:58:40.239> price 01:58:41.189 --> 01:58:41.199 align:start position:0% see the price 01:58:41.199 --> 01:58:43.350 align:start position:0% see the price right<01:58:41.599> auctions<01:58:42.080> but<01:58:42.400> i'm 01:58:43.350 --> 01:58:43.360 align:start position:0% right auctions but i'm 01:58:43.360 --> 01:58:45.589 align:start position:0% right auctions but i'm i'm<01:58:43.520> much<01:58:43.760> more<01:58:44.000> comfortable<01:58:44.400> saying<01:58:44.639> that<01:58:45.360> we 01:58:45.589 --> 01:58:45.599 align:start position:0% i'm much more comfortable saying that we 01:58:45.599 --> 01:58:47.669 align:start position:0% i'm much more comfortable saying that we used<01:58:45.920> 50<01:58:46.480> of<01:58:46.639> all<01:58:46.719> available<01:58:47.119> funds<01:58:47.360> for<01:58:47.520> this 01:58:47.669 --> 01:58:47.679 align:start position:0% used 50 of all available funds for this 01:58:47.679 --> 01:58:48.870 align:start position:0% used 50 of all available funds for this winter 01:58:48.870 --> 01:58:48.880 align:start position:0% winter 01:58:48.880 --> 01:58:50.709 align:start position:0% winter and<01:58:49.119> didn't 01:58:50.709 --> 01:58:50.719 align:start position:0% and didn't 01:58:50.719 --> 01:58:52.310 align:start position:0% and didn't cut<01:58:50.960> too<01:58:51.119> deeply<01:58:51.520> into<01:58:51.679> the<01:58:51.840> other<01:58:52.080> in<01:58:52.239> the 01:58:52.310 --> 01:58:52.320 align:start position:0% cut too deeply into the other in the 01:58:52.320 --> 01:58:54.149 align:start position:0% cut too deeply into the other in the shoulder<01:58:52.639> months<01:58:52.880> of<01:58:52.960> the<01:58:53.040> summer 01:58:54.149 --> 01:58:54.159 align:start position:0% shoulder months of the summer 01:58:54.159 --> 01:58:56.310 align:start position:0% shoulder months of the summer but<01:58:54.400> that's 01:58:56.310 --> 01:58:56.320 align:start position:0% but that's 01:58:56.320 --> 01:58:57.750 align:start position:0% but that's i<01:58:56.400> think<01:58:56.560> that<01:58:56.639> makes<01:58:56.880> sense<01:58:57.119> i<01:58:57.199> mean<01:58:57.280> we<01:58:57.599> want 01:58:57.750 --> 01:58:57.760 align:start position:0% i think that makes sense i mean we want 01:58:57.760 --> 01:59:00.470 align:start position:0% i think that makes sense i mean we want to<01:58:57.920> do<01:58:58.080> a<01:58:58.159> test<01:58:58.480> run<01:58:58.880> right<01:58:59.199> and<01:58:59.520> the<01:58:59.599> 5<01:58:59.760> million 01:59:00.470 --> 01:59:00.480 align:start position:0% to do a test run right and the 5 million 01:59:00.480 --> 01:59:02.229 align:start position:0% to do a test run right and the 5 million hopefully<01:59:00.880> will<01:59:01.040> help<01:59:01.280> cover<01:59:01.679> the<01:59:01.840> earlier 01:59:02.229 --> 01:59:02.239 align:start position:0% hopefully will help cover the earlier 01:59:02.239 --> 01:59:04.149 align:start position:0% hopefully will help cover the earlier deployment<01:59:02.719> and<01:59:02.800> maybe<01:59:03.199> keep<01:59:03.440> us<01:59:03.520> competitive 01:59:04.149 --> 01:59:04.159 align:start position:0% deployment and maybe keep us competitive 01:59:04.159 --> 01:59:05.990 align:start position:0% deployment and maybe keep us competitive and<01:59:04.480> i<01:59:04.639> start<01:59:04.960> you<01:59:05.119> know<01:59:05.199> as<01:59:05.520> we<01:59:05.599> look<01:59:05.840> at 01:59:05.990 --> 01:59:06.000 align:start position:0% and i start you know as we look at 01:59:06.000 --> 01:59:08.310 align:start position:0% and i start you know as we look at option<01:59:06.320> one 01:59:08.310 --> 01:59:08.320 align:start position:0% option one 01:59:08.320 --> 01:59:10.709 align:start position:0% option one versus<01:59:08.719> option<01:59:09.119> two<01:59:09.520> you<01:59:09.920> do<01:59:10.159> cut<01:59:10.400> into<01:59:10.560> the 01:59:10.709 --> 01:59:10.719 align:start position:0% versus option two you do cut into the 01:59:10.719 --> 01:59:13.030 align:start position:0% versus option two you do cut into the summer<01:59:11.040> by<01:59:11.280> maybe<01:59:11.840> a<01:59:11.920> little<01:59:12.159> bit 01:59:13.030 --> 01:59:13.040 align:start position:0% summer by maybe a little bit 01:59:13.040 --> 01:59:14.629 align:start position:0% summer by maybe a little bit less<01:59:13.360> than 01:59:14.629 --> 01:59:14.639 align:start position:0% less than 01:59:14.639 --> 01:59:16.709 align:start position:0% less than a<01:59:14.719> million<01:59:15.280> i<01:59:15.360> believe 01:59:16.709 --> 01:59:16.719 align:start position:0% a million i believe 01:59:16.719 --> 01:59:18.229 align:start position:0% a million i believe but<01:59:17.119> we<01:59:17.280> certainly<01:59:17.679> don't<01:59:17.840> want<01:59:18.000> to<01:59:18.080> be 01:59:18.229 --> 01:59:18.239 align:start position:0% but we certainly don't want to be 01:59:18.239 --> 01:59:19.990 align:start position:0% but we certainly don't want to be chipping<01:59:18.560> at<01:59:18.639> the<01:59:18.800> summer<01:59:19.280> um<01:59:19.599> we<01:59:19.679> want<01:59:19.840> to<01:59:19.920> be 01:59:19.990 --> 01:59:20.000 align:start position:0% chipping at the summer um we want to be 01:59:20.000 --> 01:59:22.229 align:start position:0% chipping at the summer um we want to be prepared<01:59:20.400> for<01:59:20.480> the<01:59:20.560> winter<01:59:21.040> we<01:59:21.199> want<01:59:21.360> to 01:59:22.229 --> 01:59:22.239 align:start position:0% prepared for the winter we want to 01:59:22.239 --> 01:59:23.990 align:start position:0% prepared for the winter we want to certainly<01:59:22.560> be<01:59:22.719> competitive<01:59:23.199> for<01:59:23.360> the<01:59:23.440> winter 01:59:23.990 --> 01:59:24.000 align:start position:0% certainly be competitive for the winter 01:59:24.000 --> 01:59:26.709 align:start position:0% certainly be competitive for the winter to<01:59:24.159> attract<01:59:24.880> um<01:59:25.599> keep<01:59:25.920> our<01:59:26.000> load<01:59:26.239> resources 01:59:26.709 --> 01:59:26.719 align:start position:0% to attract um keep our load resources 01:59:26.719 --> 01:59:29.430 align:start position:0% to attract um keep our load resources and<01:59:26.880> attract<01:59:27.199> new<01:59:27.360> ones<01:59:27.520> if<01:59:27.679> we<01:59:27.760> can<01:59:28.480> so 01:59:29.430 --> 01:59:29.440 align:start position:0% and attract new ones if we can so 01:59:29.440 --> 01:59:30.709 align:start position:0% and attract new ones if we can so i<01:59:29.520> think 01:59:30.709 --> 01:59:30.719 align:start position:0% i think 01:59:30.719 --> 01:59:32.550 align:start position:0% i think 5<01:59:30.960> million<01:59:31.360> is<01:59:31.520> probably<01:59:31.840> the<01:59:32.000> 10<01:59:32.159> million<01:59:32.480> i 01:59:32.550 --> 01:59:32.560 align:start position:0% 5 million is probably the 10 million i 01:59:32.560 --> 01:59:34.149 align:start position:0% 5 million is probably the 10 million i was<01:59:32.639> a<01:59:32.719> little<01:59:33.040> uncomfortable<01:59:33.599> with<01:59:34.000> just 01:59:34.149 --> 01:59:34.159 align:start position:0% was a little uncomfortable with just 01:59:34.159 --> 01:59:36.310 align:start position:0% was a little uncomfortable with just because<01:59:34.400> it<01:59:34.560> is<01:59:34.639> a<01:59:34.719> sizable<01:59:35.119> amount<01:59:35.360> to<01:59:35.520> add 01:59:36.310 --> 01:59:36.320 align:start position:0% because it is a sizable amount to add 01:59:36.320 --> 01:59:38.310 align:start position:0% because it is a sizable amount to add but<01:59:36.480> i<01:59:36.560> think<01:59:37.040> from<01:59:37.199> a<01:59:37.280> cost 01:59:38.310 --> 01:59:38.320 align:start position:0% but i think from a cost 01:59:38.320 --> 01:59:40.229 align:start position:0% but i think from a cost cost<01:59:38.800> conservative<01:59:39.360> basis<01:59:39.760> i<01:59:39.840> think<01:59:40.000> 5 01:59:40.229 --> 01:59:40.239 align:start position:0% cost conservative basis i think 5 01:59:40.239 --> 01:59:41.189 align:start position:0% cost conservative basis i think 5 million 01:59:41.189 --> 01:59:41.199 align:start position:0% million 01:59:41.199 --> 01:59:42.830 align:start position:0% million makes<01:59:41.440> sense<01:59:41.679> to<01:59:41.760> me<01:59:42.000> are<01:59:42.080> you<01:59:42.159> all 01:59:42.830 --> 01:59:42.840 align:start position:0% makes sense to me are you all 01:59:42.840 --> 01:59:45.830 align:start position:0% makes sense to me are you all comfortable<01:59:44.000> i<01:59:44.080> don't<01:59:44.239> really<01:59:44.400> have<01:59:44.800> a<01:59:45.199> a<01:59:45.760> i 01:59:45.830 --> 01:59:45.840 align:start position:0% comfortable i don't really have a a i 01:59:45.840 --> 01:59:47.750 align:start position:0% comfortable i don't really have a a i haven't<01:59:46.080> come<01:59:46.239> to<01:59:46.400> an<01:59:46.639> answer<01:59:46.960> yet<01:59:47.199> in<01:59:47.280> my<01:59:47.440> mind 01:59:47.750 --> 01:59:47.760 align:start position:0% haven't come to an answer yet in my mind 01:59:47.760 --> 01:59:49.589 align:start position:0% haven't come to an answer yet in my mind so<01:59:48.159> okay<01:59:48.480> dave<01:59:48.719> when<01:59:48.800> do<01:59:48.880> you<01:59:48.960> need<01:59:49.119> an<01:59:49.280> answer 01:59:49.589 --> 01:59:49.599 align:start position:0% so okay dave when do you need an answer 01:59:49.599 --> 01:59:50.629 align:start position:0% so okay dave when do you need an answer for 01:59:50.629 --> 01:59:50.639 align:start position:0% for 01:59:50.639 --> 01:59:52.149 align:start position:0% for well<01:59:50.880> i<01:59:51.040> i<01:59:51.119> believe<01:59:51.360> the<01:59:51.520> plan<01:59:51.760> is<01:59:51.840> to<01:59:51.920> try<01:59:52.080> and 01:59:52.149 --> 01:59:52.159 align:start position:0% well i i believe the plan is to try and 01:59:52.159 --> 01:59:54.229 align:start position:0% well i i believe the plan is to try and get<01:59:52.320> the<01:59:52.480> rfes<01:59:52.960> out<01:59:53.199> pretty<01:59:53.440> shortly<01:59:53.840> here<01:59:54.080> so 01:59:54.229 --> 01:59:54.239 align:start position:0% get the rfes out pretty shortly here so 01:59:54.239 --> 01:59:55.589 align:start position:0% get the rfes out pretty shortly here so i<01:59:54.400> know<01:59:54.639> i<01:59:54.719> know<01:59:54.960> there<01:59:55.119> are<01:59:55.199> some<01:59:55.440> pretty 01:59:55.589 --> 01:59:55.599 align:start position:0% i know i know there are some pretty 01:59:55.599 --> 01:59:57.430 align:start position:0% i know i know there are some pretty close<01:59:55.840> deadlines<01:59:56.239> for<01:59:56.400> that<01:59:56.719> november<01:59:57.280> think 01:59:57.430 --> 01:59:57.440 align:start position:0% close deadlines for that november think 01:59:57.440 --> 01:59:58.870 align:start position:0% close deadlines for that november think about<01:59:57.599> it<01:59:57.679> over<01:59:57.920> lunch<01:59:58.159> yeah<01:59:58.400> i'll<01:59:58.560> come<01:59:58.639> back 01:59:58.870 --> 01:59:58.880 align:start position:0% about it over lunch yeah i'll come back 01:59:58.880 --> 02:00:00.310 align:start position:0% about it over lunch yeah i'll come back after<01:59:59.040> that<01:59:59.520> yeah<01:59:59.679> their<01:59:59.840> deadline<02:00:00.159> is 02:00:00.310 --> 02:00:00.320 align:start position:0% after that yeah their deadline is 02:00:00.320 --> 02:00:02.629 align:start position:0% after that yeah their deadline is november<02:00:00.719> 8th<02:00:01.040> yeah<02:00:01.440> so<02:00:02.000> i'm<02:00:02.159> okay<02:00:02.400> with<02:00:02.560> your 02:00:02.629 --> 02:00:02.639 align:start position:0% november 8th yeah so i'm okay with your 02:00:02.639 --> 02:00:04.470 align:start position:0% november 8th yeah so i'm okay with your five<02:00:03.040> yeah<02:00:03.199> so 02:00:04.470 --> 02:00:04.480 align:start position:0% five yeah so 02:00:04.480 --> 02:00:05.990 align:start position:0% five yeah so i<02:00:04.560> mean<02:00:04.719> listen<02:00:05.280> if<02:00:05.360> y'all<02:00:05.599> are<02:00:05.679> okay<02:00:05.920> with 02:00:05.990 --> 02:00:06.000 align:start position:0% i mean listen if y'all are okay with 02:00:06.000 --> 02:00:08.229 align:start position:0% i mean listen if y'all are okay with five<02:00:06.159> i'm<02:00:06.320> okay<02:00:06.560> with<02:00:06.719> five<02:00:07.040> i'm<02:00:07.280> i'm 02:00:08.229 --> 02:00:08.239 align:start position:0% five i'm okay with five i'm i'm 02:00:08.239 --> 02:00:10.709 align:start position:0% five i'm okay with five i'm i'm uh<02:00:08.639> decimal<02:00:09.040> dust<02:00:09.280> at<02:00:09.360> some<02:00:09.520> point 02:00:10.709 --> 02:00:10.719 align:start position:0% uh decimal dust at some point 02:00:10.719 --> 02:00:12.629 align:start position:0% uh decimal dust at some point right<02:00:11.280> that's<02:00:11.440> right<02:00:11.679> i'm<02:00:12.000> trying<02:00:12.159> to<02:00:12.239> get<02:00:12.400> the 02:00:12.629 --> 02:00:12.639 align:start position:0% right that's right i'm trying to get the 02:00:12.639 --> 02:00:14.229 align:start position:0% right that's right i'm trying to get the the<02:00:12.800> big<02:00:13.040> basket<02:00:13.440> of<02:00:13.520> fruit<02:00:13.920> you<02:00:14.000> know 02:00:14.229 --> 02:00:14.239 align:start position:0% the big basket of fruit you know 02:00:14.239 --> 02:00:15.510 align:start position:0% the big basket of fruit you know together<02:00:14.560> here<02:00:14.719> what<02:00:14.880> we're<02:00:15.040> talking<02:00:15.360> about 02:00:15.510 --> 02:00:15.520 align:start position:0% together here what we're talking about 02:00:15.520 --> 02:00:17.030 align:start position:0% together here what we're talking about in<02:00:15.679> the<02:00:15.760> future 02:00:17.030 --> 02:00:17.040 align:start position:0% in the future 02:00:17.040 --> 02:00:19.030 align:start position:0% in the future no<02:00:17.440> hanging<02:00:17.760> fruit 02:00:19.030 --> 02:00:19.040 align:start position:0% no hanging fruit 02:00:19.040 --> 02:00:22.790 align:start position:0% no hanging fruit correct 02:00:22.790 --> 02:00:22.800 align:start position:0% 02:00:22.800 --> 02:00:24.470 align:start position:0% yeah 02:00:24.470 --> 02:00:24.480 align:start position:0% yeah 02:00:24.480 --> 02:00:25.589 align:start position:0% yeah all<02:00:24.560> right<02:00:24.719> if<02:00:24.800> you're<02:00:25.040> comfortable<02:00:25.360> 5 02:00:25.589 --> 02:00:25.599 align:start position:0% all right if you're comfortable 5 02:00:25.599 --> 02:00:27.910 align:start position:0% all right if you're comfortable 5 million<02:00:26.239> we'll<02:00:26.639> uh<02:00:27.119> direct<02:00:27.360> aircod<02:00:27.760> to 02:00:27.910 --> 02:00:27.920 align:start position:0% million we'll uh direct aircod to 02:00:27.920 --> 02:00:29.189 align:start position:0% million we'll uh direct aircod to proceed<02:00:28.400> with 02:00:29.189 --> 02:00:29.199 align:start position:0% proceed with 02:00:29.199 --> 02:00:30.629 align:start position:0% proceed with the<02:00:29.440> rfp 02:00:30.629 --> 02:00:30.639 align:start position:0% the rfp 02:00:30.639 --> 02:00:32.550 align:start position:0% the rfp adding<02:00:31.040> 5<02:00:31.199> million<02:00:31.440> to<02:00:31.599> the<02:00:31.679> existing<02:00:32.239> planned 02:00:32.550 --> 02:00:32.560 align:start position:0% adding 5 million to the existing planned 02:00:32.560 --> 02:00:34.390 align:start position:0% adding 5 million to the existing planned 21<02:00:33.040> million<02:00:33.360> euros<02:00:33.760> procurement<02:00:34.239> for<02:00:34.320> the 02:00:34.390 --> 02:00:34.400 align:start position:0% 21 million euros procurement for the 02:00:34.400 --> 02:00:35.750 align:start position:0% 21 million euros procurement for the winter<02:00:34.719> season 02:00:35.750 --> 02:00:35.760 align:start position:0% winter season 02:00:35.760 --> 02:00:38.550 align:start position:0% winter season uh<02:00:36.239> inc<02:00:36.639> and<02:00:37.280> adjusting<02:00:37.760> the 02:00:38.550 --> 02:00:38.560 align:start position:0% uh inc and adjusting the 02:00:38.560 --> 02:00:40.870 align:start position:0% uh inc and adjusting the proposed<02:00:39.040> contracts<02:00:39.760> to<02:00:40.159> account<02:00:40.560> for<02:00:40.800> the 02:00:40.870 --> 02:00:40.880 align:start position:0% proposed contracts to account for the 02:00:40.880 --> 02:00:43.109 align:start position:0% proposed contracts to account for the deployment<02:00:41.360> of<02:00:41.520> ers 02:00:43.109 --> 02:00:43.119 align:start position:0% deployment of ers 02:00:43.119 --> 02:00:45.830 align:start position:0% deployment of ers outside<02:00:43.520> of<02:00:43.599> ea 02:00:45.830 --> 02:00:45.840 align:start position:0% outside of ea 02:00:45.840 --> 02:00:48.470 align:start position:0% outside of ea either<02:00:46.320> in<02:00:46.639> in<02:00:46.800> conjunction<02:00:47.360> or<02:00:47.520> ahead<02:00:47.840> of 02:00:48.470 --> 02:00:48.480 align:start position:0% either in in conjunction or ahead of 02:00:48.480 --> 02:00:50.070 align:start position:0% either in in conjunction or ahead of there's<02:00:48.719> some<02:00:48.880> operational<02:00:49.360> details<02:00:49.840> there 02:00:50.070 --> 02:00:50.080 align:start position:0% there's some operational details there 02:00:50.080 --> 02:00:51.189 align:start position:0% there's some operational details there that<02:00:50.320> i<02:00:50.480> know 02:00:51.189 --> 02:00:51.199 align:start position:0% that i know 02:00:51.199 --> 02:00:52.629 align:start position:0% that i know you<02:00:51.280> all<02:00:51.360> have<02:00:51.520> already<02:00:51.760> sorted<02:00:52.159> out<02:00:52.400> but 02:00:52.629 --> 02:00:52.639 align:start position:0% you all have already sorted out but 02:00:52.639 --> 02:00:55.189 align:start position:0% you all have already sorted out but essentially<02:00:53.599> deploying<02:00:54.159> that<02:00:54.560> or<02:00:54.800> accounting 02:00:55.189 --> 02:00:55.199 align:start position:0% essentially deploying that or accounting 02:00:55.199 --> 02:00:56.709 align:start position:0% essentially deploying that or accounting for<02:00:55.360> that<02:00:55.520> deployment 02:00:56.709 --> 02:00:56.719 align:start position:0% for that deployment 02:00:56.719 --> 02:00:58.470 align:start position:0% for that deployment uh<02:00:57.040> before 02:00:58.470 --> 02:00:58.480 align:start position:0% uh before 02:00:58.480 --> 02:01:00.310 align:start position:0% uh before ercod<02:00:58.960> asked<02:00:59.119> texans<02:00:59.599> to 02:01:00.310 --> 02:01:00.320 align:start position:0% ercod asked texans to 02:01:00.320 --> 02:01:04.470 align:start position:0% ercod asked texans to power<02:01:00.639> down<02:01:00.800> their<02:01:01.280> homes<02:01:01.599> and<02:01:01.679> businesses 02:01:04.470 --> 02:01:04.480 align:start position:0% 02:01:04.480 --> 02:01:06.550 align:start position:0% thank<02:01:04.639> you<02:01:04.719> sir<02:01:04.960> anything<02:01:05.199> else<02:01:05.360> for<02:01:05.520> dave 02:01:06.550 --> 02:01:06.560 align:start position:0% thank you sir anything else for dave 02:01:06.560 --> 02:01:08.709 align:start position:0% thank you sir anything else for dave all<02:01:06.719> right<02:01:06.800> we're<02:01:07.520> a<02:01:07.599> little<02:01:07.840> past<02:01:08.080> that<02:01:08.239> 11<02:01:08.480> 30 02:01:08.709 --> 02:01:08.719 align:start position:0% all right we're a little past that 11 30 02:01:08.719 --> 02:01:12.390 align:start position:0% all right we're a little past that 11 30 mark<02:01:09.440> so<02:01:09.679> we<02:01:09.840> will<02:01:10.000> recess<02:01:10.639> until<02:01:11.119> 12 02:01:12.390 --> 02:01:12.400 align:start position:0% mark so we will recess until 12 02:01:12.400 --> 02:01:14.790 align:start position:0% mark so we will recess until 12 20. 02:01:14.790 --> 02:01:14.800 align:start position:0% 20. 02:01:14.800 --> 02:01:24.870 align:start position:0% 20. thank<02:01:14.960> you<02:01:15.119> much 02:01:24.870 --> 02:01:24.880 align:start position:0% 02:01:24.880 --> 02:01:26.960 align:start position:0% you