Ready to act on flexibility? Start with the scope

Home » Blog » Flexibility » Ready to act on flexibility? Start with the scope
Ready to act on energy flexibility? Learn how NZ electricity distribution businesses can scope use cases, connections and costs before implementation.

Flexibility is no longer a new idea for New Zealand’s electricity distribution businesses.

Most Electricity Distribution Businesses (EDBs) understand that flexibility will play a role as electrification increases and networks look for ways to manage demand, defer investment, and make better use of existing infrastructure.

The harder question is what to do next.

For an EDB that wants to move from interest to action, the starting point should not be a large implementation. It should be a clear scoping exercise that defines the use case, identifies the parties and systems involved, and works through what will be required to make it operational.

A good scope reduces uncertainty before you commit significant time or money.

Start with the use case, not the technology

The first question is simple:

What are you actually trying to achieve?

Flexibility can mean very different things depending on the network problem being addressed.

An EDB might want to explore dynamic operating envelopes for connected inverters. It might want to send more dynamic pricing signals to retailers or flexibility service providers. Or it may want to work with commercial customers to shift load away from periods of network congestion.

Those are different use cases, involving different participants, connections and technical requirements.

That is why the first step is not choosing a platform or protocol. It is defining one or two clear use cases and understanding who needs to participate.

In the early stages, that may also mean identifying supportive customers, retailers, or other partners willing to collaborate while you establish the process.

Scope it before you build it

A flexibility scope is essentially a pre-project plan.

Its job is to work through practical questions before committing significant money to software, hardware, or integration.

That includes questions such as:

  • What use case are we pursuing?
  • Who are we interacting with?
  • What devices or organisations need to be connected?
  • What signals need to be sent?
  • How will those connections work?
  • What interface does the EDB need with its own systems?
  • What standards or protocols are required?
  • What external services or development work may be needed?
  • What will implementation and ongoing operation cost?

The aim is to get the pieces of the puzzle on the table before implementation starts.

In some cases, the scope may be relatively straightforward. In others, the number of devices, manufacturers, participants and systems involved can make the picture considerably more complex.

Either way, those questions need to be answered first.

The first implementation step should be big enough to learn from

The scope should be broad enough to uncover everything the EDB needs to understand before moving forward. That does not mean the first implementation needs to be large.

Once the scope is clear, the next step is to choose an initial implementation that is meaningful enough to test how the model works in practice, but controlled enough to manage risk, cost and complexity.

Terry describes the right size as:

“Enough to learn from, but no more and no less.”

For one EDB, that may mean working with 20 connected sites before thinking about 1,000. For another, the right starting point may be larger or smaller.

The scope should help answer that question.

The objective is to take a first step large enough to expose the real operational, technical, and commercial issues while creating a clear pathway to scale.

The connections are where the complexity appears

One of the most common assumptions is that all devices, connections and signals are broadly the same. They are not.

An EDB may need to connect through an inverter manufacturer’s cloud platform, a home energy management system, a retailer, a flexibility service provider or another endpoint entirely.

Each pathway can introduce different technical and commercial requirements.

A manufacturer may need to approve access to its cloud environment. An endpoint may need new software capability. A connection may involve an international protocol such as OpenADR, IEEE 2030.5 CSIP-AUS (or both). Licensing, cybersecurity, development, or ongoing service costs may also apply.

Those details matter because they can materially change both the implementation path and the cost.

The purpose of the scope is to uncover them before the project starts.

Commercial value and implementation cost are different questions

Two separate commercial questions also need to be kept distinct. The first is whether the flexibility use case itself has value. That is something the EDB should already have a view on.

For example, shifting demand away from a peak may help defer a major network investment. That avoided or delayed expenditure creates the economic case for using flexibility in the first place.

The second question is what it will cost to implement the required solution. That is where the scoping exercise becomes important.

The scope should identify the likely project costs, including software, integrations, manufacturer connections, implementation work and any ongoing external service costs.

That gives the EDB the information it needs to compare the expected value of the flexibility use case with the practical cost of enabling it.

The output should be an implementation plan

At the end of the process, the EDB should have much more than a technical description. It should have an implementation plan.

That plan should make clear:

  • what the EDB wants to implement
  • who needs to participate
  • what needs to connect
  • what systems and standards are involved
  • what the first implementation phase should look like
  • what the likely project costs are
  • what ongoing costs may apply
  • what dependencies or risks still need to be managed
  • how the approach could scale over time

Flexibility is still a developing market. Some answers will be similar from one project to the next, while others will depend entirely on the network, the use case, and who is involved.

The aim is to identify the least-regrets step that gives the EDB enough confidence to move forward.

Then implement

Once the scope is complete, the next step is implementation.

That may mean issuing an RFI or RFP, delivering part of the work internally, engaging technology providers, working with manufacturers, or bringing in external partners.

The key is that those decisions are now based on a defined plan rather than assumptions.

For an EDB that knows flexibility needs to become part of its network strategy but is still working out how to move from interest to action, the first useful conversation is often simply:

What are you trying to achieve?

From there, the right scope can start to take shape.

Cortexo is currently working on several flexibility scopes with EDBs in New Zealand. If you are considering where flexibility could fit within your network and what the first practical step should look like, talk to Terry.

Photograph of Terry Paddy, CEO of Cortexo.

Terry Paddy

Managing Director, Cortexo Limited

SHARE THIS POST

Facebook
Twitter
Pinterest
LinkedIn
Recent Posts

Newsletter Signup

Seasonal updates from our blog and other news.

Make a connection.
Get in touch with Cortexo

Contact Cortexo today to learn how we can help connect you to better insights and save money.

Cortexo logo colour
Sign up to stay in the loop