Project Megrez, Neneva Gujrat – 250 MW

Executive summary

The Neneva, Gujarat plant is a 250 MW ground-mounted utility asset in Gujarat tracker rows with seasonal dust on moving tables where dust, water scarcity, and array scale broke the manual washing model. Taypro deployed 10 GLYDE automatic robots (~0.04 robots/MW, automatic-only) under CAPEX ownership, implementing tracker-aware GLYDE-X with low robot count per MW and NECTYR accountability. GLYDE-X units are engineered for single-axis tracker geometry—not fixed-table GLYDE paths.

Operations attribute roughly 35 million litres of water saved per year, improved cleaning cadence, about 9.38 GWh of additional clean generation, and 4,650 metric tons CO₂ equivalent with consistent grid factors. This case study is written for owners, O&M leads, and technical advisors evaluating robotic cleaning at utility scale— with statistics, procurement lessons, and internal links to Taypro products and peer deployments.

Validate every litre and MWh with your SCADA before investment committee use. Start with the ROI calculator, then compare peers listed in the statistics and benchmarking sections below.

Site statistics at a glance

Figures are site-reported. Pair with performance methodology and cleaning technology guidance when building acceptance criteria.

Regional soiling and performance ratio economics

Gujarat tracker rows with seasonal dust on moving tables produces fast dust return on module glass. Fine particulate bonds during long dry spells; short rains may rinse some blocks while leaving mud spotting on downwind edges and haul-road-facing strings. At 250 MW, a sustained half-point performance ratio (PR) drift is a material annual MWh event—owners care whether cleaning is programmed, logged, and correlated with recovery, not whether glass looks acceptable from a service road.

Before Taypro, manual programmes struggled with frequency, water logistics, and auditability. Tanker dependence and crew mobilisation across remote tables could not match dust season; supervisors lacked block-level proof when finance asked why generation moved month to month.

Fleet design philosophy at 250 MW

The owner deployed 10 GLYDE-X tracker-aware robots (~0.04 robots/MW) because single-axis tables need stow-aware cleaning logic, not fixed-table paths copied from ground-mount peers. Low robots/MW can still win when tracker rows are long and repeatable and NECTYR proves completion per block group. Explore NYUMA-X / GLYDE-X tracker cleaning and tracker automatic pages.

Low robots/MW does not mean low cleaning intensity—it means coverage is prioritised, not uniform. Model row kilometres and SCADA, not MW alone.

Operations rhythm and accountability

NECTYR provides fleet visibility, cycle scheduling, and alert management. Day supervisors review completion maps, wind holds, and idle trends; scheduled cycles run; faults tier locally with remote support for path exceptions. Weekly meetings tie cleaning KPIs to inverter availability reviews—missed blocks are rescheduled before month-end PR surprises.

Wind holds are mandatory. Brush preventive maintenance follows Taypro intervals. Downwind haul roads and quarry-adjacent strings stay atop the priority queue because soiling arrives there first.

Cleaning cadence: scheduled cycles and weather-aware holds

GLYDE-X tracker robots follow scheduled waterless cycles in block-wise windows aligned with tracker stow and OEM guidance—configured in NECTYR. Automatic rows are scheduled for daily waterless dry-cleaning cycles in NECTYR, with stand-down only when rain, wind limits, tracker stow, or site access rules make a run unnecessary.

NECTYR combines weather forecasts, wind limits, and fleet telemetry. After effective rain, robots often stand down; stow-limited nights are logged separately from wind holds. Each completed run is a dual-pass waterless cycle per performance methodology.

Commissioning and handover

Commissioning sequenced the dustiest blocks first, validated end-of-row turns, cable zones, and inverter-yard proximity, and placed parking or charging to limit deadhead time. Technicians trained on waterless brush compliance, fault codes, and hold rules before vendor demobilisation. Handover included path maps, escalation contacts, and spare thresholds sized for local dust abrasiveness.

Robotics entered the standing O&M calendar beside vegetation control and thermography—not as a one-off retrofit.

