Energy & Utilities

Power & Electricity

How power systems actually run: generation, transmission, distribution, grid operations, smart metering, billing, outages, renewables, and market settlement across utility networks worldwide.

Last updated:

400+ GW

Installed Capacity

250M+

Smart Meters

₹3L Cr

RDSS Investment

1,400+

Power Stations

What Engineers Miss When They First Enter Power & Electricity

Power systems are the opposite of a casual software domain. Electricity has to be balanced in real time, and if the balance slips, customers see flicker, outage, equipment damage, or cascading instability. The software around it is therefore built for control, telemetry, and exception handling rather than just convenience.

A modern utility or grid operator is really a collection of tightly linked operating layers. Generation teams plan output, transmission teams move bulk energy, distribution teams deliver it to consumers, and market or billing teams turn physical electrons into financial and operational records.

The interesting part is that this industry is changing from both ends. On one side, older infrastructure still depends on SCADA, RTUs, and legacy ERP systems. On the other, utilities are absorbing smart meters, IoT sensors, cloud analytics, EV charging, solar rooftops, batteries, and energy trading platforms.

What Teams Actually Do Day To Day

  • 1Operate control rooms that monitor generation, frequency, load, and switching state in real time.
  • 2Manage utility billing, consumption validation, subsidy processing, arrears, and consumer service workflows.
  • 3Detect outages, locate faults, dispatch crews, and restore service with minimal downtime.
  • 4Integrate smart meters, feeders, substations, and data historians into a reliable operational picture.
  • 5Balance renewables, storage, and demand response while keeping the grid within safe operating limits.

One End-to-End Utility Journey: From Consumption to Bill to Restoration

A consumer sees only a bill or an outage notice, but the utility is managing multiple independent flows underneath: telemetry collection, validation, billing, collections, outage detection, fault isolation, and restoration confirmation.

1

Smart meter or field meter captures consumption

Meters transmit interval data to the utility through AMI, or a field reader records consumption when the meter is still legacy. That data has to survive gaps, duplicates, clock drift, and tamper events.

Systems Involved

AMI, meter data management, head-end system, communication network

Where It Usually Breaks

If meter reads are missing or invalid, the billing engine has to estimate consumption and that can trigger disputes later.

2

Billing engine converts readings into a bill

The utility applies tariff slab, fixed charges, taxes, subsidies, arrears, and customer category rules. The bill is only as correct as the tariff, reading, and consumer master data behind it.

Systems Involved

Billing platform, tariff engine, consumer master, subsidy processor

Where It Usually Breaks

A wrong category, outdated tariff, or bad reading can turn into a revenue leak or a consumer grievance.

3

Consumer pays and the revenue cycle updates

Payments may come through UPI, cards, auto-debit, counters, or agent collection. The system must clear the payment, update balances, reduce arrears, and preserve a traceable receipt.

Systems Involved

Payment gateway, revenue management, receipting, collections, CRM

Where It Usually Breaks

If payment settlement and bill status are out of sync, consumers may be marked delinquent even after paying.

4

The grid detects an outage

A feeder trip, breaker alarm, or meter last-gasp event shows that service is down. The utility correlates the signals to identify which zone or feeder is affected.

Systems Involved

SCADA, AMI, outage management system, alarms, GIS

Where It Usually Breaks

The hard part is not seeing the outage; it is locating the fault precisely enough to repair it quickly.

5

Fault is isolated and crew is dispatched

The OMS or control room determines the likely fault location, isolates the affected section if possible, and sends a repair crew with map and asset context.

Systems Involved

Outage management, GIS, workforce dispatch, switching orders

Where It Usually Breaks

If field and control-room systems disagree on asset location or switching state, restoration can be delayed.

6

Power is restored and the event is closed

SCADA and meter confirmations verify restoration, consumers receive notifications, and operational metrics capture duration, root cause, and affected customers.

Systems Involved

SCADA, AMI, notifications, reliability analytics, crew closeout

Where It Usually Breaks

Without post-event analytics, the same feeder failures keep repeating and the utility never learns from the incident.

Where Production Incidents Usually Happen

A meter reading is missing but billing still has to run

Symptom: The consumer does not see a bill or sees an estimated bill that later gets disputed.

Why it happens: Meter communication failed, data validation rejected the read, or a device was offline during the capture window.

What good teams do: Utilities need estimation rules, exception queues, and later correction workflows instead of assuming every meter will report on time.

The outage is visible but the fault location is not

