FERC’s Generation Control Audit: Do Separate Companies Diversify Operations?

From company counts to the reach of a common command

In a nonbinding staff report released on October 13, 2026, the Federal Energy Regulatory Commission (FERC) described parent-company or common-contractor control across generation operators: individually identified low-impact systems collectively met medium-impact criteria.^[1]

The question for companies and markets is whether the unit that saves operating costs matches the unit exposed to an effect. Separate businesses can own their assets and pay separate service bills while still sharing a control capability. Adding up their contracts does not describe that dependency. Assessing an investment in generation therefore calls for a second view alongside the ownership list: which assets could be affected by the same action?

Consider a choice between staffing each facility and using a common operating centre. Pooling may improve access to specialists and reduce routine work. Set that benefit beside the replacements needed if a fault in a shared component affects several facilities. A saving in normal operation cannot simply be converted into an equal saving in replacement capability available under every condition. That comparison is the focus of the purchasing decision.

Overlay the ownership map with a command map

A corporate chart helps trace capital relationships. Operational dependencies require a different set of lines, running from control capabilities to equipment. Lines reaching separate companies may originate in the same function. Conversely, assets within one company may have independent local control. Treating the number of legal entities as the number of independent operating units misses both possibilities.

The two maps answer different questions. Ownership connects to funding, distributions and corporate decisions. A command map describes how far an action can reach. Adding contracting parties need not separate those lines; a contract with one provider could also limit the reach of each control capability. Identifying what has been separated reveals service differences that a count of supplier names cannot capture.

The Eramet analysis of ownership and voting rights explores economic participation and authority from another angle. Generation operations add a question about the functions that can physically affect equipment. After a change of asset ownership, reading the ownership transfer separately from any change in command paths makes the diversification effect easier to assess.

Observing equipment is different from changing its operation

A shared display of information does not by itself define the supply that could be lost together. Reading a status and changing a setting or operating state have different effects. A monitoring service that contacts a local operator, who then decides what to do, differs from a common capability that can deliver changes directly. The phrase central management can obscure that distinction.

The ability to make a change also differs from evidence that the ability was exercised. Its reach informs contingency planning; an operating history helps establish what happened. Inferring a loss volume directly from capability overstates the evidence. Ignoring capability because a history shows no anomaly can miss the conditions under which protection matters. A useful service comparison accommodates both questions.

When one supplier performs several tasks, distinguish observation, advice, approval and execution, and establish which functions are shared. A single contract need not confer uniform capabilities. Define what the fee purchases before comparing prices. This can help avoid both the expense of unnecessary separation and an arrangement that leaves a common dependency despite appearing to separate it.

Annual totals do not reveal overlapping interruptions

Imagine several facilities stopping briefly in succession, and then imagine them stopping together. Even with the same total energy lost, the replacement required at one moment differs. Spare capability that can be reused across sequential events may be insufficient when all facilities need it at once. Annual averages and totals conceal this overlap.

Whether individual interruptions can be treated as unrelated is therefore central to the comparison. A common factor able to affect every facility prevents simply using individual interruption rates to calculate a joint event. Equally, a shared service name does not establish that every outcome will be identical. The relevant dependency depends on what acts in common and what can be stopped or limited separately.

The guide to holding counts, overlap and correlation offers a related financial distinction. Historical asset-price correlations cannot, however, be transferred into generation outage probabilities. Prices moving together and commands reaching several facilities have different causes. The analogy helps frame a question about dependencies; it does not supply an engineering probability.

Contingency costs need not rise in proportion to lost output

Suppose existing spare capability can cover a shortfall up to a point, beyond which another source or demand adjustment is needed. The cost of widening the jointly affected range cannot then be represented by applying one price to every unit of generation. Crossing the boundary changes the available replacement. An additional facility has different economic implications depending on whether it fits within the existing contingency.

Where spare capability is ample, or at a time when it is readily available, pooling control may add little burden. Assuming a fixed proportion of damage from nameplate capacity is too crude. Compare the output exposed, the speed of response required and the replacement supply available then. Different conditions can produce different joint burdens even with the same operating arrangement.

The explanation of electricity demand, pricing and capacity factors provides background. A change visible to one company as an outsourcing saving may alter how the wider supply system prepares for a contingency. Comparing a low operating fee with the total cost of sustaining supply requires consistent locations, times and functions.

An individual buyer may not see other customers’ assets