Water economics and OPEX narrative

Reported 35 million litres per year avoided versus wet-wash baselines removes tanker convoys, runoff handling, and conflicts between washing and electrical maintenance. Dry night brushing avoids thermal shock from midday sprays. Finance should pair water savings with labour stability and attributed GWh—not water alone.

For managed-service commercial models (different from CAPEX), see solar panel cleaning service.

Generation, carbon, and finance stress tests

Site-reported uplift is 9.38 GWh with 4,650 metric tons CO₂ equivalent. Stress-test at 50% and 75% GWh attribution in your model—if robotics still clears hurdle rate, the business case is robust. Dividing GWh by 250 MW nameplate illustrates intensity but does not replace curtailment-aware SCADA attribution.

ESG reviewers use water and carbon figures alongside O&M logs; lenders ask for proof cleaning happened—NECTYR exports answer that question.

Peer benchmarking within Taypro case studies

Versus Bachau DVC (300 MW ground mount, 172 GLYDE): ground-mount automatic density reference.

Versus SECI-2 (200 MW mixed fleet): mixed-mode comparison on non-tracker tables.

Versus Agar (200 MW mixed GLYDE/NYUMA): higher robots/MW on fixed tables.

Browse all projects, automatic, semi-automatic, and CAPEX galleries to filter by mode and procurement.

SCADA correlation and root-cause discipline

String-level trends often flag soiling before visual walks. Pair inverter snapshots with block completion timestamps (from NECTYR). If a block was logged clean and PR remains soft, investigate brush wear, partial coverage, or equipment faults—not default “soiling anyway” explanations.

That discipline protects robotics budgets during annual reviews.

Monthly seasonal calendar

Jan–Feb: review brush wear and cycle plans after winter dryness; validate wind and rain hold rules in NECTYR or inspection logs. Mar–Jun: peak dust—cadence stays daily for automatic rows, while NECTYR applies weather-aware holds after effective rain, unsafe wind, tracker stow, or site access restrictions. Monsoon transition: stand down or lighten cycles after effective rain; inspection-heavy weeks when nature rinses glass. Post-monsoon: re-walk paths after vegetation or civil works; update block timers before the next approved cleaning window.

Spares, training, and lifecycle cost

Brush sets and drive components dominate lifecycle cost. Size spares for March–June peaks. Training includes shadow nights, fault trees, and escalation paths to Taypro support. Turnover plans matter—especially when a small automatic fleet must still cover the full table through prioritisation.

Technology, safety, and warranty alignment

Waterless cleaning requires brush materials, traverse speeds, and hold logic aligned with OEM warranty guidance—see cleaning technology. Safety covers night traffic near inverter yards and lockout coordination; robots do not run parallel to energized maintenance in the same block.

Procurement checklist

Request row repeatability maps, robots/MW justification, night-window hours, monitoring exports (NECTYR samples), and spare lead times. Legal reviewers should see hold logs and completion evidence before CAPEX approval.

Who should use this site as a benchmark?

Owners with large tracker assets, automatic-ready rows, and dashboard accountability—not rooftop-only sites without portables planning.

Is ~0.04 robots/MW enough?

Only if SCADA and row maps prove it. Compare peers on this page before copying brochure density.

CAPEX vs Opex service?

This deployment is CAPEX. Evaluate Opex service separately if you want managed operations with different commercial terms.

How do reported statistics translate to ESG slides?

Use 35 million litres and 4,650 tCO₂e with the same 9.38 GWh assumptions auditors review—do not mix inconsistent grid factors.

Vegetation, civil works, and path governance

Treat path maps as controlled documents when civil or vegetation contractors work near rows. Update schedules before approved cleaning windows after geometry changes—prevents ghost cleans and wasted cleaning windows on 250 MW tables.

Curtailment, heat, and night-first discipline

Night-first cleaning keeps technicians off modules during peak radiation and aligns with OEM cleaning guidance. When export limits compress hours, prioritise downwind and high marginal MWh blocks; document grid-limited skips separately from wind holds.