Symptom: Control room knows the feeder is down, but crews still spend time searching for the exact fault section.

Why it happens: Telemetry is not mapped cleanly to GIS assets or meter events are not correlated strongly enough with the feeder topology.

What good teams do: Correlate SCADA, AMI, and GIS in the outage workflow so the utility can isolate and restore faster.

Renewables create a ramp the grid was not tuned for

Symptom: Even when total generation looks sufficient, frequency or local congestion still causes instability at sunset or during weather swings.

Why it happens: Solar and wind are variable, so the net load shape changes faster than older thermal fleets can respond.

What good teams do: Use forecasting, reserves, storage, and flexible dispatch to keep the grid balanced through the ramp period.

Data Model Hotspots

Consumer And Billing State

consumerIdaccountIdtariffCategorybillCyclearrearssubsidyStatus

Billing data has to be legally defensible because it drives cash collection, grievances, and regulatory reporting.

Meter And Interval Readings

meterIdtimestampkwhvoltagetamperFlagconnectionState

Smart-meter interval data is one of the largest utility data streams and must support validation, theft detection, and outage analysis.

Grid Asset And Switching State

substationIdfeederIdbreakerIdlineStatusalarmStaterestorationStatus

Control-room systems depend on up-to-date topology, otherwise switching and restoration logic can be unsafe.

Integration Realities

Power utilities never run on one system

SCADA, AMI, GIS, ERP, billing, CRM, and outage tools each carry part of the truth. The engineering challenge is keeping those truths aligned.

Real-time control and batch billing coexist

Grid telemetry is seconds or sub-seconds, while billing and revenue runs are often batch-oriented. Good architecture must support both cadences.

Operations teams need explainability

If a reading is estimated, a consumer is disconnected, or a feeder is isolated, teams need to know why. Hidden automation is risky in utilities.

Renewables and storage change the model

Utility systems now have to integrate weather data, battery dispatch, EV charging, and demand response into planning and operations.

Regulation Changes The Software Shape

  • Power utilities are governed by a mix of national and state regulators, grid codes, market rules, and consumer-protection requirements.
  • Billing, subsidy, and disconnection workflows must be auditable because they directly affect households, industry, and public policy.
  • Grid operators need resilient control systems because outages can escalate from a single fault into a regional incident.
  • Renewable integration, open access, and energy markets all introduce new compliance and scheduling obligations into the software stack.

Common Misconceptions New Engineers Have

  • ×"Power software is just SCADA screens." The sector also includes billing, meter data, outages, market settlement, and field operations.
  • ×"If electricity is available at the outlet, the software job is done." Utilities still need to know what was consumed, what was billed, what was lost, and what failed on the way there.
  • ×"Smart meters are only for reading consumption." They also enable tamper detection, remote connect/disconnect, outage correlation, and demand response.
  • ×"Renewables can be added without changing the grid software." Variable generation changes forecasting, dispatch, balancing, and curtailment behavior.

Technology Architecture — How Power & Electricity Platforms Are Built

The diagram below reflects how production Power & Electricity systems are structured at scale — nine layers from client channels through edge security, API gateway, domain microservices, polyglot data stores, async event streaming, analytics, external partners, and cloud infrastructure. Solid arrows show synchronous REST/gRPC calls; dashed arrows show async event flows via Kafka or a message queue.