A company outsourcing operations can examine its own fee, availability and requested service standard. Its contract may not reveal how much other equipment the supplier can affect. If the provider adds another customer without changing the existing customer’s price, the purchasing team may have no immediate reason to review its arrangement. Joint exposure can expand on a timetable different from individual contract renewals.

The unit purchasing a benefit from pooling differs from the unit assessing the resulting exposure. More customers may spread the cost of common staff and equipment, creating room for lower individual fees. If the set of assets reachable through a shared function grows at the same time, savings and dependency expand together. A lower price alone cannot value that exchange.

The analysis of shared property and operating agencies examines the allocation of benefits and work. The additional issue here is that separate buyers can enter a common sphere of operational influence without consciously forming a joint purchasing group. Looking for dependencies only where a formal joint venture exists can miss concentration arising from ordinary separate contracts.

A provider’s growth can change existing customers’ conditions

Investors in an operating service may welcome additional customers and a broader base over which to recover fixed costs. Yet the way new customers share functions with existing ones also changes the business. Selling more contracts differs from expanding the generation range reachable through one action. The contingency cost accompanying additional revenue need not be the same.

Compare expanding an existing common capability with creating a separate operating range after a certain point. The first can preserve pooling benefits; the second may require additional people and equipment. Neither cost must rise in direct proportion to customer counts. Understanding the margin on a new contract requires connecting the revenue unit to the unit at which operating capability has to be added.

Growth is not unambiguously reassuring or troubling for an existing customer. A larger provider may develop deeper expertise, and it may limit common reach while sharing that expertise. Evidence supporting growth therefore concerns more than scale: it includes how the functions of additional customers fit into the operating arrangement.

Revenue concentration and operational concentration differ

Customer revenue shares describe the concentration of income. They do not show which customers’ assets can be affected by the same capability. Revenue may be spread across many customers whose operations depend on one function. Conversely, one dominant customer may own equipment divided into separate control ranges.

Assessing operational concentration starts by defining what can be changed together, then examining the output or function associated with that range. Nameplate capacity differs from electricity actually supplied at every moment. Assuming all assets operate at maximum output serves a different purpose from studying a particular operating condition. The former makes a stress assumption explicit; the latter examines an outcome under specified conditions.

Combining revenue shares, customer counts, equipment counts and controllable output into a single concentration score risks false precision. Income stability, common operational reach and replacement supply require different denominators. Selecting a unit suited to the question explains business differences more clearly than imposing one ranking.

Value the benefits of keeping operations together

Common operations can bring information from several facilities into one decision. Separating every decision can delay recognition of changes elsewhere or encourage actions that do not fit together. A shared function can both transmit a problem and gather information that helps contain it. Leaving out the second role overstates the benefit of separation.

Staffing presents the same trade-off. If each location can sustain adequate expertise, separation may preserve service quality. Otherwise, spreading scarce specialists thinly may weaken decisions. Losing access to expertise gained through pooling cannot be priced solely as the purchase of additional terminals. Smaller operating units need the capability to support them.

A sensible comparison therefore goes beyond total centralization versus total separation. Information could be shared widely while the reach of changes is limited. Separating the functions that create pooling benefits from the common effects worth limiting allows consideration of designs that retain both advantages. Their feasibility depends on the equipment and operating arrangement.

Two contractors may still share a dependency

Choosing separate contractors can expand bargaining options. But if both depend on the same subcontractor, common function or control path, effects originating there may remain shared. Two supplier names do not establish operational independence. The buyer needs to explain what has actually been divided.

Conversely, two services bought from one provider could limit their operating reach separately. Two terminals or two contracts are not evidence that the limitation works. Distinguish spending on visible separation from spending that changes the reach of an action. Without that connection, the buyer cannot identify what a premium purchases.

The guide to revealing underlying investment overlap introduces a related way of looking through labels. Tracing contractors to the functions they share is useful, but a diagram of commercial relationships cannot establish technical independence without examining the operating arrangement.

Geography alone cannot define the unit of separation

Distance between facilities can reduce dependence on an event at one location. Yet distance does not remove a dependency on the same capability to change their operation. Geographic and control diversification address different causes. Achieving one does not eliminate the need to examine the other.

It also matters how jointly affected facilities are connected for the purpose of supplying electricity. A distant generator is not an equivalent replacement if the means or capacity to deliver its output where required are unavailable. Neither closeness on a map nor geographic separation alone settles the operational comparison.

