Tungsten
We deal our life in half-hour measurements. Forty-eight trading periods a day, every day, for the life of the asset. Tungsten is the engine that models them, dispatches them, and shows the working on every one of them.
Tungsten is ASKA's own software — the feasibility engine, dispatch controller, and operating record behind every battery we run. It models a site before we build, decides what the battery does every half-hour once it's live, and keeps the reasoning for every decision. One system, from the first proposal to the monthly report.
Representative site · figures indexed
Every half-hour, Tungsten reads the site load, the tariff band, the spot price, and the state of charge — then makes a decision and writes it down. This is what a morning at a representative site looks like.
This is the Dispatch Visualizer — the operator tool every ASKA figure ships with. All 17,520 slots of a modelled year, coloured by what the battery decided: charge in the cheap hours, clip the demand peaks, discharge into price spreads. Filter any behaviour, hover any slot, click any day and read the whole story — down to the margin it settled at.
This is not a marketing render — it is the tool the operator runs, fed with a representative dataset. On a real engagement it runs on your meter data, and every figure in your proposal can be traced back to the slots on this screen.
In most of this industry, the savings model that wins the sale and the reporting tool that tracks the asset are different systems — often from different companies. The numbers drift, and nobody can say why. Tungsten closes that gap by being both.
Your interval data and your actual tariff go into Tungsten. It simulates the asset against your real year — every trading period — and produces the business case. No generic assumptions, no borrowed load profiles.
The same engine that modelled the site now runs it. Dispatch decisions follow the same logic the proposal was built on — so the asset does what the business case said it would.
Monthly performance comes from the same calculations again. When the report says you saved a number, that number reconciles to the dispatch log, the tariff dataset, and the engine version that produced it.
Measured half-hourly data and published tariff schedules in; a slot-by-slot dispatch priced into a stacked, non-double-counted return out. Every stage is instrumented and audited. Only the optimisation core is proprietary.
Before any number leaves the engine, a fixed register of checks runs — and every run closes on a recorded pass or fail carrying the engine version that produced it.
The method is not the secret. Slot-by-slot dispatch optimisation is a known technique, and we're happy to name it. What's proprietary is how we formulate and tune it — the objective, the constraints, and the calibration that turn a generic solver into an accurate model of real battery behaviour. The technique is shared. The engine is ours.
Before any battery is modelled, the engine rebuilds your invoice from the half-hourly meter data and the published schedules — and has to match it. If we can't reproduce your bill, we don't get to predict your savings.
Every tariff in Tungsten carries its source reference and the date it took effect. When a network company changes a rate, we know which day — and every calculation before and after uses the right one.
nz-tariff-2026-04-01Every dispatch decision and every report records the engine version that produced it. If the logic improves next quarter, last quarter's numbers still reconcile to last quarter's code.
engine f9e1a3dThe load data behind every model run is kept with the run. Ask how a feasibility number was reached two years later — the inputs are still there.
icp-interval-2026-Q2Tariffs move, spot patterns shift, your operation evolves. Each quarter we re-tune the dispatch strategy — and the change, the reason, and the expected effect are logged like everything else.
tuning 2026-Q3 · reviewOne engineered cabinet, deployed to the scale your site needs — with Tungsten making forty-eight decisions a day on top of it.
Explore GridStore →Send us twelve months of interval data. We run it through the engine and show you exactly what a battery would have done — period by period.
Start the conversation