Recommended Bundles

Use evidence gates first, then compare prices.

• Run Coastal Bundle →
• Run Desert Bundle →
• Run Operations Bundle →

The Procurement Rule (Evidence First, Price Second)

A solar street light bid should be labeled “Incomplete / High Risk” if it cannot provide:
1) Energy budget + autonomy calculation basis (aligned with dimming profile)
2) Photometric evidence for roadway projects (IES files for offered optics)
3) IP/IK requirements + sealing / impact evidence approach
4) Battery safety statement + BMS protections list (and transport test summary when required)
5) Warranty scope + claim workflow (what proof is needed, how replacements are handled)

Price comparison should only begin after compliance.

Evidence Levels (What Counts as Proof)

Level A — Auditable Documents (strongest)

• Standard-based test reports (photometric/electrical)
• Declared acceptance criteria and measurable results
• Serial/batch traceability records

Level B — Process Evidence (strong)

• QC checklist screenshots (with revision dates)
• Sealing points photos taken during assembly
• Commissioning records (mode settings, runtime verification)

Level C — Marketing Claims (weak)

• Brochure claims without methods
• “IP68 design” without sealing/QC evidence
• “Salt spray hours” used as a lifetime guarantee

Environment Evidence Matrix (Request Evidence by Risk)

Environment	Primary risks	Minimum evidence to request	Typical field deliverables
Coastal / Humid	corrosion, connector failure	Corrosion strategy statement + hardware/coating notes + connector protection method	connector protection photos + hardware grade list
Desert / Dust	dust ingress, PV soiling	sealing strategy evidence + dust control + maintenance SOP	sealing points photos + cleaning schedule
Monsoon / Heavy rain	water ingress, low charging	sealing evidence + conservative sizing assumptions	commissioning checklist + energy budget sheet
High vandal risk	impact damage, theft	IK/impact approach + anti-tamper hardware options	anti-theft hardware spec + installation photo requirements
Cold regions	battery performance, charging limits	low-temp operating notes + battery protections statement	conservative autonomy basis + commissioning record

QC Workflow (Factory-Proof Structure)

A robust supplier should be able to describe a repeatable QC workflow:

1) Incoming Inspection (IQC)

• Housing materials, coatings, fasteners
• PV module and connectors
• Battery pack components (cells, BMS)
• Controller PCB/components (if applicable)

2) Assembly Controls (Process QC)

• Torque control for critical fasteners
• Sealing controls (gaskets, vents, glands)
• Connector corrosion prevention measures
• Controller programming verification (dimming mode)

3) Functional Testing (Pre-aging)

• Charging function check
• Lighting output check (basic functional)
• Sensor behavior check (if included)
• Protection behavior check (basic safety)

4) Aging / Burn-in (Reliability Screening)

• Early failure screening before shipment
• Record results by batch/serial (recommended)

5) Final Inspection + Packing

• Serial labeling and traceability record
• Accessories completeness (brackets/bolts/manuals)
• Packing integrity and damage mitigation

Test & Evidence Library (What to Ask For)

A) IP (Ingress Protection) — Sealing Consistency

Request:

• sealing design notes (gaskets, vents, glands)
• sealing points photos (assembly stage)
• QC checklist items for sealing verification

Minimum deliverable:

• a sealing checklist and photo set per batch (recommended)

B) IK (Impact / Vandal Risk)

Request:

• enclosure reinforcement notes
• lens protection approach
• anti-tamper mounting hardware options

Minimum deliverable:

• declared IK strategy aligned with site risk

C) Corrosion Control (Coastal Projects)

Important note:

• Do not treat “salt spray hours” as a direct lifetime promise.
  Request a corrosion strategy statement:
• coating approach (type + thickness policy if applicable)
• hardware grade selection policy
• connector/cable protection method
• maintenance expectation and inspection frequency

Minimum deliverable:

• corrosion strategy statement + hardware list

D) Photometric Evidence (Roadway Projects)

Roadway projects should not rely on wattage charts.
Request:

• IES photometric files for the offered optic (mandatory)
• optic family identification (roadway distribution vs flood)
• DIALux-ready input support (pole height, arrangement, spacing validation)

Minimum deliverable:

• IES files matched to quoted model/optic

E) LED / Lumen Performance Evidence

Request:

• photometric/electrical test summary (flux, power, CCT)
• thermal management notes (heat path concept)
• lumen maintenance approach explanation (component-level + method)

Minimum deliverable:

• performance test summary aligned with spec sheet

F) Battery Safety Evidence (LiFePO4 Systems)

Request:

• chemistry (LiFePO4), nominal Wh, usable assumptions
• BMS protections list (OC/SC/OV/UV/temperature)
• transport test summary availability when required in the supply chain
• warranty scope for battery and BMS

Minimum deliverable:

• battery statement + BMS protections list

G) Controller Evidence (Dimming & Protections)

Request:

• protections list
• dimming logic description (time steps / PIR boost behavior)
• confirmation that autonomy calculation matches dimming profile

Minimum deliverable:

• declared dimming profile + protection list

Commissioning & Acceptance Records (Site-Proof)

Require these records for handover:

• Serial number list mapped to installation locations
• Installation photos:
• PV orientation/tilt
• shading check (nearby trees/buildings)
• mounting hardware and anti-theft measures
• Commissioning settings record:
• dimming mode
• base brightness
• sensor behavior (if included)
• Basic functional check record (on/off, charge indicator, mode confirmation)

Warranty Claim Workflow (Evidence-Based)

A practical warranty policy should specify:

• Coverage by component (battery/controller/LED/PV/housing)
• Response time (SLA) and replacement method
• Claim evidence requirements:
• serial number
• photos/video of issue
• commissioning settings record
• installation photo proof (PV orientation/shading)

If a warranty policy is vague, project risk increases.

Copy/Paste Evidence Request Pack (RFQ-Ready)

Supplier must submit the following evidence package:

1) Energy budget sheet (autonomy basis)

• average power under declared dimming profile
• nightly runtime hours
• usable battery Wh assumptions
• resulting autonomy nights

2) Roadway photometrics (for highways/main roads)

• IES files for offered optics
• DIALux input support for spacing/uniformity validation

3) IP/IK and sealing/impact strategy

• target IP and sealing evidence request list (photos + QC checklist items)
• target IK strategy (if vandal risk) and anti-tamper options

4) Corrosion strategy (coastal/humid sites)

• coating and hardware selection policy
• connector/cable corrosion prevention method
• maintenance expectations

5) Battery safety package

• chemistry, nominal Wh, usable assumptions
• BMS protections list
• transport test summary availability (when required)

6) Warranty package

• scope by component + SLA
• claim workflow + required evidence list

Request Evidence Checklist + Acceptance Forms

Get the editable package used for tender evaluation and acceptance:

• Evidence request checklist (fillable)
• Environment evidence matrix (fillable)
• Commissioning & acceptance record templates
• Warranty claim evidence checklist

Send it to me:

• Work email
• Country/city
• Project environment (coastal/desert/monsoon/vandal)
• Road type and quantity

FAQ