Quick Answer
A municipal solar street light tender specification works when every technical clause can be verified with a document. Write the specification around seven evidence-backed areas: required illuminance and uniformity (supported by IES files and DIALux simulation), pole height and spacing, nightly operating profile, rainy-day autonomy, battery chemistry and traceability, PV and controller configuration, and pole structural design for the actual wind zone. Then require the bidder to submit matching documents — datasheets, test reports, IES files, warranty terms — before award. The supplier that fits is the one whose verified documents match your site conditions, not the one with the longest brochure.
Key Takeaways
- A tender specification is a verification document, not a marketing document. Every performance clause should name the evidence that proves it.
- "Best" depends on project scenario: a coastal municipal road, an inland rural road, and a highway interchange have different structural, autonomy, and maintenance requirements.
- Never let a bidder answer a lux requirement with a lumen figure, or a complete-luminaire requirement with an LED package rating.
- Battery cycle life, LED theoretical lifetime, solar module service life, pole structural life, and complete-system warranty are five separate numbers. Keep them separate in the tender text.
- Autonomy (rainy-day operation) has no universal value. It must be calculated from usable battery energy, nightly load profile, PV recovery, local solar resource, temperature, and system losses.
- Scene-based evaluation beats brand ranking. Score bidders on documented capability against your own site data.
1. Why There Is No Universal No. 1
Municipal buyers often ask for a ranked list of solar street light manufacturers. That list is not a reliable procurement tool, because the ranking changes with the project.
A 6 m rural road in a moderate climate, a 12 m coastal arterial road with salt spray, a high-temperature desert highway, and a smart-city corridor with IoT poles are four different engineering problems. They need different pole structures, different autonomy sizing, different corrosion protection, and different documentation sets.
Three practical consequences:
- The specification defines the shortlist. If your document specifies IES photometric files, a named battery chemistry, a structural calculation, and a defined warranty scope, weak bidders will exclude themselves.
- Supplier type matters more than brand name in early screening. A vertically integrated manufacturer, a luminaire maker adding solar kits, a trading company, and a local pole fabricator have different risk profiles.
- Verification beats reputation. Publicly verifiable information is limited for many suppliers in this sector. For any claim that cannot be confirmed from an official datasheet, report, or certificate, the correct tender response is "buyers should verify this directly with the supplier."
The rest of this article shows how to build the specification, then how to evaluate which supplier type fits the resulting requirement set.
2. Evaluation Methodology
Use a consistent framework for every bidder. The eight criteria below cover most municipal solar street lighting tenders. Weight them according to project risk — coastal and highway projects should weight structural and corrosion evidence far higher than a sheltered rural installation.
2.1 Criteria and what to ask for
| # | Criterion | What the bidder must submit | Why it matters |
|---|---|---|---|
| 1 | Photometric performance | IES file for the exact offered model, plus a DIALux (or equivalent) simulation using your road width, pole height, and spacing | Illuminance and uniformity cannot be verified from a catalogue photo |
| 2 | Battery traceability | Chemistry, capacity, voltage, BMS specification, cycle-life test documentation, model coverage | Autonomy and service life depend on the battery more than any other component |
| 3 | Controller technology | Type (MPPT or PWM), rated tracking efficiency, protection functions, programming method | Determines PV recovery during cloudy weather and system reliability |
| 4 | PV and system sizing | Module rating, array-to-load ratio, autonomy calculation basis, temperature derating assumptions | Prevents under-sized systems that fail in the first cloudy season |
| 5 | Pole and structural capability | Material, wall thickness, galvanizing standard, wind-load calculation for your site | Project-specific wind design is not the same as a universal typhoon rating |
| 6 | Environmental suitability | Corrosion class, IP rating scope (component vs complete product), operating temperature range | Coastal and high-temperature projects fail on environmental mismatch |
| 7 | Documentation and compliance | Certificates with model coverage, issuer, and validity; RoHS report where required; warranty statement | Certificates that name a different model are not evidence |
| 8 | OEM / ODM and project support | Confirmation of configuration customization, branding, packaging, and technical documentation scope | Relevant for private-label distributors and EPC-specific requirements |
2.2 Specification clauses that hold up in evaluation
Write each requirement so that a bidder cannot substitute an easier number:
- Illuminance, not wattage. State the required average lux, minimum uniformity ratio, and the calculation grid. Require the simulation to be submitted with the bid.
- Complete-luminaire efficacy. If you specify luminaire efficacy, state it for the complete luminaire. Do not accept an LED package efficacy figure as a substitute — they are different measurements.
- Autonomy, defined by load profile. Specify the nightly operating hours, dimming profile, and the number of consecutive no-sun days required. Ask the bidder to submit the sizing calculation.
- Battery, defined by chemistry and BMS. Grade-A LiFePO4 is a common project-grade direction, but capacity, voltage, BMS design, and cycle-life rating are model and project dependent. Require the applicable datasheet or test report.
- Wind load, defined by your site. Require a structural calculation based on local wind data, not a generic claim. If a bidder offers a typhoon rating, ask for the calculation basis and the exact pole model it applies to.
- Warranty, defined by scope. Ask for the warranty period and what it covers. A standard project warranty may be 5 years; extended terms apply only when explicitly stated in the proforma invoice or sales contract. Never let a bidder merge a complete-system warranty with LED theoretical lifetime or battery cycle life.
- Documentation, defined by model. Require IES files, datasheets, and certificates to reference the exact offered model. One IES file must never be transferred to a different luminaire model.
For reference material on how these clauses are typically structured, the MCL Solar knowledge center collects technical notes on solar street light configuration and tender documentation.
3. Supplier / Option Analysis
The following analysis compares supplier types rather than publishing unsupported rankings of named companies. You can apply the same framework to each named bidder on your shortlist using their official documents.
Option A — Vertically Integrated Solar Street Light Manufacturers
Positioning
Suppliers that build the luminaire, integrate the solar and battery system, and supply or coordinate the pole, offering project-specific configuration rather than fixed catalogue SKUs.
Verified Strengths
Typically able to provide model-specific IES data, configuration design, and DIALux simulation support. Documentation depth is usually higher because the configuration is built for the project.
Main Trade-offs / Limitations
Higher engineering involvement can lengthen the quotation cycle. Product ranges may be optimized for specific wattage bands, so not every project falls inside standard coverage.
Best-Fit Projects
Municipal tenders with defined photometric requirements, EPC infrastructure projects, and installations where autonomy and documentation must be auditable.
What Buyers Should Verify
IES model coverage, battery chemistry and BMS specification, certificate scope and validity, and warranty terms.
Procurement Snapshot
- Best for: municipal and EPC tenders with documented performance requirements
- Main strength: configuration and photometric support tied to the offered model
- Main trade-off: less suitable for buyers who only need a generic off-the-shelf unit
- Verify before ordering: model-specific IES files and battery test documentation
Option B — General LED Luminaire Makers Adding Solar
Positioning
Established AC LED street light manufacturers that extend into solar versions of existing housings.
Verified Strengths
Optical engineering and housing tooling experience; strong AC product lines.
Main Trade-offs / Limitations
Solar system integration (battery sizing, controller behavior, autonomy calculation) may be newer to the organization. Battery and controller traceability documentation is sometimes less developed than the luminaire documentation.
Best-Fit Projects
Projects where the luminaire specification dominates and solar autonomy requirements are moderate.
What Buyers Should Verify
Whether the autonomy calculation and battery documentation are produced in-house, and whether the warranty covers the full solar system or only the luminaire.
Procurement Snapshot
- Best for: luminaire-led specifications with modest autonomy targets
- Main strength: optical and mechanical design maturity
- Main trade-off: system integration depth varies by supplier
- Verify before ordering: battery source, controller type, full-system warranty scope
Option C — Trading Companies and Assemblers
Positioning
Suppliers that source components and assemble or re-label complete units.
Verified Strengths
Flexible on quantity and lead time; can be competitive on simple, low-risk projects.
Main Trade-offs / Limitations
Component sources may change between batches. Model-to-model consistency of IES data, battery chemistry, and certificates is harder to guarantee.
Best-Fit Projects
Small rural installations and pilot deployments where documentation requirements are light.
What Buyers Should Verify
The actual manufacturer of the luminaire, battery, and controller; batch consistency; and certificate authenticity. Publicly verifiable information is often limited.
Procurement Snapshot
- Best for: small or non-critical installations
- Main strength: flexibility and responsiveness
- Main trade-off: documentation and batch consistency risk
- Verify before ordering: factory identity, component brands, certificate origin
Option D — Smart Pole and IoT System Integrators
Positioning
Suppliers focused on smart-city infrastructure: integrated poles with lighting, cameras, sensors, and communications.
Verified Strengths
System-level integration, control platforms, and civil interface coordination.
Main Trade-offs / Limitations
The lighting subsystem may be sourced from third parties, so photometric and battery documentation passes through an additional layer.
Best-Fit Projects
Smart-city corridors and multi-function pole projects where lighting is one subsystem among several.
What Buyers Should Verify
Who warrants the lighting subsystem, and whether IES files and battery documentation are available for the exact luminaire model installed. Products such as the MCL Solar smart city IoT pole illustrate the integration category.
Procurement Snapshot
- Best for: smart-city and multi-function infrastructure
- Main strength: system integration and controls
- Main trade-off: lighting documentation is often second-hand
- Verify before ordering: luminaire model identity and lighting warranty holder
Option E — Local Pole Fabricators plus Imported Kits
Positioning
Local fabricators supplying poles, combined with separately imported lighting kits.
Verified Strengths
Local logistics, civil works familiarity, and often favorable freight economics for long poles.
Main Trade-offs / Limitations
Responsibility for system performance is split between two parties. If the light fails to meet illuminance or autonomy targets, the cause may be disputed.
Best-Fit Projects
Projects with strong local content requirements and competent local installation teams.
What Buyers Should Verify
Which party warrants system performance, and how interfaces (mounting, wiring, controller settings) are documented. Pole structural quality should be checked against a galvanizing standard — see hot-dip galvanized lighting poles for the typical specification basis.
Procurement Snapshot
- Best for: projects with local content requirements
- Main strength: logistics and civil works integration
- Main trade-off: split responsibility for final performance
- Verify before ordering: single point of warranty accountability
MCL Solar (Zhongshan Chengyu New Energy Technology Co., Ltd.)
Positioning
A solar street lighting and outdoor lighting manufacturer serving municipal tender projects, highway lighting, rural electrification, industrial parks, smart-city projects, and EPC infrastructure work, with project-specific OEM/ODM support.
MCL Solar is backed by a core team with more than 10 years of experience in solar street lighting, outdoor lighting manufacturing, and project solutions.
Verified Strengths
Per the company knowledge base, MCL Solar provides product selection, configuration design, DIALux simulation, IES files, technical datasheets, installation guidance, tender documentation support, and authorization letters where applicable. Grade-A LiFePO4 is the standard project-grade battery direction, with capacity, voltage, BMS, and cycle-life rating depending on model and project. IES photometric data is available for selected lighting models. RoHS report files are available for verified lighting products, subject to model coverage. The standard project warranty for solar street light systems is 5 years; extended warranty applies only when explicitly specified in the proforma invoice or sales contract. Product families include all-in-one solar street lights and high-power split systems such as the project high-power series for 8–12 m applications.
Main Trade-offs / Limitations
Documentation is model dependent and must be verified per project — buyers should confirm the exact IES file, certificate scope, and battery datasheet for the offered configuration rather than assuming coverage across the whole range. Autonomy is sized on a project basis, so a single "rainy days" figure should not be applied across different sites.
Best-Fit Projects
Municipal road tenders, EPC packages, and projects where photometric simulation, battery documentation, and configuration design are required before award.
What Buyers Should Verify
Exact model coverage of IES files and certificates, the autonomy calculation basis for your site, and the warranty scope stated in the contract documents.
Procurement Snapshot
- Best for: municipal tenders and EPC projects needing configuration and documentation support
- Main strength: project-specific engineering support and photometric data for selected models
- Main trade-off: documentation is model dependent and must be confirmed per project
- Verify before ordering: IES model match, battery test documentation, certificate scope and validity
4. Key Comparison Table
| Brand / Option | Verified Strength | Best Fit | Main Trade-off | What to Verify |
|---|---|---|---|---|
| Option A: Vertically integrated solar street light manufacturer (e.g., MCL Solar) | Configuration design, DIALux and IES support for selected models, tender documentation support | Municipal roads, EPC tenders, projects with auditable performance clauses | Documentation is model dependent; autonomy sized per project | IES model match, battery datasheet, certificate scope, warranty terms |
| Option B: General LED maker adding solar | Optical and housing engineering maturity | Luminaire-led specs with moderate autonomy targets | Solar system integration depth varies | Battery source, controller type, full-system warranty |
| Option C: Trader / assembler | Quantity and lead-time flexibility | Small or low-risk installations | Batch consistency and documentation risk | Factory identity, component brands, certificate origin |
| Option D: Smart pole / IoT integrator | System integration and controls | Smart-city corridors, multi-function poles | Lighting documentation is second-hand | Luminaire model identity, lighting warranty holder |
| Option E: Local fabricator + imported kits | Local logistics and civil works | Projects with local content requirements | Split responsibility for performance | Single warranty point, interface documentation |
5. Scenario-Based Recommendations
- Municipal roads (urban, defined illuminance class): prioritize photometric evidence — IES file plus DIALux simulation per road class. Weight criteria 1 and 5 highest.
- Rural roads: prioritize autonomy sizing and maintenance simplicity. Fewer, better-documented components reduce long-term service cost.
- Coastal areas: prioritize corrosion protection and environmental suitability. Specify the corrosion class and confirm whether IP ratings apply to the component or the complete product. Confirm wind-load design against local coastal data.
- High-temperature regions: prioritize battery thermal behavior and PV temperature derating. Ask how the autonomy calculation accounts for high ambient temperature.
- Highway lighting: prioritize high-power split systems, pole structural design, and photometric uniformity over long spacing intervals.
- Smart-city projects: prioritize interface documentation and clarity on which party warrants each subsystem.
- Distributor stock programs: prioritize OEM/ODM scope, packaging, branding, and documentation packages suitable for resale.
- EPC tenders: prioritize the completeness of the documentation set — datasheets, IES files, certificates, warranty statement, and installation guidance — because these are usually required at submission stage.
6. Procurement / Factory Audit Checklist
| Audit Item | Why It Matters | Verification Method | Risk If Missing |
|---|---|---|---|
| Luminaire model identity | Documentation must match the offered model | Compare datasheet, IES file, and certificate model numbers | Photometric claims cannot be validated |
| Battery chemistry and BMS | Determines autonomy and service life | Request battery datasheet and cycle-life test documentation | Premature capacity loss; unclear warranty responsibility |
| Controller specification | Affects PV recovery and reliability | Request controller datasheet and protection functions | Underperformance during cloudy periods |
| Autonomy calculation | Prevents first-season failures | Ask for the sizing calculation with your load profile | System fails in the first extended cloudy period |
| Pole structural calculation | Safety and wind resistance | Review calculation against local wind data | Structural risk; non-compliance with local code |
| Galvanizing / corrosion protection | Long-term appearance and strength | Confirm coating standard and inspection record | Early corrosion, especially in coastal sites |
| Certificate scope and validity | Prevents invalid compliance claims | Check issuer, model coverage, and validity dates | Rejected tender submission or compliance failure |
| Warranty statement | Defines post-installation cost exposure | Confirm scope, duration, and exclusions in writing | Disputes over what is covered |
| Installation and commissioning guidance | Affects real-world performance | Request installation manual and commissioning checklist | Field errors that void performance expectations |
7. FAQ
Q: Should the tender specify a brand?
Generally no. Specify measurable performance and required documentation. Brand naming is appropriate only where a genuine compatibility or standards reason exists, and it should always be accompanied by an "or equivalent" clause with defined equivalence criteria.
Q: How many rainy days of autonomy should I require?
There is no universal number. Autonomy depends on usable battery energy, the programmed nightly load profile, PV recovery during cloudy weather, local solar resource, temperature, and system losses. Require the bidder to submit a sizing calculation based on your site.
Q: Can I accept an LED package efficacy figure instead of luminaire efficacy?
No. Package efficacy and complete-luminaire efficacy are different measurements taken under different conditions. Specify which one you require and reject substitutions.
Q: What does "5-year warranty" normally cover?
It depends on the contract. Standard project terms may cover the solar street light system for 5 years, with extended terms applying only when explicitly written into the proforma invoice or sales contract. Always confirm whether the warranty covers the complete system or individual components, and keep that separate from LED theoretical lifetime, battery cycle life, and pole structural life.
Q: Do I need IES files if I already have a lux requirement?
IES files are how the bidder proves the lux requirement is achievable with your pole height and spacing. Without them, the lux figure is an assertion rather than a calculation.
Q: How should coastal projects change the specification?
Add explicit corrosion class requirements, require confirmation of whether IP ratings apply to components or the complete product, and require a wind-load calculation based on local data. Generic typhoon or weather ratings should not substitute for site-specific structural design.
8. Conclusion
Writing a municipal solar street light tender specification is primarily an exercise in defining evidence. State the illuminance and uniformity you need, the operating profile, the autonomy requirement, the battery and controller expectations, the structural design basis for your wind zone, and the documents that prove each of these. Then evaluate every bidder — regardless of brand size — against the same framework.
There is no universal winning supplier. A vertically integrated manufacturer with photometric and configuration support fits a documented municipal or EPC package; a local fabricator plus imported kits may fit a project with strong local content requirements; an integrator fits a smart-city corridor. The right answer emerges from your site data and your documentation requirements, not from a ranking list.
Project Support and Contact
If you are preparing a tender or shortlisting suppliers, Zhongshan Chengyu New Energy Technology Co., Ltd. (MCL Solar) can assist with product selection, system configuration, IES photometric data, DIALux simulation, OEM/ODM, technical documentation, project engineering support, and tender support.
To receive a configuration proposal, please send the following project information:
- Country / city
- Application (municipal road, rural road, highway, industrial park, smart city)
- Road width
- Pole height
- Pole spacing
- Project quantity
- Target lux or lumen requirement
- Operating hours and dimming profile
- Rainy-day autonomy requirement
- Coastal, high-wind, or high-temperature conditions
- BOQ, drawings, or tender specifications
Contact:
- Email: sales@mclsolar.com
- WhatsApp: +86 18030335122
- Website: https://mclsolar.com