Insurer and lender evidence pack

Include training records, completion evidence, wind hold policies, and spare planning. NECTYR timestamp exports demonstrate cleaning discipline beyond verbal assurance.

Ten-year O&M horizon

Plan brush refresh, drive inspections, and firmware governance for schedules. Capital plans should reserve refresh tranches; completion history shows which assets retire first.

Utility operations integration

Align robotics with vegetation windows, thermal scans, and grid events—see utility operations framing. Cleaning competes for calm nights; publish calendars so electrical and robotic teams do not conflict.

Tracker rows demand GLYDE-X—not ground-mount logic copied sideways

Neneva is a 250 MW Gujarat plant where ten GLYDE-X tracker-aware robots (~0.04 robots/MW) clean single-axis tables with stow-aware logic. Ground-mount peers like Bachau DVC scale very different paths; comparing robot counts without tracker context misleads procurement committees.

GLYDE-X aligns with single-axis automatic cleaning and NYUMA-X tracker product narratives—low machine count can still win when row length and tracker repeatability are high and NECTYR proves completion.

NECTYR on a low-density tracker fleet

With only ten machines, idle minutes and missed blocks are visible immediately in NECTYR. Supervisors treat each robot as high-value capital: wind holds, brush wear, and stow conflicts are escalated fast. Weekly KPI reviews include blocks completed per night and repeat fault codes per tracker block group.

Water and generation at 250 MW tracker scale

Reported 35 million litres avoided, 9.38 GWh, and 4,650 tCO₂e should be validated against tracker-specific PR baselines—stow seasons and tracker availability belong in the same narrative as soiling recovery.

Benchmarking against mixed and ground-mount peers

SECI-2’s mixed 179-robot fleet and Agar’s 272-robot mixed ground-mount programme illustrate higher robots/MW on fixed tables. Neneva illustrates the opposite problem statement: make a small tracker fleet accountable with telematics and disciplined scheduled windows.

Commissioning tracker cleaning safely

Acceptance includes stow interlocks, tracker manufacturer cleaning guidance, and night traffic plans near inverter yards. Training covers tracker-specific fault trees—not only ground-mount habits ported from other sites.

Finance and ESG reviewers

Stress-test GWh at half attribution; include consumables and training in CAPEX models. Link utility operations calendars so tracker O&M and cleaning do not collide during export-limited nights.

Stow-aware cleaning windows on single-axis tables

Tracker plants introduce stow conflicts that ground-mount peers ignore. GLYDE-X schedules must align with tracker OEM guidance and scheduled cleaning windows where stow positions permit safe brush contact. NECTYR should log stow holds separately from wind holds so month-end reviews stay honest.

Owners comparing ground-mount automatic density must normalize for tracker availability and stow seasonality in the same SCADA narrative as soiling recovery.

Why ten machines still demand enterprise discipline

Low robot count raises the cost of every idle hour. Supervisors run weekly KPI reviews on completion and faults; spares are pre-positioned before March–June; training includes tracker-specific fault trees. Treat each GLYDE-X unit as high-value capital—not a pilot toy.

Finance stress tests for 9.38 GWh

Model 9.38 GWh at 50% and 75% attribution; include consumables and stow-related downtime. Link outcomes to calculator inputs only after local PR baselines are agreed.

Tracker OEM coordination meetings

GLYDE-X programmes require tracker OEM alignment on stow, cleaning windows, and warranty language—co-signed acceptance criteria, not robot vendor alone.

Seasonal stow and cleaning interplay

Stow seasons compress windows; document stow-limited nights separately from wind holds in NECTYR.

Ten-machine spare strategy

Pre-position brushes and drive spares before March–June; one idle GLYDE-X during peak season has outsized MWh impact on long tracker rows.

Tracker cleaning economics on 250 MW