Power & Electricity — Enterprise Architecture ReferenceSolid arrows: synchronous calls (REST / gRPC) · Dashed arrows: async event flows (Kafka / Message Queue)CLIENTS & CHANNELSWeb SPAiOS / AndroidAdmin PortalPartner API3rd-Party WebhooksBatch / CronEDGE SECURITY & DELIVERYCDN (CloudFront / Akamai) · DDoS Shield · WAF (OWASP rules) · SSL/TLS Termination · Global Load Balancer (ALB / NLB)API GATEWAYKong / AWS API Gateway / NGINX / ApigeeRate Limiting · Routing · Versioning · Throttling · BFF PatternIDENTITY & ACCESSOAuth 2.0 · OpenID Connect · SAML 2.0JWT · RBAC · MFA · SSOCORE DOMAIN MICROSERVICES · REST / gRPC🖥️ SCADA / Energy Managemen…Real-time monitoring of grid stat…Automatic Generation Control (AGC…GET /api/v1/grid/statusSiemens Spectrum Power📊 Advanced Metering Infras…Automated meter reading (no manua…Real-time consumption monitoring …GET /api/v1/meters/{id}/consumptionItron OpenWay💰 Utility Billing & Custom…Bill generation from meter readin…Tariff management (residential, c…POST /api/v1/billing/generateSAP IS-U📈 Energy Trading & Market …Day-ahead market (DAM) — auction …Real-time market (RTM) — trading …POST /api/v1/market/bidIndian Energy Exchange (IEX)Service Mesh: mTLS · Circuit Breaker (Resilience4j / Hystrix) · Service Discovery (Consul / Eureka) · Distributed Tracing (Jaeger)DATA PERSISTENCE · PolyglotOSIsoft PI / Hi…OLTPPostgreSQL / Or…PrimaryRedis CacheCacheElasticsearchSearchS3 / BlobObjectASYNC MESSAGING & EVENTSApache Kafka / SQSPub/Sub · TopicsDead Letter QueueError HandlingStream ProcessorFlink / SparkANALYTICS & DATA PLATFORMData Warehouse (BigQuery / Snowflake / Redshift) · ETL/ELT (dbt / Airflow) · BI Tools (Tableau / Metabase) · ML Feature StoreEXTERNAL INTEGRATIONS & PARTNERSAMI (smart meter data)Weather service (rene…Energy trading (dispa…Protection relaysGIS (asset location)Billing system (consu…PLATFORM: Azure IoT Hub / AWS IoT Core / Kafka / Event Hubs · Kubernetes (EKS/AKS/GKE) · Docker · Helm · ArgoCD · CI/CD (GitHub Actions) · IaC (Terraform)OBSERVABILITY: ELK / Datadog · Prometheus / Grafana · Jaeger · PagerDutySECURITY: TLS 1.3 · Vault / KMS · SAST/DAST · SOC2 / ISO 27001Sync (REST / gRPC)Async (Kafka / Events)Each service owns its bounded context · CQRS & Event Sourcing where applicable · Polyglot persistence per domain

Industry Players & Real Applications

🇮🇳 Indian Companies

NTPC Limited

Power Generation (Thermal + Renewable)

SCADA, SAP, Oracle, IoT sensors, predictive maintenance

India's largest power generator — 70+ GW capacity, operates 70+ power stations, transitioning to renewables

Power Grid Corporation (PGCIL)

Power Transmission

SCADA/EMS, WAMS, SAP, GIS, Oracle

Operates 170,000+ circuit km of transmission lines, India's central transmission utility, 99.8%+ availability

Tata Power

Integrated Power Utility

Smart grid, AMI, SAP, Azure IoT, data analytics

India's largest integrated private power utility — generation, transmission, distribution, solar rooftop

Adani Power / Adani Green

Power Generation + Renewables

SCADA, SAP, IoT, cloud analytics

World's largest solar energy developer — 20+ GW renewable portfolio, rapid expansion

BSES / CESC / MSEDCL

Power Distribution (DISCOMs)

Billing systems, AMI, GIS, mobile apps

State distribution companies — manage last-mile delivery, billing for millions of consumers

Indian Energy Exchange (IEX)

Power Trading Exchange

Real-time trading platform, market algorithms, .NET

India's largest energy exchange — 90%+ market share in electricity trading, real-time market

🌍 Global Companies

Siemens Energy

Germany

Power Equipment + Grid Technology

SCADA, EMS, MindSphere (IoT), digital twin

Global leader in power generation equipment and grid management technology

GE Vernova

USA

Power Generation + Grid Solutions

Predix (IoT), SCADA, digital twin, ML

Gas turbines, wind turbines, grid solutions — one of the largest power technology companies

Schneider Electric

France

Energy Management + Automation

EcoStruxure platform, SCADA, IoT

Global leader in energy management — smart grid, building energy, industrial automation

ABB

Switzerland

Grid Automation + Electrification

ABB Ability, SCADA, protection relays, DCS

Leading supplier of high-voltage equipment, grid automation, and power quality solutions

🛠️ Enterprise Platform Vendors

OSIsoft PI (AVEVA)

Data Historian

Industry-standard real-time data historian for power plants — collects sensor data from turbines, boilers, and grid equipment

GE Grid Solutions / Siemens Spectrum Power

Grid Management

Advanced Distribution Management System (ADMS) and Energy Management System (EMS) for grid operations

Itron / Landis+Gyr

Smart Metering

Smart meter and Advanced Metering Infrastructure (AMI) — hardware and software for 250M+ meter rollout in India

SAP IS-U / Oracle Utilities

Utility ERP

Utility billing, customer information, meter data management — ERP for power distribution companies

Core Systems

These are the foundational systems that power Power & Electricity operations. Understanding these systems — what they do, how they integrate, and their APIs — is essential for anyone working in this domain.

Business Flows

Key Business Flows Every Developer Should Know.Business flows are where domain knowledge directly impacts code quality. Each flow represents a real business process that your code must correctly implement — including all the edge cases, failure modes, and regulatory requirements that aren't obvious from the happy path.

The detailed step-by-step breakdown of each flow — including the exact API calls, data entities, system handoffs, and failure handling — is covered below. Study these carefully. The difference between a developer who “knows the code” and one who “knows the domain” is exactly this: the domain-knowledgeable developer reads a flow and immediately spots the missing error handling, the missing audit log, the missing regulatory check.

Technology Stack

Real Industry Technology Stack — What Power & Electricity Teams Actually Use. Every technology choice in Power & Electricityis driven by specific requirements — reliability, compliance, performance, or integration capabilities. Here's what you'll encounter on real projects and, more importantly, why these technologies were chosen.

The pattern across Power & Electricity is consistent: battle-tested backend frameworks for business logic, relational databases for transactional correctness, message brokers for event-driven workflows, and cloud platforms for infrastructure. Modern Power & Electricityplatforms increasingly adopt containerisation (Docker, Kubernetes), CI/CD pipelines, and observability tools — the same DevOps practices you'd find at any modern tech company, just with stricter compliance requirements.

⚙️ backend

Java / Spring Boot

Enterprise SCADA backends, billing engines, energy trading platforms (IEX)

C/C++

Real-time SCADA control systems, embedded firmware for RTUs and smart meters

Python

Demand forecasting ML models, analytics pipelines, grid optimization algorithms

.NET

Utility billing (SAP IS-U plugins), customer portals, legacy DISCOM systems

🖥️ frontend

React + TypeScript

Modern utility dashboards, consumer portals, trading platforms

Angular

Enterprise grid management UIs, SCADA HMI web interfaces

Native Mobile (Kotlin/Swift)

Consumer apps for bill payment, outage reporting, usage monitoring

🗄️ database

OSIsoft PI / Historian

Time-series sensor data from power plants and grid — industry standard, millions of tags

PostgreSQL / Oracle

Billing, consumer records, trading transactions — ACID compliance for financial data

TimescaleDB / InfluxDB

Smart meter interval data — 250M meters × 96 readings/day = massive time-series

Redis

Real-time grid state cache, trading session state, alert queues

☁️ cloud

Azure IoT Hub / AWS IoT Core

Smart meter connectivity — bidirectional communication with 250M+ devices

Kafka / Event Hubs

Real-time event streaming from SCADA, meters, and trading — millions of events/second

Spark / Databricks

Meter data analytics, loss analysis, demand pattern mining at population scale

Kubernetes / OpenShift

Container orchestration for utility microservices — billing, CRM, analytics

Interview Questions

Q1.How would you architect a smart metering system for 250 million meters in India?

India's smart meter rollout (under RDSS) is one of the world's largest IoT deployments. Architecture: 1) Meter Hardware: Smart meters with bidirectional communication — RF mesh (for dense urban), cellular NB-IoT/4G (for rural/sparse). Each meter: measures kWh (import/export for solar), records 15-min interval data, stores 45 days locally, supports remote connect/disconnect, tamper detection (magnetic, bypass, reverse current). 2) Communication: Tiered architecture — meters talk to Data Concentrator Units (DCUs) via RF mesh (~500 meters per DCU). DCUs aggregate and forward to Head-End System (HES) via cellular/fiber. For cellular meters: direct to HES via NB-IoT. Protocol: DLMS/COSEM (international smart metering standard). 3) Head-End System: Receives data from all meters — 250M × 96 readings/day = 24 billion readings/day. Must handle: scheduled reads (every 15 min), on-demand reads (billing verification), events (tamper, outage, power quality). Architecture: distributed message queue (Kafka) → data validation → time-series DB (TimescaleDB cluster). Partitioned by DISCOM/zone. 4) Meter Data Management (MDM): Validates raw readings: gap filling (missing readings estimated), outlier detection (impossible consumption), theft detection (consumption pattern anomalies). Validated data → billing system. VEE process: Validation, Estimation, Editing — standard utility practice. 5) Scale Challenges: Storage: 24B readings/day × 365 days × 5 years retention = petabytes. Solution: hot (30 days in TimescaleDB), warm (1 year in columnar storage), cold (archive in S3/Glacier). Compute: billing run for 5 crore consumers in 4-hour window — parallel processing across partitioned data. Network: 250M concurrent IoT connections — carrier-grade infrastructure.

Q2.How does SCADA work in power grid management, and what are the key design considerations?

SCADA (Supervisory Control and Data Acquisition) is the nerve center of power grid operations. Architecture: 1) Field Devices: Remote Terminal Units (RTUs) at substations — interface with: circuit breakers (open/close commands), transformers (tap changer control), measurement devices (voltage, current, power flow). Modern: Intelligent Electronic Devices (IEDs) with IEC 61850 protocol. Data types: analog (voltage 220kV, current 500A, frequency 50.02Hz) and digital (breaker open/closed, alarm triggered). 2) Communication: Redundant paths — primary (fiber optic, 99.99% availability) + backup (microwave radio). Protocol: IEC 60870-5-104 (TCP/IP based) or DNP3. Latency requirement: < 2 seconds for monitoring, < 100ms for protection signals. 3) SCADA Server: Receives data from 1,000+ RTUs, 100,000+ data points, updated every 2-4 seconds. Functions: data acquisition, alarm processing (priority-based, flood suppression), event logging, trending. Redundancy: dual servers in hot-standby. If primary fails, standby takes over in < 2 seconds. 4) EMS Functions (on top of SCADA): State Estimation: compute the 'true' state of the grid from noisy measurements (weighted least squares). AGC (Automatic Generation Control): maintain frequency at 50Hz by adjusting generator output every 4 seconds. Economic Dispatch: minimize generation cost while meeting demand. Contingency Analysis: simulate 'what-if' — if Line X trips, will any other equipment overload? 5) Design Considerations: Availability: 99.99%+ (< 53 min downtime/year). Security: air-gapped networks (SCADA not connected to internet), defense-in-depth, IEC 62351 security. Determinism: real-time OS, guaranteed response times. Cybersecurity is critical — Stuxnet showed SCADA vulnerabilities.

