CEA and DISCOM Requirements for BESS Projects in India

A stage-by-stage guide to connectivity, metering, protection, telemetry, scheduling and evidence requirements for Indian grid-connected BESS projects.

By Madhusudan Chakrapani · Policy & Regulations · 14 minute read

CEA and DISCOM Requirements for BESS Projects in India

There is no single universal BESS approval checklist

An Indian BESS project may interact with the Central Electricity Authority, CERC or a State Commission, CTU or STU, the relevant SLDC or RLDC, the DISCOM, electrical inspectorate, fire authority and contracting agency. The applicable requirements depend on connection point, voltage, ownership, service, state and whether the battery is standalone or co-located.

Use this guide as a requirements map, then verify the current regulations, state grid code, connectivity procedure and tender for the actual project.

1. Connection and system studies

Begin with the proposed point of connection, import and export capacity, fault contribution, transformer arrangement, reactive capability and operating modes. The network licensee may require load-flow, short-circuit, harmonic, dynamic or protection-coordination studies. Assumptions should cover charging as well as discharging; a battery can be both demand and generation at different times.

The CEA connectivity standards establish technical expectations at the grid interface. State-level procedures and utility requirements can add project-specific submissions and study formats.

2. Protection, controls and power quality

Define protection zones, anti-islanding behaviour, breaker control, emergency stop, active and reactive power limits, voltage and frequency response, ramp rate, harmonics and fault ride-through where applicable. Record which function is owned by the BMS, PCS, PPC, plant SCADA or EMS. The control-system comparison provides a responsibility framework.

3. Metering, telemetry and communications

Revenue metering and operational telemetry are different systems even when they observe the same power flow. Confirm meter accuracy class, location, check metering, time blocks, data acquisition, remote visibility, protocol, redundancy and time synchronisation. SLDC or DISCOM telemetry lists should be treated as controlled interface documents.

The CEA communication regulations and applicable grid code inform availability and cyber-security expectations. Utility requirements should specify who owns communication links, gateways, certificates, SIMs or leased lines, and who responds to outages.

4. Scheduling, dispatch and accounting

Clarify whether the battery follows a fixed schedule, dispatch instruction, renewable schedule, ancillary-service signal or commercial optimiser. Define gate closure, revision rules, state-of-charge responsibility, charging-energy accounting, auxiliary consumption and treatment of losses. The dispatch optimisation guide shows how these rules become EMS constraints.

5. Commissioning and continuing compliance

Commissioning evidence should cover equipment certificates, settings, interface tests, protection trips, remote commands, metering comparison, communications loss and restoration, ramp response, usable capacity and efficiency test methods. Continuing obligations can include periodic tests, event reporting, meter calibration, cyber-security controls and availability records.

Build a compliance matrix

Maintain one matrix with the requirement, source document, clause, responsible party, design response, evidence, approver and status. Freeze the applicable document revision at contract award while retaining a process for mandatory regulatory change. This avoids vague statements such as “comply with all CEA requirements” that cannot be tested or priced.

For tender-ready interface and evidence language, continue with the India BESS procurement checklist. For the supervisory platform that captures this evidence, see UrjaEnergyXEMS.

References