GLYDE-X economics differ from ground-mount GLYDE: stow rules, tracker availability, and row length dominate—not MW alone. Ten robots (~0.04/MW) can be sufficient when NECTYR proves completion and idle minutes stay controlled through dust season.

Finance should model 9.38 GWh at 50–75% attribution with stow downtime explicit. Insurers need night plans and training records alongside water and carbon statistics (35 million litres, 4,650 tCO₂e).

Coordination with tracker O&M

Tracker mechanical O&M and cleaning O&M must share calendars. Stow conflicts are not robot faults—log them separately. OEM meetings should occur before commissioning sign-off, not after PR drift appears.

Benchmarking discipline

Compare Bachau ground-mount and SECI-2 mixed only after normalizing for tracker variables. Use NYUMA-X / GLYDE-X pages for spacing reviews.

KPI reviews for low-density fleets

Weekly: blocks completed, idle minutes, stow holds, wind holds, repeat faults. Monthly: brush spend versus plan. Quarterly: path updates after civil works.

Extended operations FAQ

Why only ten GLYDE-X robots?

Tracker row length and NECTYR accountability can make low robots/MW viable—compare only with tracker-normalised PR baselines.

How are stow holds logged?

Separately from wind holds in NECTYR so month-end reviews stay honest.

Tracker fleet discipline at low robots/MW

Ten GLYDE-X machines demand stow-aware schedules, OEM coordination, and NECTYR hold logs separated from wind events. Normalize ROI against tracker availability, not ground-mount peers.

Stow-limited nights versus wind holds

Tracker programmes must log stow-limited nights separately from wind holds in NECTYR so month-end reviews stay honest. Finance should model 9.38 GWh with explicit stow downtime, not ground-mount availability assumptions.

OEM coordination and warranty language

GLYDE-X acceptance requires tracker OEM alignment on stow, cleaning windows, and warranty language—co-signed criteria, not robot vendor alone. Training includes tracker fault trees, not ground-mount habits ported from other sites.

Ten-machine fleet economics

With ~0.04 robots/MW, each idle hour during March–June has outsized MWh impact on long tracker rows. Pre-position brushes and drives before dust season; weekly KPI reviews on completion and faults are mandatory at this density.

Peer normalization for procurement

Compare Bachau ground-mount automatic and Agar mixed only after normalizing for tracker stow and row length—not MW alone.

Export-limited nights and tracker O&M

Link utility operations calendars so tracker O&M, stow events, and cleaning windows do not collide during export-limited nights. Document curtailment skips separately from wind and stow holds.

Tracker seasonality in board reviews

Board slides should separate stow-limited nights, wind holds, and curtailment skips when discussing cleaning KPIs. Tracker availability belongs beside soiling recovery in the same narrative as 9.38 GWh scenarios.

GLYDE-X lifecycle planning

Ten GLYDE-X machines require enterprise-grade spare strategy: brushes, drives, and stow-related downtime explicit in ten-year models. Compare ground-mount peers only after normalizing tracker row length and stow rules.

Tracker cleaning audit narrative

Audit packs should separate stow holds, wind holds, and curtailment skips; include OEM co-signed acceptance criteria and sample NECTYR weeks. Model 35 million litres, 9.38 GWh, and 4,650 tCO₂e with tracker-normalised PR—not ground-mount peers.

Ten GLYDE-X machines require pre-positioned spares before dust season; one idle tracker row week costs outsized MWh on long tables.

Neneva tracker audit addendum

Audit addendum: stow-hold log separate from wind-hold log, OEM co-signed cleaning acceptance, sample NECTYR week, and tracker-normalised GWh stress tests for 9.38 GWh.

Pre-position GLYDE-X spares before dust season; document curtailment skips separately from weather holds in board slides.

Neneva tracker programme charter

Charter assigns OEM liaison, stow-hold logging separate from wind, curtailment-skip documentation, quarterly GLYDE-X spare review, and tracker-normalised GWh workshops for 9.38 GWh.

Ten GLYDE-X machines at ~0.04 robots/MW require weekly completion and fault review—low count raises cost per idle hour on long tracker rows during March–June.