Define the common action being considered before choosing which capacities to aggregate. Changing generation types or locations can leave the same command dependency intact. Conversely, equipment at one location might allow individual actions to be limited. A regulatory classification and an economic comparison of alternative arrangements should not be forced into the same mechanical calculation.

Staggering a planned change has its own cost

Consider planned changes that can be postponed or stopped between applications. If a problem appears before the next application and the remaining rollout can be halted, staggering changes may limit the effect. This protects the sequence of a change; it does not separate a common command capability available continuously. The relevant comparison connects the time before a problem appears with the range over which further applications can be stopped.

Delay also has costs. A useful improvement may arrive later, and different operating states may have to be supported simultaneously. The efficiency of keeping everything aligned must be compared with the option to revise a decision partway through. Avoiding duplicate capabilities does not make the work of managing the interval free.

The analysis of Italian electricity demand and supply timing provides background on matching quantities to moments. The same discipline helps value shared operations. Specifying which overlap is being reduced allows staggered changes and separate operating ranges to be compared as alternatives serving the same objective.

Does the backup use the same dependency?

Counting backup locations or capabilities can conceal a component that disables both the normal and reserve arrangement. If they share a necessary authentication, communication or decision function, that dependency still requires consideration. A backup is not proof that every common effect has been removed.

Making everything entirely separate can also increase expense and disperse expertise. Define which function should remain available under a particular common event. Separating the necessary range might preserve normal information sharing while limiting the operations affected together. Independence needs to be assessed against the cause it is meant to withstand.

The analysis of refrigeration settings and maintenance addresses the work of restoring equipment. Aggregated generation adds a question about support needed by several facilities at once. A specialist or replacement function available to each customer individually may not be able to provide the same service to all simultaneously. This congestion is another shared dependency.

Limiting the set of customers affected together offers an alternative to expanding support capability indefinitely. Equally, a pooled specialist service with sufficient capability may be the better choice. Compare the cost of limiting common reach with the cost of handling joint demand for assistance. Headcounts alone are less informative than the combinations of requests a provider can accommodate.

Compensation does not create replacement electricity

Suppose an operating contract provides financial compensation for a failure. It may transfer part of a generator’s financial exposure. The right to receive money is not equipment capable of supplying electricity at the required moment. The loss shifted by payment and the disruption borne by electricity users need not cover the same range.

Who receives compensation also matters. Payment to the contracting generator may reduce its loss without reaching everyone affected elsewhere. Strengthening an individual company’s financial protection and reducing joint operational consequences are different economic outcomes. Preserve that distinction when comparing the price of compensation with the price of operational separation.

If one provider owes compensation to several customers simultaneously, its ability to fund those payments matters too. Individual limits need to be read alongside the funding and aggregate terms applicable to simultaneous claims. The actual provisions require individual contracts. The analytical point is that common effects can concentrate burdens on the paying side as well as the side experiencing damage.

How separation costs reach a provider’s margin

Where spending on separate operating ranges precedes repricing, short-term profit and long-term service value can move differently. Investing in separate operating ranges may create options to sell later. If customers do not value the premium, the provider retains the cost. Spending alone establishes neither a competitive advantage nor pricing power.

The guide connecting profit, assets and cash supports the financial reading. Identify where separation expenditure appears, what recurring costs remain and when fees can recover them. Revenue growth and margins alone can blend the gains from wider pooling with the upfront burden of limiting common effects.

Buyers must also price what separation gives up

An additional separation fee cannot be ranked simply as a choice between cheap and dangerous or expensive and safe. Limiting common effects may sacrifice integrated information, flexible staffing and coordination between facilities. The cost includes lost benefits alongside additional expenditure.

Align the service being compared. If one offer provides advice while another executes operating changes, their price difference is not a clean price for independence. Hold the task, operating range and response time consistent, then compare the common reach. A cheaper offer that removes a function differs from one providing the same function through a different arrangement.

The EverWind analysis of grid costs compares demand adjustment with financial responsibility. For generation services, the useful comparison connects individual service terms to jointly affected operations. A large investment headline cannot establish which pooling benefits were retained or which effects were limited. Define what the buyer receives before assessing the expenditure.

International expansion depends on operating combinations

For a provider selling across countries, geographic growth can diversify income. But a business affecting physical equipment also needs to explain which functions support each region. Separate national names and contracting entities do not by themselves divide a common control dependency. Alternatively, common expertise might be shared while operating reach is limited regionally.

Expansion costs differ depending on whether the additional work is sales and local support or the continuing maintenance of another operating unit. Shared technology and people may offer an advantage, yet limiting joint effects can leave recurring local expenditure. Valuing international growth solely by the low cost of copying software misses this work.

