Skip to main content

Know the windows
your portfolio keeps repeating

Flux Energy brings hourly market prices, recurring curtailment windows, bids, bilateral trades, and settlement into the same workflow. Your desk can plan from recorded patterns instead of rebuilding them after the fact.

  • Prices sync hourly for every ISO you name
  • Recurring windows learned from your last 90 days
  • Bids and bilateral trades, one lifecycle
  • Revenue posts to the ledger automatically

The recurring constraint everyone remembers but nobody records

  • Trading works from a price screen and a spreadsheet. Operations knows about the Tuesday-afternoon congestion window, but it lives in someone's head, not in a record.
  • The battery finds out about a constraint when it starts, not before. It is empty when the spike comes, or full when the price goes negative.
  • Bids, bilateral trades, ISO settlements, and the general ledger are four systems, and forecast-versus-realized revenue is rebuilt by hand every month-end.

How market activity moves through Flux Energy

1. Sync hourly and day-ahead prices

Real-time and day-ahead prices sync hourly for every ISO your projects and contracts name, and one failed feed never blocks the others. Market rule profiles cover the US ISOs plus Canadian, European, and Australian markets, including settlement cadence, negative-pricing rules, and ancillary catalogs.

2. Turn repeated curtailments into named windows

Flux Energy folds the last 90 days of your curtailment events into recurring windows by market, weekday, and start hour. Each includes frequency per month, typical duration and megawatts, and a confidence that grows with every observation. Congestion, negative pricing, dispatch instruction, and economic curtailment are tracked as distinct patterns.

3. Set a charge target before the window opens

Each pattern carries a state-of-charge target. When the battery is below it ahead of an expected window, the advisory says so, with the reason attached. Wind and storage are then dispatched as one plan.

4. Keep bids, trades, and settlement connected

Day-ahead bids and bilateral trades move through one lifecycle with counterparty exposure tracked. Market revenue posts to the general ledger automatically, reconciliation variance raises an alert, and forecast-versus-realized revenue is decomposed hour by hour.

Plan from recorded patterns, not memory

Put the recurring window on the calendar

The recurring constraint is a record with a confidence number, not a hunch.

Give the battery a target ahead of time

Charge targets arrive ahead of the window, not during it.

Reconcile month-end from the same activity

Forecast, realized, and the ledger entry are the same rows.

Energy markets, without the jargon

Where the market record is used

BESS routing

The charge target becomes part of the battery’s operating plan.

Bankability

PPA valuation and merchant price risk carry into the lender-facing finance case.

Common questions

Does Flux Energy forecast prices?

No. It finds recurring windows in your own curtailment history and shows them with a confidence number. The trading decision stays with your desk.

Which markets are covered?

Price feeds for NYISO, PJM, ERCOT, CAISO, MISO, SPP, IESO, AESO, and ENTSO-E in Europe. Settlement parsing for IESO, AESO, and 14 European markets. Market rule profiles extend further, including Australia.

Can Flux Energy submit bids to the ISO?

Adapters exist for NYISO, PJM, and ERCOT. Live submission uses your own ISO credentials and is off until you opt in; otherwise bids run in simulation.

How much history does it need?

A window appears after two observations in 90 days, and confidence rises with each repeat.

Does it handle PPAs and RECs?

Yes. PPA valuation, merchant price risk scenarios, and REC forward hedges sit alongside bilateral trades.

The rest of the platform

Use your own curtailment history

You’ll work directly with the people building Flux Energy. We’ll run your curtailment history through the pattern engine and review the recurring windows together.

Request a demo