Recommended Bundles

Photometrics and spacing validation should happen before quote comparison.

• Run Highway Bundle →
• Run Urban Bundle →

The 60-Second Rule (Roadway Projects)

A roadway bid is NOT verifiable unless it includes:
1) IES photometric files for the offered optics (not generic)
2) A DIALux-ready input set (road geometry + pole arrangement)
3) A report that shows spacing, uniformity, and glare-related metrics (as applicable)
4) A clear assumption list (mounting height, tilt, maintenance factor, target class)

If any item is missing, spacing claims should be treated as “Unverified / High Risk”.

What an IES File Is (and when it’s mandatory)

An IES file is a standardized electronic photometric data file that describes a luminaire’s light distribution. It is used by lighting software to calculate roadway performance.

When IES is mandatory

• Highways / main roads
• Any project where pole spacing and uniformity are important
• Any project requiring an auditable lighting report

When IES is still recommended

• Streets with mixed traffic and pedestrian conflict
• Large outdoor areas where glare complaints are possible

IES File Acceptance Checklist (Procurement-Ready)

Before using an IES file to justify spacing or compliance, confirm:

A) Correct file identity

• The IES file is provided for the exact offered model and optic
• The optic family / distribution is named clearly (not “all-purpose”)

B) Usability in software

• File imports successfully into DIALux (or other common software)
• No corrupted or missing data blocks

C) Consistency with the quotation

• Luminous flux and input power are consistent with the quoted configuration
• CCT and optic type match the specification (if stated)

D) Traceability

• File naming and revision control are clear (version/date)
• Supplier can provide updated files if optics or LED package changes

If a supplier cannot provide model-specific IES files, treat roadway spacing claims as unverified.

DIALux Intake Form (DIALux-Ready Inputs)

Use these fields in your website form to collect consistent inputs:

1) Project Basics

• Country / City
• Road type (highway / main road / local / park)
• Project quantity (estimated)

2) Road Geometry

• Road width (m) and lanes
• Median (yes/no) and median width (if applicable)
• Sidewalk / pedestrian zones (yes/no)

3) Pole Layout

• Pole arrangement (single-side / staggered / opposite / median)
• Pole height (m)
• Arm length / overhang (m)
• Target pole spacing (m) or “optimize spacing”
• Mounting tilt angle (if fixed)

4) Performance Targets (If you have them)

• Target class / requirements (if specified by local authority)
• Priority: higher uniformity vs lower energy vs lower glare

5) Environment & Risk

• Coastal / desert / monsoon / vandal risk
• Dust and soiling severity (light / medium / heavy)

6) Energy & Operation

• Dusk-to-dawn runtime (hours)
• Dimming preference (time-based / PIR boost)
• Required autonomy nights (backup nights)

Attachments (optional but helpful):

• Site drawing, typical cross-section, or reference spacing plan
• Any local lighting requirement document

Project inputs: Download the Project Input Sheet (PDF) or DOCX and send it with your road class, pole height, and target lux/uniformity.

What You Should Receive (DIALux Deliverables)

A “DIALux-ready proposal” should include:

• DIALux report (PDF) showing:
• road geometry, pole arrangement, mounting details
• luminaire model + optic used (IES referenced)
• spacing results and key performance metrics
• Layout summary:
• pole schedule (height, spacing, arm length)
• recommended optic and mounting notes
• Assumption list:
• mounting height, tilt, maintenance factor (if used)
• target class/criteria used (if specified)
• IES file package:
• IES files clearly named for the quoted models/optics

Copy/Paste RFQ Clauses (IES + DIALux)

Clause 1 — IES Photometric Files (Mandatory for Roadway)

Supplier must provide model-specific IES photometric files for the offered optic(s). Generic or “similar model” IES files are not acceptable for spacing validation.

Clause 2 — DIALux-Ready Report Deliverables

Supplier must submit a lighting calculation report that includes:

• road geometry and pole arrangement assumptions
• luminaire model and optic identification (IES referenced)
• spacing and key performance metrics (as applicable)
• revision control (report version/date)

Clause 3 — Assumptions Disclosure

Supplier must explicitly declare:

• pole height, arm length, tilt
• spacing assumptions (or optimized spacing method)
• target class/criteria used (if specified)
• any maintenance factor assumptions

Clause 4 — Bid Comparability Rule

Bids without IES files and a DIALux-ready input/output package shall be labeled “Unverified / High Risk” before price comparison.

Request IES & DIALux Starter Pack

Get the editable starter pack used to standardize roadway lighting proposals:

• DIALux intake form (fillable)
• IES acceptance checklist (fillable)
• Deliverables checklist (report + IES package)
• Sample RFQ clauses (copy/paste)

Send it to me:

• Work email
• Country/city
• Road type and quantity

FAQ