Architecture
The rulebook that lets any system in the power sector talk to any other
A DISCOM, an aggregator, a lender, a regulator, a technology provider: each runs its own systems, built at its own pace, for its own purpose. IES does not ask any of them to change what they run. It gives every one of them a common way to identify each other, agree terms, and exchange data, so a connection built once works with every other system that follows the same specification.
How IES works: register, discover, exchange
IES tells any two systems in the power sector how to talk to each other. It works in three steps. Tap a card for details.
Register once
Tap to reveal ↓Discover before every exchange
Tap to reveal ↓Exchange the interaction itself
Tap to reveal ↓What IES architecture covers, in short
IES brings shared rules to four things that move across the sector: information (e.g., meter and operational data), services (e.g., connections, demand response, market services), trust (e.g., identity, credentials, provenance), and money (e.g., billing, settlement, incentives).
It does this without a central database, and without asking any participant to redesign its internal systems. Four capability layers carry the weight:
Identifiers
Every actor and asset gets one stable, verifiable name.
Registries
Authoritative, machine-readable lists. No central registry: each one is kept by whoever already holds that authority, the regulator for licences, the utility for connections.
Credentials
An institution signs a record once. The holder keeps it. Anyone can verify it later without contacting the issuer.
Data Exchange
One pattern for every exchange: discover, agree, exchange, receipt. Data stays where it was created.
Agreements, Consent & Policy Packs
What was agreed, what was permitted, and which rule was in force, all signed and versioned, so a dispute resolves against evidence rather than correspondence.
Security
Sector standards secure the estate. IES secures the exchange: the boundary where data crosses between organisations.
Observability
Every interaction leaves standard evidence. The programme learns from receipts and aggregates, never from anyone's raw data.
The principles IES is built on
These 15 principles govern every design decision in IES, in four groups. Hover a card to see each group's principles.
Trust and Control
4 principles- Data federation
- Privacy and trust
- Cybersecurity by design
- Sovereignty
Open by Design
4 principles- Interoperability
- Ecosystem neutrality
- Open innovation
- Transparency and efficiency
Built to Last
4 principles- Scalability and resilience
- Minimalism
- Build on what exists
- AI readiness
Built for Everyone
3 principles- Inclusivity
- Unified, not uniform
- Asynchronous adoption
The IES taxonomy
Before two systems can exchange data, they need to agree what words mean. The taxonomy settles that, in three layers:
Core Vocabulary
The terms every domain shares: who a participant is, what an asset is, the roles of DISCOM, aggregator, regulator, consumer, etc.
Domain Vocabularies
One controlled vocabulary per subject (meter data, energy credentials, tariffs), each mapped explicitly to the external standard it draws from.
Crosswalk
A published, field-by-field map from every IES term back to the standard it came from, so an implementer can always trace where a term originated.
Existing standards first, new specifications last
A schema fixes the exact field names, formats and validation rules for one kind of message. IES does not invent these from scratch. It works through a fixed order of preference, and stops at the first standard that meets the need:
BIS
PreferredAn Indian standard, where one exists. It already reflects Indian practice, Indian equipment and Indian regulatory requirements.
CEA
A regulation, technical standard or reporting format issued by the Central Electricity Authority. These are already binding on the sector, so building on them adds no new compliance burden.
IEC
An international standard, where neither of the above covers the need.
IEEE
Where IEC does not cover it, typically at the device and interconnection level.
Other recognised open standards
Where the need sits in a domain these bodies do not cover, a standard from another recognised body already in sector use: ISO, ITU, SAE, W3C and IETF among them, and domain specifications such as OCPP.
A New IES Specification
Only where none of the above covers the need. This is the exception, not the method, and every new specification goes through the same public review and versioning as any other.
A participant already compliant with the applicable Indian standard is already most of the way to conforming with IES.
The IES adapter: connect once, nothing else changes
Whoever you are (a DISCOM, an aggregator, a lender, a technology provider), becoming IES-ready works the same way. Your own systems are not changed. A piece of software, the adapter, sits at the edge of your system and makes it conform to the IES specifications.
Handles finding other systems and exchanging messages with them.
A one-time mapping between your own data formats and the IES specifications.
The adapter works like a USB-C port. Standard on the outside, whatever the device on the inside. Once any two participants each wear one, they connect to each other with no further integration work. The first connection carries most of the effort; every one after it carries almost none.
IES is evolving rapidly. Subscribe to our monthly newsletter to stay informed about new developments, use-cases, and opportunities to participate.
INDIA ENERGY STACK.
DIGITAL PUBLIC INFRASTRUCTURE FOR ELECTRICITY.
BUILT IN INDIA, FOR THE WORLD.
Copyright © 2026 INDIA ENERGY STACK. All rights reserved.