Deploy

4.1 Set standards and grid codes 

To ensure that all assets within the grid ecosystem behave in predictable and interoperable ways, it is crucial to establish and enforce standards, and to review and update grid codes. Interoperability requirements ensure that assets can exchange standardised information about their capabilities, status and availability, and act on common instructions to enable flexible operation. Similarly, grid codes need to keep pace with new resource types and changing system dynamics, anticipating future needs while avoiding undue burden on existing asset owners and operators. Together, up-to-date standards and grid codes enable flexible operation, reduce operational costs and ensure that new resources do not undermine reliability as systems change.

Why this recommendation matters

Standards and grid codes are the shared rules that turn a heterogeneous mass of equipment into a controllable system. Standards allow diverse hardware and software to exchange information and instructions, while grid codes govern how assets connect and behave on the power system. Both must evolve as the grid diversifies; when either lags, new resources get blocked or fragmented, market power concentrates, and system reliability or cost falls unevenly on whoever is left covering the gap. 

Standards help to manage a grid ecosystem that is coming to encompass millions of diverse assets from a wide range of global technology providers. This gives rise to a familiar commercial dynamic: providers compete to establish their own proprietary protocols and platforms as dominant, seeking to lock customers in and capture long-term commercial advantage, much as has happened in the consumer technology sector. The result is a fragmented grid ecosystem that drives up integration costs, slows the deployment of new technologies, concentrates market power among dominant vendors, and makes it harder to switch or upgrade components over time. Early smart meter rollouts in the UK and US illustrate what happens when interoperability is not enforced from the outset, with billions in public investment failing to deliver the intended benefits, requiring costly remediation programmes. 

Grid codes, in turn, specify how assets connect and operate to keep the system stable as its composition changes, through measures such as voltage and frequency ranges, fault ride-through and reactive power. Two pressures are rendering existing frameworks obsolete.

Technically, codes were built around large synchronous generators delivering predictable, one-way flows to passive demand. However, with the rise of inverter-based generation, distributed resources, bidirectional flows and active demand-side participation, those assumptions no longer hold. This risks blocking new resources from connecting while also affecting power system stability as the generation mix shifts. Commercially, new contracting models such as power purchase agreements, flexibility contracts and aggregation are decoupling energy supply from system services such as inertia, frequency response, voltage support and grid-forming capability. Traditionally, synchronous generation provided these services for free as a physical by-product. This is not the case for new sources of supply. Consequently, they need explicit assignment through grid codes to avoid responsibility falling between the cracks. 

Standards and grid codes shape the asset stock, which is why early action is crucial to avoid costly post-installation interventions. Requiring equipment to have a specific capability at the point of manufacture – when hardware and firmware are being specified – is much lower cost than requiring the addition of the same capability afterwards. Proportionality is what keeps this affordable and burden-sharing fair: a household rooftop system should face fewer obligations than a transmission-connected utility-scale installation. Clear standards and codes provide certainty to manufacturers and project investors. Open standards foster competition and eliminate bespoke integration. A fleet of assets that can operate smoothly together can further lower costs, and can ensure that reliability is maintained, or even improved, as the system composition evolves. 

How to act on this recommendation

Core measures

Implementation considerations

Stakeholder interests around both interoperability standards and grid codes are likely to diverge. System operators prefer equipment to meet demanding capability requirements because they are responsible for managing the consequences if equipment cannot be coordinated. Manufacturers prefer requirements that are stable, internationally aligned and announced with enough lead time, since fragmented national variations raise costs and shrink production runs. Dominant technology vendors may resist interoperability requirements that undermine proprietary ecosystems, while smaller manufacturers, new entrants and aggregators benefit from the level playing field common standards create. Asset owners resist obligations they see as serving the system rather than their own interests, particularly where a capability must be provided without payment. Existing asset owners also face compliance costs when requirements tighten or extend to cover them for the first time, while new resource types need clear codes in place before they can connect at all. The design question that recurs is where to draw the line between a capability an asset must have, a service it must provide as a condition of connection, and a service that is procured competitively (see recommendation 6.2). 

The equity dimension turns on who gets to set the standards and who has to bear the compliance costs. Standard-setting processes, typically run through international bodies, tend to be dominated by larger vendors and wealthier countries with the resources for sustained participation. Policymakers should be aware of this, invest in participation where possible and retain flexibility to adapt requirements to local context. Requirements that are proportionate to asset size protect households and small businesses from obligations designed for utility-scale plant, and tiered verification keeps the cost of demonstrating compliance in line with the scale of the connection. Where legacy equipment must be brought up to standard, the allocation of retrofit costs is a policy decision with real distributional consequences that policymakers should settle deliberately.