From standalone batteries to distributed portfolios

The first project and the tenth project are different

Developing one battery project requires solving a specific set of technical, commercial and operational questions.

As the number of projects grows, the challenge changes.

The organisation must be capable of managing:

• multiple sites;
• different customers;
• varying network conditions;
• equipment across different locations;
• maintenance obligations;
• operating data;
• financial performance; and
• long-term asset management.

The value of the platform increasingly lies in its ability to manage that complexity.

Scale is therefore not just a question of deploying more megawatt-hours. It is about creating an organisation and operating system capable of supporting a larger asset base.

Common infrastructure, different sites

Distributed portfolios naturally contain variation.

Two battery projects may use similar equipment but operate in very different environments. One may be connected to a cold-storage facility. Another may support a logistics site. A third may sit within a water or industrial facility.

Each has its own operating requirements and electrical conditions.

The goal is not to make those sites identical. Instead, the portfolio can create consistency around the areas that benefit from common oversight.

This may include:

• project governance;
• data and reporting;
• operating systems;
• maintenance standards;
• procurement;
• safety frameworks; and
• asset-management practices.

The site-specific conditions remain important, but they can sit within a broader operating structure.

Operations become more important as the portfolio grows

The development phase receives much of the attention in new infrastructure. Over time, operations become increasingly important.

A distributed portfolio needs visibility across many assets at once. Operators need to understand whether assets are available, how they are performing and whether there are issues requiring attention.

This becomes particularly important when assets have different obligations at their individual sites.

Portfolio-level optimisation cannot ignore local constraints. A battery still needs to operate within the requirements of its host facility, its grid connection and its equipment.

The portfolio layer therefore needs to coordinate assets without losing sight of what is happening at each site.

Data creates a feedback loop

A larger operating portfolio also produces more information. Actual project performance can inform future decisions.

Over time, operating experience can improve understanding of:

• equipment performance;
• maintenance requirements;
• project delivery;
• site operations;
• energy behaviour; and
• portfolio-level performance.

This creates a feedback loop between existing assets and future development.

The value is not simply the data itself. It is the ability to use operating experience to improve how the next generation of projects is developed and managed.

Aggregation can create a different investment proposition

Distributed assets are typically smaller than traditional infrastructure projects. Individually, that can make them less efficient for larger pools of capital to assess and manage.

A portfolio can create a more coherent investment proposition by bringing multiple assets under common ownership, governance and reporting. This may provide exposure to a broader group of underlying projects rather than a single site.

At the same time, aggregation does not remove project-level risk. Individual assets will still differ by location, customer, operating profile and commercial structure.

A strong portfolio therefore needs transparency at both levels: the performance of the individual asset, and the performance of the wider portfolio.

Portfolio value is built gradually

Distributed infrastructure does not need to begin as a large portfolio. It can grow through successive projects.

The first projects establish operating experience. Additional projects broaden the asset base. Over time, systems, processes and governance can become increasingly standardised.

This creates the possibility of moving from individual battery installations toward a scalable distributed-infrastructure platform.

But scale should be the result of repeatability, not the objective at any cost. The quality of the portfolio ultimately depends on the quality of the assets within it.