Frequency Control Ancillary Services (FCAS) are the services the Australian Energy Market Operator (AEMO) uses to help keep power-system frequency within the required range. In the National Electricity Market (NEM), an enabled provider changes generation or consumption in the direction and timeframe required by a specific FCAS market.
FCAS is not one generic fast-response product. AEMO's current introductory guide lists ten NEM FCAS markets: two regulation markets and eight contingency markets. Each has its own control path, response direction and assessment rules. A frequency-reading meter or a battery that accepts a set point proves only one part of the complete service.
Some AEMO overview copy still refers to eight FCAS markets. The dated 17 September 2025 guide and MASS v8.2 include very fast raise and very fast lower alongside the earlier eight services, giving ten. For engineering and registration, use the current MASS and applicable guide rather than an undated summary or search snippet.
The ten NEM FCAS markets
The service names combine three questions:
- Is the service regulation or contingency response?
- Is it raise or lower response?
- For contingency response, how quickly must it act?
| FCAS family | Raise service | Lower service | Purpose in AEMO's guide |
|---|---|---|---|
| Regulation | Regulation raise | Regulation lower | Correct minor supply-and-demand deviations within the normal operating band |
| Very fast contingency | 1-second raise | 1-second lower | Arrest a major frequency deviation within one second |
| Fast contingency | 6-second raise | 6-second lower | Arrest a major frequency deviation within six seconds |
| Slow contingency | 60-second raise | 60-second lower | Stabilise frequency over the 60 seconds after a major deviation |
| Delayed contingency | 5-minute raise | 5-minute lower | Recover frequency to the normal operating band within five minutes |
The labels describe service objectives, not a universal test waveform. The controlling specification is AEMO's current Market Ancillary Services Specification (MASS), together with the applicable registration guide and an AEMO-approved arrangement.
Regulation and contingency use different control paths
Regulation FCAS continually corrects smaller imbalances. AEMO's automatic generation control (AGC) sends raise or lower signals through the central control path, and the facility changes its active power relative to its reference trajectory. Providing regulation therefore requires more than measuring local frequency: the facility must support the required AGC, SCADA, control and feedback arrangement.
Contingency FCAS is enabled in advance but responds when a contingency causes a local frequency deviation. The local controller detects frequency and changes generation or consumption. A battery may change charge or discharge power; a generator may change output; an eligible load may change consumption. The event record must show what the participating facility delivered at the agreed measurement boundary.
Do not use “dynamic”, “static” or “FCAS” as though they identify the same control method. The MASS recognises variable and switching controllers, while Great Britain's system operator uses dynamic and non-dynamic as names for a different service distinction. Specify the market and controller behaviour directly.
What raise and lower mean
A raise service acts in the direction that raises system frequency. Depending on the asset, that can mean increasing generation, increasing battery discharge, reducing battery charge or reducing electricity consumption.
A lower service acts in the direction that lowers system frequency. That can mean reducing generation, increasing battery charge or increasing consumption.
This direction must remain unambiguous through metering, control and reporting. Record the sign convention at the facility boundary and at every interface. A technically correct response can look inverted if an inverter, meter, gateway and analysis workbook use different import/export conventions.
Dynamic vs static frequency response
“Static” often describes switching a discrete load or generator after frequency crosses a threshold. “Dynamic” often describes varying active power with the frequency deviation. Those are useful engineering descriptions, but neither is an AEMO registration decision.
The full control chain matters:
- how local frequency is acquired and filtered;
- the controller's deadband, droop, trigger or switching logic;
- controller and communications delay;
- the asset's ramp, saturation and operating limits;
- coordination with AGC, protection and other control modes; and
- measurement of delivered active power on the same time base as frequency.
A dashboard refresh rate does not establish any of those properties. A 20 ms record also does not prove that the source quantity was acquired every 20 ms. Keep acquisition, calculation, storage and upstream publication intervals separate in the design record.
Distributed energy resources in frequency response markets
Batteries, generators and controllable demand can all be relevant, but nameplate power is not the same as continuously available FCAS capacity. Availability can be restricted by state of charge, site import or export limits, inverter capability, process constraints, maintenance, temperature, warranties and simultaneous operating objectives.
Aggregation introduces another measurement problem. If participating equipment shares a connection point with unrelated load or generation, a change in site net power may not identify what the participating assets did. MASS section 5.3 contains specific rules for aggregated facilities, shared connection points and time alignment. Draw the electrical boundary before choosing the recorder.
For a battery project, define at least:
- the registered facility and connection-point topology;
- the asset, plant controller and FCAS controller responsibilities;
- state-of-charge and charge/discharge constraints;
- the local-frequency and active-power measurement points;
- the reference trajectory or counterfactual used for delivery assessment;
- the communications, acknowledgements and fallback states; and
- the configuration and firmware versions represented by the test.
Measurement requirements are service-specific
MASS v8.2 Table 5 is a matrix, not one universal “FCAS sample rate”. Its requirements vary by service, controller and aggregation arrangement.
For example, the table commonly requires local-frequency and power measurements at 50 ms or faster for very fast and fast contingency FCAS. Some aggregations of 25 or more facilities without inertial response may use 100 ms or 200 ms measurement under stated initiation-delay conditions. MASS also defines registration discounts for certain aggregated arrangements that use those slower rates. Slow and delayed services have different limits, and regulation has its own power-measurement and SCADA requirements.
The same table specifies measurement range, intrinsic uncertainty, resolution, time alignment and recording windows. For contingency FCAS, it includes:
- power-flow intrinsic uncertainty no greater than 2% and resolution no greater than 0.2% over the required range;
- service-dependent local-frequency uncertainty and resolution;
- event records covering defined periods before and after the frequency disturbance; and
- comparison of frequency and power on a common time scale.
MASS section 5.4 requires digital measurement records to be retained for at least 12 months from the frequency disturbance time and supplied to AEMO on request. These are provider obligations; a product datasheet does not allocate the operational responsibility.
What the verification tool does
AEMO publishes the FCAS Verification Tool (FCASVT) for calculating contingency FCAS delivery under the MASS. The current publication page pairs FCASVT v6.2 with MASS v8.2 and identifies the service calculations it supports.
The tool applies the specified analysis to suitable source data. It does not certify a meter, approve a controller, register a facility or repair missing observations. Retain the original data, configuration, analysis method, tool version and output so another reviewer can reproduce the result.
Registration is more than a successful event trace
AEMO's updated Battery Energy Storage System and wind/solar contingency-FCAS registration guides took effect on 2 September 2026. The final consultation record says the changes clarify testing, simulation and assessment, including the role of on-site testing relative to simulation-derived capability.
Treat these as distinct evidence:
- the equipment manufacturer's specification;
- laboratory or type-test evidence for measurement performance;
- the proposed topology, control design and test plan;
- simulation evidence where required;
- site test observations from the installed arrangement;
- the provider's verification and retention process; and
- AEMO's registration or classification decision.
Passing one stage does not silently approve the others. Reconfirm the current MASS, guide versions and AEMO process before a design freeze or test campaign.
Where EpiSensor's ZDR family fits
The current ZDR datasheet describes three controller variants:
- ZDR-20: static frequency response using relay switching;
- ZDR-21: static frequency response with 20 ms event-data recording and GPS/GNSS time synchronisation; and
- ZDR-22: battery control with dynamic frequency response, high-speed data and GPS/GNSS time synchronisation.
The same datasheet states frequency reaction and sample times of 100 ms or faster, 0.01 Hz resolution, frequency accuracy of ±0.01 Hz, lists Class 0.5S under three-phase power with a reference to IEC 62053-22, and describes optional Modbus RTU master communications over RS-485.
Those specifications are inputs to a qualification review, not a claim that every ZDR variant is approved for every FCAS market. MASS uses service- and facility-specific acquisition rules and the metrological term intrinsic uncertainty. A datasheet accuracy or IEC energy-class statement is not automatically interchangeable with the MASS power-measurement requirement. Very fast and fast arrangements may also require acquisition faster than the ZDR's stated 100 ms figure. Confirm the exact model, measurement evidence, topology, controller path and AEMO acceptance route before procurement.
Global perspective on frequency regulation
FCAS is NEM terminology, not a worldwide synonym for every ancillary service. Western Australia's Wholesale Electricity Market uses Frequency Co-optimised Essential System Services (FCESS) with its own accreditation and communications procedures. Great Britain procures Dynamic Containment, Dynamic Moderation and Dynamic Regulation. Continental Europe uses functions such as Frequency Containment Reserves, automatic Frequency Restoration Reserves and manual Frequency Restoration Reserves.
Similar objectives do not make registrations portable. Keep the system operator, synchronous area, service name and effective document set on the first page of every design and test record.
Ensure you meet the technical requirements for participating in frequency response markets
Before offering capacity or buying hardware, complete this sequence:
- Name the market and service. Record NEM or WEM, raise or lower, regulation or the exact contingency family.
- Confirm the current rules. Freeze the applicable MASS, registration guide and AEMO instructions by title, version and effective date.
- Define the participating boundary. Draw the connection points, shared loads, generators, meters, controllers and communications paths.
- Allocate responsibilities. Identify the FCAS provider, asset owner, market participant, controls integrator, metering owner and evidence custodian.
- Map every requirement to evidence. Separate product claims, calibrated or accredited test evidence, simulations, site tests and operational records.
- Test failure states. Include stale data, clock loss, communications loss, inhibited assets, state-of-charge limits, saturation and conflicting controls.
- Retain a reproducible record. Preserve raw observations, quality flags, configuration, analysis version, decisions and approvals.
Commercial prices and availability payments change with market conditions. Build the technical and operational case first, then model economics from current AEMO data and the actual provider arrangement rather than a historic headline rate.
Working out what this needs on your own site? Answer a few questions