Q3.Explain the Indian electricity market structure and how power trading works on IEX.

India's electricity market has evolved from a state-monopoly model to a competitive market. Structure: 1) Players: Generators (NTPC, private IPPs, solar/wind developers). Transmission: PGCIL (central), state transmission utilities. Distribution: state DISCOMs (MSEDCL, BSES, etc.). Traders and exchanges: IEX, PXIL. Regulators: CERC (central), SERCs (state). 2) Market Segments: a) Long-term: Power Purchase Agreements (PPAs) — 10-25 year contracts between generator and DISCOM. 80% of India's power sold this way. Tariff set by CERC/SERC or discovered through competitive bidding. b) Medium-term: Bilateral contracts (1 month to 5 years). c) Short-term (IEX/PXIL): Day-Ahead Market (DAM): auction-based, trades for next day's 96 time-blocks. Real-Time Market (RTM): introduced 2020, trades every 15 minutes for immediate delivery. Green DAM: separate market for renewable energy. d) Ancillary services: frequency regulation, spinning reserves. 3) IEX Trading Process: Participants deposit margin money (bank guarantee). Bids submitted by 10 AM for next day. Market clearing: uniform price auction (all matched trades at single price per block). Congestion management: if transmission constrained, market splits into zones. Settlement: T+1 (next business day). Average price: ₹3-8/unit depending on time and season. 4) Price Dynamics: Peak (6 PM-10 PM): highest prices — ₹8-15/unit (cooling demand + lighting). Off-peak (2 AM-6 AM): lowest — ₹2-3/unit. Solar hours (10 AM-3 PM): increasingly cheap due to solar supply — 'duck curve' emerging. Monsoon: hydro abundant → lower prices. Summer: cooling demand → higher prices.

