A renewable-energy developer had already shortlisted land, spoken with battery suppliers and collected quotations for a large Battery Energy Storage System. On paper, the project looked ready. The batteries were available, the Power Conversion System could be procured, and several EPC companies were willing to quote.
Then the real questions started.
Where exactly would the project connect to the grid? What would be the required MW and MWh configuration? Would the system operate for 2 hours or 4 hours? Who would guarantee usable energy after degradation? Who would be responsible for the EMS integration? Would augmentation be included in the original CAPEX? What testing would be required before grid charging? And most importantly, was the project being designed around its business use case, or was equipment being purchased first and the commercial model being worked out later?
This is where many grid-scale BESS projects become complicated.
A Battery Energy Storage System is not simply a collection of battery containers. A utility-scale project combines batteries, BMS, PCS, EMS, transformers, switchgear, SCADA, grid connectivity, civil infrastructure, protection systems, safety systems and commercial performance guarantees into one integrated power asset.
For developers planning a grid-scale BESS project in India, procurement is only one stage. The complete roadmap begins with defining the use case and continues through feasibility, grid studies, DPR preparation, engineering, tendering, procurement, construction, integration, testing and final commissioning.
India’s electricity system is also moving toward significantly larger energy-storage deployment. National planning estimates have indicated BESS requirements rising from around 34.72 GWh by 2026-27 to more than 236 GWh by 2031-32. Projects are now being structured in hundreds of MW and several hundred to several thousand MWh, making proper project planning increasingly important.
A grid-scale Battery Energy Storage System stores electricity when power is available and discharges it when required by the grid, utility, renewable-energy project or electricity market.
Two numbers are especially important.
MW represents power. It tells you how quickly the battery can charge or discharge.
MWh represents energy. It tells you how much electricity the battery can store.
For example:
This difference changes almost every part of the project, including battery quantity, land requirement, CAPEX, operating strategy, revenue model, degradation profile and augmentation requirement.
A 100 MW / 400 MWh system is not simply a larger version of a 100 MW / 200 MWh plant. It is effectively a different commercial and technical project.
The first decision should not be which battery supplier to approach.
The first decision should be why the storage system is being developed.
A grid-scale BESS may be designed for renewable-energy shifting, peak-power management, capacity support, grid balancing, ancillary services, frequency response, energy arbitrage or a combination of several services.
The operating requirement determines the equipment specification.
For example, a battery required mainly for short-duration grid response may have a very different duty cycle from a project expected to discharge continuously for 4 hours every evening.
Before issuing an RFQ, the developer should define:
If these inputs are unclear, vendor quotations may appear competitive but may not actually be comparable.
One of the most common mistakes in early BESS planning is focusing only on MW.
Suppose a developer wants a 100 MW project.
That information alone is insufficient.
A 100 MW / 200 MWh BESS can theoretically discharge at full rated power for approximately 2 hours. A 100 MW / 400 MWh project can theoretically provide the same power for approximately 4 hours.
That additional 200 MWh affects battery containers, DC architecture, HVAC requirements, auxiliary consumption, land, cables, protection systems and capital investment.
The developer must also distinguish between nameplate energy and guaranteed usable energy.
Battery degradation means the available energy changes over the project life. Therefore, procurement documents should clearly define whether the supplier must guarantee required usable MWh at commissioning, after 5 years, after 10 years or throughout the contractual period.
Consider a simple numerical example.
If a project requires 400 MWh usable energy, a 5% shortfall equals:
400 MWh x 5% = 20 MWh
On a grid-scale project, a 20 MWh difference is commercially significant.
This is why energy guarantees must be addressed at the procurement stage rather than after installation.
A technically good BESS project can still become commercially weak if it is developed at the wrong location.
Site selection should therefore happen alongside grid analysis.
The developer should study distance from the proposed substation, available evacuation capacity, voltage level, transmission availability, access roads, land topography, drainage, flooding risk, ambient temperature and room for future augmentation.
Grid connectivity can become a major project dependency.
A site located 2 km from a suitable substation may have very different economics from a site requiring a new evacuation line of 15 or 20 km.
Land should also be evaluated from a safety perspective. Container spacing, transformer placement, emergency vehicle access, internal roads, drainage and fire separation need to be considered early.
The cheapest parcel of land is not necessarily the lowest-cost BESS location.
Once the broad project configuration and location are understood, the developer should prepare a proper feasibility assessment and Detailed Project Report.
The DPR should connect the technical system with the commercial model.
A good BESS DPR should address project capacity, storage duration, expected operating cycles, site conditions, grid connectivity, technology configuration, major equipment, project CAPEX, OPEX, degradation assumptions, augmentation strategy, revenue model and financial sensitivity.
For example, consider a 100 MW / 400 MWh BESS operating one theoretical full discharge cycle every day.
Annual theoretical energy discharged would be:
400 MWh x 365 days = 146,000 MWh or 146 GWh
Actual output would be lower because of SOC limits, efficiency losses, auxiliary loads, downtime and degradation.
But this simple calculation demonstrates why assumptions about cycling materially affect project economics.
The DPR should therefore not use only one optimistic revenue assumption. It should test different operating conditions and performance outcomes.
Procurement should begin only after the project has a reasonably defined technical architecture.
At this stage, the engineering team normally develops the preliminary Single Line Diagram, battery block configuration, PCS arrangement, transformer sizing, MV collection system, switchyard arrangement, auxiliary power system and communication architecture.
The interaction between the major systems should be defined clearly:
Battery cells and racks -> BMS -> PCS -> EMS -> SCADA -> Transformer -> Switchyard -> Grid
Each interface matters.
For example, the Battery Management System may correctly monitor the battery while the Energy Management System is unable to execute dispatch commands properly. The PCS may perform correctly individually but may not communicate with the plant controller as expected.
BESS is therefore an integration project as much as it is a battery project.
The procurement specification is one of the most important documents in the entire project.
A weak specification transfers ambiguity into the contract.
Instead of asking suppliers simply to quote “100 MW BESS”, the tender should define exactly what the developer expects at the point of delivery and operation.
Important parameters normally include required MW, required MWh, usable energy, interconnection point, storage duration, operating SOC range, number of cycles, system availability, round-trip efficiency, degradation guarantee, design life, auxiliary consumption, battery chemistry, PCS performance, EMS functions and warranty.
The procurement package should also address augmentation.
If a project must continue delivering 400 MWh after several years, additional battery capacity may eventually be required.
The contract must clarify who is responsible for this future addition.
Otherwise, an apparently cheaper bid can become more expensive over the project life.
Price comparison alone is not enough.
BESS suppliers should be evaluated on technology, manufacturing capability, operating references, warranty strength, safety credentials and long-term support.
Important areas for evaluation include battery-cell manufacturer, cell chemistry, rack architecture, container design, BMS capability, PCS supplier, EMS platform, thermal management and fire detection systems.
The developer should also review actual operating references.
A supplier with experience in several hundred MWh of grid-scale projects may carry a different project risk profile from a company whose experience is mainly behind-the-meter storage.
Warranty language requires particular attention.
A 10-year warranty sounds attractive, but the value of that warranty depends on what exactly is guaranteed.
Is the warranty based on years, cycles, energy throughput, remaining capacity, operating temperature or combinations of these parameters?
The contract must align the warranty with the intended operating profile.
There is no single procurement structure suitable for every BESS project.
Some developers prefer a complete EPC contract. Others separate battery supply, PCS, balance of plant, switchyard and civil works.
A typical utility-scale project may involve packages for:
Splitting packages can increase purchasing flexibility but also creates additional interface risk.
For example, if the battery supplier, PCS vendor and EMS provider are three different companies, the EPC contract must make it clear who owns overall system integration.
Otherwise, technical problems may result in each supplier stating that its individual equipment is functioning correctly while the complete plant still cannot operate as required.
Regulatory planning should run in parallel with engineering.
The exact approval framework depends on the project location, connection voltage, land status, project ownership structure and whether the BESS is standalone or integrated with another generation project.
Depending on the project, coordination may involve CEA requirements, CTUIL or STU connectivity, SLDC or RLDC requirements, electrical inspector or CEIG approvals, metering arrangements, protection approval, fire-safety requirements and local development permissions.
Environmental approvals should be reviewed project by project rather than assumed.
A BESS project should not automatically be described as requiring the same CTE, CTO or environmental authorization package as a manufacturing or recycling plant. Applicability needs to be evaluated against the actual facility, activities and state-level requirements.
Battery Waste Management compliance may also become relevant depending on the role of the project company and how batteries are procured, managed and ultimately handled at end of life.
After vendor selection, detailed engineering begins.
At this point, preliminary drawings become construction documents.
The engineering package may include detailed SLDs, protection philosophy, cable schedules, earthing design, structural drawings, foundation design, drainage, equipment layout, communication architecture and SCADA mapping.
At the same time, major equipment enters manufacturing.
Long-lead items require close monitoring because a delay in one component can hold up the entire commissioning programme.
A project with all battery containers delivered but no power transformers cannot be commissioned.
Similarly, a completed switchyard has limited value if PCS equipment is delayed.
The project schedule should therefore follow critical-path logic rather than simply tracking equipment purchase orders.
Factory Acceptance Testing should be completed before critical equipment is dispatched.
FAT requirements may differ for battery systems, PCS, transformers, switchgear and control systems.
The objective is to identify problems before equipment reaches site.
Testing may review electrical performance, communication, protection logic, control functions, alarms, emergency shutdown behaviour and documentation.
Correcting a problem in a factory can be far easier than correcting it after dozens of containers have been installed hundreds of kilometres away.
Site construction can progress while equipment is being manufactured.
Civil works normally include site development, foundations, internal roads, drainage, cable trenches, control buildings, switchyard works and equipment pads.
After civil readiness, battery containers, PCS blocks, transformers and electrical equipment are installed.
The sequence matters.
Heavy equipment movement should be coordinated with roads and crane access. Cable trenches should be completed before extensive cabling begins. Earthing should be implemented according to the approved design rather than retrofitted later.
Poor construction sequencing can add weeks or months to commissioning.
This is often where the project moves from equipment installation to actual power-system engineering.
The BMS must communicate with the PCS. The PCS must follow commands from the EMS. The EMS must communicate with plant SCADA. Protection systems must coordinate with the switchyard. Metering must communicate correctly with relevant systems.
A communication failure in one interface can prevent the entire plant from dispatching electricity.
Integration testing should therefore cover both normal operation and abnormal conditions.
For example, the system should be tested for loss of communication, emergency shutdown, PCS trip, high battery temperature, abnormal SOC condition and grid disturbance behaviour.
Before grid charging, individual systems should be verified.
Typical activities include cable testing, insulation testing, protection checks, transformer testing, earthing verification, communication tests, interlock testing and emergency-response checks.
The project then progresses toward controlled energisation.
Performance testing may verify:
Availability deserves careful attention.
The difference between 95% and 98% annual availability appears small, but across 8,760 hours in a year the 3% difference represents approximately:
8,760 x 3% = 263 hours
For a 100 MW project, that difference can materially affect the amount of time the asset is commercially available.
Grid charging is not simply switching on the plant.
The project must demonstrate that electrical systems, protection schemes, control systems and battery equipment can operate safely together.
Testing normally progresses in stages.
The transformer and electrical network may be energised first. PCS systems are then commissioned. Battery blocks are brought online progressively. Communication with EMS and SCADA is verified before full-capacity tests are attempted.
Once required performance tests and contractual conditions are successfully completed, the project can move toward commercial operation.
The exact notice periods, test requirements and commissioning documentation depend on the applicable tender, contract, grid authority and project structure.
They should therefore be established in the project schedule from the beginning instead of being discovered during the final weeks.
Consider an illustrative developer planning a 100 MW / 400 MWh standalone BESS near a major substation.
The original plan was to approach battery vendors immediately because the developer already knew the desired power capacity.
During feasibility assessment, however, the project team discovered that several decisions had not been frozen.
The project initially assumed 2-hour storage, but the expected commercial requirement actually pointed toward 4-hour discharge capability.
That changed the project from approximately 200 MWh to 400 MWh.
The developer also found that the lowest-cost land parcel required significantly more evacuation infrastructure than another site located closer to the proposed point of interconnection.
The second site had a higher land cost but offered a potentially simpler electrical connection.
The procurement specification was then developed around 100 MW / 400 MWh usable performance rather than simply “100 MW battery storage”.
The tender separately addressed degradation, availability, augmentation, auxiliary consumption, EMS integration and performance testing.
This changed vendor comparison significantly.
One quotation appeared around 8% cheaper at initial procurement stage, but augmentation responsibility was excluded. Another bid included defined long-term energy-performance obligations.
The project evaluation therefore moved from comparing purchase price to comparing life-cycle performance.
That is the fundamental difference between equipment procurement and BESS project development.
Several project problems can be prevented during the feasibility and procurement stages.
Developers should avoid issuing a battery RFQ before the duty cycle and grid connection philosophy are understood. MW capacity should never be evaluated without MWh capacity. Degradation and augmentation should be commercial decisions, not afterthoughts.
Other common issues include unclear EMS responsibility, incomplete fire and emergency planning, weak interface definitions between battery and PCS suppliers, inadequate FAT requirements and unrealistic project schedules.
A project can purchase excellent equipment and still face commissioning delays if system integration is not properly managed.
Before issuing the main procurement package, the project team should ideally have clarity on:
If several of these inputs remain unresolved, procurement may be premature.
Commissioning does not complete the BESS life cycle.
Once operational, the project must monitor State of Health, State of Charge, temperature, alarms, availability, auxiliary consumption and energy performance.
Battery degradation also needs to be tracked against supplier guarantees.
If augmentation is planned, the owner must know when additional battery blocks should be introduced and how new equipment will integrate with the existing system.
Cybersecurity and software management are also becoming increasingly important because modern BESS plants depend heavily on digital control systems and remote communication.
Finally, end-of-life batteries require an appropriate compliance and recycling pathway.
A project designed for 15 or 20 years should consider these responsibilities during development rather than waiting until the original battery system reaches the end of its useful life.
Grid-scale BESS development is moving rapidly from pilot-scale activity toward large infrastructure projects.
A 100 MW, 250 MW or 500 MW storage project involves much more than choosing battery chemistry and negotiating equipment prices.
The commercial model affects the technical configuration. The grid connection affects the site. The site affects the layout. The duty cycle affects degradation. Degradation affects augmentation. Augmentation affects CAPEX. Procurement conditions affect long-term performance. And all of these decisions eventually affect commissioning and project returns.
The most successful development approach is therefore sequential but integrated:
Use case -> Feasibility -> Site and grid -> DPR -> Engineering -> Procurement -> Approvals -> Manufacturing -> Construction -> Integration -> Testing -> Commissioning -> O&M
When these stages are planned as one project rather than separate activities, developers are in a much stronger position to control cost, schedule and performance risk.
Green Permits supports developers and investors with BESS project feasibility studies, DPR preparation, site and approval assessment, project planning and implementation advisory for renewable-energy and storage projects in India.
📞 +91 78350 06182
📧 wecare@greenpermits.in
🌐 www.greenpermits.in
👉 Book a Consultation with Green Permits
