Contact

No. IES does not store, run or control any data or systems. Everything an organisation runs today continues to run. IES only standardises the way systems share data with other organisations' systems.

Mainly for connecting an organisation's systems to those of other organisations, which is where most of the difficulty lies today. The same adapter and standard also help within an organisation, where several systems from different vendors may not be able to exchange data with each other. The larger gain is external, across DISCOMs and States; the internal improvement follows.

No. IES asks for no new data. It only puts the data already produced into a common format when it is shared.

No. IES does not require redoing what has been built. It sets the common standard the next integration will follow, so the next one is easier.

Nowhere new. Data stays where it is created. IES only standardises how the data is described and requested when it has to move from one organisation to another.

No. IES is a set of open, published specifications, with no licence fee and no central platform to install. A ready-made connector, the adapter, is provided to start with.

The connector, called the adapter, is mostly ready-made. IES provides it as open software, based on the Beckn ONIX reference implementation, together with a working sample. An organisation's technology vendor configures it for its systems and adds the translation between its data format and the IES format, building to one published standard rather than a fresh custom integration each time.

No. IES only turns the existing CEA and CERC rules into a form software can read. If putting a rule into practice reveals a gap, IES points it out to the regulator, who alone decides what to do about it.

The consumer can prove a single fact, for example that the sanctioned load is above a certain level, without revealing the rest of the data.

It is live. The sandbox is running, and four pilot DISCOMs built their adapters in it and demonstrated live use cases.

A few functions can be done alone today, but IES is built for the whole country and benefits every participant. A consumer moving States arrives with a record that's trusted at once; a bank or scheme anywhere in India can accept a DISCOM-issued record; and a service proven in one State is available to others without being rebuilt. Working alone, every DISCOM solves the same problem by itself - with one common standard, the work is done once.

A portable, verifiable record of their connection with the DISCOM — sanctioned load, any sanctioned generation, and consumption history - held in DigiLocker. The consumer can share it, on their own terms, for a green loan, a subsidy, or a service, without returning to the DISCOM for paperwork each time.

Yes. The same one-time adapter serves both purposes -it improves how current systems exchange data today, and provides the base to add new services later on the same standard.

No. Each asset is given its digital identity at the moment a use case first needs it, not all at once. Everything already in place - verified identities, trust checks, agreed data formats - is reused. The first asset connected takes the most effort; each one after is far easier.

Yes. Every message carries a digital signature, and the identity, consent and data layers are kept separate. The adapter sits at the edge of a system only and creates no new internal integration points; security incidents follow the established power-sector incident response process.

Yes. IES does not store personal data. Consumer data is shared only with the consumer's explicit consent, and only for the stated purpose, following applicable data protection law.

Three things: lower cost, as one published standard replaces repeated custom integration work with no vendor lock-in; better operations, from reliable data supporting forecasting and loss reduction; and wider use of existing data, as verified records support services like green lending, with demand flowing back through the DISCOM. IES is not a revenue scheme and does not monetise personal data.

Yes, with no size limit. IES specifies the data format and coordination, not the transport, so data moves over the organisation's normal channels — either inline in batches, or by a signed link to fetch a file. Either way IES handles discovery, consent and the audit trail.

The IES Cell, an executive unit reporting to the IES Steering Committee under the Ministry of Power. The Central Electricity Authority has a standing seat on the Architecture Group to review and propose, alongside representation from across the sector.

Any participant can propose a change to the IES Cell. Proposals are reviewed, and accepted changes are published as a new, versioned specification, so every implementation knows what changed and when. The detailed process will be set out once the IES Cell's governance framework is notified.