Q4.How do you handle Aggregate Technical & Commercial (AT&C) losses in power distribution?

AT&C losses are the power sector's biggest challenge — India loses ~15-20% of electricity between generation and revenue collection. Breakdown: 1) Technical Losses (8-10%): Inherent in transmission and distribution — resistance losses in conductors, transformer core losses. Unavoidable but reducible. Fix: upgrade conductors (ACSR to HTLS), install capacitor banks (power factor correction), reduce transformation stages, use higher voltage distribution (11kV instead of LT). 2) Commercial Losses (10-15%): Theft and billing inefficiency. Types: a) Direct theft: hooking (illegal connection before meter), meter tampering (slowing/stopping meter). b) Billing errors: incorrect meter reading, wrong tariff category, unmetered supply. c) Collection losses: billed but not collected (defaults, political interference). 3) Smart Grid Solution: AMI deployment is the primary tool. Smart meters detect: magnetic tamper (magnet placed near meter to slow it), bypass (wire around meter), reverse current (meter runs backward). Remote disconnect for non-payment. Interval data reveals: consumption during meter-tamper events, unexplained consumption drops. 4) Analytics Approach: Compare: energy input to a feeder (measured at transformer) vs. sum of all consumer meters on that feeder. Difference = losses on that feeder. Drill down: which section? which consumer? ML models flag: consumers whose consumption pattern suddenly dropped, areas with high loss %, transformers with input-output mismatch. 5) Financial Impact: India's DISCOMs lose ₹90,000+ crore annually to AT&C losses. RDSS targets: reduce from ~20% to 12-15%. 1% loss reduction = ₹4,500 crore saved nationally. ROI on smart meters: investment recovered in 3-5 years through loss reduction.

