Fleet network access (binding constraints)
get_network_accessHow often binding network (transmission) constraints limited each NEM battery's access to the energy market over a date window, split by direction. Per unit: pct_discharge_limited, pct_charge_limited, pct_top_price_discharge_limited (share of the top-10% regional price intervals that were discharge-limited), pct_neg_price_charge_limited (share of negative-price intervals that were charge-limited), commissioning_days and top_constraint (AEMO constraint ID, direction, description). Also the constraints behind the most fleet exposure. This is EXPOSURE, not lost revenue: a binding constraint caps what a unit could do, not what it wanted to do, and AEMO often resolves it by moving other units — never present these as lost dollars or lost dispatch. Commissioning units (commissioning_days > 0) dispatch on test schedules; leave them out of comparisons. Check commercial_context: TOLLED/CONTRACTED units dispatch for an offtaker. Minimum window is 30 days (shorter is widened); data from July 2024; constraint data lags about two days (days_covered vs days_requested). Large response (every unit); for one battery use get_battery_network_access.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"date_from": "<date_from>",
"date_to": "<date_to>"
},
"name": "get_network_access"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| date_to | Yes | End date YYYY-MM-DD. | |
| date_from | Yes | Start date YYYY-MM-DD. Ranges under 30 days are widened to the last 30 days ending date_to. |