> For the complete documentation index, see [llms.txt](https://india-energy-stack.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://india-energy-stack.gitbook.io/docs/readme.md). # Home **India Energy Stack (IES)** is a common set of specifications for sharing data across the power sector. It works the way UPI works for banking β€” UPI holds no money of its own; money stays in the customer's bank, and UPI is only the shared rules that let any bank pay any other. **IES is the same idea, for energy data.** The data stays in the systems that already hold it, and IES specs let any two systems exchange and act on it directly. IES is **live**. [Four pilot DISCOMs](/docs/what-ies-provides/what-ies-is.md#pilots-and-status) built their adapter and demonstrated DER Visibility, Consumer Energy Passport, Consumer Meter Digest and Smart Meter Data Exchange in the 30-day Challenge (21 May – 21 June 2026). {% hint style="info" %} πŸ“„ **Printable version:** download this entire guide as a single PDF β€” [**ies-report.pdf**](https://india-energy-stack.github.io/ies-accelerator/ies-report.pdf). Schema reference material is included as an appendix at the end. Regenerated automatically whenever the docs change β€” see [Download PDF](/docs/download-pdf.md). {% endhint %} *** ## How IES works β€” three steps Every IES interaction follows the same three steps. They are the **spine of this entire GitBook**. | Step | What it does | Example standard | | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | | [**1. Register**](/docs/what-ies-provides/register.md) | Every participant gets a verifiable digital identity and is listed in a shared directory. *Done once.* | [W3C Decentralised Identifiers](https://www.w3.org/TR/did-core/) | | [**2. Discover**](/docs/what-ies-provides/discover.md) | Before every exchange, both systems look each other up, confirm the other is genuine, and agree on what will be exchanged and on what terms. *No bilateral arrangement is needed.* | [Beckn protocol](https://github.com/beckn/protocol-specifications-v2) | | [**3. Exchange**](/docs/what-ies-provides/exchange.md) | Data moves using agreed field names and structure, following the public standard for that domain. Where the use case needs a durable record, a **verifiable credential** is issued that the holder keeps. | DLMS/COSEM, IEEE 2030.5, OpenADR; W3C VCs | IES picks the right open standard for each step and publishes a specification on top. **IES does not write new standards.** Build to the IES specs once, and a system can connect to any other IES-ready system without fresh integration work. Two capabilities build on the shared identity foundation: **data exchange** β€” B2B exchange of structured datasets, for which IES recommends the Beckn protocol β€” and **energy credentials** β€” W3C Verifiable Credentials issued with OpenCred, verified against the issuer's published key, and delivered to consumers over DigiLocker, web portals or any channel the issuer already runs. Credentials do not require a Beckn network. *** ## How this guide is organised Three top-level sections, each organised by the **Register / Discover / Exchange** spine. ### [What IES Provides](/docs/what-ies-provides/what-ies-provides.md) The specifications. What is published. | Section | What's in it | | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [What IES Is](/docs/what-ies-provides/what-ies-is.md) | The intro, on one page. Problem, UPI analogy, what IES is and is not, sector impact, the four pilots, FAQ. | | [Register](/docs/what-ies-provides/register.md) | Verifiable digital identity (W3C DIDs) and the shared directory (DeDi) β€” one page. | | [Discover](/docs/what-ies-provides/discover.md) | How two registered organisations find each other, agree terms and sign β€” the Beckn-protocol interaction (B2B). | | [Exchange](/docs/what-ies-provides/exchange.md) | How data moves once discovered: the Taxonomy, and where verifiable credentials (B2C) fit. | | [Taxonomy](/docs/taxonomy/schemas.md) | The master vocabulary of IES β€” every domain object, its plain-language overview, and the schema that describes its shape; standards precedence, versioning, proposal flow. | ### [How you implement IES](/docs/how-you-implement-ies/how-you-implement-ies.md) The action guides. What you do. | Step | Action page | Time | | ---- | ---------------------------------------------------------------------------------------------- | --------- | | 1 | [Setup Register](/docs/how-you-implement-ies/setup-register.md) | 1–2 days | | 2 | [Issue Credentials](/docs/how-you-implement-ies/issue-credentials.md) *(credential use cases)* | Β½ day | | 3 | [Setup Exchange](/docs/how-you-implement-ies/setup-exchange.md) *(data-exchange use cases)* | 1–2 days | | 4 | [Build your Internal-facing Adapter](/docs/how-you-implement-ies/build-adapter.md) | 1–4 weeks | | 5 | [Conformance Checklist](/docs/how-you-implement-ies/conformance.md) | 1 day | ### [Use Case Implementation Guides](/docs/use-case-implementation-guides/use-cases.md) What you can ship, organised per the [**IES Documentation Template**](/docs/use-case-implementation-guides/use-cases.md#how-each-guide-is-organised) so once you've read one, you know where to look in any other. | Stage | Use cases | | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Live in pilot** | [Consumer Energy Passport](/docs/use-case-implementation-guides/consumer-energy-passport.md) Β· [Consumer Meter Digest](/docs/use-case-implementation-guides/consumer-meter-digest.md) Β· [Smart Meter Data Exchange](/docs/use-case-implementation-guides/smart-meter-data-exchange.md) Β· [DER Visibility](/docs/use-case-implementation-guides/der-visibility.md) | | **Live or staged** | [DISCOM Regulatory Filing](/docs/use-case-implementation-guides/discom-regulatory-filing.md) Β· [Tariff Intelligence](/docs/use-case-implementation-guides/tariff-intelligence.md) | | **In progress** | [P2P Energy Trading](/docs/use-case-implementation-guides/p2p-energy-trading.md) | *** ## Where to start * **New to IES?** Read [**What IES Is**](/docs/what-ies-provides/what-ies-is.md) β€” five minutes. * **Decision-maker / reviewer?** Skim [**What IES Provides**](/docs/what-ies-provides/what-ies-provides.md) in order: What IES Is β†’ Register β†’ Discover β†’ Exchange. * **DISCOM / regulator / vendor onboarding?** Go straight to [**How you implement IES**](/docs/how-you-implement-ies/how-you-implement-ies.md) β€” the same path the pilot DISCOMs followed in 30 days. * **Picking a first use case?** Browse the table in [**Use Case Implementation Guides**](/docs/use-case-implementation-guides/use-cases.md) β€” pilot cases at the top. * **Need a term defined?** Always-visible [Glossary](/docs/glossary.md). *** ## Why IES? The Indian power sector has spent heavily on digital tools but not on a common way for those tools to work together. A single DISCOM often runs several metering systems supplied by different firms and spends years making them work together because none was built to a common standard. The same effort is repeated across the country. IES is the **shared digital infrastructure** that ends that duplication β€” open specifications, verifiable data, interoperable protocols. The data stays where it is; the way it is described and requested becomes common. For the longer answer, read [**What IES Is**](/docs/what-ies-provides/what-ies-is.md). *** ## Key standards and protocols | Standard | Role in IES | | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- | | [W3C Decentralized Identifiers (DIDs)](https://www.w3.org/TR/did-core/) | The **Register** layer β€” cryptographic identity for issuers, holders, verifiers, assets and datasets | | [Beckn Protocol v2.0](https://github.com/beckn/protocol-specifications-v2) | The **Discover** layer β€” peer-to-peer discovery, contracting, consent, audit | | [W3C Verifiable Credentials](https://www.w3.org/TR/vc-data-model/) | The durable-record half of **Exchange** β€” signed, machine-verifiable credentials | | [DLMS-COSEM / IS 15959](https://en.wikipedia.org/wiki/IEC_62056) | The meter-data half of **Exchange** β€” smart-meter wire protocol used in RDSS AMI deployments | | [IEC 61968 / CIM / MultiSpeak](https://en.wikipedia.org/wiki/IEC_61968) | The asset-data-model half of **Exchange** β€” HES↔MDMS interoperability standards | | [IEEE 2030.5 / IEEE 1547](https://standards.ieee.org/ieee/2030.5/5897/) | The DER / flexibility half of **Exchange** β€” solar, storage, EV charging | | [OpenADR 3.1.0](https://www.openadr.org) | The demand-response half of **Exchange** β€” DR events and flexibility reporting | | [DigiLocker](https://digilocker.gov.in) | India's national digital document wallet β€” consumer-facing credential store | *** ## Related Repositories * [ies-docs](https://github.com/India-Energy-Stack/ies-docs) β€” IES architecture primitives and implementation guides * [Digital Energy Grid (DEG)](https://github.com/Beckn-One/DEG) β€” upstream open protocol specification * [DDM](https://github.com/beckn/DDM) β€” Decentralized Data Marketplace (`DatasetItem` schema family) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://india-energy-stack.gitbook.io/docs/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.