India's energy data standard, and the layer it leaves out.
The India Energy Stack specifies how power-sector data moves between the parties entitled to it. Its published use cases state that it does not build the analytics on top. Sutra builds that layer.
Seven use-case notes, a technical specification and a public schema repository are published. Four utilities completed a 30-day challenge against the specifications, each building an adapter and demonstrating the first four use cases.
The programme's own status note records no dated evidence that the pilot sandbox is running, that any utility exchanges data through it, or that any use case is in production. So we do not describe the stack as live.
How it works
It adds no central database or platform, and does not change a utility's meter systems.
Register
Each participant, such as a utility, metering operator, regulator or consumer, gets a decentralised identifier and a directory listing.
Discover
A party entitled to data finds who holds it and on what terms, with no central broker.
Exchange
The record moves over a signed channel in a published format, with consent attached and a trail a third party can verify.
The seven use cases, and where Sutra fits
The programme marks two of them as work in progress.
01 Consumer Energy Passport A signed certificate of a connection and the assets behind its meter, held by the consumer. not ours
Consumer-side. Sutra can read a passport. We do not issue them.
02 Smart Meter Data Exchange One standard interface for meter data to move between a metering operator, a utility and an authorised recipient, with consent receipts and an audit trail. we read this
Our ingest surface. Today we read vendor export formats. We are building to the published meter-data schema.
03 Consumer Meter Digest A utility-signed statement of a consumer's own readings for a chosen period. adjacent
Built on the same reads our loss and billing work uses.
04 DER Visibility A per-feeder register of behind-meter assets, linking panel to inverter to meter to transformer. No personal data. we build this
Our network model already links these assets. A standard register would let hosting-capacity work move between utilities.
05 Tariff Intelligence The regulator publishes each tariff order as a signed machine-readable file: slabs, time-of-day surcharges, and a version chain. work in progress we build this
Tariff rules already run in Sutra as deterministic code.
06 DISCOM to Regulator Data Exchange Tariff filings, true-ups and compliance returns as structured signed data, line item by line item, versioned and non-repudiable. work in progress we build this
The regulator-facing surface, and the closest to what we ship.
07 Peer to Peer Energy Exchange Cross-utility prosumer trading, with contract, meter evidence and settlement, and no central exchange. not ours
Outside distribution analytics today.
The two work-in-progress use cases are the two Sutra is built around.
Tariff intelligence and utility-to-regulator filing sit in the programme's work-in-progress section, outside its report. Both face the regulator, and both are what Sutra was built for.
Tariff slabs, time-of-day surcharges and eligibility rules run as versioned, deterministic code.
Each line item of a filing or true-up traces to its record and formula.
The published use cases say they build no analytics.
What we are doing
The schemas ship with their own validation scripts, so anyone can check conformance.
The meter-data schema
The filing schema
One acronym, two quantities
Identity, which we do not have yet
We have not published a validation report, so we do not claim conformance. When we do, it goes on this page with its date, and you can rerun it with the same public scripts.
Start with a paid pilot.
One zone, with a measure we agree on day one. If the result is not better, we refund the fee. After the pilot, the license is a flat fee per utility, whatever your meter count.