> 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/use-case-implementation-guides/use-cases.md).

# Overview

Each guide takes a real outcome and shows how to ship it on IES — what schemas it uses, what your adapter needs to do, who is involved, and what good looks like at the end.

Every guide follows the same **IES Documentation Template** (eleven numbered sections + use-case extras), and every guide's **Setup** section is organised by the same [**Register → Discover → Exchange**](/docs/readme.md#how-it-works-three-steps) spine that runs through the whole GitBook. Once you have read one guide, you know where to look in any other.

***

## Piloted in the 30-day Challenge

These four use cases were [demonstrated by the four pilot DISCOMs](/docs/readme.md#pilots-and-status) in the 30-day Challenge — a completed, historical outcome; see [**Status**](/docs/status.md) for current status.

| Use case                                                                                           | Issuer / Provider | Audience                              | Schema                                                                                                                                                                                                                                     |
| -------------------------------------------------------------------------------------------------- | ----------------- | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [**Consumer Energy Passport**](/docs/use-case-implementation-guides/consumer-energy-passport.md)   | DISCOM            | Consumer (held in DigiLocker)         | [ElectricityCredential v1.2](https://india-energy-stack.gitbook.io/docs/schemas/electricitycredential/v1.2) (holder-bound)                                                                                                                 |
| [**Consumer Meter Digest**](/docs/use-case-implementation-guides/consumer-meter-digest.md)         | DISCOM            | Consumer (held in DigiLocker)         | [MeterDataCredential v0.6](https://india-energy-stack.gitbook.io/docs/schemas/meterdatacredential/v0.6) (holder-bound)                                                                                                                     |
| [**Smart Meter Data Exchange**](/docs/use-case-implementation-guides/smart-meter-data-exchange.md) | AMISP / DISCOM    | DISCOM / SERC / consented third party | [MeterData v0.6](https://india-energy-stack.gitbook.io/docs/schemas/meterdata/v0.6)                                                                                                                                                        |
| [**DER Visibility**](/docs/use-case-implementation-guides/der-visibility.md)                       | DISCOM            | Grid operator, aggregator             | [ElectricityCredential v1.2](https://india-energy-stack.gitbook.io/docs/schemas/electricitycredential/v1.2) energyResources, per consumer today; a PII-free per-feeder aggregate is an illustrative future profile, not yet its own schema |

## Work in progress (WIP)

These guides are still being finalised and may change.

| Use case                                                                                         | Issuer / Provider | Audience              | Schema                                                                              |
| ------------------------------------------------------------------------------------------------ | ----------------- | --------------------- | ----------------------------------------------------------------------------------- |
| [**DISCOM Regulatory Filing**](/docs/use-case-implementation-guides/discom-regulatory-filing.md) | DISCOM            | SERC                  | [ArrFiling v0.5](https://india-energy-stack.gitbook.io/docs/schemas/arrfiling/v0.5) |
| [**Policy as Code**](/docs/use-case-implementation-guides/tariff-intelligence.md)                | SERC              | DISCOMs, applications | (tariff schema — in progress)                                                       |

## In progress

| Use case                                                                                 | Schema                                                 | Status                                            |
| ---------------------------------------------------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------- |
| [**P2P Energy Transaction**](/docs/use-case-implementation-guides/p2p-energy-trading.md) | [External — Energy Trading](/docs/schemas/external.md) | Schema published; pilot integrations being staged |

> **OutageNotification** — the schema is published ([v0.1](https://india-energy-stack.gitbook.io/docs/schemas/outagenotification/v0.1)), but there is no IES use-case guide for outage visibility yet. See the [OutageNotification family page](/docs/schemas/outagenotification.md) for the plain-language walkthrough of what the schema covers.

***

## How each guide is organised

Every page follows the **IES Documentation Template** — eleven sections plus the use-case-specific extras:

1. **Scope and Purpose** — the problem, in plain words
2. **What It Records / Covers** — what is captured
3. **How Each Item is Identified** — DIDs, identifier patterns
4. **Definitions** — terms and acronyms
5. **Basis of Standards** — the standards this use case follows (BIS → CEA → IEC → IEEE precedence)
6. **Where Indian Standards Do Not Yet Exist** — gaps and the international standards used
7. **The Record(s)** — the artefacts produced
8. **Schedule I — Static Fields** — field reference (links to the schema for the full table)
9. **Schedule II — Report Templates** — where applicable
10. **How It Fits Together** — diagram or short narrative
11. **Points for Confirmation** — open decisions

* **Schemas Used in This Use Case** (use-case-specific extra)
* **Value Unlock** (use-case-specific extra)
* **Setup steps (Register → Discover → Exchange)** + **Checklist** + **Dev kits**

***

## Picking a first use case

If you are a DISCOM implementing IES for the first time, the [Build your Internal-facing Adapter guide](/docs/how-you-implement-ies/build-adapter.md#pick-your-first-use-case) has a decision table — which use case to ship first based on what internal data is easiest for you to expose.

***

## See also

* [**Register**](/docs/what-ies-provides/register.md) · [**Discover**](/docs/what-ies-provides/discover.md) · [**Exchange**](/docs/what-ies-provides/exchange.md) — the three IES steps each use case combines.
* [**How you implement IES**](/docs/how-you-implement-ies/how-you-implement-ies.md) — the one-time setup that supports every use case.
* [**Schemas**](https://github.com/India-Energy-Stack/ies-accelerator/tree/main/schemas/README.md) — schema map showing which schemas each use case combines.


---

# 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/use-case-implementation-guides/use-cases.md?ask=<question>&goal=<endgoal>
```

`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.
