REDSM
From the 15-minute block to the settled bill.
REDSM runs forecasting, scheduling and deviation settlement for wind and solar in one system of record. Every schedule revision, meter block, band rate and bill line is stored, versioned and hash-chained.
Start a free 90-day pilotStarts with a 45-minute walkthrough on live data, then a free 90-day pilot on your own data.
Download the brochure PDF, 7 pages, 6.5 MB
Bills you can explain
Each deviation charge is computed against the regulation in force on the block date. A bill can be explained line by line months later.
Fewer disputes, faster
Disputes are filed, reviewed and adjudicated inside the system, against the same records the bill was built from.
Rates are data, not code
Band tables, multipliers and revision caps are effective-dated data. A weekly regulation watch files change proposals; nothing changes until an operator applies one.
Why REDSM
The regulation moved to slabs and 15-minute blocks. Most settlement desks are still on spreadsheets.
Forecasting, scheduling and deviation settlement regulations for wind and solar require every generator, through its QCA, to schedule 96 blocks a day, revise within caps, and settle deviation against effective-dated band tables. The 2024 amendments replaced flat single-band charges with slab-progressive charges and, where applicable, multipliers of a contract or market-clearing rate.
That is a weekly cycle of schedule intake, meter reconciliation, band lookup, frequency-linked adjustment, bill publication, dispute handling, pool-account accounting and regulator reporting, across thousands of pooling substations and QCAs. Done by hand it is slow, contestable and impossible to audit end to end.
REDSM replaces the spreadsheet chain with one system of record. Every schedule revision, meter block, band rate, bill line and adjudication is stored, versioned and hash-chained, so a bill can be explained line by line, months later, to a generator, a regulator or an auditor.
- 5,000
- QCAs per state deployment
- 9,999
- pooling substations
- 16
- revisions a day, capped in code
design limits, as configured
The settlement week, as REDSM runs it
- Availability and schedule intake
- API, CSV, XLSX, SFTP and pooled QCA files, with revision numbering and caps.
- Block promotion
- Five seconds after every block boundary; curtailment, moderation and day finalisation.
- Meter and telemetry ingestion
- Main against check mismatch, recheck, missing blocks and a coverage matrix.
- Deviation per block
- To slab or band, then frequency multiplier, on the table in force that day.
- Weekly bill
- Per pooling substation and QCA, one line per day per direction; surcharge accrual; corpus auto-adjustment.
- Disputes and reports
- Adjudication, pool account and regulator reports, every step on the audit chain.
Regulation engine
Rates are data, not code. The engine follows the order in force on the block date.
- Two settlement mechanisms, switchable
- Scheduled-generation basis (2024-style amendment, default) and available-capacity basis (2018-style) run side by side. A comparison view shows the delta for any pooling substation before a state switches.
- Slab-progressive charge engine
- Deviation is integrated across slabs, the first 15% at one rate and the next 10% at another, under two pricing modes: flat rupees per kWh per slab, or a multiplier of a contract or market-clearing rate, split solar and hybrid against wind, over against under. Earlier block dates keep the legacy single-band computation so historical bills stay reproducible.
- Frequency-linked multipliers
- 15-minute grid frequency is banded (below 49.85, 49.85 to 49.95, 49.95 to 50.05, 50.05 to 50.15, above 50.15 Hz) and an effective-dated multiplier is applied by direction.
- Regulation watch
- A weekly sweep fingerprints the regulator's archive, extracts numeric changes such as band rates, multipliers, surcharge, block minutes and revision caps, and files change proposals. Nothing changes until an operator applies one, and the application itself is written to the audit chain.
- Weekly bill mechanics
- One bill per pooling substation and QCA per settlement week; a line per day per direction; explanation that drills from total to block; what-if and mechanism comparison before publication; late-payment surcharge accrual and overdue auto-adjustment against the corpus.
- Pool account and frequency profiles
- Settlement cases and pool-account periods close on schedule; frequency profiles are stored per block so every multiplier is reproducible.
| Slab | Energy | Rate | Charge |
|---|---|---|---|
| 0 to 15% | 75 kWh | ₹0.50 | ₹37.50 |
| 15 to 25% | 25 kWh | ₹1.50 | ₹37.50 |
| Block total | ₹75.00 |
Illustrative seed rates. Actual tables are loaded per state and per effective date. The legacy flat band on the same block: 100 kWh × ₹1.50 = ₹150.
Platform
Eleven tender-grade modules, plus the control-room layer.
- Admin and configuration
- Block size, mechanism, revision caps; effective-dated band tables; operators, lock and unlock, MFA reset; audit tail, verify, export.
- Registration
- QCA, generating company, utility, consumer, pooling substation owner, substation and unit, with multi-step approvals and QCA-to-substation mapping.
- Scheduling and forecasting
- Availability and schedule intake with revision numbering; curtailment, moderation, day finalisation; wind and solar forecasts with P10, P50 and P90; auto-revise.
- Meter data
- CSV, XLSX and encrypted meter files; main against check mismatch, recheck, missing blocks; coverage matrix, daily summaries, timeline.
- Accounting and billing
- Block deviation to the slab-progressive engine; weekly bill; what-if, mechanism compare, bill explanation; dispute filing and finalisation.
- Finance
- Payments with gateway verification and webhooks; corpus accounts, ledgers, utilisation; surcharge accrual; ageing and outstanding by QCA.
- Power and weather visibility
- Real-time P, Q, status, irradiance, wind and temperature; daily visibility per unit; degraded, penalty and stoppage states; availability-to-visibility mismatch detection.
- Historian and MIS
- Pre-defined reports, top-N deviation leaderboards, ad-hoc query over whitelisted tables, bounded CSV, XLSX and PDF exports.
- QCA workspace
- Dashboard across all represented substations; pooled schedule upload; de-pooled meter upload; stoppage notices on default or de-registration.
- External interface
- API keys for programmatic access; SLDC dispatch ingest of declared, dispatched and curtailed energy; notification feed; adapter registry and call logs.
- Support and ticketing
- Severity SLAs; assignment, escalation, public and internal threads; knowledge base fed by regulator circulars.
- Control-room layer
- Settlement cases, pool-account periods, frequency profiles; approval chains with SLA escalation; auto-generated single-line diagrams; market ticker, monitoring matrix, map and operations wall.
AI co-pilot over live data
34 tools that read the same schedules, meters and bills the operators see. Ask why a bill moved, which substation breached a cap, or what a mechanism switch would cost. Answers cite the rows they used, and the anomaly agent files findings, not alerts.
One code base, one database, one audit chain
Every module reads and writes the same schedule, meter and bill records. There is no reconciliation between systems because there is only one system.
Audit
A bill you can defend, line by line, months later.
- Hash-chained audit trail
- Every write, from schedule revision and meter block to rate table, bill line and adjudication, is chained to the one before it. Tail it, verify it, export it.
- Versioned, never overwritten
- Revisions are numbered and capped; superseded schedules stay readable next to the one that settled.
- Bill explanation
- From weekly total to day, direction, block and slab, with the band table and frequency multiplier that applied.
- What-if before publication
- Re-run a week under the other mechanism, a proposed table or a corrected meter file, and see the delta before anyone is billed.
- Disputes with a paper trail
- Filing, evidence, adjudication and finalisation live in the same record as the bill they contest.
- Bounded exports
- Reports are sized and whitelisted, so an export is a document, not a database dump.
- Security and access
- Role-based access for SLDC operators, utilities, QCAs, generators and auditors; multi-factor login; scoped API keys with call logs; hardening reviewed against a published checklist.
- Integrations and feeds
- Schedules and meters over API, CSV, XLSX and SFTP; OPC-UA and IEC-104 sidecars for telemetry; SLDC dispatch ingest; weather and market feeds; a bridge from AION RE-cast so forecast, schedule and settlement share one identity for every plant.
- Observability
- Health, queue depth and job timings exported to Prometheus and Grafana; scheduled jobs with SLA escalation; every adapter call logged with its outcome.
- Honest by construction
- REDSM does not invent a block. Missing meter data is flagged as missing, not estimated silently; every estimate that is made is labelled as one, and stays labelled on the bill.
What it does
- Scheduling, meter data, deviation accounting, weekly bills, disputes and pool accounts
- Slab-progressive and legacy single-band charge engines, switchable per state
- Telemetry sidecars for OPC-UA, IEC 60870-5-104 and SFTP
- 22 modules, 19 catalogued reports and a co-pilot with 34 live-data tools as shipped, 13 Sep 2026
- Hash-chained audit log, MFA and role scoping for seven stakeholder types
- Self-hosted on state, DISCOM or private-cloud infrastructure; 5-minute blocks by configuration
Send one week of schedules and meter files. We return the weekly bills, the deviation statements and the line-by-line explanation.
Who it is for
- State load despatch centresRun the settlement week on one system: intake, promotion, billing, pool account and regulator reports. Switch mechanisms by order date.
- DISCOMs and state utilitiesSee deviation exposure by substation and QCA before the bill; reconcile meter and schedule without a second system.
- QCAsOne workspace across every represented substation: pooled schedules up, de-pooled meters up, bills and disputes down.
- Generators and IPPsKnow which block, which slab and which multiplier moved the bill, and dispute it with the evidence attached.
- Regulators and auditorsVerify the chain, replay a week, export a bounded report. No spreadsheets to trust.
- Traders and RE desksMarket ticker, deviation leaderboards and top-N views across the fleet, on the same data the bill is cut from.
The free 90-day pilot
Free for 90 days, and configured to your regulation pack, not rebuilt for it.
Weeks 1 to 2: regulation pack
Load your band tables, mechanism, block size, caps and effective dates. Register substations, QCAs and units from your existing lists.
Weeks 3 to 6: shadow settlement
Ingest live schedules and meter files alongside your current process. Compare bills line by line.
Weeks 7 to 10: operators on the console
Disputes, approvals, pool account and reports run in REDSM; the spreadsheet chain stays as a check.
Weeks 11 to 13: cut over
Publish from REDSM. Hand the auditor the chain.
What we need from you
The regulation pack in force, a registry extract, two weeks of schedule and meter files, and one operator who knows how the current bill is built.
What you keep
- A shadow bill for every week of the pilot.
- A line-by-line reconciliation against your current process.
- A system already configured to go live.
Deployment
Runs on your cloud tenancy or on premises; one code base, one database; observability and backups included. Data stays in your jurisdiction.
Bring us one settlement week. We will hand it back, explained.
Write with the regulation pack you settle under. We will come back with a pilot plan and a configured instance.
Email info@aionpl.com