Insurer pack includes night traffic plans, training attendance, and sample NECTYR week with 35 million litres and 4,650 tCO₂e on assumptions matching GWh slides.

Compare Bachau ground-mount only after normalising stow and row length—not MW totals.

Neneva stow-season operating brief

Stow seasons compress cleaning windows—document stow-limited nights, wind holds, and curtailment skips in separate NECTYR or board categories. Finance must model 9.38 GWh with tracker availability explicit.

Quarterly OEM briefings cover brush materials, stow positions, and warranty cleaning language co-signed with tracker vendor. Ten GLYDE-X units are high-value assets: weekly fault review, spare pre-positioning, and night traffic plans near inverter yards.

Insurer and lender packs should include training attendance, sample NECTYR week, and 35 million litres / 4,650 tCO₂e aligned with GWh assumptions—not ground-mount peer slides without stow normalization.

Neneva annual tracker review pack

Annual pack separates stow, wind, and curtailment categories; includes OEM meeting minutes, GLYDE-X spare log, sample NECTYR week, and tracker-normalised 9.38 GWh workshops.

Ten-machine fleets require weekly executive review of completion and faults—document idle hours during March–June and tie to downwind tracker block PR recovery.

Lenders receive 35 million litres, 4,650 tCO₂e, and GWh scenarios on assumptions matching board slides—not ground-mount copies without stow normalization.

Neneva lender refresh paragraph

Refresh attaches stow-hold category summary, OEM meeting minutes, sample NECTYR week, and tracker-normalised 9.38 GWh scenarios with 35 million litres and 4,650 tCO₂e aligned—never ground-mount peer slides without stow normalization.

Neneva operations closing standards

Closing standards separate stow holds, wind holds, and curtailment skips; require quarterly OEM sync on brush and stow rules; mandate weekly GLYDE-X completion review for ten machines at ~0.04 robots/MW.

Finance workshops model 9.38 GWh with tracker availability and stow downtime explicit. Insurer packs include night traffic plans, training logs, and sample NECTYR weeks with 35 million litres and 4,650 tCO₂e aligned to GWh slides.

Procurement committees must not copy ground-mount robot density from Bachau or Agar without stow normalization and row-length context.

Neneva sign-off

Sign-off requires stow-hold category summary, OEM co-signed acceptance, and tracker-normalised GWh workshop before lender refresh.

Operations evidence summary

Owners should validate reported water, generation, and carbon statistics with local SCADA and tariffs; pair this case study with performance methodology, the projects hub, and the ROI calculator when building procurement packs. Scheduled cycles and weather-aware holds—not plant-wide daily washing—define Taypro utility programmes on this site.

Validate block-level cleaning evidence, conservative GWh attribution, and peer benchmarks on the projects hub before investment committee sign-off.

Validate block-level cleaning evidence, conservative GWh attribution, and peer benchmarks on the projects hub before investment committee sign-off.

Validate block-level cleaning evidence, conservative GWh attribution, and peer benchmarks on the projects hub before investment committee sign-off.

Validate block-level cleaning evidence, conservative GWh attribution, and peer benchmarks on the projects hub before investment committee sign-off.

Validate block-level cleaning evidence, conservative GWh attribution, and peer benchmarks on the projects hub before investment committee sign-off.

Validate block-level cleaning evidence, conservative GWh attribution, and peer benchmarks on the projects hub before investment committee sign-off.

Validate block-level cleaning evidence, conservative GWh attribution, and peer benchmarks on the projects hub before investment committee sign-off.

Conclusion

This 250 MW Gujarat case study shows tracker-aware GLYDE-X with low robot count per MW and NECTYR accountability: 10 robots, Semi-automatic (tracker-aware automatic units), CAPEX ownership, and reported outcomes of 35 million litres water saved, 9.38 GWh, and 4,650 tCO₂e. Validate with your data; use the projects hub, calculator, and peer links above when building procurement packs.