The most direct market channel is a change in the terms on which operating services and contingency capability are purchased, rather than an immediate forecast for global electricity prices. Providers may compete both in pooling work and in selling a bounded operating range. One staff report does not establish identical rules across countries. Where institutions differ, compare the work customers require and how it is priced.

SG Group View: put savings and joint exposure side by side

SG Group sees value in reporting two units alongside each other: the party and task generating a saving, and the set of equipment reachable through a common action. The first alone can overstate pooling benefits; the second alone can neglect expertise and coordination. Return both to a comparison serving the same supply objective.

Three axes guide that comparison: individual savings versus joint contingency needs; nominal diversification versus actual reach; and the efficiency sacrificed to limit that reach. Together they help distinguish additional entities or contracts from an arrangement that changes operational dependency. Maximum fragmentation is not the objective. The objective is a configuration that meets the same supply purpose with a lower total burden.

This concern weakens where common functions have demonstrably bounded reach, additional customers do not expand existing customers’ joint exposure, and pooling improves decision quality. Such evidence supports a stronger valuation of shared operations. Conversely, if lower fees accompany wider joint reach without information for assessing the burden, price reductions are less convincingly explained by efficiency alone.

Three paths change what customers pay for

The first path keeps common operating capability while placing concrete limits on where actions can reach. Spending may support defined operating boundaries while retaining shared information and specialists. Success is measured by what remains common and what is limited, rather than by additional terminals or companies.

The second divides contracting parties or customers formally while leaving an important common component unchanged. It may improve procurement choice, but that is a different benefit from reducing joint operational reach. Where operational diversification was the reason for paying more, reconcile the purpose with the actual arrangement. More names alone do not establish lower contingency costs.

The third creates separate operating ranges but loses substantial pooling benefits. Additional people and equipment, and coordination across fragmented information, can add costs. If the burden is large, one option is to restore shared information functions rather than reversing every separation. These are conditional paths for comparing expenditure, not forecasts with assigned probabilities.

Do not assign one cause to the same observed result

Even if interruptions fall after pooling, improved expertise need not be the only explanation. Equipment replacement, different operating conditions or an easier comparison period could also matter. A decision to retain pooling needs to connect improved functions with the common effects still present. A good outcome does not validate every part of an arrangement.

Likewise, higher costs after separation are not necessarily all inefficiency. The buyer may have purchased capability that reduces a joint exposure previously omitted from its assessment. Returning expenditure to the earlier level could remove that capability. This is why a comparison can use the burden of sustaining the same supply conditions rather than the service fee alone.

That does not justify attaching a safety label to every expense. If additional spending cannot be connected to changed reach or replacement capability, the objection that it merely adds cost remains valid. Aligning configuration, function and expense applies the same question to sellers of separation and sellers of pooling.

Evidence about the joint range changes the assessment

The first material input is an explanation of which functions can affect which equipment. Beyond customer names, identify how observation and changes are divided. Sensitive connection details need not be made public without limit, but buyers and evaluators need enough understanding of the relevant range to compare a price for independence.

A second input is replacement capability under a specified common effect, including simultaneous demand from several customers. Success for one facility cannot establish success for the group’s joint requests. Explanations of bounded reach and of the capability to meet common demand make the case for retaining pooling more concrete.

Financially, examine the connection between separation expenditure and fee recovery, and how growth changes the operating units that must be sustained. For regulatory developments, read the scope and legal effect of the document actually issued. Configuration, economic consideration and regulatory classification are related, but one document need not establish all three. Update the assessment according to the layer the information changes.

Value pooling alongside the reach of its actions

The attraction of pooled generation operations lies in sharing work required by separate assets. Valuing that benefit requires considering both the work saved and the range exposed to a common action. Adding up individual purchasing choices does not necessarily produce the best arrangement once joint effects are included.

Additional companies, contracts and locations can have different purposes: greater bargaining choice, less exposure to one place, or limited reach for a command. Defining the purpose of the spending brings pooling efficiency and separation benefits into a consistent price comparison. That is more useful to companies and electricity users than counting nominal divisions.

For international operating providers, the relevant capability is not scale alone. It is the ability to choose which work to share and which effects to limit. Where those choices fit customer needs and earn a return, both pooling and separation can create business value. The case for growth then becomes an explanation of which operating range can be supported at which total burden, rather than simply a rising customer count.