Find the market pathway before promising the revenue.

A practical APAC primer on aggregation, market access and the limits of revenue stacking. Start with eligibility and net value, then decide whether a deeper study is justified.

Read the guide Check project readiness

Version 1 · Reviewed 25 October 2026 · Historical examples are not current admission rules. No universal APAC revenue rate or guaranteed return is assumed.

01 / DECISION GUIDE

From questions to verifiable decisions

1. Set the boundaries

A microgrid has a defined electrical boundary and coordinated local operation; island capability depends on its design. A VPP coordinates distributed resources to provide services. DERMS manages distributed-resource interactions with network needs; an EMS manages energy within its operating scope. Commercial aggregation, network security and local control are different responsibilities.

Identify the asset owner, local operator, network operator, aggregator and market counterparty.
Document who can dispatch, who can override and who remains accountable for safe operation.
A microgrid may participate in a VPP; neither label guarantees islanding, market eligibility or grid-forming capability.

2. Australia: learn from a completed demonstration

The ARENA-supported AEMO VPP demonstration ran from 2019 to January 2022. It observed contingency FCAS, responses to energy prices and local network services. This establishes demonstrated service types, not today's eligibility for a particular battery or a guaranteed customer return.

For an Australian project, check the current NEM participant pathway, service specification, registration and metering requirements with AEMO and the proposed aggregator.
Compare customer reserve settings, warranty permissions, telemetry and connection/export constraints.
Request net customer settlement examples and contract terms; do not reuse historic trial prices as a forecast.

3. Singapore: distinguish sandbox access from open market access

EMA announced a VPP regulatory sandbox initiative in October 2025. A sandbox provides a route to test an approved arrangement under defined conditions. It does not mean every DER owner is automatically entitled to earn energy or ancillary-service revenue.

Confirm the applicable EMA and market-operator requirements for the specific service and participating entity.
Obtain written confirmation of sandbox participation or the relevant commercial route, including scope, term and exit arrangements.
Validate settlement, telemetry, cyber requirements and the network interface before assuming a monetisable service.

4. Underwrite net value, not gross revenue

Separate tariff savings, energy-market margin, availability payments and performance payments. They may depend on different baselines, dispatch rights and settlement periods. Some services compete for the same MW, MWh or operating hours.

Net value = eligible incremental receipts − aggregator/platform fees − incremental energy/losses − degradation − additional O&M − penalties − foregone site value. Avoid subtracting a cost twice if already netted in settlement.
Run low-dispatch, low-price, reduced-availability and non-performance cases; leave uncontracted income uncertain.
Set an explicit reservation for site resilience, and forbid dispatch that breaches the reservation.

5. Review contracts before building the interface

A technically capable asset can still be unsuitable if the dispatch contract conflicts with its original purpose. Review the connection agreement, OEM warranty and site obligations together with the aggregation agreement.

Record dispatch limits, override rights, customer opt-out, data ownership and termination provisions.
Allocate cybersecurity, communications outages, baseline disputes and non-delivery liability.
Agree measurement, verification, settlement audit and dispute handling; require evidence of how payments reach the asset owner.

02 / DATA REQUEST

Turn gaps into a trackable request

Keep unknowns visible. Download the editable checklist and add evidence, status, owners and dates.

Critical gate

Market

Country, service, programme/sandbox, eligibility and rule version

Market adviser · Written eligibility + rule links

Critical gate

Asset

MW/MWh, export limits, controls, telemetry, tests and warranties

Asset / OEM lead · Datasheets + test evidence

Critical gate

Site priority

Protected reserve, outage duties, override and operational consent

Asset owner · Approved operating envelope

Net value only

Commercial

Settlement formula, fee, penalties, degradation and foregone value

Aggregator + finance · Contract + settlement example

Before contracting

Governance

Cyber access, data rights, liability, dispute and exit terms

Legal / operations · Responsibility matrix

03 / ILLUSTRATIVE EXAMPLE

Illustrative capacity conflict: a 1 MW battery

Fictional teaching example. Assume a 1 MW PCS currently discharging 0.8 MW. A proposed service requires an additional 0.4 MW upward response. Energy/SOC and reactive capability must be checked separately.

Options against shared assumptions; not a recommendation ranking
Check	Calculation	Decision
Power headroom	1.0 − 0.8 = 0.2 MW; requested 0.4 MW exceeds available headroom by 0.2 MW.	Do not commit both duties as stated.
Possible revised schedule	Limit site discharge to 0.6 MW to retain 0.4 MW of simplified active-power headroom.	Recalculate lost peak savings and service qualification.
Energy and reserve	No duration, SOC, efficiency or reserve data provided.	Power arithmetic alone does not qualify the service; energy and availability remain unresolved.

Nameplate capacity is not dispatchable headroom.
Do not add tariff savings and market revenue without modelling their scheduling conflict.
The next step is an operating-envelope and contract review, not a revenue promise.

04 / EVIDENCE DIAGNOSTIC

Six evidence checks, with next actions

References and actions stay in this browser and are not sent with usage analytics. Browser clearing removes them; download a copy. All ratings are self-reported and independently unverified.

01 · Critical gate