Recommended Bundles

Use this kit to lock baselines, evidence gates, and scoring—then shortlist the right system type.

• Run Procurement Bundle →
• Run Operations Bundle →

Download: Project Input Sheet (Tender-Ready)

Use this input sheet to request sizing + IES/LDT + spacing/layout proposal.

Tip: If you are running a tender, pair this with the RFQ & BOQ Kit.

What This Page and Download Provide

The ZIP contains the Project Input Sheet. The sections below are on-page procurement guidance, not separate files in the current download:

• RFQ outline (copy-and-adapt guidance below)
• BOQ outline (line items, options and spares below)
• Evidence request guidance (confirm model-specific files separately)
• Bid evaluation guidance (scoring and pass/fail approach below)
• Acceptance and commissioning guidance (agree project-specific forms separately)

How to Use This Kit (Procurement Workflow)

1) Define project scenario (road type + environment + autonomy nights).
2) Standardize terms using the Spec Definitions Hub (so quotes are comparable).
3) Require evidence using the Quality & Testing Hub (so claims are verifiable).
4) For roadway projects, validate optics and spacing using IES files and DIALux inputs.
5) Score bids using the rubric (compliance first, price last).
6) Require commissioning and acceptance records for handover and warranty.

RFQ Template (Copy/Paste)

A) Project Overview

• Project location (country/city)
• Road type (highway/main/local/park)
• Environment (coastal/desert/monsoon/vandal/cold region)
• Quantity and delivery timeline
• Installation responsibility (contractor/in-house)

B) Lighting Requirements (Roadway vs Area)

• Road width and number of lanes (if roadway)
• Pole height, arm length, pole arrangement (single-side/staggered/opposite/median)
• Target runtime (dusk-to-dawn or specified hours)
• Optics requirement:
• Roadway projects must include photometrics (IES files) for the offered optics

C) Energy & Autonomy Requirements (Mandatory)

Supplier must submit an energy budget sheet showing:

• dimming profile used (time steps / PIR behavior)
• average power under dimming (W)
• nightly runtime hours (h)
• battery nominal energy (Wh) and usable assumption (%)
• resulting autonomy nights

D) System Configuration Requirements

• Battery chemistry (LiFePO4 recommended)
• BMS protections list (mandatory)
• Controller protections list (mandatory)
• Dimming options (time-based / PIR boost)
• PV module rating (Wp) and disclosed sizing assumptions (worst-month preferred)

E) Protection & Durability Requirements

• Target IP (dust/water ingress protection)
• Target IK (impact/vandal protection) if vandal risk exists
• Corrosion strategy statement required for coastal/humid sites:
• coating approach + hardware selection
• connector/cable corrosion prevention method
• maintenance expectations

F) Mandatory Deliverables (Submission Package)

Bid is incomplete if missing any of the following:

• Energy budget sheet (autonomy basis)
• Roadway photometrics (IES files) for highway/main-road projects
• Battery statement: chemistry, nominal Wh, usable assumptions, BMS protections list
• Controller statement: protections list + dimming profile description
• Warranty policy: scope by component + SLA + claim workflow
• Installation + commissioning checklist

G) Warranty & After-Sales (Evidence-Based)

Warranty document must specify:

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

BOQ Template (Structure + Line Items)

1) Primary Supply Items

• Solar street light luminaire system (model/configuration)
• Mounting bracket / arm (type, length)
• Pole (if included): height, thickness, material, finish
• Foundation components (if included)

2) Options (Declare separately)

• Smart monitoring (if applicable)
• Anti-theft hardware package
• Higher corrosion protection package (coastal)
• Higher impact protection package (vandal risk)

3) Spares (Recommended for Deployment)

• Controller module (qty %)
• Sensor module (if used)
• Fastener kit and gasket kit
• PV connector kit / cable accessories (if applicable)

4) Documentation & Services

• Installation manual + commissioning checklist
• Photometric package (IES files for offered optics)
• Optional: DIALux-ready proposal support

---

Evidence Submission Checklist (Pass/Fail)

Mark each bid as PASS or FAIL before comparing price:

PASS requirements:

• Energy budget sheet submitted (with dimming profile assumptions)
• Battery statement includes nominal Wh + usable assumptions + BMS protections list
• Controller statement includes protections list + dimming profile behavior
• Roadway projects: IES files submitted for offered optics
• IP/IK targets stated and matched to environment risk
• Coastal/humid: corrosion strategy statement included
• Warranty policy includes scope + SLA + claim workflow evidence list

FAIL triggers:

• “Autonomy X days” without energy budget and dimming profile
• Only Ah is stated for battery without Wh/usable assumptions
• Roadway spacing claims without IES files
• “Salt spray hours = outdoor lifetime” used as guarantee
• Warranty language without process and evidence requirements

Bid Evaluation Rubric (Compliance First, Price Last)

Recommended scoring after PASS/FAIL screening:

Category	Weight	What “good” looks like
Technical compliance	30	all mandatory deliverables submitted
Energy sizing credibility	20	usable Wh + dimming profile + sizing assumptions disclosed
Photometric credibility	15	IES files provided + DIALux support for spacing/uniformity
Durability evidence	15	sealing approach + environment strategy (corrosion/impact)
Warranty & service	10	clear SLA + claim workflow + replacement method
Price	10	evaluated after compliance

---

Common Bid Traps (How to Spot Hidden Risk)

1) Autonomy claims without an energy budget

• Fix: require Wh/day and dimming profile assumptions.

2) Battery capacity shown only in Ah

• Fix: require nominal Wh and usable assumptions.

3) Roadway spacing claims without IES files

• Fix: treat as unverified; request IES and DIALux-ready inputs.

4) Salt spray hours used as lifetime promise

• Fix: request a corrosion control strategy and field-relevant maintenance plan.

5) Warranty without a workflow

• Fix: require claim evidence list + response time + replacement method.

Request an Engineering Review (Optional)

If you already collected supplier bids, we can review:

• comparability (same assumptions)
• missing evidence (risk flags)
• sizing credibility (autonomy, worst-month assumptions)
• photometrics readiness (IES/DIALux inputs)
• warranty enforceability

Project-Specific Tender Support

Tell us about your project and the documents you need.

• Work email
• Country/city
• Road type (highway / main road / local / park)
• Project environment (coastal / desert / monsoon / vandal)
• Estimated quantity
• Target autonomy nights (if known)

FAQ

What is the difference between an RFQ and a BOQ?

RFQ defines requirements and submission rules. BOQ standardizes line items so quotes can be compared fairly.

Why should roadway projects require IES files?

IES files provide photometric distribution needed to validate spacing, uniformity, and glare control in lighting software.

Why is a bid “not comparable” without an energy budget sheet?

Because autonomy depends on usable battery energy and the declared dimming profile. Without disclosed assumptions, autonomy claims are not auditable.

Can salt spray hours be used as a lifetime guarantee?

No. Salt spray is a controlled comparative test and should not be used as a direct conversion to outdoor service life.

What evidence should we request for lithium battery safety?

At minimum: chemistry, BMS protections list, and transport test summary availability when required in the supply chain.