Q5.What are the challenges of integrating renewable energy (solar/wind) into the power grid?

Renewable energy integration is the power sector's most important technology challenge. India targets 500 GW renewable by 2030. Challenges: 1) Intermittency: Solar: available only 6-8 hours/day, varies with cloud cover. A cloud over a 500 MW solar farm can cause 200 MW drop in 5 minutes. Wind: varies seasonally (monsoon = high wind) and hourly. Grid must balance supply-demand every second — frequency must stay at 50Hz ±0.05Hz. 2) Duck Curve: As solar capacity increases, net demand (total demand minus solar) creates a 'duck curve': low during solar hours (10 AM-3 PM), rapid ramp up at sunset (3 PM-7 PM). California saw this first; India now experiencing it. Challenge: need flexible generation (gas turbines, battery, pumped hydro) that can ramp fast to cover the 'neck of the duck'. 3) Forecasting: Must forecast solar/wind generation 1 day ahead for market scheduling. Inputs: satellite imagery (cloud cover), weather models (wind speed, temperature), historical patterns. Accuracy: best models achieve 90-95% for day-ahead. Error has financial penalty (deviation charges). ML models: LSTM networks on historical + weather data. 4) Grid Stability: Solar/wind are inverter-based (no rotating mass) — don't provide inertia like thermal plants. Low inertia → frequency more sensitive to supply-demand imbalance. Solutions: synthetic inertia from inverters (grid-forming inverters), synchronous condensers, battery energy storage (BESS). India mandating grid-forming standards for new renewable plants. 5) Curtailment: Sometimes grid can't absorb all renewable generation (transmission congestion, low demand). Solar/wind curtailed (asked to reduce output) — wasted clean energy. Solution: better forecasting, storage, demand response (shift EV charging to solar hours), green hydrogen production during surplus.

Glossary & Key Terms

SCADA

Supervisory Control and Data Acquisition — system for monitoring and controlling industrial processes like power grids

AMI

Advanced Metering Infrastructure — smart meters with two-way communication for automated reading and control

DISCOM

Distribution Company — entity responsible for last-mile power delivery and billing to consumers

RDSS

Revamped Distribution Sector Scheme — ₹3 lakh crore government scheme for smart metering and distribution reform

AT&C Losses

Aggregate Technical & Commercial Losses — total electricity lost between generation and revenue collection

IEX

Indian Energy Exchange — India's largest power trading platform for day-ahead and real-time markets

MCP

Market Clearing Price — the equilibrium price at which electricity supply meets demand in the exchange

AGC

Automatic Generation Control — system that automatically adjusts generator output to maintain grid frequency at 50Hz

Duck Curve

Net demand pattern showing low midday demand (solar surplus) and steep evening ramp — shaped like a duck

PPA

Power Purchase Agreement — long-term contract between electricity generator and buyer (typically 10-25 years)

RTU

Remote Terminal Unit — field device that interfaces SCADA with physical equipment at substations

FLISR

Fault Location Isolation and Service Restoration — smart grid self-healing capability for automatic outage recovery

NLDC

National Load Dispatch Centre — apex body for real-time grid operation and electricity scheduling in India

Net Metering

Billing mechanism where rooftop solar owners get credit for excess electricity exported to the grid