Flux Energy
Feature · Curtailment & Compliance
Run a wildlife curtailment on the schedule set by the permit. Operations gets the hours, trading gets the cost, settlement gets the payment treatment, and compliance gets the record for the filing.
Every summer night, the turbines on this ridge go quiet for the bats. The permit says so. Operations writes down the hours, by hand, by headlight. Trading finds the gap the next morning. The lost hours had a price, and nobody told them what it was. Settlement has to decide whether the landowner gets paid for hours that never ran. And compliance owes the state a report on all of it, built months later, from whatever got written down.
In Flux Energy, the quiet hours are one record. What kind, when it started, when it ended, which turbines, how much energy and what it was worth that night, written once against the turbines' own signal. Operations sees the hours already counted. Trading sees what the night cost, no spreadsheet. Settlement decides, on the event itself, whether it enters the royalty, and the landowner sees the same line. And when the state report comes due, the deadline was already tracked, with every night already under it.
Five fifty-two. The bats are down, the ridge comes back, and the yard below it never stopped. One night. One record. Four desks that agree.
The problem
How it works
Recurring or one-off curtailment schedules are set once, on the turbine's Environmental tab. The automated runner executes the SCADA curtail and release at the window's start and end. Nobody has to be awake for it.
Type, start and end time, turbines affected, energy lost, and the market price at that moment are captured on a single curtailment event. Environmental sits alongside grid-instruction and maintenance as a first-class type.
Revenue leakage intelligence rolls the event into lost revenue, any compensation received, net leakage, and a recovery rate, so trading sees the cost of the quiet hours without building a spreadsheet.
A loss-to-cash decision marks whether the curtailment enters the royalty base, visible on the same line the landowner sees. Regulatory filings track their deadline with the event already attached, and an automated gap check escalates anything at risk.
What you get
Operations, trading, the royalty statement, and the state report agree, because they read the same event.
The curtail-and-release cycle executes on schedule, and the record it leaves is complete before anyone checks it in the morning.
The deadline is tracked from the day the permit is issued, and the events are already there when the report is due.
Where this connects
The loss-to-cash decision on a curtailment event is the same decision that shapes the royalty statement.
The battery yard can keep working through a curtailment window while the turbine event is recorded.
Curtailment events are part of the same settled-period record a lender's model draws its production from.
Questions
No. The permit does. Flux Energy runs the schedule you set on it: a recurring window (dusk to dawn during migration) or a one-off exception, with the automated runner executing the curtail and release at the times you configured.
Yes, when the loss-to-cash decision marks it royalty-bearing. The same line appears on the landowner portal alongside production and CPI detail.
Yes. Curtailment events carry a type, such as grid instruction, environmental, or maintenance. Revenue leakage intelligence rolls up lost revenue and recovery rate across all of them.
The filing pulls from the same event record: deadlines are tracked from the permit date, and the curtailment events for the period are already attached when the report comes due. The filing itself is a package you assemble and submit, not something that writes itself.
One-off schedules can be added alongside the recurring rule, so an exception doesn't require rewriting the whole season's window.
Explore
Compare met mast and LiDAR data across layouts, then carry the selected resource case into financing.
Read morePlan wind and storage together, account for battery wear, and carry dispatch into settlement.
Read moreHourly prices from every ISO, recurring constraint windows learned from your own history, bids and trades posted to one ledger.
Read moreBuild SAM-aligned P50/P90 models and trace key figures to the operating records behind them.
Read moreApply contract terms to production, review the calculation, and carry the result into payment.
Read moreYou’ll work directly with the people building Flux Energy. We’ll map the schedule, operating event, settlement treatment, and reporting deadline in a working session.
