Download Power Flow By Monique
Lee Stlaurent
See also Joint Appendix (JA) 180 (testimony of FERC staff member) ("Producing or absorbing reactive power at a generator results in real power heating losses in the generator and [this] heating loss requires that fuel be burned [and] causes a portion of the real capacity of [sic] generator to be consumed producing the heating loss.").
Turbines are mechanical devices with fan-like blades that rotate when steam, for example, is forced though them. The resulting mechanical energy powers a connected instrument like a generator (or, more specifically, a generator's exciter): "The turbine produces the mechanical [or real] power to turn the generator, which, in turn, produces both real and reactive power." 80 FERC at 62,090 n.65;see 82 FERC at 61,611. A turbine is essential to the production of reactive power. See JA 212-13 (testimony of petitioners' witness) ("Without the turbine, there would be no production of real or reactive power [;] the exciter is driven by the rotor and turbine assembly, and thus that equipment is directly involved in the production of reactive power.").
In brief FERC disputes that it allowed recovery of turbine costs in AEP. See Brief of Commission at 34-35. In AEP, however, FERC allowed recovery of "the remaining total production investment required to provide real power to operate the exciter." 80 FERC at 65,074. AEPSC incurred costs for investment in turbines, see id. at 65,077, and the turbines provide real power to operate the exciter. See supra notes 4 and 5. The investment in turbines was not included in the first two categories, see 80 FERC at 65,076-78, but was instead part of AEPSC's third category of recoverable costs. See id. at 65,079-80.
The internet began as a borderless, global interconnected network of networks, but it has increasingly become divided along national boundaries as the internet is wielded as an instrument of power and control by governments, and as a vector of attack on our increasingly connected world of the internet of things and autonomous applications.
The Clean Power Plan was meant to be the first step along a path that would lead to substantial carbon emission reductions. The Plan would have been the first ever federal rule to reduce pollution from power plants, the second largest source of greenhouse gas emissions in the United States. These emissions have already led to grave environmental impacts by fueling climate change. If implemented, the Clean Power Plan would cut that pollution by 32 percent below 2005 levels by 2030, helping lessen climate risks for people and wildlife alike. But, did you know that the Clean Power Plan would help protect public lands as well?
Lower snowpack (layers of high-altitude, compressed snow that melt slowly) is also a threat to wildlife and public lands. Snowmelt supplies about 60 to 80 percent of the water in major western river basins, including the Columbia, Missouri, and Colorado Rivers. This snowmelt is also the primary water supply for about 70 million people. Lower winter snowpack will lead to reduced stream flow during the summer months, which will impact temperature sensitive aquatic species like trout, and amphibians like frogs and newts. Scientists estimate that one-third of the current cold water fish habitat in the Pacific Northwest will be unsuitable by the end of the century. Fishing on public lands is a favorite American pastime, but fishing may be increasingly restricted as a result of low stream flows, hotter water, and reduced fish populations.
As the first ever regulations on carbon emissions from the power sector, the Clean Power Plan is a critical step in the path towards a stable climate. Power sector emissions account for nearly one third of U.S. carbon emissions, and are therefore one of the leading causes of the wildlife crisis on public lands.
A container class (like Scope) that supports initializing variables, so I can collapse all my declarations at the beginning of my flow to "move them out of the way" so we can see the useful actions at a glance. Maybe this could even be accomplished by an "Initialize VariableS" action where we can stack them in a collapsed UI similar to conditions on a Condition control. Maybe even grouping by type in the same way that conditions can be grouped/nested inside of AND/OR branches.
A better way/more native way to call PowerShell than setting up runbooks as the increased permissions required to enable and configure them in Azure leaves it as an inaccessible method to citizen developers. If the user has permission to run the script, but no access to Azure then they can't make a flow to call that script programmatically.
I noticed when you copy/paste actions, that a GUID is stored in the clipboard. The ability to share Steps/Actions would be huge. I think about using OneDrive and sharing a file vs a folder when I think about sharing a step vs a whole flow. It'd be hugely collaborative to share a link to a single action with a peer, whether for collaboration or just to share as a template. I recognize this is a huge ask as the current permissions aren't structured this way.
The ability to still save a flow even if it's in an error state. I can't tell you how many times I've had to stay at my desk for an extra hour or two trying to get it to a working state so I can leave it and come back without worrying my progress will be wiped out by my browser timing out.
Warn me, wave a flag to suggest I don't do the dumb, leave a banner on screen to remind me I really shouldn't have, automatically disable my flow and harass me with email reminders to fix it, but straight up blocking me from saving my progress while troubleshooting is a major inconvenience.
Or at least be able to save it in draft mode, so if you are making edits to a workflow that is being used, the current published workflow continues to work until you publish the one in draft. Nintex has this feature for their workflow designer, so I don't see why Microsoft cannot do this with Power Automate.
If they're aware of this action's power, I'd call on my fellow Flow Ninjas, @Pstork1, @Expiscornovus, @tom_riha, @ScottShearer, @annajhaveri, @takolota, @ekarim2020, @Paulie78, @MarconettiMarco, @fchopo to join me in protesting the removal of such a tool.
Hi, @AnnaChu, something that I noticed the other day is that the forum has removed the "I've found a bug" section, plus there's nowhere to adequately ask for help with/for/about the forum itself. These feel like more things (in addition to the Graph API action) being taken away that reduce our ability to easily design flows, because they affect the very ability to report problems with that, and/or the only real interaction the community has on building flows.
Often I find myself half building flows just so that I can get data from the first part (HTTP requests being top of my list) just to re-edit the 2nd part of the flow (Parse JSON). It would be really useful to be able to make steps inactive or greyed out so that the flow could be build/saved without the required information being added.
It would also help when encountering issues with a flow when attempting "something different" that doesn't quite work as well as the initial design. This means that you have to delete and re-build when you could just make steps active and inactive accordingly.
Did you know that it was this hard to work with OneNote Notebooks in Flow (especially Shared Notebooks in Teams) - Power Automate solution: OneNote action errors involving invalid or inaccessible Notebook Keys and s... I would never have gotten my flow to work without this resource, and even then, I still cannot set or update the page title.
I had to create a delay, such as discussed here (Solved: Re: Get updated OneNote title and link - Power Platform Community (microsoft.com)) because the flow was sending instantaneously after a page was created without capturing the page title.
A new month means it's time to celebrate and welcome the new user groups that have joined our community. We are excited to announce that we have more than 8 New Groups, which is no surprise after the amazing Microsoft Power Platform Conference. This month, we are breaking them out by the different community categories. If your group is listed here, give this post a kudo so we can celebrate with you!Don't forget to take a look at the many events happening near you or virtually! It's a great time of year to connect and engage with User Groups both locally and online. Please Welcome Our NEW User Groups Power Platform:PowerIT User Group: NottinghamPower Platform User Group: BergenPower Platform User Group: DanmarkNashville Power Platform User GroupMicrosoft Ambassador Program y Mujer Latina Technolochicas NCWIT CommunityCopilot Studio: Copilot User Group ItaliaDynamics365:Dynamics User Group AdriaticDynamic 365 Azerbaijan December User Group Events 01 Dec 2023Aprendiendo Desarrollo web, creando mi primer power app y power page.01 Dec 2023 Q4 Hybrid Philadelphia Dynamics 365 & Power Platform User Group Meeting05 Dec 2023APAC Dynamics 365 FastTrack Bootcamp - BI and Analytics07 Dec 2023Bay Area Power Platform Meetup: Learn, Share, and Connect07 Dec 2023Indiana D365/AX December User Group Meeting07 Dec 2023Dynamics User Group Meeting: Houston09 Dec 2023December '23 - NEW Power Apps User Group Meeting - Online12 Dec 2023December Cleveland Power Platform User Group Meeting12 Dec 2023RW2 Data Stewardship Open Forum Discussion13 Dec 2023 Black Country Power Platform User Group - December 2023 - West Midlands
35fe9a5643